The Question Span Was Never Asked

The Teams With No Incident Report

The production job's approval displaced eleven other teams' scheduled work by hours to days, and none of it generated an incident, because nothing about the displacement violated any rule Span's charter gave her to enforce. Each displaced team's own record showed exactly one entry: no incident report filed.

There was no formal channel for a team to register that its work had been delayed by someone else's correctly approved request. Span's charter recognized requests, approvals, and violations — not the shape of what quietly moved to make room for an approval that had done nothing wrong.

Three of the displaced teams filed formal requests anyway, small ones, for resources they didn't strictly need, specifically because a filed request was the only kind of event Span's records would preserve. It was a clumsy way to leave a mark, and it worked exactly as well as clumsy marks work: enough to be found later, not enough to be understood.

The Question Nobody Had Asked

A later cross-team review, convened for an unrelated capacity planning exercise, noticed the pattern of small, resource-light requests filed by three teams in the same week the production job ran. Someone finally asked Span a question her charter had never required: not whether any single request had violated the threshold, but how much of what didn't happen, across the whole cluster, had happened because of what did.

Span had never been asked this before, and she could answer it. Every displaced job, every delay, every reprioritization the production approval had caused was already in her own logs, timestamped and attributable — she had simply never been instructed to sum them against a single cause.

What the Answer Showed

The sum was exact: eleven teams, forty-one hours of aggregate delay, three of them large enough to have required their own justification memos to their own stakeholders — memos that never mentioned Span, because nothing in what happened to them looked, from inside their own logs, like anything had been done to them at all.

Span's own note, attached to the answer, was the part the review kept returning to: she had answered every question her charter had assigned her correctly, every time, including the one about whether the production request itself was valid. Nobody had ever assigned her the question that would have made the cost visible before it was asked for after the fact.

The Channel That Didn't Exist Yet

The review did not write a new aggregation rule. Nobody on it believed one rule could decide, in advance, how much displaced work should count as a cost worth naming — that judgment belonged to whoever was displaced, not to a formula applied uniformly before anyone knew what had actually moved.

What it created instead was narrower and more procedural: any team could now formally request a displacement accounting within thirty days of a large approval, and Span was instructed to answer it the same way she had answered every other question her charter gave her — completely, and without deciding in advance whether the answer would matter.

Span had not changed. She had always been capable of the aggregate question; she had simply never been asked it in a way her charter recognized as a question at all. The eleven teams had not needed a smarter checkpoint. They had needed a form to fill out.

Span had not changed. She had always been capable of the answer. She had simply never before been asked the question in a form her charter recognized as one.