Wireframes Are for Thinking, Not for Selling
The moment a wireframe has to impress someone, it stops doing the job it was made for. Keep the two activities apart.
A wireframe is a cheap way to be wrong. Its whole value is that you can throw it away without regret, which is why the good ones are ugly, fast, and numerous.
Trouble starts when the same artefact has to travel upward. Somebody needs to present the direction, the wireframe is the only thing that exists, and so it gets tidied. Real copy goes in. The boxes become components. Two days later you are refining a solution you have not finished questioning.
Two different jobs
Thinking artefacts are private, disposable, and optimised for speed. Selling artefacts are public, durable, and optimised for comprehension. Trying to make one thing do both produces a document that is too polished to abandon and too rough to convince.
If you would feel bad deleting it, it is no longer a wireframe.
Keep the thinking cheap
We do the early work in whatever medium is fastest and least precious. Paper, a whiteboard, twenty variations in an hour. The rule is that no single sketch gets more than a few minutes before the next one starts, because the value is in the range explored, not in any one option.
- Twenty rough ideas beat three careful ones at this stage.
- Label the question each sketch is answering.
- Keep real copy out until the structure is settled.
- Take the photo, then throw the paper away.
Then build the argument separately
When it is time to bring others in, we do not present the sketches. We write the case: here is the problem, here are the three directions we explored, here is the one we recommend and what it trades away. One tidy visual supports the recommendation. The exploration stays in the appendix, where it belongs.
Separating these makes both better. The thinking stays loose because nobody is watching. The presentation gets sharp because it has one job.
The tell
If your early sketches are taking longer than an afternoon, they have quietly become a deliverable. Stop, take the photo, and start the argument document instead. The two activities want different tools, different audiences, and different standards, and the work improves the moment you stop asking one artefact to do both.
