Make
A seven-day test for a new idea
One week is enough to move an idea out of imagination and into a disciplined first encounter with evidence, without pretending it is enough to finish the work.
Luke Taylor
New ideas can remain attractive for months because nothing has required them to become specific. A short, bounded test creates momentum without demanding premature commitment. Seven days is not a formula for launching a company or completing research. It is a practical container for moving from intuition to evidence: define the problem, inspect existing work, encounter another perspective, make a small representation and decide what the response means. The pace prevents over-planning while still leaving room for thought.
Day one: define the problem
Write one sentence describing who experiences the problem, in what situation and why it matters. Then list what you are assuming. Avoid beginning with the solution. For a research idea, define the observation or tension; for a service, define the unmet need; for a creative project, define the response or experience you want to investigate.
Write the problem in a sentence and name the person experiencing it. For an idea about school clubs, the person might be a new student trying to find meeting times.
Day two: look for what already exists
Find three credible examples, approaches or sources. Note what each does well, where it differs and what remains uncertain. The purpose is not to prove the idea is original. It is to avoid repeating basic work unknowingly and to gain language for the problem. Record sources so later claims do not depend on memory.
Day three: speak to one relevant person
Choose someone close to the problem or knowledgeable about the method. Ask about their experience before explaining your full idea. Listen for behaviour and specific examples rather than requests for hypothetical features. A single conversation is not representative, but it can expose wording, assumptions and constraints that desk research missed.
Invite a relevant person to describe their experience before explaining your proposed solution. Ask what they currently do and what they find difficult; do not treat one answer as a survey of everyone.
Day four: build the smallest representation
Create a sketch, outline, sample analysis, paper interface, short scene, experiment protocol or one-page service description. It should make the central idea concrete enough for another person to respond. Do not spend the day selecting fonts or names unless visual language is the question being tested.
Day five: run one honest test
Give the representation to a relevant person or apply it to a small body of evidence. Decide what you will watch before the test. Resist explaining away confusion. Take notes on behaviour, questions and unexpected results. Ask what the person thought was happening and which part, if any, they would use or trust.
Show the simplest version you can safely share, such as a sketch or a short set of instructions. Observe whether the person understands what to do, then ask what was unclear.
Days six and seven: decide and document
On day six, identify the assumption most affected and revise one part. On day seven, write a short decision: continue, change direction, seek missing knowledge or stop. Include evidence and the next uncertainty. The week is successful when it improves the decision, even if the original idea is not pursued.
What to carry forward
At the end of the week, do not ask whether the idea is brilliant. Ask whether it is clearer, whether the problem is real enough to deserve more work and whether the student wants to learn what the next version requires. Keep the notes, rough work and decision. They are the useful outcome of the test and the foundation for a more serious commitment if one is justified.
Sources and further reading
This essay draws on Boundlearn's editorial framework for purposeful, mentored learning.