The Proof Problem
You invested in leadership development. The participants loved it. The evaluations were strong. Your stakeholders ask: "What changed?"
You do not have a good answer. Not because nothing changed. Because the measurement system was not designed to capture what changed. You have satisfaction scores and knowledge quiz results. You do not have evidence of business impact.
This is solvable. Not with a year-long research project. With a 90-day measurement plan designed before the experience begins.
Why 90 Days
Ninety days is long enough for behavior change to become visible and short enough to attribute the change to the development investment. Beyond 90 days, too many other variables intervene. Within 30 days, the change has not had time to produce measurable business outcomes.
The 90-day window also creates urgency. When leaders know they will be measured at 90 days, they take the development commitments seriously. The measurement becomes a development tool, not just an evaluation tool.
The 90-Day Measurement Plan
Before the experience (Week -1):
Establish baselines for three to five specific metrics that the development is designed to influence. Choose metrics that matter to your stakeholders and that leadership behavior directly affects. Pick those numbers before the work starts. How to measure leadership development ROI lays out the three-level frame these baselines sit inside.
Examples: - Decision cycle time (days from strategic decision to team-level execution) - Meeting effectiveness (percentage of meetings that end with clear commitments) - Team engagement pulse (monthly survey of leader's direct reports) - Strategic alignment score (can leaders articulate the connection between their team's work and strategic priorities?) - Escalation rate (number of decisions escalated to the next level per month)
During the experience (Day 0):
At Lead the Endurance, every leader leaves with a specific 90-day commitment built on the POW Framework. The commitment is not generic. It is a specific change in their leadership behavior, tied to a specific metric, with a specific timeline.
Example commitment: "I will use the POW Framework to open every team meeting for the next 90 days. I expect this to reduce our average meeting-to-action cycle from 14 days to 7 days."
This commitment serves double duty: it drives behavior change and creates a measurable outcome.
At 30 days:
Check in on commitment execution. Not on results. On behavior. Is the leader actually doing the thing they committed to? If not, what is getting in the way?
The 30-day check-in catches drift early. Leaders who stopped using the new approach after two weeks get a nudge. Leaders who are struggling get support. The 30-day check is about sustaining the practice, not evaluating the outcome.
At 60 days:
Begin tracking the specific metrics. By 60 days, consistent behavior change has had enough time to start producing visible outcomes. Compare current metrics to the baseline.
Decision speed is usually the first metric to move. By 60 days, an organization that captured a baseline can see it in reporting it already runs: the call that used to sit in a queue for a week now gets made inside the meeting. That reading only exists because someone measured decision speed before the experience, not after the fact.
At 90 days:
Compile the full measurement report. Compare baselines to current metrics. Document specific examples of behavior change that produced business outcomes. Present the data to stakeholders in their language.
The Report That Convinces Stakeholders
Your 90-day report needs three sections:
Section 1: What changed in behavior. Specific examples of leaders who changed how they operate. Not generic claims. Specific, named examples with before-and-after descriptions. "VP of Operations reduced her team's average decision cycle from 12 days to 5 days by using the POW Framework in every team meeting."
Section 2: What changed in metrics. The baseline-to-90-day comparison for each metric. Present the data clearly. If decision speed improved 30%, say so. If escalations dropped 40%, say so. Use numbers, not narratives.
Section 3: What it is worth. Translate the metric changes into business value. If faster decisions produced $200,000 in earlier strategic execution, state it. If retained talent avoided $300,000 in replacement costs, state it. This section speaks the CFO's language. Before that meeting, read what a skeptical CFO asks next so no question lands cold.
Making Measurement Automatic
The most effective approach embeds measurement into the development design rather than adding it afterward.
The POW Framework naturally produces measurable commitments. When every leader leaves with a specific commitment tied to a specific metric, the measurement framework builds itself.
Three design choices make 90-day measurement automatic:
Choice 1: Pair every participant with an accountability partner. The partner checks in at 30 and 60 days. This creates both accountability and data collection.
Choice 2: Use the same metrics across all participants. When 30 leaders all measure decision speed, the aggregate data is compelling. Individual data points become a pattern.
Choice 3: Collect stories alongside numbers. Numbers convince the CFO. Stories convince everyone else. Capture two or three specific examples of how the development investment changed a business outcome.
What Stakeholders Actually Want
Most stakeholders do not need a perfect ROI calculation. They need confidence that the investment produced real change. The 90-day measurement plan provides that confidence through a combination of metric improvement and specific examples.
The results page shows how Learn2 clients have documented these outcomes. The pattern is consistent: organizations that design measurement into the experience from the beginning produce compelling evidence of impact.
See why leadership development ROI is measured wrong for why traditional approaches fail.
Read next: How to Get Buy-In from Leaders Who Didn't Build the Strategy