When it’s unclear what “done” means, work comes back
When it’s unclear what “done” means, work comes back
A colleague gives you a task: “Prepare a proposal as soon as possible.” You put together a short price overview, but they were expecting delivery dates, warranties, and two solution options as well. The document has to be redone. The time wasn’t lost because you worked too slowly. It was lost because expectations weren’t clear. A lot of unnecessary rework starts before the task even begins, when no one checks what a usable result should look like.
Before starting, try to clarify four things: the deliverable, the recipient, the acceptance criteria, and the deadline. For example: “I’ll prepare a proposal with two pricing options, an estimated delivery date, and a list of exceptions. I’ll send a draft for review today.” That’s clear. If there’s a question, the other person knows exactly what they’re being asked. For an important task, spending a few minutes clarifying expectations is often a sensible investment.
Sometimes requirements change while work is underway. In that case, make the impact clear: “If we add another option, we’ll need to adjust the deadline or the scope of the other sections.” This isn’t about rejecting change; it’s about making sure it doesn’t become an invisible burden. Also check who has the authority to approve the deliverable. If that’s unclear, work may bounce between several people.
Think of a task that recently had to be redone and ask what hadn’t been agreed in advance. Next time, try including the sentence “It will be done when…” in the instructions. This can save time and prevent unnecessary conflict about who was supposed to understand what.