How to validate an idea in four weeks with a small squad
A week-by-week plan for a three-person squad to find out whether an idea deserves more time.
6 min read · Updated 10 October 2026
Start with the riskiest assumption
Most ideas fail on one belief: that a specific person has a specific problem and will change behaviour to solve it. Write that belief as a sentence you could be proven wrong about. Everything else in the four weeks serves that sentence.
Skip features, names and logos for now. A validation squad needs people who can talk to customers, make something visible and keep the plan honest.
Pick three roles, not ten
A product lead who owns the question and the decision. A designer who can turn the idea into something people can react to. An outreach or growth person who can find ten people to talk to.
Each person should commit 4 to 6 hours a week. That is realistic around a day job and enough for a focused month.
Week by week
Week 1: agree the assumption, the target person and what result would make you continue or stop. Book interviews.
Week 2: run at least eight conversations. Ask about the last time the problem happened, not whether they would buy.
Week 3: show a clickable concept or a landing page to five people from the target group. Count what they do, not what they say.
Week 4: review evidence together. Decide to continue, change direction or stop, and write the reason down in the project decision log.
What counts as evidence
Evidence is behaviour: someone shared contact details, booked a call, paid a deposit or used a rough version twice. Compliments are not evidence.
Stopping is a good result. A squad that learns in four weeks that an idea is weak has saved months.