The best short-answer to give clients? It depends. . .

“It depends” is a phrase you hear a lot in both business school and management consulting.   To some, it might seem like a boring half-answer, timid, or worse – mentally lazy.  As weird as it might seem, it is often the best short-answer to give a client.

1) Most problems are complex.  This might seem obvious, but clients typically pay for us to solve the difficult and persistent problems.  If it were easy, it would already have been solved. Seth Godin calls them perfect problems.

If you can answer the parts of the problem “off the cuff”, it either means you are a genius (possible), or you are not really answering the entirety of the problem (more likely).  Brainstorm through the potential issues before you jump the gun.

Unsurprisingly, the majority of consulting works sits in the yellow area (complex problem, complex solution).  It can be a bit of a grind, but those are the type of problems that Fortune 1000 typically have, and the type of problems we know how to solve.  We can talk about the innovation and leadership quadrant in a different post.

Simple Complex Problem Solution

2) Context matters.  No question is asked in a vacuum.  If someone asks you if they should invest in Linkedin (ticker symbol: LNKD), the answer is probably “it depends”:

  • Time horizon: How long will you be holding the stock?
  • Risk tolerance: What is your comfort buying stocks with very high PE multiples?
  • Diversification: How diversified are you?  Is this the only investment you have?

Another recent example of the IT DEPENDS phenomenon was the hub-bub with Marissa Mayer banning remote work.   Personally, I believe she had some good reasons (need to get Yahoo! innovating, people were slacking etc), but at the end of the day, the answer for tel-commuting is IT DEPENDS.

Why would someone in accounts payable (clearly defined work, little interaction with others needed) be held to the same commuting standards as someone in product marketing (fluid work product, need for collaboration, interaction with customers)?

3) Beware of false choices.  People tend to over-simplify the situation and paint the pictures as if it were black / white.  This is also called the false dilemma. US politicians are notorious at this.  Watch any political TV ad, and it will make you sick how they set up issues as false choices (good sensible me vs. bad crazy them).

Last week when I was on a conference call with a few people, someone argued for his point by creating a false choice (A or B).  I had to bust him on the false choice, by saying, “That’s a little reductionist, isn’t it?  What about choice C?”

4) Too often, clients want to take short-cuts.  Like anyone, clients are impatient.  They like the rigor and process-focus that consultants take, but they want it done in 1/2 the time with 1/2 the fees.  While it’s good to give updates, make sure you follow the process you outlined in the proposal.  Don’t forget that you are the coach.

Problem with shortcuts

Related posts:

7 Key Questions: Who, What, Why, When, Where, How, How Much?

Who, What, Why, When, Where?  These are five questions kids learn in grade school or when first learning a language.  It covers the basics and helps you understand the situation and context.  My high school friends can attest to my poor memory, but even I can remember these basic words in french: Qui, Quoi, Quand, Où, Pourquoi.

These 5 questions are fairly famous and an often-quoted way to think through problems.  They have been repeated by Cicero, Thomas Acquinas, and Rudyard Kipling.  Journalists are trained to answer those 5 questions whenever they write an article or press release.  These can also be useful for consultants, with two small additions.

How and How Much?  For any consultant eager to see her recommendations implemented, a lot of thought needs to be given to how it will be implemented and how much it might cost.  For all the snark-y comments about strategy consultants giving high-minded solutions that are condemned to be “shelfware”, there is a hint of truth that many good ideas die on the hill of implementation and cost.

What kind of problem is it?   There is a good chance that the client’s problem falls into one of these buckets.  If it is a strategy project, likely it is a WHAT question.  Conversely, if it is a operations-related project, it is really looking at HOW to implement a good idea efficiently. Most seasoned consultants have been on projects that touch these areas.

Questions and Topics

Answer the right question.  It is easy to fall into the trap of addressing the wrong issue.  All too often clients hire consultants to solve problem X, only to find out that the problem is actually with Y.   On a more personal note, I had dinner with a good friend last night and he adroitly pointed out that I was too focused on answering the HOW (on a big decision in my life), instead of taking a step back and answering the WHY and the WHAT.  Sanity check.

