Decision-Ready Analytics Briefs

Stakeholders are drowning in data but starving for decisions. Raw charts and technical logs often fail to trigger action because they lack context, narrative, and clear recommendations. This skill converts raw analytical findings into executive-ready briefs that lead with the "so-what" and end with a concrete ask.

What it does

• Frame decisions by identifying the specific choices, risks, and stakes involved in the analysis.
• Select narrative patterns like Diagnostic, Directional, or Comparative to match the business context.
• Build message stacks that connect a claim to evidence, implications, and required actions.
• Design informative visuals by creating charts that prioritize takeaways over aesthetics using clear annotations.
• Synthesize executive briefs into a structured format containing bottom-line conclusions and supporting facts.

How it works

1. Define the decision context by specifying the audience, their risk tolerance, and the primary choice at hand.
2. Select a narrative pattern based on whether you are diagnosing a failure, comparing options, or reviewing performance.
3. Draft the message stack to ensure every insight includes a claim, evidence, and business consequence.
4. Generate the brief or dashboard structure using templates optimized for leadership, finance, or operations.

Frameworks & tools

This skill works with standard data stacks, providing templates for Markdown reporting, Python visualization logic (Matplotlib, Pandas), and structured dashboard layouts.

Why this beats prompting it yourself

Generic prompts often produce "data dumps" that describe metrics without interpreting them. This skill enforces a decision-first methodology that prevents the "buried lede" and ensures every output includes a calibrated recommendation.

Use cases

• Leadership reviews to provide a concise status update on critical business KPIs.
• A/B test readouts that explain not just which variant won, but why and what to ship next.
• Budget recommendations supported by sensitivity analysis and clear trade-offs.
• Post-launch analysis to identify bottlenecks in new feature adoption.

Known limitations

This skill focuses on the communication of data, not the statistical calculation or extraction of raw data from databases. It assumes the user has already performed the underlying analysis.