impact-quantification
When to use
After an analytical finding surfaces a potential action, change, or opportunity. Use to produce a defensible numeric estimate that stakeholders can act on. Also use when prioritizing a backlog of initiatives — quantified impact is the primary ranking signal.
Process
- Classify the impact type — revenue growth, cost reduction, risk reduction, or efficiency gain. Each type has a different formula family (see
references/impact_quantification_framework.md). - Gather inputs — collect baseline metrics, affected population size, expected lift/reduction, time horizon, and confidence level.
- Build the point estimate — use
scripts/revenue_impact.pyfor revenue/growth scenarios orscripts/cost_savings.pyfor cost/efficiency scenarios. - Add uncertainty bounds — use
scripts/confidence_interval.pyto produce low/base/high estimates. Never deliver a single number without a range. - Document assumptions — fill in
references/assumption_documentation.mdfor every input that is estimated rather than directly measured; note the sensitivity of the output to each. - Package the estimate — complete
assets/impact_estimate_template.mdwith the range, assumptions, confidence, and recommended action; optionally build the fullassets/business_case_template.mdfor larger decisions.
Inputs the skill needs
- Baseline metric value (current state)
- Affected population or volume
- Expected change (lift %, absolute, or rate change)
- Time horizon (monthly / annual)
- Confidence level in inputs (high / medium / low)
Output
- Impact estimate with low/base/high range
- Assumption log (source and sensitivity for each input)
- Completed
impact_estimate_template.mdorbusiness_case_template.md
More from nimrodfisher/data-analytics-skills
funnel-analysis
Conversion funnel analysis with drop-off investigation. Use when analyzing multi-step processes, identifying conversion bottlenecks, comparing segments through a funnel, or optimizing user journeys.
37metric-reconciliation
Cross-source metric validation and discrepancy investigation. Use when metrics from different sources don't match, investigating data quality issues between systems, or validating data migration accuracy.
31insight-synthesis
Transform data findings into compelling insights. Use when converting analysis results into actionable insights, connecting findings to business impact, or preparing insights for stakeholder communication.
31dashboard-specification
Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
30data-quality-audit
Comprehensive data quality assessment against business rules, schema constraints, and freshness expectations. Activate when validating data pipeline outputs before production use, auditing a dataset against defined business rules, or producing a quality scorecard for a data asset.
30root-cause-investigation
Systematic investigation of metric changes and anomalies. Use when a metric unexpectedly changes, investigating business metric drops, explaining performance variations, or drilling into aggregated metric drivers.
30