What Are We Protecting? ── The Purpose Behind Rules, Revisited

When the protagonist recovered from justice disease as a materials reviewer, one question lingered: What is this rule actually protecting? That question returned with new weight upon reaching an executive role — not as someone reading rules, but as someone responsible for creating them, sustaining them, and embedding them into organizational life. The blind spots that come from focusing too narrowly on rules rather than purposes afflict organizations just as readily as individuals. This episode asks how to build gray-area awareness into organizational design itself.

Becoming a Rule-Maker

The first assignment after becoming department head was revising the internal materials review procedures. The flowchart left by the predecessor was impressively detailed: every trigger phrase flagged, every regulatory gray zone annotated, every escalation path mapped out. It had been built by someone who understood the reviewer's perspective from the inside.

But reading through it, a persistent unease set in. This document was written as a tool for stopping things. Every judgment call was anchored to specific regulatory text. When in doubt, consult the relevant provision. What the flowchart did not address was what should happen when a genuinely novel format appeared — one that existing provisions simply had not anticipated. The chart stopped there.

As a reviewer, one of the hallmarks of justice disease had been relying exclusively on nearby, local measures — regulatory text as the only ruler available. When the rule didn't speak, the default was refusal. An organization that can only act on what the rules explicitly cover also becomes an organization that can only propose what the rules explicitly cover. A culture that freezes at rule gaps quietly loses its capacity to inform.

Reading the Purpose Behind the Rule

The legal philosopher Lon Fuller identified what he called the inner morality of law — a set of conditions that distinguish genuine rules from mere edicts. One that keeps returning is the requirement that law be understandable. Not merely legible, but comprehensible in terms of why the rule exists and what harm it prevents.

Purposive interpretation asks: when a rule is ambiguous, what purpose was it designed to serve? This is not only a lawyer's technique. Every internal guideline, every standard operating procedure, every review framework is subject to the same question. Ask what the materials review guidelines exist to accomplish, and the answers vary in wording but converge on something recognizable: that patients receive accurate information about medicines, that unrealistic expectations are not created, and that trust between pharmaceutical companies and society is maintained.

The procedures revision began by placing that purpose on a single page at the front. In Fuller's terms, rules are maps toward a destination — they are not the destination itself. When maps become outdated, the people who can still read the destination are what keep an organization oriented.

The rule of law does not collapse only when malicious actors bend the rules. It collapses quietly when no one remembers what the rules were for. ── Lon Fuller, The Morality of Law, 1964 (paraphrased)

Compliance Culture vs. Values Culture

Organizations develop different cultures around norms and rules. Neither is inherently superior, but which way an organization leans shapes the quality of everyday judgment throughout the system.

This is not an argument against compliance. In regulated industries, textual adherence to requirements often determines legal exposure. The problem arises when compliance is pursued so locally that the purpose disappears from sight. As Russell Ackoff repeatedly demonstrated in systems thinking, optimizing each part independently tends to degrade the performance of the whole. Locally optimizing compliance can paradoxically undermine the very goal — accurate information reaching patients — that the compliance regime was built to protect.

Designing Space for Gray: Psychological Safety in Practice

Building a values culture requires that people on the ground can say 'I'm not sure how to call this one' without fear of judgment. This turns out to be harder to create than any policy document suggests. Amy Edmondson's research on psychological safety produced one of its most counterintuitive findings in medical settings: teams that reported more errors were not performing worse — they were safer. The distinguishing feature was that they could talk about what happened rather than bury it.

Translated into materials review: teams where a reviewer can say 'this language is in a gray zone and I genuinely can't call it' learn faster than teams where reviewers default to rejection rather than surface the uncertainty. The friction of an honest question is more productive than the smoothness of a reflexive block.

Edmondson is careful to distinguish psychological safety from permissiveness. The goal is to maintain high standards while making it possible to voice uncertainty. The organizational design question is how to create the second condition without sacrificing the first.

