Skip to main content

W.A.I.T.: Crucial Consulting Advice

So you want to be a consultant.  You probably think this will involve yourself talking and your client respectfully listening.  Your client will put you in front of her team to present a PowerPoint deck outlining how Everything Will Be Different Now.  You will then distribute copies of your Initiative Plan to each of her subordinates.  Once you have given everyone their marching orders, they will do exactly what you outlined in orderly fashion.

But just to make sure, you personally will visit offices in New York, London, Paris, Milan, and Tokyo to double-check that everyone is doing what they should.  You will shop in Rome, buy gadgets at the Seattle Space Needle, have some fabulous meals along the way, and you will reach 1K Status this year.  That is why you want to be a consultant--you want to be consulted!

Not so fast, El Guapo!  Overbearing, meddling, quick to take offense and quicker to offend:  you aren't James Bond.  You are everyone's...mother in law.  Yes, even if you are a guy.  Guys are the worst mothers in law.
http://www.bizcrecise.com/lifestyle/what-your-mother-in-law-is-trying-to-tell-you/

How, you ask, is an enterprise hiring a consultant like a family facing a visit from the in-laws?

Put yourself briefly on the receiving end of your own advice.  Enterprise employees are seasoned professionals who have been hired, retained, and promoted within the intricate, familial dance of relationships and roles that constitutes company culture.  They know who to seek out for help, who they trust, who they don't trust, and how to get things done.  Like a family which has figured out how to handle school mornings with only one bathroom, a company arranges itself to avoid unneeded confrontations.  Any visible pattern of behavior has a reason behind it.

Now you stomp in with your big mother-in-law boots.  Your first thought is that this isn't how it's done.  Why is the mustard in the refrigerator door?  Why is Brittney allowed to eat nothing but white rice?  When did your daughter stop exercising?  The husband must weigh 300 pounds, and she's not getting any thinner.  YOU have the knowledge.  YOU have run a family for an entire generation before these amateurs were born.  Literally!  You'll get those condiments whipped into shape.  The family just needs to lead, follow, or get out of the way.  You will use your visit to get everyone to shape up, and hopefully your reforms will stick until your visit next week.  If you get invited next week.

Here's a pro tip.  The best consultants will not give advice when they first arrive at a new site, even when begged.  They will ask questions and they will listen.  As social media expert Alison Cummings says, "nothing you say is as important as what you will hear."  You may even have the answer on the first day or in the first hour, but the last thing you want to do is trot it out too early.  Ideally, you want the client herself to come to the same conclusion you did, or even a better one, and for you to therefore share ownership of the plan.  You are there to build up local leaders at all levels, give them techniques, give them mastery, and give them self confidence.  You are not there to start running the company yourself.

The inimitable Anne Lamott has released a new book about becoming a grandmother, entitled Some Assembly Required.  In a recent interview she described how she has to take really good care of herself when she visits her son and his small family, because nobody in that house is worried about her needs--they're all just focused on themselves and the new baby.  There isn't room in that house to give her the care and attention she is used to.  But of course, that's how it should be.

Lamott's advice to new mothers in law is to embrace the helpful acronym WAIT:  "why am I talking?"  And indeed this Four Letter Acronym is one that should underlie every single day you spend at a client site.  As business blogger Gary Cohen says, "start by writing WAIT on your notepad before your next meeting."  Practicing what Lauren Ekroth calls "mindful" conversation isn't just good for business--it's good for you!

I once won a high school speech contest at the Appleton Rotary Club, and the prize was a pen that had a little window in the side, and every time you clicked the pen open or closed, the saying in the window changed.  In rotation, the pen said the immortal Henry Babcock words:

-Is it true? 
-Is it kind? 
-Is it necessary? 
-If not, let it be left unsaid.

Sadly I don't have that pen any more. But instead, I have "WAIT," which is easy to remember.  I encourage all of you to remember it as well.

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
Dialogue:
WBABA:   ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …