FortumDS All articles
Enterprise Strategy

If They Can't Explain It, They Won't Use It: The Case for the Elevator Test

FortumDS
If They Can't Explain It, They Won't Use It: The Case for the Elevator Test

Walk any floor of a mid-sized American company and ask employees a deceptively simple question: what does the platform you log into every morning actually do? In many organizations, the answers are revealing. 'It's the HR thing.' 'Where we do the expense reports.' 'Something with the cloud, I think.'

These aren't careless people. They are competent professionals who have learned to operate software the way drivers operate cars — pressing the buttons that work, ignoring the ones that don't, with no mental model of what's under the hood. And that gap between usage and understanding is where software ROI quietly leaks out of the enterprise.

Why Understanding Is an Adoption Problem

The conventional response to low adoption is more training: another webinar, another quick-reference guide, another mandatory e-learning module. But training addresses mechanics, not meaning. An employee who completes training knows which buttons to press. An employee who understands the platform knows why they'd press a different one.

Consider three everyday scenarios:

In each case, the failure isn't technical. It's narrative. Nobody ever gave these employees a thirty-second explanation of what the system is for.

Running the Elevator Test

The audit itself is almost embarrassingly simple. Select a platform. Ask a random sample of its daily users — across departments and seniority — to answer one question: in one or two sentences, what does this tool do for you, and what would you lose without it?

Score the results against three thresholds:

The test costs nothing and takes an afternoon. What it reveals is usually worth more than the next training line item.

Clarity-First Onboarding Beats Training Budgets

Organizations that score well share a habit: they lead with the story, not the software. Their onboarding answers three questions in the first week — what this platform does, what it replaces, and what changes for your specific role. They name their systems in plain language rather than acronyms. They publish a one-page 'what lives where' map so employees stop guessing which tool handles which task.

Most importantly, they treat internal communication as part of the software investment, not an afterthought. A platform that costs seven figures and gets a two-paragraph launch email has a communication budget problem, not an adoption problem.

The economics are hard to argue with. Training programs are recurring costs that decay with every new hire and every reorganization. Clarity, once established — in onboarding materials, in role-based quick guides, in the way leaders talk about the stack — compounds. It survives turnover. It scales with growth.

Before the next budget cycle funds another round of training, try the cheaper intervention first. Ask your people what the software does. Their answers will tell you exactly where the ROI is going — and how much of it is recoverable with nothing more than a well-told story.

All Articles

Related Articles

Your Vendor Just Shipped an AI Feature. Did Anyone Read the Terms?

Your Vendor Just Shipped an AI Feature. Did Anyone Read the Terms?

The Two-System Handshake That Swallowed Four Years: Anatomy of an Integration Runaway

The Two-System Handshake That Swallowed Four Years: Anatomy of an Integration Runaway

Requirements by Photocopy: How Yesterday's RFP Quietly Builds Tomorrow's Architecture

Requirements by Photocopy: How Yesterday's RFP Quietly Builds Tomorrow's Architecture