Learning Objectives

• Communicate design solutions effectively
• Build stakeholder buy-in
• Plan for implementation
• Weeks 1-8: Complete design process

1. Storytelling for Design

• Once upon a time... (user context)
• Every day... (current situation/pain)
• Until one day... (your solution)
• Because of that... (impact)
• Until finally... (transformed experience)

2. Building Your Pitch

1. The Problem: User need, evidence from research
2. The Solution: What you designed and why
3. The Process: How design thinking led to this solution
4. Evidence: User testing results, quotes, data
5. Impact: Business value, user value, feasibility

3. Implementation Planning

• Identify stakeholders and champions
• Define success metrics
• Create MVP (Minimum Viable Product) roadmap
• Plan for iteration beyond launch

Q1: Why is storytelling important in design thinking?

Stories make data memorable and compelling. They connect emotionally with stakeholders, communicate user needs effectively, and build buy-in for solutions. Q2: What is the Value Arc story structure?

Once upon a time... (setup), Every day... (pain), Until one day... (solution), Because of that... (results), Until finally... (transformation). Maps to classic story structure. Q3: What is an MVP and how does it relate to design thinking?

Minimum Viable Product - the smallest version of a solution that can be tested with users. Design thinking's prototyping and testing informs what goes into the MVP. Q4: How do you measure success of a design thinking project?

User satisfaction, task success rate, time to complete tasks, adoption rate, business KPIs (revenue, retention, referrals), and qualitative feedback. Q5: What are change management considerations for design implementation?

Stakeholder mapping, communication plan, training, champions/advocates, phased rollout, feedback loops, celebrating early wins, addressing resistance. Join Discord PreviousDesign SprintsNextAdvanced Applications