Exploration note / C
Test a question
before adding detail.
A limited prototype can make an idea easier to discuss, provided its purpose and limitations are clear.
Name the uncertainty first
“Build a demonstration” is an activity, not a question. A more useful starting point might be whether a person understands a proposed comparison screen or whether two pieces of information can be brought together reliably.
Write the uncertainty in one sentence. Then decide what observation would help, what material is needed, and what the prototype will deliberately leave out. A narrow boundary makes the result easier to interpret.
Pick the simplest useful format
A paper sketch can expose missing choices. Clickable screens can show sequence and wording. A small technical experiment can investigate an unfamiliar connection. None of these formats automatically establishes that a complete product will be reliable.
For example, a hypothetical household planning tool might use invented reminders to explore how people group tasks. It would not need real account credentials or a production notification system to answer that initial question.
Separate appearance from readiness
A convincing demonstration may still omit security, error handling, ongoing support, and real-world load. Label those omissions. Avoid letting sample data or a polished interface imply that these requirements have been resolved.
Keep a brief record of the starting assumption, what was observed, and what remains uncertain. An unexpected result can be useful if it changes the next decision.
Choose the next step consciously
Possible next steps include revising the idea, examining one technical dependency, or stopping because the proposed tool does not address a meaningful need. Continuing to build is only one option.
The examples here are educational. They do not describe prototypes completed by 120 SCOTCH PINE COURT LLC or commit the company to developing a particular product.