Show a polished mockup and you get notes on the button colour. Show a rough one and you get notes on the concept. The feedback you receive is determined by the fidelity you present at, and fidelity is a control you already have.

Category
Design
Author

Justkay
Documentary Filmmaker & Founder at Storyflow
Topics
2026-08-26
•
16 min read
•
DesignEvery designer has had this meeting. You present a concept you believe in, and the client spends forty minutes on the typeface, the photograph in the second frame, and whether the blue is "our blue." Nobody mentions the idea. You leave with a list of cosmetic notes and no answer to the only question you needed answered.
The standard diagnosis is that the client does not understand design. It is almost always wrong.
What actually happened is that you showed them something finished, and finished work carries an implicit message: the thinking is done, please check the details. So they checked the details. They were being helpful, in the only register the artefact offered them.
This is the most reliable rule in client work: the feedback you receive is determined by the fidelity you present at. Not by how you frame it verbally, not by the disclaimer at the start, not by how many times you say "this is early." People respond to what is in front of them.
The corollary is the useful part. Fidelity is a control, and you can set it deliberately.
Low fidelity gets you conceptual feedback. Rough shapes, greyscale, placeholder text, a sketch. Nobody comments on a typeface that is obviously not the typeface. There is nothing to react to except the idea, so the conversation is about the idea.
High fidelity gets you detail feedback. Real copy, real images, final colours. This is correct when the direction is settled and you need sign-off, and it is catastrophic when you are still choosing a direction, because the client will approve or reject a whole direction on the basis of a photograph you picked as a placeholder.
Mixed fidelity gets you confusion. One polished frame next to three rough ones is the most common mistake in this category, and the client will assume the polished one is the recommendation whether you say so or not.
So the first question before any client presentation is not "what should I show." It is "what decision do I need out of this meeting," and the fidelity follows from the answer.
Write one sentence: what has to be true when this meeting ends.
"We need to agree the visual direction." "We need sign-off on the homepage layout so we can build." "We need to know if the messaging lands with your audience."
That sentence determines everything downstream: how many concepts, at what fidelity, in what order, and what you ask for at the end. Skipping it is why so many presentations produce enthusiasm and no progress.
If you cannot write the sentence, the meeting is a status update rather than a presentation, and it should be an email.
Now pick deliberately.
Direction decisions: low fidelity. Greyscale or a single accent, placeholder imagery that is obviously placeholder, real structure but not real content. You want the client comparing ideas, not products.
Layout and structure decisions: mid fidelity. Real structure, real hierarchy, greyed content. Enough to judge how it works, not enough to judge how it looks.
Approval decisions: high fidelity. Real copy, real images, final type and colour. And by this point the direction should already be agreed, so nothing about the concept is up for renegotiation.
The trap is presenting high fidelity early because it is more impressive, which it is. It wins the room and loses the meeting, because the feedback comes back cosmetic and the direction is never actually decided, which means it resurfaces at the worst possible moment later.
One concept is a proposal, not a choice. It puts the client in a binary position where the only available responses are approval or an attempt to redesign it in the room, and they will take the second one.
Two concepts produces a false comparison, and everybody can tell which one you prefer.
Three concepts is the number that works. It reads as genuine exploration, it gives the client a real choice, and it lets them articulate preference by comparison, which is far easier than articulating it from nothing. "I like the confidence of one and the warmth of three" is a useful sentence that only exists when there are three things.
Four or more turns the meeting into a committee. The conversation becomes elimination rather than selection, and elimination invites everyone in the room to have an opinion about everything.
Make the three genuinely different. Three variations of the same idea is one concept in three outfits, and clients see through it immediately. Different means a different underlying strategy: one safe, one that is the actual recommendation, one that pushes further than they will accept but reframes the middle option as reasonable.
Show the brief back to them first, in one slide or one board region: what you understood the problem to be, who the audience is, what success looks like.
This does two things. It gives the client a chance to correct a misunderstanding before it has cost you a week, which happens more often than anyone admits. And it establishes that the concepts are answers to a problem rather than aesthetic proposals, which changes how they get judged.
Then, for each concept, lead with the idea in one sentence before the visual appears. "This one treats you as the established authority in the category." Then show it. The sentence gives them a lens; without it they invent their own, and the one they invent is usually about colour.
"What do you think?" is an invitation to say the first thing anyone notices, and the first thing anyone notices is always a detail.
Replace it with the decision you named in step one:
And say the sentence that does more work than any other in client presentations: "Today I need a decision on direction. Type, colour, and imagery are all still open and we will settle them next." It gives permission to ignore the details, which is the permission most clients are waiting for.
Before anyone leaves, say what was decided and what happens next, and then send it in writing the same day.
"Agreed: we are going forward with concept two. Open: typeface and photography direction. Next: refined layouts by Thursday, one round of notes, then build."
Undocumented decisions get relitigated, and the relitigation always arrives later, when it is more expensive. This step costs four minutes and prevents the single most common source of scope disputes.
The tool matters less than the fidelity, and it matters a bit, because some formats push you toward polish whether you want it or not.
| Format | Fidelity it pushes you toward | Client needs an account | Best for |
|---|---|---|---|
Figma prototype | High | No, view link | Interactive layout and approval |
Canva or Pitch deck | High | No | The narrative presentation |
Milanote board | Low to mid | No, share link | Direction and concept exploration |
Storyflow board | Low to mid | No, share link | Concepts beside the research and brief |
Whatever you make it | No | The record everyone can open | |
Overflow | Mid to high | No | Walking through a flow with an audience |
Printed boards | Low to mid | No | In-person direction decisions |
InVision-style hotspot prototype | High | Usually | Clickable review of a settled design |
The two things that matter most in this table are that the client should never need an account, and that the format you choose has a gravity you will have to fight if it points the wrong way. A deck pulls toward polish. A board pulls toward exploration. Pick the one whose gravity matches your decision.
One practical note on canvases: presenting concepts on the same board as the research and the brief is quietly powerful, because when a client questions a choice you can scroll to the reason rather than recalling it. That is the main argument for presenting in a workspace rather than exporting to a deck. Storyflow, which we make, does this and its AI can read the whole board, so "what did we say the audience was" is answerable in the meeting. Milanote does the board half without the AI and has a free tier. Both are fine; a printed board on a wall is also fine.

