The observation collapses into a feature request
“Add folders” survives, while the user, situation and evidence that created the idea disappear.
How to capture product ideas
Do not rush from insight to feature.
Save the problem worth testing
Record who has the problem, what you observed, why it matters and the cheapest next validation step. The idea stays grounded before solution details take over.
The product thought becomes a hypothesis
User, problem, signal and next validation action remain connected.
A familiar moment
A product idea is more useful before it becomes a solution
A support call, sales conversation or moment of personal friction can reveal a real problem. But memory quickly compresses it into a favorite feature. Capturing the original situation and evidence keeps alternative solutions open and gives the team something that can be tested.
Three simple steps
Say it now — sort it out later
-
1
Name the user and situation
Who experienced the difficulty, and what were they trying to accomplish?
-
2
Separate evidence from solution
Record what you saw or heard before describing the feature you imagine.
-
3
Choose the smallest validation
Find similar cases, interview users, inspect behavior or test a lightweight prototype.
Instead of one big pile
Evidence, hypotheses and implementation do not collapse into one list
Keep discovery tasks with the product opportunity. Technical implementation can become a separate coding context after the idea earns it.
Team planning: signal—tasks are reassigned in chat · interview 5 leads · test shared ownership copy
What changes
Remember less — finish more
The original observation remains
Capture the phrase, behavior or situation before interpretation replaces it.
Validation becomes the next action
An idea can lead to a question or experiment instead of immediately becoming a build task.
Opportunities stay grouped
Research, interviews and decisions can share one product context.
Long thoughts fit naturally
Explain the user, situation and alternatives without squeezing them into a tiny title.
The source can be replayed
Return to the recording when a nuance disappears from the processed text.
AI assistant · beta
Say it however it comes — AI can help make sense of it
AI can suggest a title, a due date and the right context, or help turn a larger idea into a clear plan. The beta is currently available to some Premium users. We are checking quality and will gradually open it to everyone.
The essential part already works without the beta: voice capture saves immediately and does not disappear when you are offline
An idea is not evidence, and evidence is not permission
- Validate the problem before committing engineering time to a favored solution.
- Remove or avoid customer names, personal data and confidential business details.
- Keep product discovery separate from promises already made to users or stakeholders.
What people usually ask
What should I capture in a product idea?
Record the user, job they were trying to do, observed problem, evidence, possible explanation and next validation action.
How is a product idea different from a coding idea?
A product idea asks whether a user problem is worth solving. A coding idea describes how software behavior might be implemented or corrected.
Should I describe the solution too?
You can, but label it as one option. Preserve the problem and evidence so the first solution does not become inevitable.
Can research tasks live with the hypothesis?
Yes. Keep interviews, data checks and prototype tests in the same opportunity context.
Does Unload validate product ideas automatically?
No. It helps preserve and structure the thought; real validation still requires users, behavior, data or experiments.
Try it with your next thought
Say the task, then get on with your day
Unload keeps it on your phone and brings it back when you need it. The app is free.
iPhone · Web · Telegram