When 'Done' Isn't Really Done
Teams celebrate completing tasks only to discover stakeholders expected something entirely different, leading to wasted effort, re-work, and damaged trust.
If you are in a meeting right now and realize your team is arguing because everyone has a different definition of what 'done' means, follow these immediate steps:
Action
Hit the Pause Button Immediately Stop the current debate before frustration escalates. Interrupt the conversation calmly and firmly to pivot from arguing to defining standards. Say out loud: *"Hold on a second, everyone. I want to pause us right here. It sounds like we're debating whether this task is finished, but the real issue is that we don't have a shared agreement on what 'done' actually means for this piece of work."*
Action
Neutralize Blame and Name the Gap Reframe the issue away from individual performance and onto process clarity so people don't get defensive. Say out loud: *"This isn't about anyone dropping the ball or doing bad work. Everyone in this room delivered what they thought was expected. The breakdown is in our shared checklist. Let's build that checklist together right now so we're all looking at the exact same target."*
Action
Run a Live 'Done' Audit on Screen Open a shared visual document or digital whiteboard. Draw two columns: 'Completed' and 'Remaining to be Production-Ready'. Say out loud: *"Let's list what is currently complete versus what is still required before we can safely ship or hand this off. I'll scribe on screen as you call them out."*
Action
Negotiate an Immediate Bridge Definition Go through the remaining items and establish what MUST be finished today versus what can be deferred or split into a follow-up task. Ask the group: *"What are the non-negotiable criteria for us to consider this specific milestone complete today? What can safely move to Phase 2 without compromising quality or security?"*
Action
Confirm Explicit Agreement Across Roles Go around the room and get verbal confirmation from each discipline (e.g., product, engineering, QA, design). Say out loud: *"Before we move on, let's check in with everyone. Sarah, from a product standpoint, if we complete X and Y, are you satisfied calling this done? Dave, from QA, does this meet your release criteria?"*
- Tasks marked as 'complete' in tracking tools are reopened or rejected within 48 hours.
- Hearing phrases like 'I thought you were taking care of testing' or 'I didn't know you needed documentation.'
- Last-minute panics right before a release because essential quality checks were skipped.
- Handoffs between departments stall because the receiving team claims the deliverable is incomplete.
- Arguments during meetings over whether code-complete equals production-ready.
- Stakeholders expressing disappointment during reviews despite team members feeling they met all requirements.
- Team members feeling demotivated when their 'finished' work requires major revisions.
- Absence of an explicit, written Definition of Done shared across cross-functional roles.
- Implicit assumptions where individuals assume everyone shares their personal mental model of quality.
- High-pressure deadlines that incentivize team members to declare victory prematurely.
- Siloed communication channels that prevent early alignment on acceptance criteria.
- Vague requirement descriptions or user stories lacking explicit non-functional requirements.
- Differing professional standards and priorities between disciplines (e.g., engineering vs. product vs. design).
- Fear of reporting delays, prompting workers to hand over partial work to avoid negative visibility.