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.
If you're interested in a more details view of this, here is a more detailed blog post with similar ideas: mynameisjehad.com/making-the-cas…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
One of the best partners designers can have are *engineering architects*.
This might seem a bit counterintuitive but here is a bit more on why this is the case & how designers/design leaders can help transform user experience by partnering with engineering architects.
Thread 🧵
(2/ 15) Design architects have similar goals to many designers: solve complex problems by thinking through the use cases, build scalable systems, and ensure that these systems aren't necessarily always limited by today's tech (or that we can draw a line from here to there).
(3/ 15) Architects also have the responsibility to look through multiple different systems and need to ensure they're looking at the end to end experience, not just a narrow use case or a single siloed product or service.
Design teams often ask for a metric that they could own, improve, and use as a way to demonstrate the value of design in a certain company.
In my experience, there isn’t a single metric but there are ways to evolve a set of metrics that show the value of design.
Short thread 🧵
First, how you measure the value of design depends on the maturity of the team.
Early on, as you build credibility, the most important metric is how your *internal* stakeholders view you. Especially engineering and PM leaders and teams.
Building credibility with engineering and PM teams by showing the value design brings is critical.
You can do this through education but it’s most obvious when you, as a design leader, pair closely with key engineering & PM leaders to help shape strategy and deliver execution.