Development note / Defining an idea
Describe the idea
so it can be examined.
A concept note explains the intended use, the uncertainty behind it, and the boundaries of the next question. It does not need to describe a finished product.
Give the idea a setting.
Start with the situation in which the idea would matter. Who would use it? What would they be trying to do? What difficulty or limitation is being considered? A concrete setting helps readers understand the purpose without first agreeing with the proposed solution.
For an illustrative reusable storage divider, the setting could include the items being separated, the space available, and the way people access them. Those details are more informative than a general description such as a better organizing product.
Separate an expectation from an established fact.
An early concept often contains assumptions about usefulness, technical behavior, cost, or the way someone might use it. Write those assumptions down as matters to examine. Do not let a promising description turn them into results that have already been demonstrated.
Identify what is known from existing information and what still needs investigation. The next question might concern a dimension, a repeated movement, or a user's understanding of a proposed arrangement. Keeping that question narrow makes a later activity easier to interpret.
Make the next decision understandable.
Describe what information would help decide whether to continue, revise the concept, or set it aside. Include important limits, such as the setting being considered and the parts of the idea that are not yet addressed.
A useful note can be brief: the situation, the proposed idea, the key assumption, and the question to examine next. Keep the date and version so later changes do not obscure the original reasoning. This is general planning guidance; it is not a specification for a company service or a completed development project.