Loading...
Loading...
Walk through the design thinking process: empathize with your customer, define their problem, and brainstorm creative solutions.
Design Thinking was developed at Stanford's d.school and adopted by companies like IDEO, Apple, and Google as a framework for creating products people actually want. But you don't need a design team to use it. The core process — empathize, define, ideate, test — works for anyone building anything, from a SaaS product to a freelance service to a community project.
Most builders start with their solution and then go looking for a problem. Design Thinking flips this: start with the person, understand their reality, define their actual problem, and then — and only then — brainstorm solutions. This single inversion is why products built with design thinking tend to succeed while products built from assumptions tend to fail.
This journaling framework compresses the design thinking process into five prompts you can answer in 15 minutes. It won't replace deep user research, but it will force you to ground your ideas in real human needs instead of your own assumptions about what people want.
Use this when you're developing a product, service, or solution and need to ground it in real user needs. Also great when you're stuck in 'build mode' and need to step back and think about who you're building for and whether the problem is real.
Who is my customer, and what is their daily reality like?
What specific problem or frustration are they experiencing?
How are they currently solving this problem? What's broken about their current solution?
If I could wave a magic wand, what would the ideal solution look like from their perspective?
What is one scrappy experiment I could run this week to test this idea?
Move through the prompts in order: empathize (understand the person), define (pinpoint the problem), ideate (imagine the ideal), and test (find the fastest experiment). The magic wand prompt helps you think without constraints first, then the experiment prompt grounds it in reality. The gap between ideal and experiment is your roadmap.
Design Thinking works because it counteracts the 'curse of knowledge' — once you know how to solve a problem, you can't remember what it's like to not know. This causes builders to design for themselves instead of their users. The empathy-first approach in the prompts forces you to step outside your own perspective and inhabit the daily reality of your customer. The 'magic wand' prompt then removes constraints to surface the ideal solution, while the 'scrappy experiment' prompt grounds it back in reality. This oscillation between dreaming and doing is what produces innovations that are both desirable and feasible.
First-time engineering managers, ages 28-35, who just got promoted from IC roles. Their daily reality: back-to-back meetings they weren't prepared for, no management training, constant context-switching between coding and people problems, and a pervasive feeling of imposter syndrome.
They don't know how to give constructive feedback without it feeling awkward or confrontational. They know they should be having these conversations but they avoid them, which makes the problems worse over time.
They either avoid the conversation entirely (problems fester) or send vague Slack messages ('Hey, can we chat about that thing?'). Some Google 'how to give feedback' and find generic frameworks that feel corporate and inauthentic. Nothing gives them actual words to say in specific situations.
A tool that generates specific conversation scripts based on the situation: 'Your report missed a deadline. Here's exactly how to start the conversation, what to say, and how to end it.' Personalized, contextual, and ready to use in 30 seconds.
Create 5 feedback conversation templates for common scenarios (missed deadline, quality issue, attitude problem, promotion request, team conflict). Post them as a free LinkedIn carousel and measure engagement. If it gets 50+ saves, there's demand.
Describing your customer in demographics instead of psychographics. 'Males 25-35' tells you nothing useful. 'First-time managers with imposter syndrome who got promoted because they were good at their old job, not because they were ready to lead' tells you everything.
Jumping to the solution before fully defining the problem. If your problem statement is vague ('they need better tools'), your solution will be vague too. Get specific: 'They avoid giving feedback because they don't have a script and are afraid of conflict.'
Making the experiment too expensive or complex. The first test should be achievable in under a week with zero budget. Post something on LinkedIn, build a landing page, send 5 cold emails, create a Google Form. Speed beats perfection at this stage.
Talk to real customers before filling this out. Your assumptions about their reality are probably wrong in important ways.
The 'scrappy experiment' should be something you can do in under a week with zero budget. Speed beats perfection.
Revisit this framework after running the experiment. Update your answers based on what you learned.
Find uncontested market space by analyzing what your industry competes on and identifying factors to eliminate, reduce, raise, or create.
Craft a clear, compelling answer to the most common networking question. Move beyond your job title to communicate real value.
Evaluate your business from four essential perspectives: product, marketing, operations, and finance. Identify which area needs attention.
Journal with this framework and get personalized AI feedback that tracks your patterns over time. Start with 3 free frameworks, or unlock all 32 with Pro.