Ideate problems before you ideate solutions.
Clarify the problem before coming up with any solutions. Sometimes we get overly excited about coming up with solutions, before we’ve even stopped to think about what problem we’re actually solving.
The Post-it Story: What not to do
It took 3M 10 years to take a great solution, to find the right problem to solve
Introducing... ‘Design Thinking’
←Get the template or learn more
💪 Let’s try this: Ideate some problems
1. Select 2-3 of the grievances/wishes you listed earlier, to automatically turn them each into a Problem thesis 2. Describe the Target User(s) in 3-4 words max. I’m 3. Add at least 1 Assumption for each Problem thesis (what are you assuming the Target User(s) thinks, feels, sees, hears, wants, wants to avoid, finds delightful, finds challenging. Use dashes (-) or asterisks (*) to format as bulleted lists. 4. Estimate the impact & importance as Pain level in money & time; You can gauge the potential impact of a solution by seeing how actively the target audience is trying to solve this problem (pain level) as calculated by estimated cost, without a solution (in time and money). 5. Estimate Difficulty in Solving (how much effort, time, complexity might be involved) and How actively are they trying to solve (to gauge how important this issues is to the target user) for each Problem thesis
My list of perceived problems
Select a Problem thesis, based on the Grievances/Wishes you came up with earlier, then identify target users, assumptions, etc.
View all problems submitted; Disable so only authors see their own list
How actively are they in trying to solve this?
My list of proposed solutions
Select one of the Problem theses from your list, then propose new solutions for each of them. Only your Problem theses will appear here.
Proposed Coda doc solution