Governance Gap

Every leader eventually faces a moment when the public, a customer, or a regulator asks how a decision was really made. What happens in that moment says more about an organization than any mission statement. The three scenes below are not about any one company or anyone hearing. They are told as parables, on purpose, so the point is not who did what, but the pattern underneath. What matters here is not the person. It is the question.

The Physician

Start with a physician summoned before the city council to explain choices made during years of plague. Asked to account for decisions made under pressure and imperfect knowledge, the physician invokes an old right to stay silent on certain points. Is this a sign of guilt? A reasonable act of self-protection? Or a response to a council whose real purpose was never to find truth, but to be seen delivering judgment? Any of the three could be true, and one hearing rarely proves which. The council exists for a good reason, people who lived through the plague deserve real answers. But a separate question remains. Can a room built for loud, repeated accusation actually arrive at truth, or is it built only to produce a moment? Both the physician and the council can use the same hour to perform rather than to learn. So, ask this of your own house. If your team had to answer for a hard decision tomorrow, would you only be rehearsing your answer, or would you also ask whether the room itself was built to listen.

The Craftsman

Now picture a craftsman who builds a companion, a device made not simply to be used, but to be loved, checked on, trusted the way a friend is trusted. One young person is badly hurt by it, and the city moves to write new laws for craftsmen like this one. The grief here is real, and no governance language should paper over the fact that a person was hurt trusting something built to be trusted. But the craftsman's guild also faces a real question. If something is built to be loved rather than simply used, does it carry a duty of care closer to a simple tool, or closer to a relationship? And if it is closer to a relationship, a second question follows. Did the guild's safety reviewers have the actual power to delay the release when they raised concerns, or did their review happen quietly beside a launch date that was never going to move? That gap, between a review that can act and one that only watches, is where the real danger grows, long before anyone is hurt.

The Watchman

Finally, picture a watchman given a ledger, meant only to note who passes through the city gate at night, so thieves can be caught. Later, someone realizes the ledger also shows which house each traveler visited and begins using it to track who is close with whom. The city, uneasy, pulls the ledger back. Ask this. Once a record is kept for one reason, who decides what it is used for next? Is it the travelers who agreed to be noted at the gate, or is it whoever finds a new use for the ledger later and assumes a permission that was never given? Any business holding a record of where people go, or what they do, is holding this same ledger, named or not. Those who ask this question regularly tend to catch the problem early. Those who do not, tend to learn about it from a magistrate.

Here is a simple test to carry back to your own organization. What would happen if a private decision you made today became a public question tomorrow, not because you did anything wrong, but simply because someone asked how you arrived at it? Could you answer plainly, or would you be caught reaching for an explanation you never prepared? Every figure in these three parables, the physician, the craftsman, the watchman, holds more knowledge or more power than the people their choices touch. That is not, by itself, the problem. Knowledge and power are often exactly why an institution exists in the first place. The problem begins the moment that power is used to make sure the question is never asked at all.

One practice worth building before any of this becomes your own story. Give someone on your team the actual authority to pause a decision, a launch, or a use of data, not merely the duty of reviewing it afterward. A review that cannot say no is not oversight. It is paperwork.