“Management is doing things right; leadership is doing the right things.” – Peter Drucker

Think broadly about the problem. Once you have targeted the right question, think a bit more laterally and see which of the other questions should be answered too.  The level of detail will vary, but you want to be as comprehensive as the time and budget allows.  In this example below, this hypothetical project actually covers a lot of ground.

Who What Why When Example

Look for the add-on work.  Chances are very good that during the course of solving one problem, you unearth other issues.  It is all too common for a $50,000 (loss-leader) diagnostic project to lead to a  $750,000 (profitable) project with multiple work streams and consultant teams.  Clients see that you do good work, and want more help.  It is natural and good thing for the client and the consultant.  Look for those opportunities.

“My greatest strength as a consultant is to be ignorant and ask a few questions.”  – Peter Drucker

Related Posts:

What consultants can learn from improvisational theater

Went to improv last Saturday night, had a a great time and laughed a lot.  It made me think: What can consultants learn from improv?

My first reaction to the question was dismissive.  After all, improv is about entertaining the audience, making things up, and generally “winging it.”  Nothing like the well-choreographed meetings and formal presentations that I am used to giving to clients.  Did a little bit of research and I feel there are 7 things consultants can learn from improvisational theater.

Improv and Consulting1. Practice.  These actors practice.  They use games and there are real skills to learn.  In one skit, they had to imitate German, Scottish, Swedish, Klingon, and Australian accents.  Not different from the ways that consultants practice excel modeling, presenting in front of audiences, and learning to say “yes. . and”

2. Listening.  Improv actors have to build on what their colleagues say.  There is no script.  Consultants could learn to listen better to client and their colleagues.  Listen not just to the words, but also listen for meaning.  What do they “really” mean?

3. Use EQ.  Consultants think more than they feel.  This is usually a good thing because we can work with data and develop hypotheses, but it can also be a major limitation.  We forget that it is people (yes, humans with feelings) who need to implement the recommendations.

4. Stay in the moment.  Improvisational theater actors do not have a script.  There are no lines to memorize.  They are entirely committed to the moment.  That is something that we can all learn from.  Put the cell phones away.  Make eye contact with the person you are talking with.  Listen to what the other person is saying, and stop thinking of your witty rebuttal.

5. Be authentic.  This is harder than it sounds.  As consultants, we want to be experts.  We want to command respect and be authority figures.  In reality, we need to be more comfortable in our own skin – no matter how unique, geeky, or even boring.  Be yourself.

6. Don’t get stuck. This is a critical point.  There are points in every project where it seems like you won’t find the answer.  It is a dip.  It is bottleneck.  This is the time when you need  to reach out to partners, other mentors, executive sponsors – and bust through the problem.  As one consultant said, “Just model through the problem.”

7. Remember the audience.  This applies to everything consultants do.  Writing emails.  Drafting proposals.  Making phone calls.  Crafting presentations.  Know your audience.

So now, what are the 3 things that make improvisational theater ENTIRELY different from consulting?  There are many . . but here are the 3 that come to mind.

8. (Don’t) Make it up.  There is no excuse for this.  When you don’t know the answer to a question.  Don’t fake it.  Say you don’t know, and then quickly find the answer.

9.There are (most definitely) mistakes.   In improvisational theater, it is important to build off the the previous person’s “schtick” and keep going.  They say there are no mistakes.  Well, in consulting there are definitely mistakes.  Bad excel models, poorly thought-out presentations.  Uninformed clients.  Faux pas by immature consultants.  Lots of potential mistakes.  As a project manager, you cannot be careful enough.

10. (Don’t) let go of control.  It is easy for consultants to feel overly comfortable at the client site.  We specialize in exceeding expectations, and after a couple of “quick wins”, it is easy to be overly self-confident.  I remember sitting at a TGI Friday’s talking about the client (not all bad, but not all good either), and when we get up to leave – we notice that some clients are sitting in the booth right behind us.  Uh, not classy.

