Executive Translator
Turn technical findings into language executives actually understand
Takes your technical analysis — complete with p-values, confidence intervals, and methodology caveats — and generates an executive-friendly version with clear takeaways, business implications, and recommended actions.
INGREDIENTS
PROMPT
Create a skill called "Executive Translator". When I paste a technical analysis (including statistical tests, methodology descriptions, data exploration, and findings), generate a layered communication package: (1) Executive summary: 3-5 sentences covering what we found, why it matters, and what to do about it. No jargon. (2) Business narrative: 1-page version with key charts simplified, impact quantified in dollars/users/time, and risks expressed as business risks not statistical caveats. (3) Technical appendix: the full methodology, statistical details, and limitations preserved for data-literate readers. Adapt the tone to the specified audience (C-suite, VP, product manager, board). Always lead with the "so what" — the action or decision the analysis enables.
How It Works
You spent a week on the analysis. The methodology is sound. The statistical
evidence is clear. But the moment you mention "confidence intervals," the
executive's eyes glaze over. This skill bridges the translation gap.
What You Get
- An executive summary (3-5 sentences) with the key finding and recommended action
- Business impact framing ("This represents ~$2M in annual revenue at risk")
- Methodology translated to plain language ("We compared 50,000 customers over 6 months")
- Caveats expressed as business risks, not statistical terms
- Visualizations simplified for non-technical audiences
- Appendix with the full technical detail for anyone who wants it
Setup Steps
- Ask your Claw to create an "Executive Translator" skill with the prompt below
- Paste your technical analysis, notebook output, or findings document
- Specify the audience (C-suite, VP, product manager, board)
- Get back a layered document: executive summary, business narrative, and technical appendix
Tips
- The "So what?" question is everything — lead with the business impact, not the methodology
- Different audiences need different levels: a board wants 1 slide, a VP wants 1 page, a PM wants the details
- The skill preserves technical rigor in the appendix — nobody loses the full analysis
- Use it for weekly business reviews, quarterly planning presentations, and ad hoc insight delivery