A repeated rule can make an experience easier to understand. People learn what to expect, and a team gains a dependable way to work. An exception can then reveal a condition the rule does not yet handle well.
The useful question is what the difference tells us. Is this a rare situation that needs an explicit alternative, or evidence of a wider pattern? Who encounters it, and what happens if the usual process continues unchanged? Looking closely at a concrete case helps us avoid changing a whole system on the basis of an unclear impression.
Examine one difficult case closely
Consider an organization using one enquiry form for all new work. Most people can describe an ambition and an expected date. A small number arrive with an urgent problem and no clear idea of the kind of project it might become. The ordinary questions may give them little room to explain what is happening.
We can work through examples with the team. What information would help someone respond responsibly? Where do people abandon a question, supply a workaround or contact a colleague another way? A single unusual response can be worth understanding, while several related encounters may reveal a condition the form should handle more deliberately.
Possible changes can be compared before the overall structure is altered. A clearer prompt might help. An optional route could let someone describe uncertainty. Another situation may call for a separate way to contact the team. The choice depends on the needs revealed and what the organization can sustain.
We can make the ordinary route and the difficult case visible in the same prototype. The client can consider the effect of each alternative on visitors and the people receiving enquiries. That keeps the exception connected to the wider purpose of the rule.
Decide what the exception is telling us
We can compare several responses. A local accommodation may be sufficient. A clearer explanation may resolve the difficulty. In another situation, the exception may show that the underlying arrangement needs to be reconsidered. Each response has consequences for the people using and maintaining the system.
At Abstraction, we can keep the rule and its observed exceptions visible while we examine those choices. A prototype or workflow example can show how a proposed change affects the ordinary path as well as the difficult case. That gives the decision a basis people can discuss.
A Useful Exception holds its regular diagonal field beside sharply bounded changes in direction and absence. The surrounding order remains legible, giving the local deviation a specific relationship to the whole.
Return to the Gallery
Encounter A Useful Exception in the Gallery