The Feedback Black Hole Is Killing Your Projects
You send the design. You wait. Days pass. Then a Slack message arrives at 10pm: “Looks good but can you make it pop more?” No specifics. No structure. Just vibes.
This is not a client problem. It is a process problem. When you do not give people a framework for giving feedback, you get the worst kind: late, vague, and contradictory. The fix is not better clients. The fix is a feedback loop that makes it easy for them to tell you exactly what they want.
Why Most Feedback Processes Fail
Most designers send a finished mockup and ask “What do you think?” That question invites opinions, not direction. Opinions are subjective. Direction is specific. The difference between “I do not like the blue” and “The call-to-action needs more contrast” is the difference between three rounds of revisions and zero.
The other failure mode is collecting feedback in five different places. Slack messages, email threads, a Figma comment, a phone call. By the time you sit down to make changes, you have to piece together a puzzle from six sources, and half of them contradict each other.
Step 1: Create a Single Feedback Location Before You Share Anything
Before you send the first design, set up one place where all feedback lives. A single Google Doc. A Notion page. A Figma file with comments enabled. Pick one and tell the client: “All feedback goes here. If it is not here, I will not see it.”
This is not rude. This is kind. You are removing the mental load of figuring out where to put feedback. The client does not have to decide between Slack, email, or a call. There is one place. They go there. Done.
Step 2: Ask Specific Questions, Not “What Do You Think?”
Every time you share a design, attach three to five questions. Not open-ended ones. Specific ones:
- Does the hero section clearly say what the product does?
- Is the pricing section easy to scan without scrolling?
- Does the colour scheme feel premium or playful?
- Is there anything that feels confusing or out of place?
Notice what these questions do. They force the client to evaluate the design against goals, not feelings. When someone answers “Does the hero clearly say what the product does?” they either confirm it works or they tell you specifically what is wrong. No one answers that question with “make it pop.”
Step 3: Set a Deadline for Every Round
When you send a design for review, include a deadline. Not a vague one. A specific date and time. “I need all feedback by Thursday 5pm. After that, I move forward with the current version.”
This does two things. First, it creates urgency. People respond to deadlines. Without one, feedback drifts to the bottom of the to-do list. Second, it protects your schedule. You cannot plan next week if you are waiting on feedback that might arrive on Friday or next Wednesday.
If the deadline passes and you have no feedback, send one reminder. If that gets silence, move forward and note it in your project log. The client can always request changes later, but you are not pausing your pipeline indefinitely.
Step 4: Label Each Round and Track What Changed
Version names like “v2 final FINAL actual final” are useless. Use a simple naming system:
- R1: Initial design shared for first review
- R2: Revisions based on R1 feedback
- R3: Final refinements
At the top of your feedback doc, keep a changelog. “R2 changes: moved CTA above fold, increased hero font size, swapped testimonial section order.” This does two things: it shows the client you listened, and it creates a paper trail if someone says “wait, why did you change that?”
Step 5: Close the Loop With a Summary, Not Another Draft
After the final round, do not just send the files. Send a brief summary of what was decided:
- What the final design includes
- What feedback was incorporated and from which round
- What was deliberately left out and why
This summary is your safety net. It prevents the “wait, I thought we were going to add that” conversation two weeks later. It also gives the client confidence that the process worked, which makes them more likely to hire you again.
The Whole System Takes 20 Minutes to Set Up
Create a feedback template. Write your default five questions. Set your deadline format. Done. The next time you start a project, you copy the template, fill in the specifics, and share the link. The entire feedback loop is running before you even open Figma.
Your clients are not ghosting you because they do not care. They are ghosting you because you made giving feedback harder than it needs to be. Fix the process and the ghosting stops.
Want more like this? Join MOKU Club for free. Weekly resources, early access to new guides, and occasional templates you can actually use. Join below.
