The way you present work should change dramatically based on how complete it is. I've watched people show a rough wireframe and get torn apart on font choices. I've also seen people present polished work as if it were still flexible and then spend weeks on rework they didn't need to do.
Both problems come from mismatched framing.
Why this matters
When you present unfinished work without proper framing, clients give you the wrong kind of feedback. They nitpick colors on a prototype that's about validating user flow. When you present finished work too tentatively, clients assume everything is still negotiable and request fundamental changes.
Getting the framing right saves enormous amounts of time and frustration.
The principles
State the completeness level explicitly. "This is 30% complete" sets completely different expectations than "here's what we've built."
Direct their attention. "Focus on the user flow, ignore visual design for now" tells them what feedback is useful and what isn't.
Match visual fidelity to completeness. Sketchy wireframes for early work. Polished mockups for final reviews. The visual quality itself communicates how "done" something is.
Be clear about what's changeable. "The structure is locked. We're looking for feedback on details" prevents someone from requesting a fundamental restructure at the wrong moment.
What good looks like
Presenting work in progress: "This is a rough prototype, about 30% complete. I'm looking for feedback on two things: does the user flow make sense, and are we solving the right problem? Please ignore visual design, copy, and polish. Those come later. What questions or concerns do you have about the approach?"
Presenting finished work: "This is the complete deliverable, ready for launch. We've addressed all previous feedback and completed thorough testing. This is what goes live unless we spot critical issues. Questions?"
Why It Works
Each framing directs feedback appropriately. WIP invites structural feedback. Finished work invites final approval, not redesign.
What bad looks like
Showing a rough sketch: "Here's the final design!" Client: "But the colors are wrong and the text is placeholder..."
Showing polished work: "Does this general direction work?" Client: "Actually, let's rethink the whole layout."
Why It's Bad
Mismatched framing invites mismatched feedback. Time gets wasted.
Tips
- Always start with an explicit completeness level
- Provide a list of what feedback you're looking for
- Name what's NOT ready for feedback yet
- Use words like "directional," "rough," "refined," "polished," "final" to signal status
- For WIP, say "this will change"
- For final, say "this is complete unless there are critical issues"
How this connects
This requires setting clear expectations, managing feedback sessions well, reading the room to sense if framing is working, and handling criticism constructively when people give feedback you weren't looking for.
Things to try
- Before your next presentation, script your framing statement.
- Practice: "This is X% done. I'm looking for feedback on Y. Please ignore Z for now."
- After presenting, note: did people give the right kind of feedback? If not, your framing needs adjusting.