The Moving Target: 'Done'
Teams struggle when they have different understandings of what it means for a task or project to be 'done,' leading to rework, delays, and frustration.
If you realize *during* a meeting that your team is misaligned on what 'done' means, follow these steps:
Acknowledge the Disconnect
Say something like, "Okay, it sounds like we have slightly different ideas about what 'done' looks like for this task/feature. Let's pause for a moment to clarify."
Redirect the Conversation
Immediately shift the focus away from blame and toward collaborative problem-solving. Say, "Instead of focusing on who's right or wrong, let's make sure we're all on the same page moving forward."
Elicit Perspectives
Ask each team member to briefly describe their understanding of 'done' in this context. Use open-ended questions like: "When you say this task is 'done,' what does that include for you?" or "What criteria need to be met for you to consider this complete?" Actively listen without interrupting.
Document the Differences
As each person speaks, jot down the key points of their definition of 'done' on a whiteboard or shared document. This makes the discrepancies visible to everyone.
Facilitate a Discussion
Guide the team to a consensus on a shared definition of 'done' that incorporates everyone's essential requirements. Ask clarifying questions like, "So, if we combine these perspectives, it sounds like 'done' means [summarize]. Is that accurate?" "Are there any critical elements missing from this definition?" "What steps can we take to ensure we're all aligned on this moving forward?"
Create Immediate Action Items
Based on the discussion, assign specific, actionable tasks to address any gaps or misunderstandings. For example: "Sarah, could you update the documentation to reflect this new definition of 'done'?" or "John, can you create a checklist based on this definition that we can use for future tasks?"
Document and Distribute
Formally document the agreed-upon 'Definition of Done' and share it with the entire team. Make it easily accessible (e.g., in your project management tool or team wiki).
Integrate into Workflow
Incorporate the DoD into your team's workflow. Use it as a checklist during code reviews, testing, and project sign-offs.
Regular Review and Refinement
Schedule regular reviews of the DoD (e.g., every sprint or project milestone) to ensure it remains relevant and effective. As your team and projects evolve, your definition of 'done' may need to adapt.
Lead by Example
As a manager, consistently refer to the DoD in your own communications and decision-making. This reinforces its importance and encourages team members to do the same.
Provide Training
If necessary, provide training on the importance of a shared understanding of 'done' and how to effectively use the DoD. This can be a simple workshop or a series of informal discussions.
Address Underlying Issues
Explore the root causes of the misalignment. Are there communication breakdowns, unclear requirements, or conflicting priorities that need to be addressed? Resolve these underlying issues to prevent future misunderstandings.
- Tasks are frequently returned for revisions after being marked as complete.
- Team members use phrases like, "I thought that was good enough..."
- There are disagreements about whether a feature is ready for release.
- Project timelines slip due to unexpected additional work.
- Stakeholders express dissatisfaction with delivered results.
- Team members spend time clarifying requirements late in the process.
- There's visible frustration and blame when tasks aren't accepted.
- Documentation is incomplete or inconsistent with the final product.
- Lack of a shared, documented 'Definition of Done' (DoD).
- Assumptions are made about quality standards and expectations.
- Insufficient communication between stakeholders and the development team.
- Unclear or ambiguous acceptance criteria for tasks.
- Failure to regularly review and update the DoD.
- Individual team members prioritize different aspects of 'done' (e.g., functionality vs. documentation).
- Hierarchical power dynamics prevent junior members from questioning assumptions of senior members.
- Pressure to deliver quickly leads to cutting corners and incomplete work.