WORKFLOW

Notes to Actions

Convert brain dumps, meeting notes, or voice transcripts into a clean execution list.

What this solves

This workflow turns unstructured notes into an action backlog with priorities, owners, and dates so nothing important gets buried.

When to use / when not to use

  • Use after meetings, brainstorms, or rapid note taking.
  • Do not use when requirements are incomplete and decisions are still open.

Inputs needed

  • Raw notes or transcript text
  • Team members or owner names
  • Known deadlines and constraints

Copy-ready prompt block

Turn the notes below into an action plan.

Output rules:
- Group by Project, Operations, and Follow-ups
- Each task must include Owner, Due Date, Priority (P1/P2/P3), and Next Step
- Mark unclear items as "Needs Clarification"
- Keep task titles under 12 words

Notes:
[paste notes]

Execution steps

  1. Paste notes exactly as captured without cleaning first.
  2. Scan output and assign missing owners immediately.
  3. Confirm due dates are real calendar dates, not “ASAP.”
  4. Move the final task list into your project tool.

Expected output format

Project
- Task | Owner | Due | Priority | Next Step

Operations
- Task | Owner | Due | Priority | Next Step

Follow-ups
- Task | Owner | Due | Priority | Next Step

Needs Clarification
- Item | Question to resolve

Concrete example

Raw note: “Need claim workflow fix, onboarding doc rewrite, ask Jen about April launch date.” Output task: “Claim workflow bug triage | Mark | 2026-03-03 | P1 | Reproduce issue and log root cause.”

Common mistakes

  • Keeping tasks too broad to start
  • Missing owners on cross-team items
  • Skipping clarification list for ambiguous notes

Quick quality check

  • Every task has one owner
  • Every task has a due date
  • No task says “misc” or “general”
  • Top three P1 tasks are visible first

Next step

Get the free weekly prompt digest and keep your action system tight.

Join the Newsletter