Hi there,

Teams lose time when decisions live in people’s memory instead of in a clear record. The cost is repeated debates, unclear ownership, and projects that stall when someone is out. A simple decision note turns talk into action by capturing the choice, the reason, and the next steps. Today, you will write the decision question, record options and trade-offs, assign owners and dates, and publish notes where people actually look.

The Playbook

Step 1: Write the decision question

How to do it: Start the note with one sentence that states the decision in plain words. Include the deadline and what happens if no decision is made.

Proof: Everyone agrees on what is being decided and by when. Side discussions shrink because the question is clear.

Step 2: Capture the context in three bullets

How to do it: Add only three bullets: goal, constraints, and the key data point. Link deeper documents instead of copying paragraphs.

Proof: Readers understand the situation in under a minute. New stakeholders catch up without a meeting.

Step 3: Present options with trade-offs

How to do it: List up to three options and write one trade-off line for each that covers scope, time, or risk. Mark your recommended option and explain why in one sentence.

Proof: Decisions land faster because the choice is framed. People debate trade-offs, not opinions.

Step 4: Record the decision and rationale

How to do it: Write the final choice in one line and add a short rationale that names the winning criteria. Note what you are not doing to prevent scope creep.

Proof: “What did we decide?” questions disappear. Future changes reference the rationale instead of restarting the debate.

Step 5: Assign owners, dates, and follow-up

How to do it: Add an action list using “Owner | Task | Date” and schedule the next check-in. Store the note in one folder or one running thread for easy history.

Proof: Follow-through improves because accountability is visible. Handovers are faster because history is easy to find.

Skill Focus

Skill 1: Structured writing

Why it matters: Clear structure turns complex discussions into readable decisions. It saves time and reduces confusion across teams.

Practice this week: Rewrite one past meeting recap into a one-screen note with a decision question and three context bullets. Remove any line that does not change the decision.

Apply at work: Use the structure live in the next meeting and type as you go. Share the note link immediately after the meeting.

Proof to show: Readers reply with approvals instead of clarification requests. Your note becomes the link people forward.

Skill 2: : Trade-off thinking

Why it matters: Most decisions are trade-offs, not perfect answers. Naming trade-offs makes choices faster and fairer.

Practice this week: For one decision, draft three options that vary by scope, time, and risk. Write one trade-off line for each in plain language.

Apply at work: Present the options in the note with a clear recommendation. Ask the decision owner to choose based on the stated criteria.

Proof to show: The team stops looping on the same debate. Decisions land within one or two cycles.

Skill 3: Accountability design

Why it matters: Decisions fail when owners and dates are missing. Clear accountability turns a decision into delivery.

Practice this week: Create an action table template with Owner, Task, Date, and Status. Use it once and review it in the next meeting.

Apply at work: End each decision note with three to five action lines and a next check-in date. Keep the note in one running thread so status stays visible.

Proof to show: Tasks close on time more often. Fewer action items disappear between meetings.

Case study

Tarin led a cross-functional rollout where decisions were made in meetings but forgotten by the next day. Work stalled, and teams argued about what had been agreed. He introduced a one-screen decision note template with a decision question, three context bullets, options with trade-offs, and a clear action list with owners and dates.

Within two weeks, debates shifted from rehashing history to choosing trade-offs. A key decision on launch scope was documented with a clear rationale and a note on what was out of scope, which prevented late additions. Follow-through improved because every decision ended with “Owner | Task | Date,” and leadership began asking for the decision note link instead of another meeting.

Action steps

Lock the habit with small, visible moves. Do these now so every decision produces alignment and action.

• Create a one-screen decision note template with Question, Context, Options, Decision, and Actions.
• For the next meeting, write the decision question at the top before the discussion starts.
• Limit context to three bullets and link any deeper documents instead of copying text.
• Record up to three options with trade-offs and mark one recommendation in one sentence.
• Close with “Owner | Task | Date” lines and store the note in one running thread.

These steps turn meetings into decisions that survive the room. Repeat the template weekly, and you will see fewer loops, faster approvals, and cleaner follow-through.