It's the line every L&D leader has heard in a budget meeting, in one form or another: what if we invest in training and they just walk out the door? The comeback is equally well-worn: what if we don't, and they stay? It's become such a standard exchange in learning and development circles that it's practically ritual — someone raises the training-cost objection, someone else fires back the retort, and the room nods along as though a genuine argument has just been settled.
It's worth pausing on why this exchange has such staying power, because that durability tells you something useful about the underlying dynamic it's describing, even before you get into where the quote actually comes from.
Where This Actually Comes From
Worth being honest about origin, because the internet is not consistent (I know, I clutched my pearls, too), and a thought-leadership piece that gets the sourcing sloppy undermines its own credibility on exactly the kind of rigour it's asking readers to apply elsewhere.
It's most commonly credited to Peter Baeklund, a leadership consultant who described overhearing the exchange between a CFO and CEO — "What happens if we invest in developing our people and then they leave us?" the CFO asked; "What happens if we don't and they stay?" the CEO replied.[1] That's the version most frequently cited, and it has a plausible, specific attribution attached.
That said, almost identical exchanges have been credited elsewhere to Richard Branson, to Zig Ziglar at a 1985 sales convention, and even to the ancient Indian strategist Chanakya, writing many centuries before any of the modern figures credited with it. That spread — the same basic exchange, reattributed across wildly different eras, industries, and individuals, none of whom seem to be quoting each other directly — is a strong signal it's one of those phrases that have been reattributed repeatedly rather than a single traceable quote with one identifiable origin.
Treat it as a parable that's accumulated multiple tellers, not a citation you can pin to one person with confidence. It's the kind of thing that feels like it should have a clean origin story, and doesn't, which is itself a little bit instructive about how ideas propagate through professional culture.
Why It Still Lands, Every Time
So, like Beauty and the Beast, this seems to be a "tale as old as time". Why does it keep getting deployed in exactly the same form, decade after decade, industry after industry? Because it reframes a something that people reflexively get backwards. Reframing that asymmetry cleanly, in one exchange, gives critics pause for thought and reveals the hidden depths of robust training.
The visible cost of training is easy to point at: it's a budget line item, a named number in a spreadsheet, time employees spend away from productive work that a manager can quantify. It sits right there, ready to be cut when budgets tighten, because it's the most visible cost in the room.
The cost of not training is structurally different — it's invisible until it compounds into something visible, and by then it's very hard to trace back to the original decision not to invest. It shows up as skills quietly falling behind what the role now requires. It shows up as disengagement that gets attributed to "culture" or "management" rather than to the absence of growth opportunity that's actually driving it.
It shows up, eventually, as something we've talked about in the past - attrition - people leaving not because they were trained and poached, but because they weren't trained and stagnated, and left anyway, taking their accumulated institutional knowledge with them regardless. The training vs. cost objection compares a visible number against nothing, because the alternative cost was never made visible in the first place. That's the sleight of hand the quote is designed to expose.
A Useful Gut-Check, Not Just an Anecdote
For LMS selection specifically, this anecdote is more than a rhetorical device to wheel out in a budget meeting it's a genuinely useful gut-check on what an organisation is actually buying when it selects a platform, and why.
A platform chosen purely to minimise training spend is optimising for the wrong side of that trade-off. It's solving for "how do we make this as cheap as possible," which is a legitimate procurement consideration but a poor primary lens for a decision that's fundamentally about workforce capability, not just cost control. The better question to ask vendors isn't "how cheap is this to run" but "how does this help us make people good enough to be dangerous to poach, and glad enough here that they don't want to be."
This is a very different set of requirements, and a tricky balance to strike, for sure. What does this actually imply for a shortlist?
Career pathing that makes growth visible and credible, not just a static course catalogue;
Skill progression that's legible to the employee themselves, not just tracked invisibly in an admin backend
Manager tools that make development conversations easy to have regularly, rather than reserved for an annual review that arrives too late to matter to someone already considering leaving.
An LMS evaluated only against "cost per seat" and "time to deploy" will be OK for the CFO's instinctive objection but does little to address the CEO's counter-question. Instead, making the evaluation against whether it makes people genuinely better, and genuinely aware they're getting better, addresses both sides of the exchange — which is presumably why the aphorism has survived, in one form or another, since at least Chanakya's era, if the (admittedly disputed) attribution is to be believed. History lesson over, procurement and selection lesson learned!
To conclude, this is also the question we're building into how our LMS comparison tool scores vendors — not just cost per seat, but capability for growth and retention. If you're a buyer with a need to answer to that question, we're building something which will get you to vendors who can help you achieve that.
References
[1] https://dfmconsultinginc.com/2014/02/24/invest-in-people-create-an-enlivened-future/