Approvals

Feedback vs Approval: Why They're Not the Same Thing

Feedback ends a conversation. Approval ends a liability. The difference between collecting client comments and collecting client decisions, and why it costs you when you confuse them.

Feedback and approval feel like the same activity. The client looks at your work and responds. But they're two different acts with two different consequences, and confusing them is the single most common reason design projects run over.

The shortest version: feedback ends a conversation. Approval ends a liability.

Feedback is continuous

Feedback is the client reacting to the work, pointing at things, asking questions, suggesting changes. It's open-ended by nature. There's always more of it available, and you want a lot of it early, because it's how the work gets better.

The defining property of feedback is that it never has to stop. A comment thread can run indefinitely. Nothing about leaving a comment commits the client to anything. They're reacting, not deciding.

Approval is discrete

Approval is a single act: this version, this scope, accepted by this person, on this date. It's not a reaction. It's a decision. And unlike feedback, it has a hard edge. It closes the round. Before approval, the work is open. After approval, that version is settled.

The defining property of approval is that it ends something. That's the whole point of it.

A quick analogy

Think of feedback as a conversation in a shop and approval as the receipt. You can talk to the shopkeeper for an hour about which option is right, change your mind twice, ask more questions. None of that is a purchase. The purchase is one discrete act that produces a receipt, and after it, both sides know exactly what was agreed.

Design teams routinely run the hour-long conversation and then skip the purchase. They collect every reaction and never produce the receipt. So when a question comes up later, all they have is a transcript of people talking, not a record of anyone deciding.

Why the difference costs you

Here's what happens when a process produces only feedback and never approval:

There's no defined moment when the work is "done."
Every project stays implicitly open, because nothing ever formally closed.
When a client later requests changes to previously-accepted work, they don't experience it as a new request, because from their side, the conversation never ended.

That last point is the mechanism behind most scope creep. It's rarely bad faith. It's the natural result of a process with no closing punctuation. If nothing ever ends, everything is still open.

Approval inserts the punctuation. Once a round closes with a decision, a new request is visibly new, scopeable, schedulable, billable, instead of an extension of a round that never ended.

Why tools confuse them

Most client review tools are built around feedback collection. They make commenting frictionless: pin a comment, leave a note, resolve an item. That's genuinely useful, and it's most of what a review tool needs to do.

But "make commenting frictionless" and "produce a record of decisions" are different problems requiring different mechanics. A tool optimized for the conversation will leave approval undefined, because approval isn't a comment. It's a recorded decision with four parts: version, person, date, scope.

So you can use an excellent feedback tool for an entire project and end up with zero approvals on record. You collected the conversation. You never collected a decision.

What to do about it

Keep collecting feedback, generously, early, in one place. But add an explicit step where each round closes with an approval, not just trails off. Ask for sign-off on a specific version. Record it. Treat anything after as a new round.

This is the principle behind Lyba: run the feedback loop like any review tool, then end rounds with a formal sign-off so you finish with decisions, not just comments. But the principle stands on its own regardless of tooling. The moment you stop treating "looks good" as approval, the disputes mostly disappear.

FAQ

What is the difference between design feedback and approval? Feedback is the client reacting to work, open-ended and continuous. Approval is a single, dated decision by a named person to accept a specific version. Feedback improves the work; approval ends the round. Confusing them is what leaves projects permanently open.

Is a positive comment the same as approval? No. "Looks good" is feedback. It doesn't commit anyone to a specific version at a specific time, so it can't close a round or settle a later dispute. Approval is an explicit decision recorded against a version.

Why isn't a feedback tool enough? Because feedback tools optimize for the conversation, not the decision. They make commenting easy and leave approval undefined, so you can finish a project with lots of comments and no record of what was actually agreed. You need a closing step that produces an approval receipt.

When does confusing feedback and approval actually hurt me? The moment a client asks to change previously-accepted work. With only feedback on record, you can't show the work was ever settled, so you absorb the rework. With an approval on record, the request is visibly a new round.