{
  "example_kind": "invented job and manual worksheet",
  "slug": "meeting-action-versus-decision",
  "title": "Turn meeting notes into actions without losing what was decided",
  "layout": "coach",
  "story": "When meeting notes mix agreements and actions, I want the decision traceable and the next work owned so no one executes a slogan or reopens a settled choice.",
  "problem": "A meeting chooses a smaller pilot. The notes assign use the smaller pilot as one task, but omit who prepares it and who reviews the result.",
  "symptoms": [
    "An agreement is written as if it were an executable task.",
    "Follow-up actions have no owner or accepted output.",
    "Later contributors cannot tell whether scope was agreed or merely suggested."
  ],
  "failed_workaround": "Putting every meeting sentence on the board creates activity labels without preserving the decision or making the work actionable.",
  "before": "Task: use the smaller pilot. Everyone to follow up.",
  "after": "Decision: run the smaller pilot within the agreed audience and review boundary. Preparation action: the pilot owner assembles the approved example and participation plan. Review action: the receiving lead checks the pilot finding and chooses whether to continue. Unapproved redesign ideas remain proposals outside these actions.",
  "success_check": "The team can identify the agreement, two executable follow-ups and the idea that has not been approved.",
  "choices": [
    [
      "A choice was explicitly agreed",
      "Record it as decision context",
      "The decision should remain attributable."
    ],
    [
      "Work follows from the choice",
      "Prepare owned output-based actions",
      "An action is more than repeating the agreement."
    ],
    [
      "A suggestion was not accepted",
      "Keep it labelled as a proposal",
      "Meeting mention does not authorize implementation."
    ]
  ],
  "route": [
    {
      "label": "Preserve the agreed choice",
      "capability": "task-comment",
      "action": "Keep the smaller-pilot decision and its bounds with relevant work.",
      "human_check": "A person confirms which discussion was actually agreed."
    },
    {
      "label": "Prepare owned actions",
      "capability": "task-record",
      "action": "Create or adapt preparation and review tasks only within your authorized workflow.",
      "human_check": "Each action needs its own output and agreed owner."
    },
    {
      "label": "Report the follow-up result",
      "capability": "daily-report",
      "action": "Describe the pilot finding and resulting choice separately from completed preparation.",
      "human_check": "Do not call an unreviewed proposal an approved redesign."
    }
  ],
  "editor": {
    "heading": "Prepare a next-action brief",
    "fields": [
      {
        "key": "decision",
        "label": "Agreed decision",
        "example": "Run the smaller pilot within the agreed audience",
        "help": "Separate agreement from proposal."
      },
      {
        "key": "prepare",
        "label": "Preparation action and owner",
        "example": "Pilot owner prepares the approved example and participation plan",
        "help": "Use an executable output."
      },
      {
        "key": "review",
        "label": "Receiving action and owner",
        "example": "Receiving lead reviews the finding and decides continuation",
        "help": "Keep the next decision owned."
      },
      {
        "key": "held",
        "label": "Ideas not committed",
        "example": "Broad redesign remains a proposal",
        "help": "Preserve the scope boundary."
      },
      {
        "key": "reopen",
        "label": "What may reopen the decision",
        "example": "Pilot evidence shows the agreed audience cannot use the example",
        "help": "Name a justified return condition."
      }
    ],
    "template": "Meeting follow-up\nAgreed decision: {decision}.\nPreparation: {prepare}.\nReceiving review: {review}.\nUncommitted ideas: {held}.\nRevisit only when: {reopen}.\nConfirm owners before turning the actions into live work."
  },
  "limitations": "No meeting integration, automatic task creation or native decision log is verified here. The editor prepares text for review.",
  "tasks": [
    [
      "Separate agreement from suggestion",
      "Facilitator",
      "The smaller-pilot choice is agreed; redesign discussion remains a proposal."
    ],
    [
      "Name executable follow-up outputs",
      "Pilot owner",
      "Preparation specifies the example and participation plan rather than a slogan."
    ],
    [
      "Preserve the receiving decision",
      "Review lead",
      "The finding has a reviewer and a continue/change/stop decision."
    ]
  ],
  "faqs": [
    [
      "Should every decision become a task?",
      "The work needed to implement or revisit it may become tasks; preserve the decision itself as context."
    ],
    [
      "How do I avoid reopening the same choice?",
      "Record the agreed scope, decision owner and conditions that would legitimately reopen it."
    ],
    [
      "How can TeamBoost help with meeting follow-up?",
      "Its documented task creation/assignment and comments support tracking the resulting work and preserving the decision context. Review any proposed tasks before creating or assigning them."
    ]
  ]
}