Decision Writing Guide

The Formula

Every good decision follows the same pattern:

Verb + Subject + Context

That's it. Start with what you're doing, name the specific thing, add the constraint or timeline.

Test it: Say "I/We need to..." before your decision title. If it sounds natural, you nailed it.

✓ Choose vendor for billing migration (within $20k, decide by Friday)

✗ Billing vendor

The first one tells you exactly what needs to happen. The second one is just a topic.

Start with a Strong Verb

The verb sets the intent. Skip generic words like "Decide" or "Discuss" — they're too soft. Use verbs that demand action:

Choose — Selecting between clear options or vendors Approve — Giving formal go-ahead or sign-off Confirm — Verifying facts, timing, or ownership Assign — Defining ownership or responsibility Set — Establishing timelines, goals, or guardrails Align on — Achieving agreement among stakeholders Authorize — Granting permission or budget

Add Quick Context

Use the Context field to clarify why, what options exist, and any constraints. Keep it to 1–3 short lines.

Example: System stable, marketing launch fixed for Friday 2pm ET. Resources are all set and communication plan is ready.

This isn't a place to rehash the whole discussion — just enough so someone reading it cold understands the stakes.

The Clarity Checklist

Before you submit, check:

• Starts with a verb

• Names a specific subject

• Includes time, scope, or constraint

• Passes the "We need to..." test

• One clear decision per line

If you're bundling three decisions into one, split them. Each decision deserves its own owner and deadline.

Examples in Action

• Confirm QA owner before next on-call rotation

• Choose venue for Q4 offsite (A vs B)

• Set discount guardrails for Q3 pipeline (max 15%)

• Approve onboarding flow v3 for public beta

• Align on top 3 roadmap priorities for H2

Go Deeper

For the complete framework, verb reference table, and more examples: Decision Title Best Practices →