impact-narrative

Translate technical accomplishments into business impact narratives for reviews.

3|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/meaganewaller/.dotfiles --skill impact-narrative
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact-narrative
Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/impact-narrative
Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill impact-narrative

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the communication gap between technical execution and business outcomes, helping engineers articulate the value of their work to leadership.

Core Features & Use Cases

  • Impact Translation: Converts technical jargon into business-friendly language.
  • Quantification Guidance: Provides frameworks for measuring and estimating impact.
  • Audience Tailoring: Offers strategies for framing narratives for executives, technical leaders, and peers.
  • Use Case: You've just completed a complex refactoring project. Use this Skill to craft a compelling narrative for your performance review, highlighting how the refactoring reduced technical debt and enabled faster feature delivery, quantified with specific metrics.

Quick Start

Use the impact-narrative skill to translate the technical work of optimizing database queries into a leadership-ready narrative.

Frequently Asked Questions about impact-narrative

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate technical accomplishments into business impact narratives?

To translate technical accomplishments into business impact narratives, you convert technical actions into measurable outcomes like revenue, cost savings, or risk reduction using structured frameworks such as STAR-L and Problem-Solution-Impact.

What is the best way to quantify technical work for a promotion discussion?

The best way to quantify technical work for a promotion discussion is to map technical actions to measurable business outcomes, focusing on specific metrics that demonstrate velocity, scale, quality, cost savings, or risk reduction.

How do I write a self-review that highlights business value instead of technical jargon?

To write a self-review highlighting business value instead of technical jargon, use audience tailoring strategies to reframe technical execution into leadership-ready language that emphasizes measurable results and business impact.

Can I use the STAR-L framework to structure stakeholder updates for a refactoring project?

Yes, you can use the STAR-L framework to structure stakeholder updates for a refactoring project by framing the technical debt reduction as a problem and highlighting the resulting faster feature delivery as the measurable impact.

How does impact translation work for communicating with executives versus technical leaders?

Impact translation works for communicating with executives versus technical leaders by applying audience tailoring strategies, shifting the narrative focus from technical execution details to high-level business outcomes and measurable leadership impact.

When do I need to convert technical actions into measurable business outcomes?

You need to convert technical actions into measurable business outcomes when preparing self-reviews, leading promotion discussions, or delivering stakeholder updates that require demonstrating clear leadership impact and business value.