Decision Rules Instead of Taste Debates

Without something specific to check a decision against, every brand-adjacent choice inside a company quietly becomes a debate about personal preference — whether a color feels right, whether a headline sounds punchy enough, whether a campaign direction feels bold or feels risky. These debates can consume disproportionate time and organizational energy precisely because there’s no actual criterion available to settle them, only competing opinions with no way to adjudicate between them. A decision rule replaces the debate with a checkable question, and the difference in speed and organizational friction is larger than it sounds.

Why taste debates are so expensive, beyond the time they consume

A debate about whether something “feels right” has no natural resolution — it can be argued indefinitely, because personal aesthetic preference doesn’t yield to evidence the way a factual question does. Whoever is most senior or most persistent in the room tends to win, which means outcomes depend on organizational politics rather than on whether the decision actually serves the company’s position. This produces a second, subtler cost beyond wasted time: decisions made this way don’t compound into a coherent brand over time, because each one was resolved by whoever happened to prevail in that particular room, using whatever criteria felt persuasive in that particular moment, rather than a consistent standard applied across every similar decision.

What a genuine decision rule looks like

A decision rule reframes a taste question as a position question: not “do we like this creative direction” but “does this creative direction reinforce the specific claim we’ve decided differentiates us, or does it drift toward describing the category in general.” Not “is this color right” but “does this consistently signal the specific attribute we’ve decided to own.” The rule doesn’t eliminate judgment — someone still has to assess whether a given execution actually satisfies the criterion — but it gives that judgment a fixed reference point instead of leaving it to float on unstructured personal preference, which is what turns a five-minute check into an hour-long debate with no natural end.

The best-documented ancestor of the idea

A well-documented example comes from Ritz-Carlton. Its official Service Values say, among other things, that employees own and immediately resolve guest problems. The often-repeated $2,000 spending limit does not appear on that current official page. What the source does support is the underlying principle: explicit authority shortens the path from recognizing a problem to taking responsibility for a decision.

Why this requires a genuinely decided position underneath it

Decision rules only work if there’s an actual position specific enough to check against — a genuinely decided claim about where the company sits and why, not a values statement or an aspirational purpose too broad to disqualify anything. An organization that hasn’t done that underlying work can adopt the language of decision rules without gaining any of the benefit, because “does this reinforce our position” has no real answer when the position itself was never made specific enough to be checkable. This is one of the more common ways decision-rule frameworks fail in practice: the rule is procedurally sound, but the criterion it’s meant to check against was never actually decided with enough precision to do any work.

What changes once rules are actually in place and used

Well-maintained brand guidelines record those rules where teams can find them while handling real cases.

Meetings that used to be taste debates become shorter and more specific — the question shifts from “do I personally like this” to “does this satisfy the stated criterion,” which is answerable by people with very different personal aesthetic preferences, because it isn’t asking them to agree on taste, only to agree on whether a specific, stated standard has been met. This also has a useful secondary effect: decisions that fail the check can be improved against a specific, nameable gap, rather than vaguely reworked based on scattered personal feedback that often contradicts itself between reviewers.

What happens the first time a rule is actually tested

The real test of a decision rule comes the first time it produces an answer someone in the room doesn’t like — a favored creative direction fails the check, or a senior stakeholder’s preferred option doesn’t reinforce the stated position as clearly as an alternative does. How the organization handles that first real test matters disproportionately: honoring the rule’s verdict even when it’s unwelcome establishes that the rule genuinely governs decisions rather than only applying when convenient. Quietly overriding it for a senior voice teaches everyone watching that the rule is decorative, and the next taste debate returns in full force, this time with added cynicism about the process meant to prevent it.

Source Code B is meant to supply rules that can be used without repeatedly consulting Inceptik. Their practical test therefore happens inside the company: which option does a rule exclude, and can two people apply it independently with similar results? If it excludes nothing or needs fresh interpretation every time, it is still too broad. Useful rules help embed a position inside the company.

Continue with related topics

• How to Actually Embed a Position Inside a Company
• What Brand Positioning Actually Means (And What It Doesn’t)
• Guidelines Nobody Uses: Fixing the Enterprise Manual Graveyard

FAQ

Do decision rules remove the need for creative judgment entirely? No — they redirect judgment toward a more useful question. Assessing whether a specific execution satisfies a stated criterion still requires skill and discernment; what changes is that the discernment is being applied to a shared, specific standard rather than to unstructured personal preference, which is what actually shortens the debate.

How many decision rules does an organization typically need? Usually a small number tied directly to the specific position and its most important implications — a handful of clear checks tend to cover the large majority of recurring brand decisions. A very long list of rules often signals that the underlying position wasn’t distilled sharply enough, producing many narrow rules instead of a few that do real work.

Who should have the authority to apply these rules in practice? Ideally, the rules are clear enough that people across relevant teams can apply them without needing to escalate every case — that’s a large part of their value. Genuine edge cases still need a named person with the standing to make a final call, but a well-built set of rules should resolve the substantial majority of decisions without requiring that escalation at all.

---

*A good rule does not guarantee the right answer. It makes the shared standard used to judge that answer explicit.*