Three design directions presented on a Storyflow board beside the brief and the research that justified them
When a client questions a choice, the strongest answer is to scroll to the reason rather than recall it. Storyflow keeps the brief, the research and the three directions on one canvas, and its AI reads the board, so what did we say the audience was is answerable in the meeting. Milanote does the board half free.

"Can we see a version with…" This is a redesign request in the room and it is where scope goes to die. Answer with the decision instead: "We can absolutely try that. Before we do, which of these three directions should it be a version of?" It converts an open-ended request into a decision you needed anyway.
Silence. Usually means the client is not sure what they are supposed to say, which is a framing failure rather than disinterest. Ask the specific question again, narrower: "If you had to delete one of these three right now, which one goes?" Deleting is easier than choosing.
Contradictory feedback from two stakeholders. Do not arbitrate. You have no standing to decide between two people who both outrank you on their own brand. Name it out loud, kindly, and hand it back: "Those point in different directions, and both are reasonable. Which of them should we design toward?" Silence here is more professional than a compromise that satisfies nobody.
"Send it over and we will get back to you." The worst outcome, because feedback gathered asynchronously arrives fragmented, uncontextualised, and from people who were not in the meeting. If you cannot prevent it, control the container: one link, one deadline, one named person responsible for consolidating, and a request for a decision rather than for comments.
Presenting one concept. Guarantees the client tries to redesign it with you rather than choose.
High fidelity for a direction decision. The most expensive mistake here. You get colour feedback on a strategic question, the direction never actually gets decided, and it comes back later.
Mixed fidelity across the set. The polished one wins by default, regardless of what you say.
Presenting without the brief. The work gets judged as taste rather than as an answer to a problem, and taste arguments cannot be won.
Asking for "thoughts." You will receive the first thing anyone noticed, which is a detail, every time.
No decision at the end. The meeting felt productive and nothing was agreed, which you discover two weeks later.
Defending rather than asking. When a client pushes back, the instinct is to explain why the work is right. The better move is to find out what they are actually reacting to, which is frequently not what they said.
Sending it asynchronously by default. Feedback with no meeting is feedback with no context, and it arrives contradictory.
None of them give you a decision-maker. If the person in the room cannot approve, the meeting is a rehearsal and you should find that out before you build.
None of them stop a client redesigning in the room. That is prevented by structure and by the sentence in step five, not by software.
None of them make a weak concept persuasive. Presentation craft improves the odds for good work and does not rescue bad work, and it should not.
None of them resolve two stakeholders who disagree. That is a client-side decision and taking it on yourself is how you end up blamed for it.
Most advice about presenting to clients is about confidence and storytelling. Those help. They are second-order.
The first-order variable is fidelity, and it is entirely in your hands. Show finished work and you will get finished-work feedback, which is detail feedback, which is useless when what you needed was a direction. Show rough work and the only thing available to respond to is the idea.
So before the next presentation, write the sentence: what has to be true when this meeting ends. Set the fidelity to match it. Bring three genuinely different concepts, not one and not four. Show the brief before the work. Ask the specific question. And write down what was decided before anybody leaves the room.
None of that requires a tool, a template, or a better client. It requires deciding, in advance, what the meeting is for, which is the same discipline that makes the design work in the first place.
Name the decision you need first, set the fidelity to match it, show three genuinely different concepts, present the thinking before the visuals, ask a specific question rather than for thoughts, and write down what was decided before anyone leaves. The fidelity choice does more work than everything else combined.
Three. One is a proposal rather than a choice and invites redesign in the room. Two produces a false comparison. Four or more turns the meeting into a committee and shifts the conversation from selection to elimination. Three reads as genuine exploration and lets a client articulate preference by comparing, which is much easier than articulating it from nothing.
Because you showed them something finished, and finished work asks for detail feedback. It is a fidelity problem, not a client problem. Present a direction decision in greyscale with obvious placeholder imagery and the same client will talk about the idea, because there is nothing else to react to.
Whichever matches the fidelity you need, and the client should never need an account. Figma prototypes for interactive layout and approval. Canva or Pitch when the deliverable is a narrative. Milanote or Storyflow when you want concepts sitting next to the research and brief so you can scroll to the reasoning. A PDF is still a completely respectable answer.
In person or on a call, wherever possible. Asynchronous feedback arrives fragmented, uncontextualised, and from people who were not in the meeting, and it is the single largest source of contradictory notes. If you cannot avoid it, control the container: one link, one deadline, one named person consolidating, and ask for a decision rather than for comments.
Convert the request into the decision you needed. When they ask for a version with something changed, agree readily and then ask which of the three directions it should be a version of. It is not a refusal, it keeps the meeting on the actual question, and it is far more effective than defending the work.
Name it and hand it back. You have no standing to choose between two people who both own the brand, and a compromise that splits the difference satisfies nobody and gets blamed on you. Saying "those point in different directions, both reasonable, which should we design toward" is more professional than quietly arbitrating.
Only if the decision you need is approval. For direction decisions, polish is actively harmful: it invites cosmetic feedback on a strategic question, so the direction never gets settled and resurfaces later when changing it is expensive. Match fidelity to the decision, deliberately.
Show the one concept plus the two directions you rejected, at low fidelity, with one line each on why they were rejected. It costs an hour, it turns a proposal back into a choice, and it demonstrates that the recommendation was reasoned rather than the only thing you tried.
The brief as you understood it, and the decision you need. Something like: "Here is the problem as we understood it, and here is who it is for. Today I need a decision on direction. Type, colour, and imagery are all still open." That single framing prevents most of the failures in this article.
Treat it as real information rather than as an obstacle, because it usually is. Ask what it should feel like instead, or ask them to point at the part where the feeling starts. Vague feedback is a client noticing something true and lacking the vocabulary, and the vocabulary is your job, not theirs.
Same day, three lines: what was decided, what is still open, and what happens next with a date. Undocumented decisions get relitigated later, when reversing them is expensive, and this is the cheapest insurance in client work.
Table of Contents
Every Storyflow board starts from real structure and an AI that reads the whole canvas. Open one of these templates and make it yours.
A visual AI workspace where every feature lives inside one canvas. No tab-switching, no context lost.
Build your entire board from a single message
Type what you need in the AI chat at the bottom of your canvas. The AI adds cards, headings, and structure directly onto your board.
Use expert frameworks as AI context
Type @ in the AI chat and choose any Tactic. The AI tailors every response to that framework instead of giving generic advice.
Turn your board into a mind map in seconds
Ask the AI to restructure your canvas as a mindmap. It connects your ideas into a visual hierarchy so you can see how everything relates.
Storyflow actually began as a personal tool while working on creative and research projects.
We kept running into the same problem: ideas were scattered everywhere: notes, documents, and whiteboards.
Nothing helped us see how everything connected.
So we started building a workspace designed around how ideas actually grow.
→ Read how Storyflow was created
Justkay
Documentary Filmmaker & Founder at Storyflow
Published: 2026-08-26
Transform your creative workflow with AI-powered tools. Generate ideas, create content, and boost your productivity in minutes instead of hours.