3. Validate
Get feedback, early and often.
At every stage, even if you’re just starting to think of ideas. Let people know what you’re working on and ask for ideas.
1. Show, don’t tell. Then, ask questions.
👉 At every stage.
👉 Show, don’t tell.
👉 Get good at asking both open-ended, and specific questions
2. Test your assumptions.
Methods:
Examples:
💪 Let’s try this: Validate each other’s ideas
Instructions
Clear sample data
Who’s problems & solutions are we validating?
Select a name: Blank
Blank
STEP 1: Validate proposed problems
Problem thesis
Review & comment
Target User(s)
Pain level (🕓)
Pain level (💲)
How actively are they in trying to solve this?
Impact index
My Assumptions
Tools to validate
Collaborative layoff lists built using Google Sheets often run into user limits, disorganization, and are easily moderated/managed
Open
Companies & Employees
1.67
Social
College move-in lists should be digital checklists—easy to share and easy to track what you need to buy, borrow, or pack from any phone or laptop.
Open
Students
2
Social
Poll
STEP 2: Validate proposed solutions
Instructions: Upvote all the solutions you think are Desirable (the target group would love this), Viable (this solution makes sense, and could very well resolve/mitigate the problem), and Feasible (this solution is do-able and realistic)
Problem thesis
Proposed Coda doc solution
Desirable
Viable
Feasible
Collaborative layoff lists built using Google Sheets often run into user limits, disorganization, and are easily moderated/managed
1
Convert sheet to doc and show different views for different fucntions
College move-in lists should be digital checklists—easy to share and easy to track what you need to buy, borrow, or pack from any phone or laptop.
1
Digitize the move-in list and show different views as shopping lists, borrow lists; with opportunities for people to check things off from their phone
Everyone uses one platform/tool for collaboration
1
Pilot Coda with one club to show ease of use and then expand on campus to integrate collaboration tools - allowing the University of Pennsylvania to save hundreds of thousands in useless solutions for collaboration tools
Lack of proper onboarding on documentation
1
Host regular workshops/brainstorming session/hackathons to teach members how to organize notes
not consistent attendance - don’t know who will show up
1
create a doc that they can check into and confirm whether or not they will be attending, and shows the attendance of others, and how many people will be there
2
2
3
Tools
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.