Communication

Turn Bear Decisions outputs into a clear, defensible recommendation that others can act on.

This page matches how we think about Communicating the decision in client work: analysis only matters if it can be understood and used.

For in-app exploration and interpretation, see Analyze Workflow & Interpreting Results; for chart mechanics see Dashboard & Visualizations; for model discipline see Best Practices.

Recommended path

State the decision (or sequence of decisions) you are asking for: commit now, defer, hedge, monitor, or gather more information. If the right answer is conditional, say what it is conditional on. Connect any deferral or staging to the signals and timing you have already explored in analysis.

Key drivers

Explain why the recommendation follows from the model: which decisions, uncertainties, or strategies moved the outcome. You do not need to walk through every lever; focus on the few that would change the story if they were wrong. When you used grouping or views in the dashboard, name the perspective (for example by decision, strategy, or uncertainty) so reviewers can map your narrative to the analysis.

Risks and trade-offs

Make the uncomfortable parts visible: downside cases, decisions that only work under narrow conditions, and what you are giving up for the preferred path. Call out assumptions that would flip the conclusion if they shifted. This is where ranges, tails, and scenario filters belong in the story: show how robust the headline is when assumptions move, not just the mechanics of filtering (those are covered in Analyze Workflow).

Range of outcomes

Decision-makers should leave with a feel for spread as well as central tendency: what "good," "base," and "bad" look like in your framing, and which chart or export supports each. Point to exports or slides built from BD_Images or other artifacts when helpful. Step-by-step export behavior is in Copy to Clipboard and Export as PNG on the analyze workflow page.

From analysis to story

Filtering and scenario subsets are powerful for testing robustness; in a memo or deck, pair any simplified view with what was excluded and why, so the audience trusts that material risks were not hidden. Put critical assumptions next to the recommendation, not only in an appendix.

Artifacts and structure

• One-pager or executive summary: recommendation, drivers, top risks, and what you are watching next.
• Slides: lead with the decision ask, then evidence; keep sensitivity views available for the questions you expect.
• Appendix: deeper cuts, alternative groupings, and edge cases for reviewers who want to stress-test the story.

Narrative principles

Practical habits that keep the message actionable:

• Lead with insights: start with what decisions matter most, not technical detail.
• Show ranges: use range and tornado-style views to carry both opportunity and risk. Use goal likelihood views to show the probability of meeting or exceeding the goal you have set.
• Frame confidence: Use goal likelihood views to show the probability of meeting or exceeding the goal you have set.
• Address concerns: show how conclusions change under alternate assumptions your audience cares about.
• Recommend actions: spell out what to decide, what to mitigate, and what to monitor.

Stakeholder communication

Different audiences need different emphasis on the same four answers:

• Executives: expected direction, material risks, strategic implications, and what you need from them.
• Risk managers: tails, stress cases, mitigations, and triggers that would change the posture.
• Operational teams: concrete scenarios, responses, and handoffs tied to things they control.

Next Steps

Continue to Best Practices →