The simplest design that ships beats the correct one that needs a committee

There's a version of architecture that optimizes only the diagram — the cleanest separation, the most correct pattern, the textbook answer. And there's a version that also asks what the organization can actually approve and operate. The second one ships more value, and it is the harder discipline, because it requires holding a less-pure design on purpose.

Three apps were correct. Two apps shipped.

The textbook answer for the OAuth setup was three app registrations — a clean separation of concerns across the agent, the API, and the downstream resource. The client pushed hard for two, and not out of ignorance. Each app registration in their environment meant another change-advisory-board packet, another approval cycle, another form, another week. We made two work.

Paperwork is a real cost

Every approval gate has a price measured in calendar time, and that price is part of the design whether you account for it or not. A design that's ten percent purer but needs one extra governance cycle can ship a month later than the one that fits inside the approvals you already have. For a marketing site, a month is nothing. For a regulated enterprise, it can be the whole engagement. The "correct" architecture stuck in a queue delivers exactly zero value while it waits.

The best architecture isn't the one that's most correct on the whiteboard. It's the one that's correct enough, and that the organization can actually approve and run.

When to insist anyway

This is not a license to cut every corner. Some simplifications are real risk — a security boundary you shouldn't collapse, a data isolation you shouldn't merge, an audit trail you shouldn't drop. The skill is telling the difference between purity that protects something and purity that only satisfies the diagram. Spend your hard "no" on the first kind, and bend cheerfully on the second. An architect who can't tell those apart either fights every battle or loses the ones that mattered.

The short version

Process and approval cost is a legitimate architectural input, not a compromise of your standards. Optimize for the design that ships and survives contact with the organization's governance, not just for the cleanest picture — and save your insistence for the simplifications that actually carry risk.