A schedule is done when checked, saved, and sent to the superintendent. That move responds to a common problem: activity can finish while expected evidence is missing. The purpose of task definition of done is to remove that ambiguity before it creates delay or reconstruction.
Take five minutes with live work. Begin by name the artifact; continue with identify acceptance and record a quality check; finish when you stay proportional. The result should change a task, calendar, decision, or handoff that someone will actually use.
See the operating problem
Activity can finish while expected evidence is missing. With task definition of done, the control point is the smallest decision that changes what can happen next. Identify the outcome, owner, timing, input, or acceptance condition that is implied rather than visible.
Start from consequences. Ask what delay, rework, or confusion the missing decision could create, then record only the detail needed to prevent it. The method should reduce reconstruction for your future self or a colleague.
Build the first useful version
Name the artifact, then identify acceptance. Apply both actions to the actual item and place the result in its working location. If you need a long separate explanation, the task or rule is still too abstract to guide execution.
A schedule is done when checked, saved, and sent to the superintendent. This names something observable rather than repeating the topic. Adapt its detail: personal work may stay brief, while shared or consequential work needs enough context for another person to proceed safely.
Make the state trustworthy
Record a quality check, and then stay proportional. When another person participates, confirm the expected outcome and review point instead of assuming a changed assignee, status, or sent message completes coordination.
Keep sources, decisions, and exceptions close to the task. Add a field only when it changes priority, access, ownership, acceptance, or the response to a real risk.
Adjust from evidence
At review, compare the state before and after using task definition of done. Check whether the next action is clearer, the responsible person can be named, and evidence can be found without reopening an entire conversation.
Change one part when those checks fail. Keep the useful example, remove steps people do not maintain, and update live state when circumstances change. A small current practice is more trustworthy than a detailed routine built for old conditions. For task definition of done, preserve the specific constraint and example instead of replacing them with a generic productivity rule. The method should still make sense when read beside this live case: A schedule is done when checked, saved, and sent to the superintendent.
Five-minute practice: Define “Done” Before You Start a Task
- Choose one live case where activity can finish while expected evidence is missing.
- Name the artifact, then identify acceptance; save the result where work is reviewed.
- Record a quality check and ask one affected person whether the next move is unambiguous.
- Stay proportional; compare your result with this concrete model: A schedule is done when checked, saved, and sent to the superintendent.
Common questions
How much detail does task definition of done need?
Use enough to make action, ownership, timing, evidence, or acceptance clear. Begin with this level: A schedule is done when checked, saved, and sent to the superintendent. Add more only when another person or material risk requires it.
What if this task definition of done method does not fit the case?
Name the exception instead of forcing a misleading state. Recheck the constraint: Activity can finish while expected evidence is missing. Adjust one step, test comparable work, and keep it only when follow-through is easier to verify.