Culture Is Measured by How It Handles Exceptions

Every organization produces a gap between its stated values and its actual behavior. That gap becomes most visible when exceptions arise — the case that falls between categories, the judgment call that standard procedures didn't anticipate, the moment where there is no comfortable answer. What happens in those moments defines the culture more accurately than any policy document.

Max Bazerman and Ann Tenbrunsel documented in Blind Spots how systems designed with good intentions systematically produce ethical failures — not because individuals are malicious, but because the architecture of decision-making guides people toward certain choices regardless of their stated values. The same logic applies to review cultures. A procedures manual that says 'report concerns' while tacitly penalizing those who do will not produce a reporting culture. It is the experienced consequences, not the written policy, that define what a culture actually is.

Six months after the procedures revision, a mid-level reviewer brought in a case they genuinely could not call. The instinct that once might have registered that as a sign of inadequate judgment now reads it differently: someone is thinking carefully enough to know the limits of their own certainty. That kind of honesty is precisely what the old version of this reviewer — the one in the grip of justice disease — was unable to produce.

When a Former Reviewer Meets the New System

Recovery from justice disease as a reviewer had produced one durable orientation: the habit of asking what a rule is for before applying it. That question was what pulled judgment away from textual rigidity and back toward actual purpose. It served as an internal corrective — a small but reliable counterweight to the pull of local reasoning.

What executive experience has clarified is that an orientation held by one person does not propagate by itself. When procedures are rewritten, the purpose tends to thin out. When new reviewers join, they receive the text. Over time, an organization can reach a state where everyone follows the rules correctly and no one can articulate why the rules exist.

Ronald Heifetz distinguishes between technical problems and adaptive ones. Technical problems can be solved with existing knowledge and established procedures. Adaptive problems require the organization's members to change how they think, not just what they do. Embedding the ability to see gray areas into a team is adaptive. Writing better procedures is technical; building a culture that can read purpose is adaptive. The executive's task is to work on both — and to understand which kind of problem is actually being faced.

What We're Protecting Hasn't Changed

Pharmaceutical companies invest significantly in materials review because, at the end of the chain, the quality of information reaching patients matters. That purpose was present when the protagonist was a reviewer. It remains present now. What has changed is the structural responsibility for ensuring that purpose can actually be pursued — not just stated.

Peter Senge's core argument in systems thinking is that the problems people face are often embedded in causal structures they cannot see. A reviewer who clings to regulatory text is not exhibiting a personal failing — they may simply be operating in a system that offers no other stable footing. Changing behavior without changing structure is temporary at best. The structure reasserts itself.

The most important thing is to see current reality clearly — not to escape it, but to choose to change the structures within it. ── Peter Senge, The Fifth Discipline, 1990 (paraphrased)

At the front of the revised procedures, one line now reads: 'The purpose of this guideline is to protect an environment in which patients can receive accurate and useful information about medicines. The specific provisions are in service of that purpose.' Whether that design choice will hold over time will be tested by the cases that arrive, not by the text itself. But the question, at least, has been given a place to live.

When the protagonist recovered from justice disease as a reviewer, the most durable lesson was the habit of asking what a rule is for. That question served as an internal corrective against the pull of textual rigidity. Executive experience has shown that the question itself must be made structural — not carried in one person's memory but built into how the organization processes uncertainty.

The difference between compliance culture and values culture is not only about what standard is applied. It is about who is engaged in thinking. A culture anchored only in text concentrates judgment in the hands of interpreters. A culture that holds purpose in view distributes judgment more widely — and builds the organization's collective capacity to navigate genuinely ambiguous situations.

What we are protecting has not changed: the quality of information patients receive, the trust between pharmaceutical companies and society, and the capacity of medicines to reach people through accurate communication. Justice disease — at the individual level and at the organizational level — is a failure to keep that purpose in view. The work of an executive who has been through it is to ensure the purpose remains visible to people who have not.