02.DSoftware Engineering
Systems that keep the record.
The record is not for posterity. It is what keeps a system changeable, because a team that cannot tell deliberate behaviour from accident changes nothing.
The problem
The reasoning leaves with the person who had it
A system encodes hundreds of decisions: why this boundary, why this default, why this exception for one business unit. Almost none of them are written down, because writing them down was never the deliverable. Two years later a team is asked to change one and cannot tell whether the behaviour is deliberate or accidental, so they leave it alone, and the system slowly becomes something nobody is willing to touch.
The cost does not appear as an incident. It appears as an estimate that keeps growing, on a system everybody agrees is simple.
What the work produces
Three things you keep
- 01
Decision records in the repository
Written at the point the call is made, beside the code that implements it, dated. Reconstructed six months later from a chat log is not the same artefact and everybody can tell.
- 02
Stated boundaries
What the system is responsible for and what it explicitly is not. An undrawn boundary gets crossed by the next team, who had no way of knowing it was there.
- 03
A handover that survives the handover
Your engineers answering a question about the system using only the record, with nobody from Koinon in the room. That is the test, and it is run before the engagement ends.
The governed spine
How it answers the spine
Software is where definitions turn into behaviour. A service that computes a term differently from the register has changed the definition without telling anyone, so the register is what the code is reviewed against.
Three artefacts, every engagement
- The written record of what a contested term means, who owns it, and the date the wording was agreed.
- Every hop a number takes from the system that first recorded it to the report that shows it.
- When a definition changed and why, written at the point the call was made rather than reconstructed afterward.
02.DCommission the work
Bring the term two systems report differently.
A 30-minute diagnostic, not a sales call. Bring the disagreement and the deadline that made it matter.
Book a 30-minute diagnostic, opens cal.com in a new tabSheet 04, other ways to reach us