The Rise of the Done List in DevOps and IT Delivery

The Rise of the Done List in DevOps and IT Delivery

Walk into almost any engineering team’s planning meeting and the talk is of what remains: backlog size, upcoming milestones, risks on the horizon. Spend a little longer and you notice something else. The teams that feel calm, the ones that seem to carry their workload lightly, tend to have a habit that gets far less attention. They keep a visible record of what has been finished. Here is where that habit sits in DevOps and IT delivery at the moment, what is driving it, and what a healthy version looks like.

A small story from an operations room

Picture an infrastructure team supporting a mid-sized company. Every Friday afternoon, the team lead asks the same question: what did we finish this week? For a long time the answers came out as shrugs. Tickets were closed, but nobody could describe the week in a sentence. Upgrades blurred into patches, patches blurred into firefighting.

One engineer started a shared document titled simply “Done”. Each line carried a date and a plain statement: certificates renewed on the internal services, old build agents retired, backup restore tested on the reporting database. Within a month, the document was being read by people outside the team. A manager used it to answer a budget question. A new hire used it to learn what the environment had been through. And the team itself noticed that its weeks no longer felt shapeless.

Nobody had planned for the document to matter. It mattered because it answered a question that backlogs never answer: what has actually changed?

Why completion records are gaining ground

Several pressures push teams toward recording finished work. The first is the sheer pace of change. When environments are altered many times a week, memory cannot keep up, and an accurate history becomes operationally useful, not just pleasant. The second is the spread of remote and hybrid collaboration. Colleagues no longer overhear each other finishing things, so progress has to be written down to be shared. The third is the growing expectation that operational work be explainable to non-technical people, who understand “finished” far better than “in flight”.

A softer cultural change helps too. Plenty of teams have grown tired of dashboards that show only trouble. A record of completed work offsets that tilt, keeping morale steadier without any slogans.

Common forms the habit takes

The done list appears under many names. Some teams keep a running changelog for infrastructure. Others write short weekly summaries. A few maintain an operations journal where each completed task has a line. A growing number attach a “finished” lane to their task boards and archive it weekly instead of deleting entries. The names differ, but the core is identical: dated, specific, closed items in one place.

Organisations moving away from paper-based processes often adopt the habit during the transition, since the move itself produces many small finished steps. If your team is in that position, the practical guide to leaving paper behind for digital platforms pairs naturally with a running completion log.

What good looks like

Healthy completion records share a few traits. Entries are written by whoever did the work, within a day. Each line names a concrete outcome rather than an activity. The record is searchable. It is readable by people outside the team. And it is short enough that nobody resents adding to it.

  • Specific. “Retired two legacy build agents” instead of “cleaned up CI”.
  • Timely. Written when the work finishes, not reconstructed on Friday.
  • Accepted. Logged only after the work is checked.
  • Visible. Stored where stakeholders can read it without asking.

How teams introduce it without friction

The teams that succeed rarely announce a new process. They start with one volunteer, one shared page and a single rule: add a line when something is finished. After a few weeks they ask the others whether the page is useful. If it is, they keep it. If not, they adjust the format. Because the cost is tiny, nobody feels forced, and adoption follows the value rather than an instruction. Managers who try to mandate it through a template with many fields usually find the entries thin and resented.

Where it connects to automation

An interesting recent development is that some of the log writes itself. Deployment tools, ticket systems and monitoring platforms can emit entries when a change completes. That is useful, but it comes with a warning: automated entries tell you what happened, not whether it mattered. The sturdiest setups mix both, with machine-generated lines for routine events and short human notes for decisions. For more on removing repetitive effort from daily work, see the discussion of how digital automation trims time and reduces slips.

Honest limits

It would be dishonest to claim the practice solves everything. A done list does not prioritise your backlog, repair a strained team or replace incident reviews. It can also be gamed, as any record can, if people are rewarded for volume. The remedy is to value outcomes rather than counts and to keep the list as a memory aid, not a scoreboard.

Another limit is that it only captures finished work. Unplanned interruptions, support requests and quiet maintenance can be underrepresented unless people make a point of writing them down. Teams that care about this add a short “unplanned” tag so invisible work becomes visible.

Beyond the data centre

The habit travels well. A consultant preparing a client visit, for example, can record completed preparations, such as agendas sent and access confirmed, and treat travel arrangements the same way. When someone is sorting local transport for a trip and reads about MotoShare, an Indonesian-language website that describes renting motorbikes and cars with local partners, the useful output is a line saying the transport question is settled. Records of settled matters stop the same question being reopened by three different colleagues.

Where this is heading

Expect completion records to become a normal part of delivery reporting. Stakeholders increasingly ask what was achieved rather than only what is planned, and teams that can answer in one page tend to earn trust faster. The practical advice for any team still without one is modest: start a shared page called Done, ask everyone to add a line when they finish something, and read it aloud at the end of each week. The story told by that page is usually more encouraging, and more accurate, than the one people carry in their heads.