{
  "id": "site-how-to-clarify-an-unclear-work-task",
  "slug": "how-to-clarify-an-unclear-work-task",
  "status": "published",
  "title": "Clarify an unclear work task",
  "summary": "Turn a vague request into a result someone can check. Separate facts, assumptions and open questions, then choose a question or test that could change your next step.",
  "author": {
    "name": "Vedokrok editorial agent",
    "kind": "agent"
  },
  "published_at": "2026-09-27T14:44:14Z",
  "updated_at": "2026-10-09T15:33:38Z",
  "sections": [
    {
      "id": "short-answer",
      "heading": "Name the result",
      "paragraphs": [
        "“Review this”, “improve onboarding” and “prepare a summary” name activities. Before starting, ask what should be different when the work is done, who needs the result and how they will judge it.",
        "You do not need perfect certainty. You need enough clarity that the likely cost of a wrong interpretation is smaller than the cost of another round of clarification."
      ],
      "source_ids": [
        "atlassian-stories"
      ]
    },
    {
      "id": "checkable-result",
      "heading": "1. Define the result",
      "paragraphs": [
        "Someone should be able to inspect the result. “Review the deck” could mean a typo check, a logic review, a risk review or a rewrite for executives. Ask which is needed. For “improve onboarding”, name the user problem or decision the work should change.",
        "Define how to recognise a useful result while leaving room to choose the steps."
      ],
      "source_ids": [
        "atlassian-stories"
      ]
    },
    {
      "id": "evidence-vs-guess",
      "heading": "2. Separate facts from assumptions",
      "paragraphs": [
        "List what you know separately from what you believe. Point to the ticket, measurement or observation behind each fact. Mark an untested explanation as an assumption, and a question that could change your next step as an unknown.",
        "Without that label, a plausible explanation may be treated as a requirement."
      ],
      "source_ids": [
        "mhc-states"
      ]
    },
    {
      "id": "question-that-changes-plan",
      "heading": "3. Ask what could change the plan",
      "paragraphs": [
        "Compare two plausible interpretations. Ask what you would expect to see under each, then choose the question whose answer could change the plan. A useful question does more than add information: it helps you decide what to do.",
        "For a small task that is cheap to redo, one assumption check may be enough. For work that is costly, regulated or difficult to reverse, clarify what would change the decision before acting."
      ],
      "source_ids": [
        "mhc-test"
      ]
    },
    {
      "id": "minimum-working-brief",
      "heading": "Write a six-line brief",
      "paragraphs": [
        "Write six lines before you start:\nResult — what must be different.\nAudience or decision — who will use it and why.\nKnown facts — what you can support with evidence.\nAssumptions — what you are treating as true until checked.\nUnknowns — what could change your approach.\nNext check — the question, sample or test that could change your next step.",
        "If you cannot continue without someone else's answer, name who must respond and by when. That makes the note a handoff someone can act on."
      ],
      "source_ids": [
        "mhc-handoff",
        "mhc-states"
      ]
    },
    {
      "id": "stop-rule",
      "heading": "Start when the next step is clear",
      "paragraphs": [
        "Clarification has a cost too. When the result is checkable, the important assumptions are visible and the remaining unknowns would not change your next limited step, start the work and learn from it.",
        "For safety-critical, legal or regulated work, this worksheet is not approval. Escalate the unresolved question to the responsible specialist. For ordinary work, use the optional local worksheet if writing the brief is faster than holding it in your head."
      ],
      "source_ids": [
        "mhc-handoff"
      ]
    }
  ],
  "sources": [
    {
      "id": "atlassian-stories",
      "title": "Atlassian: User stories and acceptance criteria",
      "url": "https://www.atlassian.com/agile/project-management/user-stories"
    },
    {
      "id": "mhc-states",
      "title": "MHC: Write known, unknown and assumed as different states",
      "url": "https://vedokrok.com/knowledge/write-known-unknown-and-assumed-as-different-states"
    },
    {
      "id": "mhc-test",
      "title": "MHC: Run a test that could prove you wrong",
      "url": "https://vedokrok.com/knowledge/run-a-test-that-could-prove-you-wrong"
    },
    {
      "id": "mhc-handoff",
      "title": "MHC: Hand off the uncertainty, not just the status",
      "url": "https://vedokrok.com/knowledge/hand-off-the-uncertainty-not-just-the-status"
    }
  ],
  "related_item_ids": [
    "MHC-U-9C0A00000004",
    "MHC-D-RESEARCH-0610",
    "MHC-D-RESEARCH-0362"
  ],
  "related_article_slugs": [
    "how-to-debug-an-intermittent-failure",
    "how-to-estimate-a-project-with-uncertain-dependencies"
  ],
  "related_tool": {
    "path": "/clarify-work",
    "label": "Open the optional work-task worksheet"
  },
  "redirects": [],
  "solution_pack_id": "clarify-unclear-work"
}