How can you explain a project idea before you can code it?
Use paper, slides or static screens to show one situation: where someone starts, what they do and what they receive. State what does not work instead of presenting a sketch as a finished product.
Build one understandable path
A reading-notes tool might show adding a thought, choosing a topic and finding an earlier entry. Focus on the step you want to discuss rather than simulating accounts and payment. Use invented data instead of private notes or real credentials.
Ask what the person expects
Provide the situation and ask where they would begin. If constant explanation is needed, record unclear labels rather than blaming technical ability. Understanding a sketch does not establish functionality or willingness to pay.
A worksheet you can use
Situation: __. Starting point: __. Main action: __. Expected result: __. Unimplemented part: __. Interpretation gap: __.
Can an untidy sketch be useful?
Yes, if wording and relationships are legible. Questions about visual taste may require more finished material.
Evidence and scope
Paper prototypes cannot verify performance, security or production reliability. Do not collect unexplained charges through them.
IDEO.org discusses iterative prototyping. WKND examples are editorial, not endorsed. IDEO.org Design Kit — Rapid Prototyping
Sources and further reading
This collection in Chinese and English · Life possibilities library