Decision Brief

Facing a call your leadership team has to make together? Ask Joy to pull the docs, the debate, and the data in your Knowledge Center into a one-page decision brief: the options weighed with pros and cons, the key risks, and a clear recommendation everyone can decide on.

For Executives & Founders VPs & Department Heads Chiefs of Staff Strategy & Operations Leads
Sample prompt to Joy's Assistant

Pull together the context in our Knowledge Center — [the scattered inputs behind the call] — and give me a one-page decision brief on [the decision]: the decision to make, the options with their pros and cons, the key risks, and a clear recommendation with the rationale behind it.

What it can look like

An illustrative example. Your output will reflect your own sources, data, and prompts.

Pull together the context in our Knowledge Center — the tooling audit, the #support-tooling debate thread, and the ticket-volume and cost data — and give me a one-page decision brief on whether to consolidate our two customer-support platforms onto one before the December renewal: the decision to make, the options with their pros and cons, the key risks, and a clear recommendation with the rationale behind it.

Here's the one-page read pulled from everything in the Knowledge Center — the tooling audit, the #support-tooling thread, and the ticket-volume and cost data. The decision comes down to three options, and the cost and training picture points fairly clearly to one of them

Decision brief: consolidate support tooling

Prepared for the Aug 12 leadership review · Owner: VP Customer Experience · Decide before the Dec 15 Frontline renewal

Decision: whether to consolidate our two customer-support platforms — Frontline and Deskly — onto a single tool before the December renewal, or keep running both.

Support runs on two platforms today at a combined $210,000 a year. Agents work about 3,400 tickets a month split across the two, reporting is stitched together by hand, and both contracts renew inside the next five months. Three options are on the table.

OptionProsConsCost / effort
Consolidate onto FrontlineTeam is already trained on it; strongest automation and reporting; single source for ticket historyLive chat is weaker than Deskly’s; higher per-seat license~$180,000/yr; 8–10 week migration to move Deskly’s chat history over
Consolidate onto DesklyBest live-chat and messaging experience; lowest license costReporting gaps leadership relies on; whole team needs retraining; weaker self-service portal~$140,000/yr; 12 week migration and the heaviest retraining
Keep bothNo migration risk; no retraining; nothing to time against a renewalMost expensive; reporting stays split; agents context-switch daily; duplicate admin overhead~$210,000/yr; no project, but the ongoing drag never goes away

Key risks

  • Migration integrity. Roughly 40,000 historical chat transcripts live in Deskly; an incomplete import would break context on open and returning conversations.
  • Renewal timing. Frontline auto-renews on Dec 15. Miss that window and we’re locked in for another year regardless of the decision.
  • Change fatigue. Support was reorganized six months ago; a second tool change too soon could dent morale and CSAT in the short term.

Recommendation. Consolidate onto Frontline. It carries the lowest change cost because the team already runs on it, it closes the reporting and automation gaps leadership feels most, and combined spend drops from ~$210,000 to ~$180,000 a year. The one real weakness — live chat — is narrower than Deskly’s retraining and reporting cost, and it’s addressable with the messaging add-on. Commit before the Dec 15 renewal, but schedule the cutover for January so it lands after the Q4 support peak rather than during it.

Want me to draft the recommendation memo for the leadership review, or model the two-year cost of each option so the numbers are on the table?

From scattered context to a decision-ready page

Point Joy at the material behind the decision — the analysis docs, the debate thread, the numbers — sitting in your Knowledge Center, and ask for the brief. Joy reads across all of it and returns a single page: the decision to be made stated plainly, the real options laid out with pros and cons, the risks worth naming, and a recommendation with the reasoning that got there.

  1. Gather the context behind the call

    Make sure the material that informs the decision is in your Knowledge Center — the analysis and comparison docs, the discussion threads, the cost and usage data. Joy reads across all of it together, not one file at a time.

  2. Name the decision and ask for the brief

    Tell Joy what call you're facing and ask for the one-page brief. Joy frames the decision, surfaces the realistic options, and weighs each one against what the material actually says.

  3. Get the structured read

    Joy returns the brief: the decision stated in a line, the options with pros, cons, and cost or effort, the key risks, and a recommendation with its rationale. Every point traces back to the underlying context.

  4. Pressure-test and refine

    Ask follow-ups: "What changes if we weight migration risk higher?" or "Draft the version that recommends keeping both." Joy reworks the brief with the full context behind it, so the team can stress the reasoning before deciding.

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.

Make it yours

The decision, stated plainly

Joy opens with a single clear line on exactly what is being decided, so the team starts aligned on the question.

Options weighed side by side

Each realistic option laid out with its pros, cons, and cost or effort, so the tradeoffs are visible at a glance.

The risks named, not buried

The handful of risks that could actually change the answer, called out where a room can see and debate them.

A recommendation with reasoning

Joy closes with a clear recommendation and the rationale behind it, so the team can agree with it or argue it on the merits.

Build-vs-buy brief

Weigh building in-house against buying or partnering, with the cost, timeline, and control tradeoffs on one page.

Market-entry brief

Frame a decision to enter a new region or segment, with the upside, the commitment, and the risks laid out.

Org-structure brief

Compare ways to restructure a team or reporting line, with the disruption and the payoff each option carries.

Investment brief

Line up competing bets for the same budget so leadership can see what each buys and what it costs to say no.

Frequently Asked Questions

What is a decision brief?

A decision brief is a short, structured document that frames a decision for a group: the call to be made, the realistic options with their pros and cons, the key risks, and a recommendation with the reasoning behind it. Joy assembles it on demand from the docs, discussion, and data already in your Knowledge Center, so leadership has one clear page to decide from instead of scattered context.

How does Joy build the brief from our own material?

Joy reads across the analysis docs, discussion threads, and cost and usage data in your Knowledge Center together, frames the decision, identifies the realistic options, weighs each against what the material says, and closes with a recommendation. Every point traces back to the source, so you can check the reasoning rather than take it on faith.

Does the brief make the decision for us?

No. The brief is a structured basis to decide, not a verdict. It lays the options and tradeoffs out clearly and recommends one with a rationale, but the point is to give your leadership team a shared, complete view to debate and decide from. You can ask Joy to re-weight the factors or draft the case for a different option and see how the recommendation changes.

What kinds of decisions does this work for?

Any call where the context is scattered and the tradeoffs matter — consolidating overlapping tools, entering a new market, restructuring a team, a build-versus-buy question, or choosing between competing investments. Wherever a group has to weigh real options against real constraints, the same brief structure fits.

Can we adjust the brief before taking it to the room?

Yes. Ask Joy to add an option, weight a risk more heavily, tighten it to a single page, or draft the version that argues the opposite recommendation. Joy reworks the brief with the full context behind it, so you can pressure-test the reasoning before anyone has to decide.

Related Recipes

Executive

Meeting Prep Brief

Get a meeting brief with attendee backgrounds, context, and talking points before every meeting.
Executive

Board Deck Preparation

Turn your metrics, wins, and risks into a slide-by-slide board deck outline.
Executive

Executive Dashboard Brief

Get an AI-written summary of the key insights and action items from your dashboards.

Ready to bring the decision to the table already framed?

Join the waitlist and be first to try this workflow when JoySuite launches.

Join the Waitlist Browse All Recipes