Welcome back!



Forgot password?

Don’t have an account? Subscribe now

Consulting Storyboard for Strategy Engagements

Storyboard matters in consulting studies because useful insights mean very little unless they can be woven into a compelling story. Critical insights which are not presented as a story, generally fail to get any traction at a client. In fact, that is one reason strategy studies collect dust on a client’s desk: they did not present a clear message.

When one of FIRMSconsulting partners, Michael, was a corporate strategy partner, he pretty much drove teams a little crazy to constantly refine the story. He still does that. If you are following the US Retail Banking Study (one of step by step consulting studies we released to help train our clients) you would have seen us push for a crisp and compelling story. We do the same on the current power sector study (another step by step consulting study we released for our clients to help them develop strategy, problem solving, leadership, and communication skills). We just push and push for the best story out of the data. A great storyboard will get the client to act.

That’s exactly why you should be looking into a consulting storyboard – to create a compelling story that will convey the key message to your client. Whether you have your team do an analysis and create storyboard ideas based on that, or you have a completely different strategy, your client will see a well-defined path to success. 

And that is what you want at the end of the day.

Where a storyboard fits in a consulting strategy study

Boiled down to the basics, the business consulting strategy engagement structure can be explained as follows. First the key question the team needs to answer in the engagement is determined. The key question has to be split into smaller questions in a logical format. This allows the team to develop a decision tree.

The decision tree has to meet two criteria. It has to be mutually exclusive and collectively exhaustive (MECE). There are two other criteria to be met and that is taught in our programs on strategytraining.com, though if you stick to the MECE rule that will be fine. Based on the decision tree, the hypotheses are developed.

The consulting storyboard is the message engagement team delivers to the client, using the decision tree and hypotheses that have been developed, and it is based on the anticipated results of the consulting project.

Next the team develops analyses to test each hypothesis. Based on the results of the analyses the hypotheses are proved or disproved and the consulting storyboard is refined.

The diagram below shows a structure of a strategy study and a point at which the rough consulting storyboard is developed. Although this diagram helps to understand how strategy engagements are conducted from the structural perspective, keep in mind that a strategy engagement is an iterative process and can be messy. In fact, it is usually messy.

Finally, the idea of using an objective function works in almost all types of strategy and operations engagements, but does not work in corporate strategy. In corporate strategy a very different approach is used because those engagements are different. That will be covered in a different article since corporate strategy studies are so rare. And it is also covered in our advanced strategy training programs, including Corporate Strategy and Transformation Study.

 

What is a storyboard?

To explain the management consulting storyboard concept, let’s use an example from the animation industry. Before producing detailed animations and more, the animation team must first agree on the story.

The animation team gathers together in a room and takes blank pieces of A4 paper, they write out a short 10-word description of a scene on the top of the page and produce a rough 15-second pencil sketch to outline the animation which could go into this part of the movie.

In all, they can produce about 30 to 120 such A4 pages, stick them on a wall in sequence and everyone will be able to follow the story. This allows the animation team to debate the story and messaging without expensive animation work which would definitely change as the story changes.

To extend this analogy to a management consulting storyboard, the team needs to prepare a story of their message so that everyone in the team can understand their thinking and provide feedback. The management consulting storyboard is basically the headlines of the presentation which summarize the anticipated results from the work stream or from the entire strategy study.

In the management consulting industry, these kinds of storyboarding presentations can prove useful to everyone, from seasoned veterans to aspiring consultants trying to improve a crucial set of skills for their consulting career. It helps visualize the key takeaways and create a presentation for the client to see where they are and where they’re going. 

Question from a reader about developing a consulting storyboard

To dig deeper into the concept of developing a storyboard, we will answer a question we received from a reader, let’s call him Henry.

Henry was avidly following the life blog on a study we did in the United States, where we were helping one of the largest Latin American banks to put together a strategy to enter the profitable, large and rapidly growing US financial services market. The study was focused around providing financing to low income entrepreneurs, either immigrants or US citizens.

We had been live blogging the study so everything we did you could follow in real time and we spent a lot of time discussing what we were putting together. Fascinating work. It is definitely a new way to teach strategy consulting and tends to be very popular.

Henry wrote:

Michael, what you are doing is very interesting but one thing I don’t understand is how is it that you are able to come up with a storyboard for the client only in the beginning of your 3rd week of a 8 to 10 week strategy study?

This kind of seems to me as if you are giving a client a solution that you already have versus relying on the analysis to tell you what the answer will be. And isn’t that the criticism that consultants get that they don’t really develop new ideas for clients but put out what they already know? It does not make any sense to me so I am not sure how it can be right.

I can understand the reader’s confusion but he is wrong and I want to explain why he is wrong.

Piece of advice on how to communicate

First it is important to point out one thing about this guy’s communication style. And, to be fair, many people have this style of communicating so it is worthwhile to address it here.

Henry is basically saying, “I don’t understand something. And because I don’t understand it, it must be wrong“. This is a really bad way to communicate.

It is extremely naïve or egotistical, or arrogant, you pick, to assume that if there is something you don’t understand then it must be wrong. For all you know, it may make perfect sense but you don’t have the necessary mindset or the necessary prerequisite knowledge to understand it.

If you don’t understand, it is better to say, “Look, I am sure it makes sense. I don’t actually get it so I will let you try it out and maybe I will get it later.” But don’t make it sound that if you don’t understand it then there is something wrong with the actual work.

It is just not appropriate. It sounds really bad to clients, superiors and colleagues when you do it. You sound like a 5 year old child.

How we could come up with a storyboard in such a short time

Besides that piece of advice on how to communicate, let’s get into how we were able to write a storyboard in such a short time.

Note that anything that we will be able to teach you here will be at a high level. You can learn these concepts in depth as you go through our strategy training. How to develop a storyboard and other strategy capabilities is also taught in our book “Succeeding as a Management Consultant“.

Now let’s address how we were able to come up with the storyboard so early.

Think about the logic here. We are not doing analysis just because we have to do it. We are doing analysis because we are trying to answer some questions.

If you are just doing the analysis because this is the analysis you always do in a strategy study (e.g. market segmentation, cost effectiveness and revenue analysis), then yes, you have to wait for the analysis to be done to see what the analysis will tell you.

But this is not the way we do things. We do the analysis for a reason and that is the fundamental mind shift you have to make.

We start off with the objective function. What is the problem we are trying to solve for the client? We then break that objective function into the direct drivers of the problem. We then continue breaking down those drivers until we get what looks like a Christmas tree, that is actually a decision tree.

The objective function is the apex of the tree and the tree breaks out. We then prioritize the branches that are most important in the decision tree to help us figure out where to spend most of our time (refer to the exhibit below for an example).

For each of those prioritized branches we then say, “Ok, what is the hypothesis to explain why this is the issue impacting the objective function?”.

Once we have the hypotheses, we can then say, “Hey, if these are the hypotheses, what tests do we need to do to prove or disprove the hypotheses?”.

Those tests then become the analyses.

We do the analyses which directly help us answer the hypotheses, which directly helps us determine if each of the prioritized branches should in fact be prioritized and, therefore, what drives the objective function.

So even before we finish the analysis, because we know why we are doing the analysis, we can say, “Ok, if the analysis turns out to be this, what is the message we will give to the client?”.

For each analysis you probably will have one or two, at most 3, possible outcomes. Rather than writing a storyboard for each outcome, we write a storyboard for what we think is the most likely outcome. And then, if the analyses turn out to be a little bit different than we expected, obviously the storyboard will be revised.

But more or less we don’t turn out to be wrong. We turn out to be right most of the time because of the logic we apply and because we are attacking the problem from so many angles that this allows us to cross reference and cross check things.

And that is the crucial point here. We don’t just do analysis for the sake of doing it. And, therefore, we don’t have to wait to see what the analysis is telling us. The analysis is being done to check certain hypotheses that we developed at the start of the consulting study. And the hypotheses are not random. They are built off the decision tree, which is also not random because the decision tree is actually brainstorming the issues which are driving the objective function.

And this is the important difference in which elite firms do analysis. We don’t just decide, “Ok, this is the checklist of analysis we need to do, let’s do it”.

We say, “Hey, hold on a second, why are we doing the analysis? What purpose does it serve?”. In our mind we are developing the storyboard which states if these are the issues and this is the way the issues turn out in the analysis, then this is the recommendation we give to the client.

We can write that consulting storyboard in the first, second or third week. And once we complete the analysis, we can go back and check if the storyboard we wrote out, based on what we thought the analysis will turn out to be, makes sense.

And if it does not, we will revise the storyboard. But I can tell you right now, 80-90% of the storyboard usually turns out to be correct. The more and more you think about it, even 95% of it could turn out to be correct.

By the 3rd week of the study, the storyboard is more or less there. Yes, few things will change. The data will definitely change. For example, we may know that a certain segment of the market is unprofitable, but likely will not know why it is unprofitable or by how much it is unprofitable. But we more or less will be able to figure out it is unprofitable.

So that explains how we are able to come up with the consulting storyboard so early. Because we are not doing analysis for the sake of doing it but because we have a reason for doing it, and the reason allows us to structure the storyboard.

What is next?

If you need an example of developing a consulting storyboard, presenting a storyboard and using a storyboard to structure analysis you may find this article helpful.

SPREAD THE WORD! Like this? Please share it.

Subscribe to the Firmsconsulting podcast on iTunes.

Follow us:
https://www.facebook.com/Firmsconsulting
@firmsconsulting

Image from Trey Ratcliff under cc.

Want to learn more about how FIRMSconsulting
can help your organization?

Related Articles

Uncategorized

Start Here: Reaching Your Potential

Approximately 6.7% of the world’s population has a university degree. Less than 1% of this select group has the intent and the will to make a difference. Because you are receiving this email, I know you are likely a part of that small group. Thank you for being the kind of person who wants…

Uncategorized

Career Stagnation. When Promotions End and the Runway Ends

In the final piece for Strategy Insights, called “When Promotions End and the Runway Ends,” I'm going to talk through an interesting client situation. We have an Insider, who later also became a coaching client, named Addie. He works for a large multinational company. There's nothing unusual about his career. He…

Uncategorized

CEO of Danone Learns That Being Good is Not Good Enough

CEO of Danone Learns That Being Good is Not Good Enough The next big theme is about how Danone’s CEO has just learned that being good is not good enough. If you follow the saga of Danone, it has branded itself as the socially responsible consumer packaged goods company, or as they…

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.