A prototype beats a wireframe for validating requirements
A wireframe shows a screen but can't prove branching logic, so 50 functional requirements stayed theoretical until product, QA and dev could click through a working flow. Validate the behavior, not the picture.
[The note "A prototype beats a wireframe for validating requirements" in full — short, conversational, first person.]
What a wireframe can't validate
[Draft section: what a wireframe can't validate. Written when this piece is published — left as a placeholder here rather than fabricated.]
Building the flow in an afternoon
[Draft section: building the flow in an afternoon. Written when this piece is published — left as a placeholder here rather than fabricated.]
Catching gaps by clicking, not reading
[Draft section: catching gaps by clicking, not reading. Written when this piece is published — left as a placeholder here rather than fabricated.]