{
  "title": "A clearer first useful moment.",
  "question": "Where does a new team lose confidence between choosing a workflow and putting its first result to work?",
  "demo": true,
  "notesHash": "fbc525df66bc6b4898244193ca190864dc8f370aa1ea3ec993789977e6d0a556",
  "limitations": "Seven fictional participants for a worked example. Frequency describes this small supplied study; it does not establish market prevalence or product uplift. Severity and effort are authored judgments.",
  "participants": {
    "p1": "Designer",
    "p2": "Designer",
    "p3": "Designer",
    "p4": "Operator",
    "p5": "Operator",
    "p6": "Developer",
    "p7": "Developer"
  },
  "observations": [
    {
      "id": "o1",
      "participant": "p1",
      "segment": "Designer",
      "kind": "reported",
      "text": "I reached the dashboard, but I could not tell what a finished first task looked like.",
      "location": "Fictional session 1, note 1"
    },
    {
      "id": "o2",
      "participant": "p1",
      "segment": "Designer",
      "kind": "observed",
      "text": "I opened three setup panels before I saw a useful result.",
      "location": "Fictional session 1, note 2"
    },
    {
      "id": "o3",
      "participant": "p2",
      "segment": "Designer",
      "kind": "reported",
      "text": "The preview helped me choose, then the install step felt like a different product.",
      "location": "Fictional session 2, note 1"
    },
    {
      "id": "o4",
      "participant": "p2",
      "segment": "Designer",
      "kind": "observed",
      "text": "I looked for a sample result before committing to a tool.",
      "location": "Fictional session 2, note 2"
    },
    {
      "id": "o5",
      "participant": "p3",
      "segment": "Designer",
      "kind": "reported",
      "text": "I wanted to keep one reliable workflow for my weekly reporting.",
      "location": "Fictional session 3, note 1"
    },
    {
      "id": "o6",
      "participant": "p3",
      "segment": "Designer",
      "kind": "reported",
      "text": "I could not tell which version my teammate had installed.",
      "location": "Fictional session 3, note 2"
    },
    {
      "id": "o7",
      "participant": "p4",
      "segment": "Operator",
      "kind": "reported",
      "text": "I need an owner and acceptance check before handing a workflow to the team.",
      "location": "Fictional session 4, note 1"
    },
    {
      "id": "o8",
      "participant": "p4",
      "segment": "Operator",
      "kind": "reported",
      "text": "A gallery screenshot alone does not tell me what files I will receive.",
      "location": "Fictional session 4, note 2"
    },
    {
      "id": "o9",
      "participant": "p5",
      "segment": "Operator",
      "kind": "reported",
      "text": "Our team already knew the setup. The short onboarding was enough for us.",
      "location": "Fictional session 5, note 1"
    },
    {
      "id": "o10",
      "participant": "p5",
      "segment": "Operator",
      "kind": "reported",
      "text": "A clear download list helped me approve the package.",
      "location": "Fictional session 5, note 2"
    },
    {
      "id": "o11",
      "participant": "p6",
      "segment": "Developer",
      "kind": "reported",
      "text": "I needed an exact install path and a small command I could verify.",
      "location": "Fictional session 6, note 1"
    },
    {
      "id": "o12",
      "participant": "p6",
      "segment": "Developer",
      "kind": "observed",
      "text": "The requirements were easy to find once I expanded the details.",
      "location": "Fictional session 6, note 2"
    },
    {
      "id": "o13",
      "participant": "p7",
      "segment": "Developer",
      "kind": "reported",
      "text": "The output looked right, but I needed the underlying editable file.",
      "location": "Fictional session 7, note 1"
    },
    {
      "id": "o14",
      "participant": "p7",
      "segment": "Developer",
      "kind": "reported",
      "text": "Version notes matter when I rebuild an older deliverable.",
      "location": "Fictional session 7, note 2"
    }
  ],
  "themes": [
    {
      "id": "first-win",
      "title": "Show the first win before the setup.",
      "interpretation": "Several participants want a concrete finished result before navigating installation. A useful preview may bridge the choice-to-use gap.",
      "supportIds": [
        "o1",
        "o2",
        "o3",
        "o4",
        "o11"
      ],
      "contradictIds": [
        "o9"
      ],
      "supportParticipants": [
        "p1",
        "p2",
        "p6"
      ],
      "contradictParticipants": [
        "p5"
      ],
      "severity": 5,
      "effort": 2,
      "priorityScore": 1.0714,
      "action": "Add one complete sample, its download list and a three-step first run beside the primary install action.",
      "owner": "Product & design",
      "acceptance": "In the next usability round, a participant can identify the expected files and locate the first run without opening unrelated setup panels."
    },
    {
      "id": "editable-handoff",
      "title": "The deliverable includes the source.",
      "interpretation": "An attractive preview is useful, while an editable artifact and acceptance checklist support actual team handoff.",
      "supportIds": [
        "o7",
        "o8",
        "o10",
        "o13"
      ],
      "contradictIds": [],
      "supportParticipants": [
        "p4",
        "p5",
        "p7"
      ],
      "contradictParticipants": [],
      "severity": 4,
      "effort": 2,
      "priorityScore": 0.8571,
      "action": "Expose editable file formats, acceptance checks and the delivery owner in the result preview.",
      "owner": "Content operations",
      "acceptance": "A reviewer can distinguish rendered output, editable source and evidence files before download."
    },
    {
      "id": "progressive-setup",
      "title": "Let experienced teams move quickly.",
      "interpretation": "The shorter path already works for one experienced participant. Preserve a compact install path while offering deeper guidance on demand.",
      "supportIds": [
        "o9",
        "o12"
      ],
      "contradictIds": [
        "o2"
      ],
      "supportParticipants": [
        "p5",
        "p6"
      ],
      "contradictParticipants": [
        "p1"
      ],
      "severity": 3,
      "effort": 2,
      "priorityScore": 0.4286,
      "action": "Keep a concise default first run and put extra setup guidance behind a clearly named disclosure.",
      "owner": "Design systems",
      "acceptance": "First-time and experienced participants can choose the appropriate depth of guidance."
    },
    {
      "id": "version-trust",
      "title": "Keep the team on a known version.",
      "interpretation": "Version visibility is relevant to repeatable team use, though this study has only two supporting participants.",
      "supportIds": [
        "o5",
        "o6",
        "o14"
      ],
      "contradictIds": [],
      "supportParticipants": [
        "p3",
        "p7"
      ],
      "contradictParticipants": [],
      "severity": 4,
      "effort": 3,
      "priorityScore": 0.381,
      "action": "Show the active version, update notes and preserved older downloads in the account library.",
      "owner": "Engineering",
      "acceptance": "A teammate can identify the installed version and explain which source produced an older deliverable."
    }
  ],
  "nextQuestions": [
    "What did you expect the first completed result to contain?",
    "Show the point where you switched from browsing to trying the workflow.",
    "How would you check that a teammate can reproduce the result?",
    "What would make a shorter setup sufficient for your team?"
  ],
  "priorityFormula": "unique supporting participants / all participants × authored severity / authored effort"
}