Article Design Systems Property & Tourism

Record Exceptions Before They Become Unwritten Rules

In day-to-day design, when exceptions are approved only verbally, the same exception often recurs until it becomes the de facto rule. A more reliable approach is to document every exception and review regularly whether the rule should change. Use an exception log to make that decision stick.

Qingmei Future InsightsMarch 22, 20267-minute read

Key points

In day-to-day design, exception tracking should no longer mean verbally approving an exception once.
Left unchecked, the same thing keeps happening: the same exception recurs until it becomes the de facto rule.
Start instead with this: document every exception and review regularly whether the rule should change.
Put the decision in the exception log. Owner: the system steward.
From now on, review against one question: Has this exception been documented, rather than left in conversation?

01Where does exception tracking break down?

In day-to-day design, exception tracking is often reduced to verbally approving an exception once. Everyone is willing to agree because they haven't yet faced the real problem: the same exception recurs until it becomes the de facto rule.

The meeting ends quickly. Once the people who actually use exception tracking leave the room, they're left with this: the same exception recurs until it becomes the de facto rule.

Document every exception and review regularly whether the rule should change. Until that happens, exception tracking remains a matter of verbal approval.

02What is really blocking exception tracking?

The problem isn't the wording. Verbal approval can be used to explain any number of situations, which means it can't prevent the same exception from recurring until it becomes the de facto rule.

As more people look to exception tracking for answers, it becomes more abstract, and the old problem returns: the same exception recurs until it becomes the de facto rule.

03Redefine exception tracking

A more useful starting point is to document every exception and review regularly whether the rule should change. Make the refusal explicit first; only then can exception tracking support real decisions.

Keeping verbal approval may make the process smoother, but the underlying issue remains: the same exception recurs until it becomes the de facto rule.

04Turn exception tracking into a tool

Record this decision in the exception log. For exception tracking, this page is more useful than another, longer explanation.

When approving an exception, consult the exception log. Don't reinvent its wording in every discussion.

05Who owns exception tracking?

Assign ownership to a specific person: the system steward. Without an owner, the exception log will be rewritten at the first conflict.

Keep just one review question: Has this exception been documented, rather than left in conversation? If you can't answer, the exception log isn't guiding a decision.

Framework

Four layers of exception tracking

From non-negotiable principles to tools used on the ground, each layer answers one question, keeping exception tracking from being reduced to verbal approval.

L1Exceptions

This layer spells out what must not be compromised in exception tracking.

L2Reason

This layer turns exception tracking into conditions that can be checked.

L3Should the rule change?

This layer defines what can change across different contexts.

L4Duration

This layer assigns exception tracking to the people who use it and states any exceptions.

Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.

Recommended actions

Action 01

Start from the site

Identify when exception tracking is actually used in day-to-day design. Don't start by reframing it as verbal approval.

Action 02

Keep it to one page

Use the exception log instead of a longer explanation. Keep only what supports this principle: “Document every exception and review regularly whether the rule should change.”

Action 03

Judge it by one question

When approving an exception, ask just one question: Has this exception been documented, rather than left in conversation? If you can't answer, the decision isn't settled.

Action 04