• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Initiative Impact Score

Description

Initiative Impact Score measures the proportion of leadership-initiated programmes and changes that achieve their stated impact objectives — distinguishing effective leadership investment from activity that consumes capacity without producing results. It is the ultimate accountability measure: not whether work was delivered, but whether it delivered the change it was designed to produce.

This measure requires leaders to commit to impact objectives before launching initiatives and to review those commitments honestly after delivery. Leaders who maintain a strong impact score demonstrate not just execution capability but strategic wisdom in selecting and shaping work that genuinely moves the organisation forward.

How to Use

What to Measure

  • Total number of initiatives launched in a given period with defined impact objectives
  • Number of initiatives where the stated impact objective was substantially achieved (80%+) post-delivery
  • Number where partial impact was achieved (40–79%)
  • Number where impact was not achieved or was negative (below 40%)
  • Breakdown by initiative type: strategic, process improvement, cultural change, technical investment

Formula

Initiative Impact Score = (Initiatives achieving 80%+ of stated impact objective / Total initiatives with defined objectives) × 100

Optional:

  • Weighted score: weight initiatives by investment size (person-months or budget) so large initiatives have proportional influence on the score
  • Improvement trend: compare scores across consecutive quarters or years to identify trajectory

Instrumentation Tips

  • Require that all initiatives above a defined size threshold (e.g. more than 2 person-months of effort) have a documented impact objective with a measurement method and review date
  • Build post-delivery impact reviews into the governance calendar at 30, 60, and 90 days after launch — not just at go-live
  • Use a standardised impact scorecard that rates each initiative against its original objectives
  • Distinguish between impact not achieved due to execution failure versus impact not achieved due to strategy change or external disruption

Benchmarks

Score Interpretation
75–100% Excellent — high proportion of initiatives are delivering their intended impact
55–74% Good — most initiatives are landing; room to improve selection and impact definition
35–54% Moderate — less than half of initiatives achieving stated impact; review selection and scoping quality
Below 35% Poor — fundamental gap in initiative quality, impact definition, or post-delivery follow-through

Why It Matters

  • Measures the return on leadership investment Every initiative consumes capacity, attention, and organisational energy. Impact score measures whether that investment is yielding genuine returns — the most direct accountability available to a leader.

  • Creates discipline in initiative selection Leaders who know their impact score will be tracked become more selective about what they launch, investing more in discovery and impact definition before committing to execution.

  • Exposes the post-delivery measurement gap Most organisations invest heavily in delivery metrics and very little in post-delivery outcome measurement. Impact score creates structural accountability for the measurement gap.

  • Distinguishes strategic capability from delivery capability A team can have excellent delivery capability and poor strategic capability — shipping initiatives that are executed well but targeted poorly. Impact score makes this distinction visible.

Best Practices

  • Define impact objectives at initiative launch using SMART criteria and specify the measurement method and timeline explicitly
  • Schedule post-delivery impact reviews as calendar commitments at initiation — not as optional retrospectives that can be deferred
  • Create a culture where honest reporting of low-impact initiatives is valued as learning rather than penalised as failure
  • Use impact score data to improve initiative selection criteria for the next planning cycle
  • Include impact score in portfolio governance reviews alongside delivery metrics

Common Pitfalls

  • Defining impact objectives vaguely at initiative launch to give flexibility in assessment — undermining the accountability purpose of the measure
  • Assessing impact too soon after delivery before the change has had time to take effect (e.g. measuring a culture change initiative after 30 days)
  • Attributing impact to an initiative when multiple factors may have contributed — requiring discipline in impact attribution methodology
  • Using the score punitively in ways that create incentives to avoid committing to impact objectives

Signals of Success

  • Leaders proactively commission post-delivery impact reviews rather than waiting for them to be required
  • The organisation's initiative portfolio shows a reducing proportion of low-impact investments over time
  • Impact review data is explicitly used to improve the next cycle's initiative selection and scoping
  • Leaders can articulate the impact evidence for their portfolio investments in governance reviews

Related Measures

  • [[OKR Achievement Rate]]
  • [[Outcome-to-Output Ratio]]
  • [[Decision-to-Outcome Lead Time]]
  • [[After-Action Review Completion Rate]]

Aligned Industry Research

  • Benefits Realisation Management (Bradley, 2010) Bradley's research on programme benefits demonstrates that organisations with structured post-delivery benefits reviews achieve significantly higher rates of intended impact than those that measure only at delivery — making the post-delivery review a critical component of impact governance.

  • Beyond the Idea (Vijay Govindarajan & Chris Trimble, 2013) Govindarajan and Trimble's research on innovation execution distinguishes between idea quality and execution quality — demonstrating that impact failure is as often attributable to poor execution follow-through as to poor initial concept, reinforcing the need for post-delivery measurement.

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering