Describe
State the problem, intended user, setting, and limits in straightforward language.
Find guidance for preparing an idea, understanding evaluation, participating in discussions, and making sensible next steps while you develop a product concept.
A thoughtful submission and a focused prototype can be useful at any early stage. Participation does not guarantee review, development, licensing, or commercial results.
Use these starting points to find an answer that matches where you are now: preparing an idea, considering feedback, or learning what to test next.
No. A patent is not required to prepare an idea for discussion or submission. Decide carefully what you are comfortable sharing publicly, and seek qualified legal guidance when intellectual property protection or confidentiality matters.
Describe the user, the problem, your proposed approach, and what makes it meaningfully different. Include any early sketches, research, testing, constraints, or questions that would help another person understand the concept.
Evaluation can consider usefulness, feasibility, alternatives, constraints, and the evidence behind important assumptions. The purpose is to identify what needs to be learned next, not to promise an outcome.
No. A submission does not guarantee selection, review, prototyping, licensing, launch, revenue, or another commercial result. Product development involves uncertainty and often requires repeated testing and revision.
Yes. Frame the problem clearly, ask a focused question, and share only information you are comfortable making visible. Constructive feedback should help reveal user needs, assumptions, limitations, and practical next steps.
That can be a useful beginning. Start by naming the problem and intended user, then create the simplest sketch, model, or test that can answer one important question about the idea.
These four steps offer a practical way to use the available guidance before deciding whether to revise, test, discuss, or submit a concept.
State the problem, intended user, setting, and limits in straightforward language.
Look at existing alternatives and identify the assumption that needs the most evidence.
Make a simple model, sketch, or prompt that can answer a focused product question.
Use what you learn to improve the explanation, adjust the concept, or choose another direction.
Explore the resource for practical notes on product thinking, or bring a focused question to the community discussion spaces.
Organize what you know, name what needs testing, and use Edison Chronicle as a practical place to develop your product thinking.