Want to be a 10x better communicator than 95% of people?

Use McKinsey's 3-step Pyramid Principle:

McKinsey is the most powerful consulting firm on earth.

• $10B in revenue
• 30,000+ employees
• 90+ years of history

This is their 3-step process for structured communication:
1/ Start with the answer first

It's natural to build up to a conclusion after presenting the facts.

Instead, give the answer first.

This allows your listener to quickly process your recommendation.

"What should we do?" → "You should do X."

You'll be more persuasive.
2/ Group and summarise your supporting arguments

Your ideas should form a pyramid under your answer.

Your ideas at one level must be a summary of the ideas below.

For each supporting argument, break down into a group of 3.

Three is the magic number– memorable and persuasive.
3/ Logically order your supporting ideas

You want to make sure your ideas belong together.

1. Time order - follow if there is a sequence of events
2. Structural order - break a single thought into its parts
3. Degree order - present your ideas from most to least important
Key take-aways of the Pyramid Principle:

1. Start with the answer first
2. Group and summarise your supporting arguments
3. Logically order your supporting ideas

Use it in written and verbal communication to persuade others.
Follow me @thealexbanks for more threads to help you in business and life.

If you liked this thread, you'll love the newsletter.

Subscribe here:
https://t.co/vlGCY549bQ
I write threads each week, here's another I think you'll enjoy:
https://t.co/nsgeZptbn7
Help others learn and quote tweet this thread:
https://t.co/KBkNMHovqy

More from Alex Banks

Over 3.5 billion tweets are posted each week.

But most people are reading the wrong ones.

Here are the 10 best tweets from the week guaranteed to make you smarter:

1/ Who: @KurtisHanni

Topic: Build an elite


2/ Who: @heykahn

Topic: Become an effective decision


3/ Who: @amandanat

Topic: Hot takes on life, careers and


4/ Who: @EvergreenMEP

Topic: Upgrade your
I have a masters degree in finance.

But I've learned 10x more from Twitter.

10 threads that will make you a better investor:

1/ Who: @naval

What: Principles to wealth creation

Tweet:


2/ Who: @10kdiver

What: Achieving financial freedom

Tweet:


3/ Who: @trengriffin

What: Money flows as a function of the


4/ Who: @girdley

What: How to get paid when investing in a new
10 threads that will teach you more about business than any business degree:

1/ Who: @naval

What: Principles to wealth creation

Tweet:


2/ Who: @sweatystartup

What: Actions to wealth creation

Tweet:


3/ Who: @RomeenSheth

What: Early career


4/ Who: @heykahn

What: Career
Hard skills get you in.

But soft skills get you far.

10 threads that will accelerate your career:

1/ Who: @RomeenSheth

What: Enter through the side door

Tweet:


2/ Who: @slizagna

What: Resume


3/ Who: @heykahn

What: Soft skill


4/ Who: @SahilBloom

What: Nail the

More from All

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.