“Work on the dashboard” describes an activity. “Provide a monthly view with a validated total” describes an outcome a team can discuss and verify.
1. Name the expected result
Specify who benefits from the deliverable and which decision it should support. A shared goal helps scope decisions when new requests arise.
2. Define observable criteria
Replace “easy to use” with situations to check: a user finds a metric, understands its definition and identifies its period. Criteria describe an outcome; technical tasks explain how to build it.
3. Organise a feedback loop
Show a small version to a stakeholder, collect feedback and record the next decision. Scrum, Kanban or a more predictive project approach provide different structures: the choice depends on context, not just a label.
Goal → a decision or a useful outcome
Deliverable → something observable
Criteria → how we will verify it
Feedback → what we learned
Next step → a documented decisionYour turn to build
Choose a simple project. Write its goal, a first deliverable, three acceptance criteria and the feedback you will request from its recipient.
Your discovery progress is saved on this device. You can clear it from My learning.