If you’re presenting to your manager, leadership team, or an executive trying to convince them to make a call, I have a presentation format for you to follow.

It's battle tested so you get to avoid my earlier mistakes.

Here's a short summary

(Short Thread 🧵)

(1/9) Start with the conclusion.

I used to think TED talk-like presentations that lead you to the conclusions are the way to go. Not in this case.

Be clear about why you’re there, what are you expecting from them, and what problem are you solving. That’s slide #1.
(2/9) What’s the problem you’re solving and why does it matter?

If you can't get people in the room on the same page about why this problem is critical to the company, it's going to be difficult for you to move forward.

You want agreement that this is a problem that matters.
(3/9) What are we currently doing about this problem?

Don't skip this part. There is likely *something* that the company is doing now to solve this issue. Even if you disagree with it, mention it.

Make it clear you understand what is our current approach.
(4/9) What are our competitors or industry leaders doing?

If other companies in your industry are solving this issue better, highlight that.

This is powerful. Nobody wants to fall behind and highlighting how others are doing better is a powerful motivation to do more.
(5/9) What’s your solution?

Now that we're clear on the problem and have similar context, what is your solution?

If this is a slight repeat of slide #1, that's okay. You want to highlight it within the context you've just provided.
(6/9) What's the cost?

Solutions cost money and resources. What are you asking for? You want to be clear and articulate about the overall cost of this solution.

This is not just about money, it’s about the overall cost of time, possible change of direction, resourcing, etc.
(7/9) What’s the cost of inaction?

Do *not* skip this part.

There is a cost to doing nothing. This is a killer way to showcase how the cost of doing something is *better* than the cost of doing what we're doing today or to not improve.
(8/9) What’s your high-level execution plan?

Depending on who you're presenting to, you might not have to show too much detail here.

However, you want to be clear that this is not a pie in the sky idea. You've thought this through and have a plan of action if this goes forward.
(9/9) The action items

What decision do you expect to be made in this room? Who's responsible for what decisions? What is blocked on these decisions?

Be clear about your ask(s). You want to leave the room either with a decision or with a clear path to one.

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.