# Turn meeting notes into actions without losing what was decided

Manual worksheet; invented situation, no automatic product import.

## Owned work

- 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.

## Workflow questions

### 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.

## Job to be done

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.

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.

### Recognizable 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.

### Shortcut that fails

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 — invented worked answer

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.

### Conditional next moves

- If A choice was explicitly agreed: Record it as decision context. The decision should remain attributable.
- If Work follows from the choice: Prepare owned output-based actions. An action is more than repeating the agreement.
- If A suggestion was not accepted: Keep it labelled as a proposal. Meeting mention does not authorize implementation.

### TeamBoost route — confirm account availability

- Preserve the agreed choice: Keep the smaller-pilot decision and its bounds with relevant work. Your check: A person confirms which discussion was actually agreed.
- Prepare owned actions: Create or adapt preparation and review tasks only within your authorized workflow. Your check: Each action needs its own output and agreed owner.
- Report the follow-up result: Describe the pilot finding and resulting choice separately from completed preparation. Your check: Do not call an unreviewed proposal an approved redesign.

### Success check

The team can identify the agreement, two executable follow-ups and the idea that has not been approved.

### Editable draft facts

- Agreed decision [decision]: Run the smaller pilot within the agreed audience — Separate agreement from proposal.
- Preparation action and owner [prepare]: Pilot owner prepares the approved example and participation plan — Use an executable output.
- Receiving action and owner [review]: Receiving lead reviews the finding and decides continuation — Keep the next decision owned.
- Ideas not committed [held]: Broad redesign remains a proposal — Preserve the scope boundary.
- What may reopen the decision [reopen]: Pilot evidence shows the agreed audience cannot use the example — Name a justified return condition.

### Draft pattern — replace every placeholder

```text
Meeting follow-up
Agreed decision: {decision}.
Preparation: {prepare}.
Receiving review: {review}.
Uncommitted ideas: {held}.
Revisit only when: {reopen}.
Confirm owners before turning the actions into live work.
```

### Limits

No meeting integration, automatic task creation or native decision log is verified here. The editor prepares text for review.

Local text preparation only; no workspace read, task creation, send or approval. Source interfaces do not establish account availability or live feature completion.