Decision Debt: Why Clients Change Their Minds Late

Round four comes back, and the notes read like round one. "Can we see it warmer?" "What if the headline led with price?" "Let's go back to the second route." The concept everyone approved three weeks ago is open again, and your team has started using the word "difficult."

If your client keeps changing requirements, the usual explanation is indecision. In our experience, something else is usually going on: the decisions were never made. They were postponed, politely, at the brief and the first review, and now they're coming due with interest. Call it decision debt.

The name borrows from technical debt, the software idea that a shortcut taken now costs more to fix later. Below are six beliefs teams hold about clients who keep changing their mind, and what's usually true instead. This is our read from agency and in-⁠house practice, not research, so treat it as opinion and test it on your own projects.

Myth 1: "This client just can't make up their mind"

Reality: most changes of mind are first decisions, made late.

Round four feels like round one because, for the decision that matters, it is round one. The early rounds were spent reacting to work with no agreed test for it. Reviewers can only say "not quite" until someone defines what right looks like, and a string of "not quite" sounds exactly like a client changing their mind.

Pay it down: stop asking whether they like it. Ask what it has to do.

Myth 2: "The brief was signed off, so the decisions are made"

Reality: a brief can be approved with no success criteria at all.

Plenty of briefs list the audience, deliverables and date, then leave "what good looks like" to taste. Taste shifts with every review, so each round gets judged against whatever the reviewer wants that day.

Pay it down: add one line to the brief that starts "This works if..." and list two or three things the work can pass or fail. Our guide to writing a creative brief covers the rest of what belongs there.

Myth 3: "Our day-⁠to-⁠day contact makes the call"

Reality: the person sending feedback often can't say yes.

The marketing manager you talk to every day approves the concept. Then the work reaches their director, or the regional lead, or legal, for the first time in round three. The notes change because the decider changed. It looks like a reversal, but it's the first review by the person who counts.

Pay it down: at kickoff, ask "Who else will see this before it runs, and who can stop it?" Then write the answer into an approval matrix so approvers and commenters are named before round one.

Myth 4: "Everything they need is in the brief"

Reality: the requirement that sinks round three is usually one nobody wrote down.

The product team can't make price claims this quarter. The CEO dislikes a color. A retail partner has its own specs. None of it was secret, and nobody asked. When it surfaces late, it reads as a new requirement, though it was true from day one.

Pay it down: ask the question briefs skip: "What would make you reject this, even if you loved it?"

Myth 5: "More reviewers means fewer surprises"

Reality: review by committee turns each round into a vote, and the result moves with whoever spoke last.

Each reviewer's notes make sense alone. Put five sets together and they contradict, so the team picks a side and the next round reverses it. Nobody changed their mind. The project never had one mind to change.

Pay it down: one consolidated batch per round, sent by one named approver. Our post on writing revision rounds into your SOW has the wording. When a meeting tries to reopen approved work anyway, see what to do when a quick sync reopens a decision.

Myth 6: "A real change of mind is just another round"

Reality: sometimes the client did decide, and then the world moved. That's new scope, with its own cost and date.

The product spec changes, the budget gets cut, or the launch moves to a new market. Those are legitimate. Absorbing them as "feedback" hides the cost and teaches everyone that direction is free to change.

Pay it down: take it down the change-⁠order path. Name what changed, what it affects, the cost, the new date and who approves it, in writing, before anyone opens a file. What to say when creative scope changes has the scripts.

Writing tighter briefs and handling feedback, revisions and scope creep are core material in the CPMA Level I certification ($147, self-⁠paced).

Client keeps changing requirements? How to handle it

You can't refuse feedback, but you can ask for the decision behind it. Here are the questions we'd use. None of them needs to sound rude.

• When the notes contradict an approval: "Before we make these changes, can I check one thing? The concept was approved on [date]. Are we revising inside that direction, or reopening it? Either is fine. They just have different costs and dates."
• When nobody has named a test: "So we stop guessing, what would make this version right? Give me two or three things it has to do, and we'll judge every round against them."
• When the feedback comes from someone new: "Thanks for passing on these notes. Does [role] sign off on this, or does [approver] still make the call?"
• When the answer is "let me think about it": "Of course. When should we expect the decision?" Then hold them to a date, using the steps for turning "I'll circle back" into a decision date.

Each question moves the conversation from the work to the decision. That's where the debt is, and it's the only place you can pay it down.

Decision debt FAQ

Why does my client keep changing their mind?

Usually because a decision was skipped earlier, not reversed. The usual gaps are no written success criteria, the wrong person approving, a constraint nobody mentioned, and feedback from a committee with no single owner. Each one makes later rounds look like changes of mind. Find which gap you have, then close it in writing.

How do you tell a client they're changing the scope?

Name the approval, then offer the choice. Say what was approved and when, explain that the new request changes it, and give two options: revise within the approved direction, or reopen it with a new cost and date. Keep it factual and calm. You're describing the project, not judging the client.

Should changing requirements cost the client?

If the change alters an approved brief, concept or deliverable, yes, through a change order agreed before the work starts. Revisions inside the approved direction use up included rounds. Changes outside it are new scope. Charging is easier to defend when your SOW defines both and names who approves a change.

Pay it down before round one

Most decision debt is borrowed at the brief and the kickoff, so that's the cheapest place to settle it. Write down what success looks like, who decides and what can't change, and later rounds get much harder to reopen.

For the full foundation behind this (briefs, feedback, revisions and scope creep), start with CPMA Level I: Training + Certification. It's $147, one-⁠time. Eight self-⁠paced modules, typically 10 to 15 hours. Pass the exam with 70%, with unlimited retakes. Your Certificate of Completion is emailed when you finish, and it never expires. If it's not the right fit, there's a 5-⁠day full refund. Start with Level I.

Want the whole path? The Bundle is $297 and includes Level I, Level II, the Creative PM AI Kit and the PM Resume Kit. Bought separately they're $498, so you save $201. Get the Bundle.

CPMA was developed with veterans from Disney, Google, Snap Inc., Red Bull, Sony Pictures, Accenture, and Paramount Pictures.