The Monolith That Ate the Roadmap

01 — Scene of the incident

The call came the way these calls always do: from the CFO, not the CTO. Eleven months without a customer-visible feature, a roadmap frozen mid-quarter, and an engineering org of ninety that could not explain — even to itself — where the time was going.

On arrival, the body presented as healthy. Deploys ran daily. Dashboards were green. Standups were punctual. But vital signs measured at the surface tell you nothing about internal bleeding, and this patient had been bleeding for years.

Green dashboards on a dead roadmap are not a paradox. They are a symptom.

02 — External examination

The repository told the first half of the story. One service, 1.4 million lines, twelve teams committing to it. Every feature, regardless of domain, passed through a single shared module the staff engineers called — without irony — the spine.

03 — Internal examination

Dissection of the deploy pipeline found the wound channel. Any change touching the spine required sign-off from one of three engineers. Two had left. The third — the hero — was reviewing forty pull requests a week and writing none of his own.

# Every domain routes through here. Do not touch without approval.
module Spine
  def route_change(change)
    return reject!(change) unless APPROVERS.include?(change.reviewer)
    change.wait_in_queue(days: 9.4) # median, Q2
  end
end

04 — Cause of death

The roadmap did not starve. It suffocated. Ninety engineers produced work that funneled through a nine-day median review queue guarded by one exhausted person. The organization mistook motion for circulation.

Cause of death is recorded as unbounded coupling, complicated by hero dependency. Manner of death: self-inflicted, over approximately four years, with the best of intentions.

05 — Recommendations

The full remediation plan runs eleven pages; the spine of it is three moves:

1. Declare the spine legally dead. Freeze it, wrap it, and route new domains around it.
2. Replace approver sign-off with ownership boundaries enforced in CI — a queue of nine days becomes a boundary check of nine seconds.
3. Retire the hero with honors, then make heroism structurally impossible.