Give the Idea a Week, Not Your Savings.
Seven days to question an idea, show a small sample, and decide what deserves more effort.
Practical guide · By FIERCE
The website can wait a week. If the idea is worth pursuing, it can survive a few honest questions before you build a home for it.
An idea can quickly become a course, a community, and a dozen services in your notes. Bring it back to this: does a specific group describe this problem as important enough to spend time addressing?
That's an early signal, not proof of a business. But it's something you can investigate rather than admire.
Day one: write the assumption
Choose one person, one problem, and one possible output. For example: “Project coordinators in small creative teams may need help making recurring handoffs clearer. A facilitated session and one-page checklist might help.”
That's an illustrative hypothesis, not a validated market opportunity. Write down what would make you reconsider. Perhaps people can't recall the problem, already have an adequate solution, or can't use your proposed output in their workflow. Those are things you need to hear, not objections to talk away.
Days two and three: ask about actual experience
Request short conversations with people who know the work. Say you're exploring an idea and aren't asking them to buy anything during the conversation.
Ask: “When did this last happen?” “What did you do?” “What was difficult about the current approach?” “Who else was involved?” Skip “Wouldn't it be great if someone fixed this?” It's too easy to agree with and tells you too little.
Take notes with permission. Get separate consent before publishing names or quotations. If you can't recruit anyone, record that constraint. Don't fill the gap with invented feedback or decide that silence means demand.
Day four: make the smallest useful example
Use a fictional situation to sketch the output. A checklist, outline, or sample session agenda may be enough. Label it as a sample and explain what would need to change for a real engagement.
Set an effort limit and keep it. You're making the idea understandable, not doing unpaid production work. A “quick sample” shouldn't quietly swallow the week you're supposed to be using to learn.
Day five: ask for a specific next step
Show the sample to a suitable person. Ask what's missing and whether they'd consider a clearly scoped pilot. If you're discussing price, state it. Agreement to a free test doesn't show willingness to pay.
Don't take money until you can explain the deliverable, timing, responsibilities, and terms—and you're ready to meet them. Interest doesn't remove the need to be clear about what you're offering.
Days six and seven: decide
Write a short decision note: what you heard, what you still don't know, and whether you'll continue, change, or stop.
A weak signal might justify another conversation. It doesn't justify a confident revenue forecast. If the evidence is thin, say so. You're deciding where to spend the next bit of effort, not presenting a success story.
Your move this week
Pick one assumption and a maximum amount of time you're willing to spend investigating it. Finish the week with the decision note, even if the decision is to stop.
The test has done its job when you can make a better choice about next week. You don't have to build a business to prove the week was worthwhile.
Try the One Useful Move worksheet →
General guidance, not legal, financial or medical advice. Read our editorial standards.