Back to Blog
    LeadershipAdam FridmanOct 9, 202610 min read

    Leadership Development ROI: How to Build a Number Finance Will Accept

    Leadership Development ROI: How to Build a Number Finance Will Accept

    Only 8% of organizations measure the business impact of their learning programs (McKinsey), and 67% of L&D leaders say proving the value of leadership development is unsolved. Those two facts are usually treated as a measurement problem. They are a sequencing problem. You cannot put a credible dollar sign on a program until you have a behavior number, and most programs never produce one, because they measured who finished the course. Get the behavior number first. The ROI conversation becomes straightforward after that, and nearly impossible before it.

    The CFO question is never really "what was the ROI."

    It is "what changed, how do you know, and who else agrees with you."

    Quick answer

    Leadership development ROI is built in three steps, in order. First, prove a behavior changed, using leading indicators that move in weeks. Second, connect that behavior to a business metric it plausibly touches. Third, ask finance for the dollar value of a unit change in that metric, rather than inventing one. Programs that skip to step three produce numbers nobody believes. Programs that start at step one can defend something at every stage.

    Key takeaways

    • Almost nobody has a baseline. Only 8% of organizations measure business impact at all (McKinsey).
    • The formula is not the problem. The numerator is empty because completion was measured instead of behavior.
    • Finance owns the dollar value, not you. Your job is the behavior and the metric. Borrow the conversion rate from the people who already maintain it.
    • Three year frame. Year one behavior, year two team impact, year three culture.
    • Put everything in the denominator, including manager time. A small denominator reads as a sales pitch.

    Why the standard formula breaks for L&D

    The classic version is simple enough: benefit minus cost, divided by cost.

    It works for a machine. You know what the machine cost and you know what it produced.

    For leadership development, three things go wrong at once.

    What breaksWhy
    The numerator is emptyTransfer to the job runs 10 to 20%, and 75% of managers show no measurable improvement without structured follow-up (Brandon Hall Group). Often there genuinely is no benefit to count
    The benefit is indirectLeadership behavior does not produce revenue directly. It moves turnover, engagement, safety and customer metrics, each one with other causes
    The clocks do not matchThose metrics move over quarters. Budget cycles ask monthly

    The instinct at that point is to reach for a bigger multiplier and a confident slide. That is exactly the move that loses the room, because a finance partner can tell the difference between a measurement and an assertion in about four seconds.

    Step one: get a behavior number

    This is the step that makes everything after it possible, and it is the step almost everyone skips.

    Three leading indicators move in weeks rather than quarters:

    IndicatorWhat it answers
    Commit rateAre people saying yes to a specific action
    Completion of commitmentsAre they doing what they said
    Stories sharedDid it matter enough to tell someone

    These are not softer than financial metrics. They are earlier. Each one is a behavior that either happened or did not, counted at the individual level, available from week two.

    The independent read on whether that kind of measurement holds up is the Claremont Graduate University evaluation (Felkey et al. 2021): 136 employees, daily prompts each ending in a commitment, a 64% check in rate against a 41% industry average, p < .001. Check in and NPS were measured directly; wider organizational outcomes were extrapolated. The full method for collecting your own version is in How to Measure Leadership Behavior Change.

    Step two: connect the behavior to a metric

    Only once a behavior has moved does it make sense to ask what that behavior touches.

    If this behavior movedIt plausibly touchesWho owns that number
    Recognition frequency, feedback qualityVoluntary turnover, engagementHR and finance
    Supervisor coaching in the momentSafety incidents, liability claimsRisk and operations
    Customer facing behaviorsNPS, retention, repeat rateCustomer and revenue teams
    Decision delegationCycle time, escalation volumeOperations

    The word doing the work in that table is plausibly. You are not claiming the behavior caused the metric. You are claiming a mechanism, showing that the behavior moved first, and letting the metric move second.

    The strongest version of this is a comparison design, because it removes most of the argument. At Romano's Macaroni Grill, managers in half the restaurants ran a campaign and were compared against the rest. In that group, manager turnover fell 60% year over year and 72% of surveyed managers improved on every measured behavior. Hourly turnover fell 4%. Half the business acted as the control, which is a far better answer to "how do you know" than any multiplier.

    Step three: let finance supply the dollar value

    Here is the discipline that separates a credible business case from a deck nobody forwards.

    You do not calculate the cost of a manager leaving. Finance or HR already has that number, or an agreed method for it, and theirs is the one that will survive review. Ask for it. Use it unchanged. Attribute it to them in the slide.

    The same applies everywhere else. Risk owns the cost of a claim. Operations owns the cost of an escalation. Revenue owns the value of a retained customer.

    Two reasons this matters more than it sounds. The number becomes theirs, so it stops being a thing you have to defend alone. And you avoid the single most common failure, which is importing a benchmark cost figure from an industry article and watching someone ask where it came from.

    Worth seeing what a real one looks like. At Gaylor Electric, a president running a daily prompt to eliminate process waste noticed that inter-office mail was being couriered while team members were already driving between the same offices. The change saved $18,000 a month. Said precisely: one month of measured savings, which annualizes to a projection of nearly a quarter million, not a measured annual result. That distinction is the whole game.

    The three year frame

    YearWhat you are provingWhat you report
    Year oneBehavior changeCommit rate, completion of commitments, stories shared, by segment
    Year twoTeam impactThe metrics those behaviors touch: turnover, engagement, NPS, claims
    Year threeCultureThe behaviors persisting without the program pushing them

    The trap is being asked for year two evidence in month two and trying to supply it. Turnover cannot move before behavior moves. Saying so, and then showing a real behavior number instead, is a stronger position than a speculative dollar figure.

    What goes in the denominator

    Business cases get caught here more often than on the benefit side, because an implausibly small cost makes a reviewer distrust everything above it.

    Include: program or vendor fees, facilitator and venue cost, the reinforcement layer, participant time at loaded cost, and manager time.

    That last one is worth sitting with. If your reinforcement plan asks managers for an hour a week across a population of 500, that is a real and large cost, and a reviewer will find it. It is also the practical argument for keeping the manager ask small: a kickoff huddle, a short message every two weeks, a midpoint one to one, a recognition cascade, and a close. Minutes a week, scripted. The reasoning is in The Manager Multiplier.

    Three questions to take to finance

    Short meeting, and it changes the shape of everything afterward.

    What does one unit of this metric cost us? One voluntary manager exit, one liability claim, one point of engagement. Their number, their method.

    What counts as evidence here? Some finance partners accept a comparison group. Others want a trend against a baseline. Asking in advance costs nothing and prevents building the wrong case for six months.

    What is the smallest result that would be worth the spend? This reframes the entire project. You stop trying to prove a big number and start trying to clear a known bar.

    How ProHabits fits

    ProHabits is the reinforcement layer for leadership development, and the measurement is a side effect of the reinforcement rather than a separate exercise.

    One MicroAction a day, by email or text, no app and no login, each ending in the I commit button. That button is the implementation intention research puts at a 2 to 3x effect on follow-through across 94 studies (Gollwitzer), and it is also the data point: a specific action a person said they would take and then did.

    The dashboard reports commit rate, completion of commitments and stories shared, live, by segment across the 20/60/20. That is your year one evidence, collected without anyone filling out a survey.

    We will not hand you a modeled ROI figure. We will hand you the behavior number that makes the ROI conversation possible, and tell you plainly which parts of our own proof were measured and which were extrapolated.

    90% of training vanishes in a week. ProHabits makes it stick, and makes it countable.

    The full argument, with the day after framed as the product, lives here:

    The Day After Leadership Training

    Keep reading

    Two next steps

    Bring us the last program you had to justify and we will show you the behavior number it should have produced, or build a campaign and start collecting one now.