An 80-person logistics company serves several distinct B2B client types. Over three years, internal product requests had accumulated — dispatch tooling, quoting flows, exception handling, a client portal — each raised by a business team that genuinely needed it, each stalled because the development process had no shared specification layer. Requests took twelve to eighteen weeks from raised to usable. Most never got there.
We started not with the backlog but with the rules underneath it. What does every quote have to carry, regardless of client type or carrier? What exceptions must never be resolved without a human dispatcher’s judgment? Two invariants emerged. Everything else — the feature prioritization, the prototype sequencing, the client-facing configuration — was judgment. That is the arc: one meta-rule (the operation runs on encodable rules), two invariants (the company’s private instances of that rule), and judgment freed to do its actual job.
Two invariants, one clear boundary
The first invariant: any exception affecting a service-level agreement must route to a human dispatcher. Not a queue. Not a heuristic. A person. The second: every quote must record cost, lead time, carrier constraints, and the client commitment together in one place — not split across three tools, not reconstructed from email.
Those two rules had never been written down. Once they were, the backlog became a sequencing problem, not a judgment problem.
“For the first time, what the business team asked for didn’t fall into a black hole.” — COO, anonymized
The harness
We did not deliver a prioritization framework. We delivered a running system: a spec-to-prototype pipeline that takes each internal request through a decision trace — request, specification, prototype, live — visible to both the product and business teams. The trace is the audit record; the record is what ends re-litigation of the same decisions.
Over a 30-day concentrated effort in 2026 Q1, the ~120–150 open P0 and P1 internal requests were cleared. Median time from internal request to usable prototype dropped from roughly 45 days to under 7. Client satisfaction, measured by client-success survey over a 60-day post-go-live window, moved from 70 to 93 out of 100. The burn-down was not a sprint; it was what happens when two rules are written down and the judgment that needs a person finally has room to breathe.