My go-to presentation framework for design projects
A blueprint that turns design work into a story everyone can follow
I used to build every design presentation from scratch. New project. New deck. New flow. New story every time.
It worked, until it didn’t.
Projects got bigger, and other teams relied on my work to unblock theirs. I needed a faster, clearer way to keep people aligned and get projects approved without starting over each time.
That’s when I built a reusable framework. It became my blueprint for presentations, helping me focus on the craft and walk into meetings with more confidence. Each project refined it further, turning it into one of the most reliable tools in my work.
This framework comes from years of practice. I watched, presented, and paid attention to what stuck. The lessons added up, shaping the structure I keep returning to.
When I say framework, I don’t mean a branded deck with layouts. That’s a template. The framework is the story structure that works inside any of those templates.
What you’ll find in this article:
What my framework looks like
How I use it across the project
How you can build or borrow one
Tips for different level designers
Now let’s jump in.
What my framework looks like
This framework mirrors the design process, so people follow it naturally. It feels familiar because the story takes shape the same way the work does. It isn’t rigid. Sections can grow, shrink, or even be skipped, just like the process itself.
Keeping it simple is what makes it stick, and the strength is in the details that follow.
Define
The foundation of the story. Before anyone sees design work, they should know the problem, the audience, and what success looks like. This step sets boundaries and makes sure everyone starts from the same understanding.
Problem statement
Audience and target users
Goals and success criteria
Scope of work
Key stakeholders
Constraints or limitations
Without this stage, nothing else holds together.
Discovery
The groundwork that shapes direction. This is where I show the research and analysis that guided decisions. It’s not about showing everything, just what influenced the path forward.
Audit of the current experience
Stakeholder interviews
Data review and analysis
Past studies worth revisiting
Competitor research and analysis
This is what sharpens the focus.
Design
Where ideas take shape. The designs connect back to Discovery so they’re grounded in what we learned. This is the stage where the story starts to move from problem to potential answers.
Latest explorations or concepts
Multiple directions when relevant
Pros and cons of each approach
Ties back to Discovery insights
This is where exploration turns into real options.
User testing
The checkpoint for validation. What we learned from putting the work in front of people.
Signals that showed what worked
Friction points that held people back
Data or quotes that added evidence
Insights that shaped the design
By the end, we know which ideas hold up and which don’t. That evidence is what sets up a confident recommendation.
Recommendation
The close of the story. I connect the dots between the problem, the options, and the testing. It’s where I make the case for the path forward.
Final concept or direction
Why it’s the right call
Brief recap tying it together
This is where the threads come together into something solid. The decision feels clear, and everyone knows why we landed there.
Next steps
The forward-looking piece. I lay out what’s coming so there’s no confusion on timing, priorities, or responsibilities. The specifics shift depending on where the project is, but the structure stays the same: clear, actionable items.
What’s coming immediately
Who owns what
How it fits into the broader timeline
Any key decisions or milestones ahead
Everyone leaves knowing exactly what happens next and how their role fits into the bigger picture.
Appendix
The appendix is backup. It holds details that don’t belong in the main story but are useful to have ready. I don’t use it every time, but when I do, it can make all the difference.
Extra research slides for the stakeholder who will inevitably ask for them
A direction I explored but chose not to highlight
Links to deeper resources or past decks
Older slides that still add value, just not to the core story
The appendix works because it lets me answer questions without breaking the flow, as long as it doesn’t turn into a dumping ground.
How I use it across the project
This framework isn’t just a one-off deck I pull together for approvals. I keep it in play throughout the project. Starting early gives me momentum, and adding to it along the way keeps the story clear for everyone involved.
In the beginning
By the first sprint review of a new project, I make sure something’s already in play. It might just be rough notes, screenshots, or sketches, but even bare bones, it shifts the tone right away. Define and Discovery anchor the deck, with early pieces filling the gaps.
Flipping through a deck, even early, tells the story better than scrolling a Figma file ever could.
That momentum matters. It lets me frame the story earlier and catch gaps before they grow. Partners see the progress, get excited, and lean in with sharper questions. It shows I’ve got my arms around the work and builds trust early.
In the middle
As the project moves along, the deck sharpens. By this stage, most of Define and Discovery are settled. The work is about shaping designs, testing them, and building toward recommendations. At this point, the deck becomes the shared story. Instead of scattered notes or side conversations, there’s one place everyone can follow.
Sharing it keeps partners aligned, not just designers. Misalignments surface early, which saves me from bigger surprises later. It’s also a signal that the project is being steered with care.
Ready for approval
By the time approvals are close, the deck is basically finished. The story is tight, the visuals are crisp, and each section has a clear role. At that stage, I’m only buttoning it up.
For most stakeholders, nothing should feel new. They’ve seen the story take shape over time. But I know not everyone joins the ride from day one. For those who are new, the final cut still gives them the full arc. It provides clear context, the decisions behind it, and the path forward.
That history is what gives the deck its strength. It isn’t just slides. It’s the record of a project shaped and shared from the beginning.
How you can build or borrow one
You don’t have to use mine, but you should have one.
I built mine by paying attention to the details that make presentations work. Over time I borrowed, stripped back, and reshaped pieces until they formed a framework I could rely on. I’ve seen others pick it up and make it their own, which only confirmed its flexibility.
You can build yours the same way. Start by borrowing from presentations that resonate. Or take one of your own that landed well and strip it down to the essentials. What matters is building something you can return to. That might be one framework you keep refining, or a couple that you pull out depending on the setting.
Sharing that framework is where the impact multiplies. It gives juniors a place to start and seniors a way to raise the quality of the whole team.
Tips for different levels
For Juniors: Use the framework as scaffolding. It supports you without boxing you in.
For Mid-level/Seniors: Use the framework to show how you think. Make your reasoning clear so others can see the logic behind your choices.
For Leads/Super-ICs: Use the framework to raise the bar. Share it, adapt it with your team, and grow the impact together.
These aren’t just career stages. They show how your framework creates value at every level.
Closing thoughts ☕️
A good framework won’t design the work for you. But like a trusted blueprint, it saves you from starting on loose napkin sketches every time.
For me, it’s been one of the most reliable tools in my work. It helps me see the story earlier (tying back to habits I wrote about here), keep the focus on the craft and walk into meetings with confidence. Projects go smoother, and partners engage faster when the story has a clear shape. That clarity isn’t just for my own benefit.
A strong framework helps everyone make better decisions and stay aligned. It turns design work from a solo effort into a shared path forward.
That’s why I keep returning to mine and why I recommend you build or borrow one of your own. The blueprint looks simple, but once you have it, you’ll never go back.
