Week 28 Day 2: 'Done' Is Not a Feeling -- It Is a Checklist

Feelings are subjective. Checklists are objective. When 'done' is a feeling, the standard shifts based on mood, deadline pressure, who is reviewing, and how tired everyone is. Friday afternoon done is different from Monday morning done. Stressed-about-the-deadline done is different from relaxed-timeline done. But the customer does not care about your mood or your deadline pressure -- they care about whether the product works.

Here is what a Definition of Done checklist looks like for a software feature. Code: all acceptance criteria met, code reviewed and approved by at least one peer, no critical or high-severity linting errors. Testing: unit tests cover the primary paths and the two most likely failure modes, integration tests pass, manual testing completed against the acceptance criteria. Documentation: API changes documented, user-facing changes reflected in help text or release notes, internal runbook updated if operational procedures changed. Deployment: feature deployed to staging environment, smoke tests pass, monitoring alerts configured for new endpoints or services, rollback procedure documented. Stakeholder: product manager has reviewed the deployed feature and confirmed it meets the acceptance criteria. Notice what this checklist does. It makes completion binary. Each item is either done or not done. There is no room for 'it feels done' or 'it is mostly done.' The checklist also distributes ownership: the developer owns code and testing items, the tech writer owns documentation items, the operations team owns deployment items, and the product manager owns stakeholder items. No single person decides when the whole thing is done. The checklist decides. The most powerful aspect of a Definition of Done checklist is what it does to arguments. When a reviewer says 'this is not done,' they do not need to justify their opinion. They point to the checklist item that is not checked. The conversation shifts from 'I think it should be more polished' to 'the integration tests are not passing.' The first is an argument. The second is a fact.

The checklist approach to Definitions of Done draws on Gawande's (2009) research on the power of checklists in complex professional environments. His study with the World Health Organization found that implementing a 19-item surgical safety checklist reduced surgical complications by 36% and deaths by 47% across eight hospitals in eight countries, demonstrating that even highly trained professionals benefit from explicit completion criteria. The mechanism is what Gawande calls 'enforced minimum necessary steps' -- the checklist ensures that no step is skipped due to time pressure, fatigue, or assumption. The binary nature of checklist items addresses what psychologists call the 'completion criterion problem' (Koriat, Lichtenstein, and Fischhoff, 1980) -- the difficulty humans have in judging their own degree of completion on complex tasks. Research demonstrates that self-assessed completion is systematically biased toward overestimation, with individuals reporting tasks as 'done' when they are approximately 85% complete by objective measures. The distributed ownership model reflects research by Hackman (2002) on 'enabling conditions for team effectiveness,' which identifies 'clear norms of conduct' as one of three essential conditions (alongside compelling direction and enabling structure). The Definition of Done functions as a behavioral norm that reduces coordination costs by making expectations explicit and shared.