The short answer
A design decision can be correct, well-evidenced, and carefully made, and still be reversed months later by someone who spent three minutes looking at the work. This rarely happens because the original decision was wrong, but because the reasoning behind it was never made visible. A decision that exists only in the designer’s head has no defence — when the designer moves on or forgets the detail, the reasoning goes with them. The work gets changed because the reasoning was never transferred in a form that could outlast the person who held it.
The experience every practitioner recognises
Most designers have a version of this story. You make a decision carefully, you test it, you refine it, you base it on evidence, and it ships. And then, some months later, it gets undone — reversed by someone who was not part of the original process, who looked at the work briefly, and who had a plausible-sounding reason to change it.
The frustration this produces is usually experienced as ‘people keep changing my work.’ That framing is understandable but it obscures the actual mechanism. The work is not being changed because the people changing it are careless or because they don’t respect design. It is being changed because the reasoning that justified the original decision is not available to them. They are working from the artefact — the screen, the flow, the specification — without access to the reasoning that produced it.
A worked example
Consider a designer who spends two weeks testing and refining a multi-step quotation journey. The final design removes a summary page that the previous version had, because usability testing showed users found it confusing rather than reassuring. The decision is deliberate and evidenced.
Six months later, a new product manager joins. They review the journey and reintroduce the summary page, on the reasonable-sounding basis that users always want to see a summary before they commit. The testing evidence that informed the original decision sits in a research repository the new manager does not know exists. That original evidence-based decision is reversed. The confusion the original designer removed comes back.
Nobody acted in bad faith here. The product manager made a reasonable call based on a widely held design heuristic and well-tested pattern. The problem is that the original decision had no way to defend itself. The evidence that would have changed the product manager’s mind was invisible to them at the moment they made their decision.
Why a decision in someone’s head has no defence
A design decision is only as durable as the record of its reasoning. When a decision that exists only in the designer’s head is completely undefended, and that designer leaves, forgets, or simply isn’t in the room when the decision is questioned, the reasoning is gone.
A decision recorded as a comment in a design file is only marginally better. It survives only as long as someone thinks to look for it, and only as long as that file remains the place people look. As soon as the work moves to a different tool, a different team, or a different phase, the comment becomes invisible. It is technically recorded, but practically it becomes inaccessible.
What makes a decision defensible is not that it was well-reasoned at the time — it is that the reasoning is recorded somewhere a future person would find it, in a form they could understand and evaluate. Without that, the decision is open to reversal by anyone with a plausible alternative and the authority to act on it. The challenge does not even have to be better than the original reasoning, it can simply be the only reasoning visible in the room.
What protecting a decision actually requires
Protecting a design decision is not about defending it more forcefully in the moment it is challenged. By the time it is being challenged, the outcome is largely determined by whether the reasoning exists in an accessible form. If it does, the conversation is about evidence and conditions, but if it does not, the conversation is about who is more persuasive in the room — and the original reasoning, unable to speak for itself, usually loses.
Protecting the decision needs to happen earlier, at the point it is made. It requires recording not just what was decided, but why: what was known at the time, what alternatives were considered, what evidence informed the choice, and under what conditions the decision should be reconsidered. That record needs to live somewhere a future person would actually find it, not buried in a tool or a thread that the next team will never open.
This is the difference between a decision that can be reversed by anyone with a plausible alternative, and a decision that can only be sensibly changed by someone who engages with the original reasoning. The rest of this series covers how to build that kind of record — and the cognitive reasons most practitioners don’t.
Instead of asking how to stop people changing your designs, ask what someone would need to know to understand why a decision was made — and where they would find it.
Frequently asked questions
Why do good design decisions get reversed?
Good design decisions get reversed when the reasoning behind them is not recorded in an accessible form. A decision that exists only in the designer’s head, or buried in a design file comment, cannot defend itself when it is questioned months later by someone who was not part of the original process. The reversal usually comes from a reasonable-sounding alternative, not a better-reasoned one — because the original reasoning is invisible at the moment of challenge.
How do you stop your design work from being changed?
You cannot prevent design work from being questioned, and you should not try to. What you can do is ensure each decision carries a visible, accessible record of its reasoning: what was decided, what evidence informed it, what alternatives were rejected, and under what conditions it should be revisited. A decision with documented reasoning can only be sensibly reversed by engaging with that reasoning, which raises the bar far above a plausible-sounding preference.
Where should design decision reasoning be recorded?
Design decision reasoning should be recorded somewhere a future person — who was not part of the original decision — would actually find it. A comment in a design file is usually insufficient because it is invisible once work moves to another tool or phase. A decision log, a research repository entry, or a delivery ticket that travels with the work are more durable. What matters is that the record is accessible to the people who will later question or build on the decision.
What makes a design decision defensible?
A design decision is defensible when its reasoning is recorded in a form a future reader can find, understand, and evaluate. This means capturing what was decided, what was known at the time, what alternatives were considered, and what conditions would justify revisiting it. A decision that carries this record forces any challenge to engage with the original reasoning. A decision without it can be overturned by anyone with a plausible alternative and the authority to act.