What a Working Definition of Done Looks Like
A working note on definition of done — what matters, what does not, and where these projects usually go sideways.
There is a short answer on definition of done and a useful one. The short answer fits in a Slack message. The useful one depends on three things nobody writes down, so we will write them down.
Where definition of done usually goes wrong
The complaint shows up as a symptom. A slow week, an irritated customer, a number moving the wrong way.
The cause normally sits two decisions earlier, in something that was never written down.
Patch the symptom and it returns in different clothes.
Two situations that read identically on a Monday call
In projects like these, one version is local. A single workflow strains, everything else is fine, and two focused weeks clear it.
The other looks the same in a status update, but the strain is systemic. Treat that one as local and you spend a quarter arriving back where you started.
Telling them apart in week one is most of the value anyone brings to the room.
Mistakes companies make
- Choosing tools before the workflow is written down.
- Scoping version one to cover every edge case.
- Leaving the work unowned, then blaming the tool.
- Skipping measurement, so nobody can prove it helped.
- Treating launch day as the end of the cost.
The first and the last are the expensive ones.
The engineering view
From inside the codebase, definition of done reduces to three questions. What happens when a step fails halfway. Who finds out. How you reverse it.
Design for partial failure before you need it. Step three fails after one and two already succeeded, and that is the case people skip.
Give retries a ceiling and some jitter. A retry storm is an outage you built yourself.
How we approach it step by step
- Reproduce the pain with a real case, not a description of it.
- Write the target outcome as a single number.
- Pick the smallest change that could plausibly move that number.
- Build it with a rollback path.
- Release to one team or a slice of traffic.
- Review in two weeks, then widen, revise, or delete.
Deleting is a legitimate result. It happens less often than it should.
What good practice looks like here
- One owner, named, with time actually cleared.
- Limits enforced in code so a bad day cannot become a bad invoice.
- A short written record of why the choice was made.
- Alerts that a human reads, not a dashboard nobody opens.
- A scheduled review, because every decision here has a shelf life.
The trade-offs nobody puts in the proposal
Every option here buys you something and charges you elsewhere. Faster now often means a rewrite later, and that can still be the right call.
What matters is naming the bill in advance so it is a decision rather than a surprise.
Common misconceptions
“We need the best available option.” You need the one your team can operate at 2am. Rarely the same thing.
“We’ll do it properly later.” Sometimes true. Put a date on later or it never arrives.
“It’s a one-off.” Anything a customer touches becomes a product, support included.
Frequently asked questions
How much should we budget?
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
How long does definition of done take to get right?
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
Is it cheaper to buy a tool instead?
Often yes for the first version. Build when the workflow is a genuine differentiator or no tool fits the data you already hold.
How do we know whether it worked?
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
When is the right time to revisit the decision?
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
Conclusion
The useful move on definition of done is almost always the smaller one. Ship a narrow slice a real user can touch this month, measure it, then decide what earns the next four weeks.
Everything gets easier once something is live.
Related reading and next steps
- AI automations — how we run this kind of work.
- SaaS and web apps — where this often connects.
- More writing from the team.
Want a second opinion on definition of done for your setup? Book a 30-minute call. If it is not worth building, we will say so.
FAQ
Frequently asked questions
How much should we budget?+
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
How long does definition of done take to get right?+
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
Is it cheaper to buy a tool instead?+
Often yes for the first version. Build when the workflow is a genuine differentiator or no tool fits the data you already hold.
How do we know whether it worked?+
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
When is the right time to revisit the decision?+
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
Building something similar?
Let's talk in 30 minutes.