The starting point
A task is finished. Doing it, you also found a workaround, a constraint, or a question that deserves a follow-up.
The update says only: “Done.”
The move
Ship what is still useful and report what doing the work taught you. If the discovery calls the requested work into question, flag it before carrying on.
Why it works
The person doing the work meets details the original framing could not know. In support, a request comes back after every refund. In a community group, several participants read the same invitation differently. In engineering, the fix touches a part nobody planned for. Those observations can confirm the original choice, improve the next task, or justify a change. Writing them down while they are still precise saves you reconstructing them later. They complete the framing work; they do not prove the person who did it got it wrong.
You are asked to fix how a form displays on mobile. Checking, you find that some sign-ups also fail after submission. Those are two different facts. Fixing the display is still useful, but it does not let you conclude that signing up works.
You do not have to solve the wider problem alone. Separate the fact you observed, your reading of it, and the follow-up you propose. Someone starting out can report a precise case and ask for help interpreting it. An experienced person can offer several options.
If carrying on risks wasting significant effort or causing damage, ask for a ruling. Otherwise, finish the agreed remit and organise what comes next. A discovery does not automatically assign you a new project.
Try this
Before you close a task, add two lines to the update:
What I observed doing it: …
What that changes, or what would need checking: …
Propose a proportionate follow-up and name who can accept it. At the next review, check whether the observation changed a decision, confirmed the result, or revealed the need for an answer. On a first project, that feedback can go to the person you are helping.
From where you sit
- Product: ask what doing the work confirmed or revealed about the need.
- Design: report a new fact that confirms or unsettles the planned flow.
- Management: if reporting a find reads as refusing to do the task, you will stop getting finds.
- Customer relations: flag a repetition, with the cases and their context.
- Recruiting: ask for an observation that confirmed or changed the course of a project.
To discuss
Which recent observation changed how we handle a task, and how did we give it a follow-up?