Bad data: 9 reasons clients often have data problems

No consulting project has perfect data.  In fact, it is usually a little bit like an Easter egg hunt where the team has a good idea where the data eggs might be, but can’t be 100% sure until they really start looking for it.

Most companies have trouble with their data.  While there is a lot of talk of BIG DATA and the revolution it will have in predictive analytics, in reality, many organizations have trouble patching together their SMALL DATA.  I would guess that only 1/3 of companies can can satisfy the consulting team’s data request.

Oddly, lack of data = consulting project.  For a bit of circular logic. . . it is often because the data is difficult to find, that the client has not really solved the problem yet.  As Seth Godin remarked in a blog post about “perfect problems”:

The only problems you have left are the perfect ones. The imperfect ones, the ones with a clearly evident solution, well, if they were important, you’ve solved them already

So, as odd as it sounds. . . consultants need to be thankful that the client’s data is usually a mess.  It means more work, projects, billing and money.

Data collection is often painfully slow.  Even when the location of the data is clear, it is common for the team to spend several days hunting down the right people to get the data.  Consultants often go to the client site just to request (read: pester, nag) the client to give them the data.  Clients could save themselves 5-10% of fees if they would just get the data to the consultants quicker.

Bad Data - Data is SomewhereGood data is hard to find.  In my experience, the larger, the more geographically dispersed, and the older the company = the messier the data.  Using the analogy of data flow like plumbing . . . the larger and older the house, the more it leaks.

Bad Data - 9 Reasons by Data is Bad#1-3. IT needs to update and standardize.  Too often IT only makes tactical repairs and spends their energy and budget just playing catch up.   Too often, clients customize the enterprise resource planning (e.g., SAP, Oracle) to match their process, instead of listening to the systems integrators and stick with best practices.  “Oh, we like to do it our way” is usually code words for messy data down the road.

#4. Sometimes legacy = bad.  Too often there is a resigned exhaustion of existing legacy processes.  “Yes, we do it on paper because we always did it that way.”   “No, I don’t have it written down because I remember it all.”  Those are all signs of trouble and poor planning. There is always someone – often with white hair and a beard – who knows how things really work. Talk about disaster planning: What happens if Al leaves?

#5-7. Time to clean the data.  The customer master (where you list all the key information of your clients) needs to be clean because it is used for billing, accounting, and other customer-relationship activities (e.g., sales calls, marketing direct mail).  Too often these are a bit of a mess.  For example, there will be 4 ways to spell Wal-mart, Wallmart, Walmart, Wall Mart.  With junky data, it is hard to analyze anything.

#8-9. Figure out the roles / responsibilities.  Who’s job is it anyways?  If it is everyone’s job, then in effect, it is no one’s job.  It’s not a good sign when veteran office workers who are uncomfortable using basic excel commands like sort and pivot.  While it seems basic, sometimes real-time analysis is just not valued enough to put into job descriptions and performance reviews.  Inevitably, it is the managers fault.

Data is not just lying around.  For those new to consulting, get ready to start digging for the data. Just some of the crazy examples from my past:

  • On my first consulting project, I spend several late nights alone typing shipping data from paper invoices into an excel spreadsheet
  • Just a few months ago, we consolidated data from 60+ separate emails into one excel.  How can you look at trend data when it is sitting in 60 daily reports?

Ask any analyst, and they will have their own hazing story of collecting data in some manual and crazy way.  As long as companies don’t take the time or the effort to do this, they will continue to pay $$$$ / hour for this mundane task to get done.

Data is a bit of a misnomer because it treats everything the same.  In my mind, there is a progression / hierarchy of the value of information which looks something like this.  It starts as noise, gets organized into data.  That data turns into information as it is structured, cleaned, rearranged, and sorted so it makes some sense.  Analysis takes shape as information is pivoted, correlated, appended, hypothesis-tested.  Insights are really gems and diamonds.  They are rare, valuable, and often very polished.  Only analysis and insights should be presented.Value of Data

