Clear outcomes over vague tasks: Define the result: 'Next shift must see open cases, owners and due actions.'; Agree on scope, authority, inputs and timing with the owner.; Check early work against the agreed outcome and boundaries.
Image: Business Productivity Guide

Prioritisation

Part of Productivity for managers

Giving a clear outcome instead of a vague task

Turn a vague assignment into a usable result with clear authority, inputs, boundaries and an early checkpoint.

Desk Workflow · · 3 min read

Tell the person what result someone needs to use, then agree on the boundaries within which they can produce it. Name the recipient, intended use, owner, relevant constraints and first review point. Leave room for the owner's judgement about how to do the work.

Turn the instruction into a result

Before saying 'look into the service handover', ask what should be possible when the work is done. An illustrative assignment might be: 'Propose a handover that lets the next shift see each open case, its current owner and the action due.' The example describes a possible result, not a standard for every service team.

Say whether the person should recommend a change, produce a version for review or implement an approved change. Those require different authority. Explain any required format or check; otherwise let the owner choose a suitable method.

Turning a Vague Task into a Clear Outcome

  1. Define the Desired ResultE.g., 'Propose a handover that lets the next shift see each open case, its current owner and the action due.'
  2. Specify the Deliverable TypeRecommend change, draft for review, or implement approved change?
  3. Confirm Authority & ConstraintsWhat can be changed without approval? What needs sign-off?
  4. Agree on Inputs & TimingAvailable records, access, people; when is early feedback needed? When is final delivery due?

Agree on the working boundaries

Settle the practical points together:

  1. Scope:Which service, period or cases are included?
  2. Authority:What may the owner change, and which choice needs approval?
  3. Inputs:Which current records, people and access are available?
  4. Timing:When would an early look help, and when is the result needed?

Invite the owner to explain how they understand the assignment and to raise conflicting commitments. Understanding the result is not enough if they lack the time, information or authority to deliver it.

When expectations, instructions or information are unclear, discuss what is missing and review how the work is assigned.

Key Elements to Agree Before Delegating

  • Scope: Which service, period or cases are included?Yes
  • Authority: What changes require approval?Yes
  • Inputs: Access to records, systems, and team members?Yes
  • Timing: When should an early check occur? When is final delivery due?Yes

Check direction before completion

Choose an early item that can expose a wrong assumption: an outline, sample case or proposed approach. Ask whether it serves the named recipient and stays within the agreed boundary.

Explain any change needed and why. If the goal or constraint changes, update the agreement and reconsider the timing.

At handover, check whether the result serves its intended use. Identify any gap and who can resolve it. Treat a new request beyond the agreed result as a new scope choice rather than silently adding it to the assignment.

Early Direction Check Before Completion

  1. Present an Outline or SampleShow a proposed approach, sample case, or structure.
  2. Confirm Alignment with Recipient & Use CaseDoes it serve the intended user? Is it within agreed boundaries?
  3. Provide Feedback with ReasoningExplain what needs adjustment and why.
  4. Update Agreement if Goals or Constraints ChangeRe-negotiate scope, timing, or authority if needed.
  5. Final Review at HandoverVerify the result meets intended use; address gaps promptly.

More from Prioritisation