Playbooks

The Decision Packet Template

By Wayne·Published ·Updated

Short answer

A one-page template that gets partners and founders out of the weekly pricing-and-scope loop. Four fields — decision needed, options considered, recommendation, and what changes if we're wrong. Two fields to leave out on purpose. Roll out over one cycle; adoption sticks or the packet was wrong for the shop.

Why partners get stuck

In most 10–50 person professional services and agency shops, one or two partners become the routing table for every non-standard decision. Pricing exceptions, scope changes, hiring calls, vendor picks. It's not because they want to — it's because the packet coming to them is always incomplete.

The four fields that matter

  1. Decision needed. One sentence. If it takes two sentences, it's actually two decisions.
  2. Options considered. Two or three named alternatives, not a maybe-list. If there's only one option, this isn't a decision, it's an update.
  3. Recommendation and why. The person surfacing the decision commits to one path. Removes the "what do you think" pattern that traps partners.
  4. What changes if we're wrong. Reversibility. Cost of reversal. This is where most decision debate actually lives — surface it up front.

The two fields that don't

Do not include "background" or "stakeholders consulted." Both expand to fill available space and neither changes the decision. The whole point of the packet is a decision, not a memo.

How to roll it out

One cycle — usually two weeks — as a required format for anything landing on a partner's desk. If the packet feels forced or the team keeps ducking it, the format is wrong for the shop, not the team. Adjust the four fields, don't add more.

Related service

Turn the operating signal from this resource into a scored map of where work, revenue, and decisions are stuck — plus a practical 30–90 day roadmap.

See what's in the diagnostic

FAQ

Who is The Decision Packet Template for?

Founder-led and operator-led teams evaluating where AI can improve workflows, decisions, revenue motion, retention, customer experience, or employee experience without adding more tool sprawl.

What should I do after reading this?

Use the concepts to identify one expensive operating constraint, then pressure-test it with the Operating Clarity Scan before investing in tools, automations, or a larger diagnostic.