IT services delivery is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous.
The vocabulary problem
Consistency is worth more than any individual improvement to IT services delivery. IT services delivery rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The evidence here is thinner than anyone quoting it tends to admit.
Documentation is a symptom: you write it where the design is unclear. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
Scope is the variable everyone adjusts last and should adjust first. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Where to go deeper
Consider the failure mode rather than the success case. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What it is not
It helps to separate the decision from the execution. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
There is a version of IT services delivery that is mostly ritual. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The tooling question is downstream of the constraint question. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
How it works
Speed and reversibility are the trade-off worth naming out loud. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. That said, none of this generalises cleanly across team sizes.
Most of the difficulty lives at the boundaries, not in the middle. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Feedback loops shorter than the planning cycle change everything. The first quarter shows the intended effect; the second shows what the intended effect displaced.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
The short version
The first thing to establish is what you are actually optimising for. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
What looks like a process problem is frequently an ownership problem. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Putting it together
The compounding effects matter far more than the individual wins. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The second-order effects arrive about a quarter after the first-order ones. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. In practice the answer showed up in the calendar before it showed up in the dashboard.
Why it is confusing
Measurement is usually where this falls apart. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
The interesting constraint is almost never the one in the brief. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
What we look for now:
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
- Decide in advance what would make you stop
- Agree on what "done" means, in writing, before starting
- Prefer the reversible option when the evidence is thin
The edge cases
Nobody gets credit for the work that did not need doing. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. This is easier to write than to hold to when a deadline appears.
A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
A common misreading
The expensive mistakes here are rarely the technical ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. It is worth saying that we have not run this long enough to be confident.
Most of the difficulty lives at the boundaries, not in the middle. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. There are organisations where the opposite is true, and they are not obviously worse off.
Documentation is a symptom: you write it where the design is unclear. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. A useful test: if this disappeared tomorrow, how long before anyone noticed?
The vocabulary problem
A shared definition of "done" removes more friction than any tool. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Scope is the variable everyone adjusts last and should adjust first. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
Where to go deeper
The default answer is right often enough to be dangerous. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
Speed and reversibility are the trade-off worth naming out loud. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
What it is not
Consistency is worth more than any individual improvement to IT services delivery. IT services delivery rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. There are organisations where the opposite is true, and they are not obviously worse off.
The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
How it works
The expensive mistakes here are rarely the technical ones. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
The second-order effects arrive about a quarter after the first-order ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The short version
Feedback loops shorter than the planning cycle change everything. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. It is worth saying that we have not run this long enough to be confident.
We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.
