How to define the expected outcome

When handing over work, explain what the finished result looks like, who needs it and when. A shared definition of done helps someone work independently and avoids unnecessary revisions.

What to do

A short brief can answer five questions:

  1. Why? One sentence on purpose: who the result is for and what it should change.
  2. What does "done" look like? Format, scope, level of detail. An example or sample often beats a description.
  3. By when? The real deadline and, if there is one, a midpoint.
  4. What are the limits? Budget, what not to do, which decisions they make alone and which with you.
  5. What's already known? Contacts, past attempts, files – so they don't start from zero.

Finish by asking them to say back, in their own words, how they understood the task. It's faster than fixing the result later.

Example

Weak: "Put something together for the new volunteers' meeting."

Better: "On Saturday 12 new volunteers are coming, most of them for the first time. We need a one-page handout: who we are, who to contact, three safety rules for the warehouse. Use last year's letter as a base, but without the old phone numbers. Printing budget: 50 hryvnias total. Show me a draft on Thursday – I'll only check the safety rules."

In Plynno

Name the task after its result and put the completion criteria in its comment. Send the agreement separately when handing work to someone else: your Plynno comment stays private.

Try this now

Take a task you plan to hand over and write one "why" sentence and one "what counts as done" sentence for it.

Sources