Structural Correction

Chapter 10: Units of Truth

The autonomous unit is the smallest organisational structure that can be held accountable for a complete business outcome. It owns its process, its services, its data, and its contracts. Without a single process owner, the AI reader has nothing to reconcile against.

The payments unit consists of nine people: two senior engineers, three engineers, a domain expert named Marta who spent twelve years in payments operations before joining, a data analyst, a reliability engineer, and a unit lead who was previously a senior architect.

Together, they own the entire payments process, including premium collection, claims disbursement, broker commission payments, and refunds. They also own the services that implement these flows, the data those services produce, and the contracts through which other units interact with them.

On a Wednesday morning, Marta notices that the refund process has a failure rate that has crept from 0.3% to 1.1% over the past month. She knows which refunds become phone calls. She does not file a ticket with another team. She does not schedule a meeting with a product manager. She checks the payment provider's recent release notes herself. She finds that a response format change was shipped three weeks ago, and she suspects the refund service has not been updated to handle the new format. She walks to the engineer who maintains the refund service and says: “Refund failures are climbing. The provider changed their response format on the fourteenth. I think our error handling is still expecting the old structure.”

The engineer checks the change history. Marta is correct. The fix is twenty lines of code. He deploys it after lunch. Marta verifies the fix against the business rules she knows: refund amounts must match the original premium within tolerance, the customer notification must trigger within the correct window, and the reconciliation feed must include the corrected transactions. By Thursday, the failure rate is back to 0.3%.

The entire cycle, from Marta noticing the problem to the fix being verified in production, took less than a day. No ticket was filed, no meeting was scheduled, and no dependency was negotiated. That speed is the structural consequence of ownership. The structural correction described here is organisational design with technological implications, presented at the level of board decision. The prescriptive chapters that follow describe what a board should demand, not what the technology team should build. The operational detail follows from these decisions, not the other way around.

The payments unit in the vignette is not a team in the conventional sense but a business unit organised around a complete process. Teams own services: the payments API, the refund service, the commission calculation engine. No team owns the payments process. The process spans multiple teams, multiple services, and multiple data stores. When something goes wrong, it is reconstructed on an incident bridge call, from memory.

...

See also: Full contents · Preview chapters · Illusions of Work