How to Create Great Slides
Slide-making is a fundamental consulting skill. Any gaps in your skills will hold you back. I learned slowly, and it cost me dearly. Don't repeat my mistakes.
This post is the most popular on my website. It’s the third edition of this post, and I keep updating it based on new insights I gain from coaching dozens of MBB consultants.
Slide-making is a fundamental consulting skill.
Whether we like it or not, we communicate our ideas through slides, and our clients assess our work through slides.
If you are a consultant, it will be a major part of your daily work for a long time.
Any friction will result in a huge loss of productivity.
But if you learn to do it well, you free up lots of time and gain an unfair advantage for yourself.
How did I learn slide-making?
I joined McKinsey at 34.
Before consulting, I had never created a single slide in my life. Then, I had to create dozens per week.
Whenever I had to create a new slide, it always turned into a soul-crushing experience.
But it all changed after one project.
Once, I worked with a superstar consultant.
His name was Alex.
He churned out impeccable documents like a machine, and partners and clients adored him.
I had to learn his approach.
Fortunately, we became good friends, and he taught me all his secrets.
Soon enough, I experienced a step change in my performance.
Finally, I could enjoy working in consulting.
This guide was created based on Alex's secrets. I also synthesized my 9-year experience working at McKinsey and the insights I gained coaching dozens of MBB consultants.
If you are an MBB consultant and sick of struggling with performance and development, I would like to speak with you.
Book a Free 1-1 Consultation to discuss whether I can help you through my coaching program. There is no commitment, and you can ask any burning questions in a risk-free environment.
Read this post to learn more about the Hero’s Journey coaching program.


Super useful, will definitely be rereading this. Please do share more on document creation
I definitely made the mistake with thinking "iteratively" at the start of the job - thanks for writing this resource :)