Lack of data requires consultant creativity. Sometimes, consultants have to uncover, create, cleanse, triangulate or even create data to answer key questions.  Creativity is needed here.  It is also a great way to “wow” the client.

Creating data is not sketchy or unethical. Some of consulting tools used to find new data include: surveys, interviews, focus groups, workshops, financial comparisons, observations, estimates, simulations, business models, benchmarks, maturity models, and others.  More on surveys in the next post.

Please feel free to add any data war stories you might have. 

SIPOC: Consulting framework to untangle problems

SIPOC is an ugly sounding acronym, but it is a useful way to think through problems.  Clients often present consultants with complex processes that seemingly don’t have a start or a finish. They go on-and-on.  They are inter-related processes and it feels like an ugly excel formula full of nested if / then statements.  The more you dig, the more you uncover.

SIPOC - Initially looks like this

Structured thinking.  Sometimes, the best thing is to stop digging.  Take a step back and think through the problem.  Untangle the problem in a more structured way.  Figure out what sits outside the process.  What is the client really asking for?  What comes before the process (#1) and what comes after the process (#3).

SIPOC - Whats outside the process

Supplier, Input, Process, Output, Customer (SIPOC): Building on that example, a SIPOC diagram can be drawn out from left-to-right; suppliers provide inputs to a process, which in turn, provides outputs to customers.  It is a simple daisy-chain of activities and the real scope of the project is the area shown in red.  The process in the middle is what you are after.  The stuff on the left (suppliers, inputs) and the right (outputs, customers) are not really under your control, or potentially out of scope.  Focus on the red part.

SIPOCSIPOC applies to any process where there are suppliers and customers:
  • Business-to-consumer (B2C): Cleaning products
  • Business-to-business (B2B): Apple Airbook
  • Internal product design: Airbus engines
  • Sales support: Allstate insurance policies

#1.  Use SIPOC to control scope.  Clients often ask for additional work or small favors, under the same contracted fee.  The consultant might say yes a few times, but eventually there is a danger that the consultant is over-promising.  SIPOC is one of the tools to guard against scope creep and better define scope of the process improvement project.

#2. Use SIPOC to rule out hypotheses.  In the example above, If SC Johnson was having process issues, one hypothesis might be related to their supplier’s chemicals.

  • If the chemicals are the problem, you are well on your way to solving the problem
  • If the chemicals are not the problem, you strike it off the list of hypotheses, and move on to other potential hypotheses “suspects”

SIPOC - Rule out Hypotheses

Process improvement projects are common.  There is a bit of a myth that management consultants spend a lot of their time on strategy and marketing projects.  In reality, a lot of project work is very operationally-focused.  As you can imagine,  Fortune 1000 companies have lots of processes (across geography, across business units, across functions) that are generally going haywire and need re-wiring.  Also, ops projects tend to have a more measurable return on investment (ROI) and lower risk of implementation.

Even the big 3 strategy firms do plenty of process-improvement projects.  A few case studies where I am sure the teams benefited from some type of SIPOC analysis.

What is scope creep?

Scope creep = client wants more work done for the same money.   Not pretty.  It’s no surprise that consultants dread it.  It usually means late nights, grumpy analysts, dissatisfied clients, and potentially lower project margins.  All bad things.

In the end, it is a fancy word for misunderstanding.  What the consultant and client expect the project to deliver is different.  Sometimes it is the consultant’s fault for being unclear, sometimes it is the client’s fault for adding things on last-minute.  The consultant thinks he is  solving problem A, and the client thinks the consultant agreed to solve A+B+C.

Scope

It takes all kinds of forms.  This monster has many different shapes and sizes.  Ask any consultant, and he will commiserate with you about scope creep for several beers.

It happens all the time.  Although it rarely derails a project completely, scope creep is like the common house cold.  It happens on every project in one form or another.  Sometimes it’s just a client’s passing suggestion and other times it’s phrased more like a demand.

Scope creep = out of control.  Beyond the work and the money, I think there are other reasons why consultants find scope creep so demoralizing.  It’s a barometer that the project is not under control.  And trust me, consultants like to be in control.

Consultants are effective because clients have loaned us some of their organizational and political clout to set the pace, nudge clients into action, and keep the takt time of the work.  We have the leverage to get things done through our interviews, workshops, surveys etc. .

So when the client question the scope of the work, well. . . .  it’s a bummer.  It’s like one parent being second-guessed by the other parent in front of the kids.  What will the kids think?  This type of push-back chips away at the perceived (or actual) control we have of the project.  Even though clients are advocating for the consultants to do more work, perversely, the clients are making it harder for the work to get done.

Scope creep = longer project.  Consultants like project-based work.  We like the challenge of new projects and tend to get bored doing the same thing month-after-month, or -gasp-, year-after-year.  Project work is great because it has a start / middle / end.  There is a sense of accomplishment when all the work is turned in and the client says “thank you”.  Scope creep means delaying the celebration and satisfaction of a job well done.

Remedy #1: Be smart from the beginning.  Ideally, the project scope is clearly outlined in the proposal and the statement of work (SoW).  It is common for the SoW to be fairly explicit on what will get done during the course of the project.  Clients sometimes find it a bit repetitive and process-oriented, but it is really the only thing that protects the team and keeps guard-rails on the project.

Remedy #2: Re-iterate scope.  Don’t want to be too heavy-handed about this, but it’s helpful to remind the clients of the project scope.  Have them confirm your progress, and implicitly, agree on the end point.  There are subtle ways to do this too.  For example, you might have a page in your interim presentations which looks like this.

Controling scope creepYou can update it regularly to track progress.  The storyline goes. . . “We finished phases 1 and 2, and now we are focused on phase 3.”  If this is the same diagram that the client saw in the SoW, even better.  The more clients see it, the less likely they will fiddle with it.

It’s like a rock climber who puts anchors in the rock as he climbs; even if he falls, he doesn’t fall that far.  In the same way, the project milestones anchor the project’s progress.

Remedy #3: Say no the right way.  Scope is the senior manager / partner / director’s job.  They must protect the project team and manage the client’s expectations.  It only makes sense that the “boss” of the project is the one to gently push-back on the client:

  • They are usually the ones who have the client relationship
  • They are the ones who approved or wrote the statement of work
  • They own the project profitability and can decide to add more resources if needed
  • They are the “bad cops”. The day-to-day team can stay in the client’s good graces

Remedy #4: Be flexible.  There are times when it makes sense to give a little and do the extra work.  Sometimes, it doesn’t.  Saying YES to clients can get consultants in trouble.

Clients want to feel like savvy buyers of consulting services.  Clients want to have an answer to their boss’ sharp question, “Did we really need to hire the consultants?”  Our job is to give the client enough value (and coaching) so they say “Yes.”

Remedy #5: Think like Ferrari.  Clients pay us for our experience, objectivity and professionalism.  As Enzo Ferrari said, “The client is not always right”

Scope Creep - Enzo FerrariRelated Posts:

Consulting cartoon: What miscommunication looks like

This is a classic cartoon about miscommunication.  You can download a copy here.  There are 12 unique pictures and each one shows a different interpretation of the same  situation.  The customer, analyst, consultant all see and hear things differently.  If you are married, you don’t need a lecture on listening, but for those singles. . . beware.

See 3 of the 12 cartoon drawings below.   You quickly get the point.  I use this when I talk to MBAs about client and team management.  The key message is simple: Listen.

How projects work cartoonReally listen to what is being said.  Put it in context. Seek confirmation by writing meeting minutes, debriefing with team mates after a meeting, paraphrasing what you heard back to the client.  Do not simply assume that you heard the client correctly.

At http://www.projectcartoon.com, the cartoon comes in 15+ languages including Japanese, Chinese, Brazilian Portuguese, and others.  For even more geeky fun, you can modify the cartoons here, by typing your own captions and changing the order of the frames.  Enjoy.

Related Posts: