Through a Bain business case, Terance discusses how to distinguish between analyzing a problem and assembling the answers to arrive at a strategy.
I felt lucky and relieved to have survived the scare of my last Bain business case. The relief did not last very long. I had to very quickly show that I deserved to be at Bain. With the engagement manager having left, I felt there was greater attention on my performance.
Would I be able to rise to the occasion and prove that this was a personal issue or was there something really wrong with my performance? I also felt a personal obligation to not disappoint the partners who had stood up for me. I did not have long to wait for the opportunity to prove myself.
Leading the business case
Just one week after my performance review, I was assigned to another aviation project. As you will see over time, the aviation sector and strategy became my area of specialization. Bain had been appointed to develop an IT strategy for one of the largest air carriers in the continental USA.
I was assigned to lead an important piece of work. The firm wanted to test me and asked me to be the analyst leading the business case under the support of a more senior consultant. It was going to be tough for me. I had no real finance or accounting background other than my 3 weeks MBA training at the Bain University.
Although I was assigned to work with an experienced consultant, the partner made it clear that I would need to drive the business case. The other consultant would oversee my work and provide input as needed. They would not be responsible for delivery. I would need to own this piece of work.
To be honest I was scared. While I appreciated the opportunity to lead something this big, I was not sure I could do it, and frankly surprised the engagement manager would place such trust in me.
My peers on the engagement did not help matters. The team assigned to this project was a stellar team. All were high-flyers within the ranks of Bain and were regularly cited for their outstanding team work, delivery excellence and exceptional client relationship.
Bain awards outstanding consultants with vacations away to some exotic locale with all expenses paid and they are allowed to take their families. Each of the guys on the team had won a vacation during the last 3 years running. The team consisted of 5 consultants including the partner leading the study.
I really appreciated the way the engagement manager approached this study. That is the reason I decided to bite the bullet and plunge into this project. We sat down and had a long discussion about what he wanted from this Bain business case. He was very hands-off, which I found surprising. He spoke a lot about the principles of the Bain philosophy.
I could see this guy led teams by bringing in smart people, inspiring them and allowing them to work. He mentioned he asked for me to be on the project because he heard I had spoken up for the client’s benefit on my last project. He admired that and wanted a similar style on this study. I clearly remember the 6 principles he had for the engagement:
- Take charge and dazzle the client, project team and Bain.
- Titles mean nothing. As far as he is concerned, I am the point man on the business case.
- A policy of no surprises.
- He would provide air-cover as needed and I just needed to ask for help.
- Follow the Bain approach but be creative.
- Have fun and work as a team.
Having this conversation really helped me. Not only did he inspire me to give my best, but he kept his word. At no point on the project was I treated like a junior member of the team. I was treated like a really senior and established Bain consultant. I remember sitting in the planning meetings and the engagement manager would deflect all finance questions to me.
He made a point of ensuring that no one, not even the engagement partner, would approach the Finance Director unless I was involved and it was part of my plan for the study. This gave me a tremendous boost in confidence. Now I just needed to deliver behind that.
Business case can mean so many things
What the hell do I do? Business cases can mean so many things. I spoke to the Bain business case experts and everyone had different ideas. In one project a business case meant working out the return-on-equity and in another it meant finding the increase in profitability. In yet in another it meant calculating the reduction in labor.
So for the first week, I worked with the engagement manager, partner and the rest of the team to see where they were taking the study. I decided that if each business case is unique, then the business case must serve the needs of the project. Therefore, I could only plan the business case once the needs of the project were clear. That sounded logical to me.
As I worked with the other team members to develop their plans, I developed a framework for my analyses. In hindsight, the framework is so obvious and logical, but at the time, I was pulling my hair out.
It helps to arrive at the framework by yourself since you can then understand why it was developed in the format chosen. The engagement manager would calmly listen to me and make polite suggestions and it was up to me to make the final decision. With power comes great responsibility – or so they say.
My analyses approach
So my analyses approach was simple:
Step 1 – Conduct a 2 weeks review of the IT department’s finances. Basically I was creating their income statement, which they did not have. I was also creating an easy to understand capital investment overview, something which they again did not have.
Step 2 – Determine if their total expenditure was appropriate.
Step 3 – Determine if investments were made in the appropriate parts of the business.
Step 4 – Determine what they could do to improve.
Step 5 – Determine the business case for the recommended strategy.
I ran this by the engagement manager and partner and both of them were happy with my analyses approach. They thought it was easy to follow, exactly what was needed and just a question of finding the information and drawing the insights.
Developing a storyboard
I already knew that the engagement partner would be on my case to prepare my storyboard. So I spent the first week doing the following:
- Summarizing the key questions and hypotheses I needed to answer.
- Building a decision tree to ensure I was not excluding anything important.
- Developing my analyses and data collection templates.
Once this was done, I started working on my storyboard. I must say that developing my first storyboard was a painful experience. It is such a foreign concept when done by yourself for the first time.
Although I had practiced this in the office when I worked in the research team, I had taken for granted the important prompts and pointers provided by the consulting partners. Their comments were really useful to nudge me in the right direction.
I would just have to work without them. I reworked my storyboard every single night and discussed it with the manager the next morning. Each morning he sent it back with the following kinds of comments:
- Do we need to tell clients we did this?
- What is this data telling us? Are you sure?
- What does it mean if they do not adhere to global best practice?
- What is the most important finding you expect? Why is it not in the story?
- Why is your story so long?
- Did you know Winston Churchill demanded his war cabinet provide feedback using one single-sided typed page with double spacing? Why is your storyboard 80 pages? Is the news eighty times as catastrophic as World War II?
He was never flippant or arrogant. He just asked interesting questions in a nice way. It forced me to think this through over and over. I used to literally spend hours talking to employees and helping the other consultants all the while stressing that I had not started my data collection and analyses. The engagement manager did not seem worried. He wanted me to first develop my storyboard.
Presenting a storyboard
By the end of week two I was still not sure how my final storyboard would look like. This was after 7 iterations. Unfortunately for me, the next day the entire project team was having a meeting and we each needed to present back our storyboard. We were scheduled to have the meeting from 9am to 11am.
My tactic was to stall and hope to buy time to gather my thoughts over the weekend and hopefully present on Monday. The project partner rarely came in between Monday and Wednesday, so if I could survive Friday I would have about 5 days to spare.
I did quite well on Friday. Stalling that is. When the partner came in Friday morning, I strongly suggested he have some pastry from the new Dean & Deluca boutique on the ground floor. That killed about 25 minutes since I was extremely polite to allow every woman to pay before me. We spent another 10 minutes on pleasantries upstairs before getting into the detail.
Once we got to work, it was an intellectually tough session. The storyboards were dissected and analyzed. The partner checked for logic in thinking, robustness of the analyses and so on. It was interesting to watch. I also kept asking questions to stall.
At 10:55am, the partner checked his watch and mentioned he was running out of time. The rest of the team got up to leave since they had 11am meetings. The partner motioned for me to stay and quickly brief him. He wanted me to give him the basic message from my storyboard.
Damn! I thought I had escaped.
I basically sucked in a deep breath and told him what I thought the analyses would show. I just went with what I think the data was telling me and its implications:
- About 75% of the IT budget is locked into legacy contracts decided at corporate level and over which the IT department has no control.
- The legacy contracts are never reviewed and likely not meeting performance criteria.
- The planned budget cuts could only be taken on the capital projects side, where passenger and ticketing IT upgrades would be made, since the rest of the budget was controlled by corporate. This would directly impact sales and customer satisfaction.
- Despite popular opinion, Pacific Air is not spending more than peers, although its pattern of spending does not make sense. It is spending too little on core systems (ticketing) and wants to cut them even more.
- It is the only airline in its peer group having such a large percentage of its IT budget tied to internal systems versus customer supporting systems.
- The IT department could invest in the customer systems without requiring a budget increase. They would be able to tighten internal IT costs and shift the savings to the customer facing systems.
I waited for the expected criticism. It never came. The partner said that was a “brilliant” storyline and he looked forward to seeing the analyses.
The insight which indicates you understand management consulting
That taught me a very, very important lesson. Sure, management consulting firms have many phenomenal tools to construct decision trees, hypotheses and hundreds of guides to work out costing and rates of return. However, those tools only breakdown the problem. They do not put the pieces together to present the answer.
That takes intuition, creativity, experience and guts. That was a fundamental lesson in this project which I believe set me up for great success as a management consultant. I realized all the tools exist to break down problems into neat parts for comparison.
The truly outstanding consultants understand this and develop a knack for looking at the pieces and trying to fit them together to present a new picture. That’s a very important lesson that I hope to convey in this piece. Great associates and engagement managers can use formidable analyses to break down problems. Those who can reassemble them into the solution become partners. It’s that simple.
Much later I realized that Henry Mintzberg and Kenichi Ohmae (McKinsey) both outlined this understanding as a critical skill for management consultants. Mintzberg said that not everyone can be a management consultant. Bringing the right combination of intuition, creativity, experience and guts to a problem is something that cannot be taught and not everyone has it. Therefore, not everyone can be a management consultant.
Ohmae arrived at the same conclusion in his book “The Mind of the Strategist” but explained it differently. He said that engineers are linear problem solvers and are excellent at breaking down problems. However, this skill at breaking down problems is a major disadvantage when combining the pieces to develop the solution. Linear thinking does not work. In other words, all management consultants must have the skills of engineering thinking, but having these skills is by itself not enough.
In hindsight I cannot think why anyone would ever solve problems by scurrying off to analyze every piece of data. It is such a waste of time. The deductive approach of solving problem with decision trees and hypotheses is so powerful, it really boggles the mind. Once you make that shift to understanding and using the process, you become a powerful and efficient thinker.
You can imagine your career consisting of 3 parts:
Part 1 – Learning to correctly break down problems and analyze them.
Part 2 – Assembling the pieces to develop the solution and recommendation.
Part 3 – Implementing the solutions and becoming an operator.
Analysts, interns, consultants, senior consultants, managers, case leaders, engagement managers (different terms for different firms) all are in phase 1. It’s that simple. They are still learning to break down problems. An analyst is helping to break down a problem, an associate is breaking down a problem and an engagement manager is overseeing many people as they break down problems.
Phase 2 is much tougher and very few consultants make the transition. Until consultants get to the associate principal, partner, senior partner, director or managing director level, they are not crafting solutions. They are just preparing the pieces which the more skilled thinkers will use to craft the final solution.
Many consultants managed out of Bain, McKinsey and the Boston Consulting Group never understand this point. They leave as associates or engagement managers and think they know how to develop solutions. Unfortunately they have not learnt the skills needed. They only have half of the skill set required. Do not get me wrong, the skills they have are still important, but not enough.
Phase 3 will be discussed much later. The bottom line is that you cannot be an operator in a management consulting firm. You need to transition to a corporate role, run a P&L with resources and fight the daily battle to succeed in the market.
Using the storyboard to structure my analyses
It would be nice to say that I worked brutal hours every day. That fits into the stereotype for management consultants. I did not. Using the storyboard to structure my analyses and data collection made the project ridiculously easy. I should not say that, but it is true.
If you follow the Bain approach to break down problems and follow the guidelines to develop the analyses, you cannot go wrong. You need to constantly think about what you are doing, communicate and incorporate information. If you do this, you will succeed.
Always learn the process for solving problems. Really understand it and use it. Then sit with the data and think about what it is saying. Think long and deep about it.
The business case did dazzle the client
Despite being the junior consultant on this team, I can safely say that the business case did dazzle the client. Most of the hypotheses were proven. The client did manage to make huge investments in the customer facing side of the business, with only a 5% increase to the IT budget.
Rather surprisingly, the client retained us for much more work. I was also surprised when people at the office started referring to me as an aviation and business case specialist. Yet that is the power of the management consulting approach. It works. My star was rising.
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 Jon Herbert under cc.