How consumer-grade UX thinking reimagined an enterprise LMS — and shipped a product 200+ customers adopted post-launch.
Engagement
Discovery Research, Personas, Concept & Prototype
Client
Workday — Enterprise HR & learning platform
Duration
Multi-phase · discovery → concept → ship
§01 · At a Glance
An LMS rebuilt from the learner up — not the compliance officer down.
Read time · 6 minutes Published 2026 · FutureProof
Discovery Scope
30+
L&D leaders, managers, and frontline learners interviewed across industries.
Personas Defined
04
distinct learner archetypes — each with a different reason to open the app.
Prototype Rounds
06
iterative concepts tested against learners and admins before the build kicked off.
Adoption
200+
enterprise customers post-launch. Still growing.
§02 · The Challenge
Every employee had it. Nobody opened it voluntarily.
Enterprise learning systems had become synonymous with compliance training — annual modules people clicked through as fast as they could, then closed the tab. L&D leaders knew the product had more to offer. Employees didn't believe them.
The system-of-record was in place. The content library existed. The mobile app shipped. Engagement stayed flat. The gap wasn't features — it was that nobody had designed the experience around why a real human would open a learning app on a Tuesday afternoon.
The problem beneath the problem
Enterprise LMSes were optimised for the buyer (compliance), not the user (a learner mid-career).
01
Consumer learning apps had taught employees what "good" feels like — short sessions, personalised paths, visible progress. Enterprise LMSes still felt like HR software from a decade earlier.
02
The app served four very different learners — compliance-driven, role-development, manager-assigned, self-directed — but presented the same flat library to all of them.
03
L&D leaders could see engagement dashboards but couldn't act on them. The feedback loop between "what the numbers show" and "what the product serves people" was broken.
“
The LMS wasn't broken because it was missing features. It was broken because nobody had asked what would make a person choose to open it.
FutureProof thesis
§03 · The Approach
Three moves that replaced a content catalogue with a consumer-grade experience.
We ran 30+ structured interviews — learners, managers, L&D leads — with prompts designed to surface why learning gets started and why it gets abandoned. Most enterprise research weights the buyer's voice; we weighted the learner's, because the learner is the one who either opens the app tomorrow or doesn't.
Discovery surfaced four learner archetypes — compliance-bound, role-developing, manager-assigned, self-directed. Each had a distinct entry point, a distinct attention budget, and a distinct definition of "useful." The product couldn't serve all four with one flat library. The personas became the scaffolding for the redesign.
Six concept rounds. Design by testing, not by consensus.
We ran six concept rounds against real learners — short sessions, new home experience, personalised paths, visible progress, manager-to-learner handoffs. Each round killed assumptions that a feature deck would have preserved. By the time engineering started, the core product experience had already been validated end-to-end.
Consumer UX patterns are well-known. Enterprise context is not. Importing one into the other without translation almost always fails.
Consumer learning apps can assume a single user, a single device, and a motivation the app doesn't need to manufacture. Enterprise learning has to work across thousands of employees, multiple managers' assignments, compliance deadlines, and a buyer who evaluates the product on dashboards the learner never sees.
Our team brought the consumer-grade design sensibility — but filtered through enterprise-platform literacy. We knew which patterns would translate, which would break on permissioning or audit requirements, and which would quietly fail in the enterprise buyer conversation.
"The risk wasn't under-designing. It was over-designing in ways that wouldn't survive enterprise procurement."
§05 · Impact
An LMS people open voluntarily. 200+ customers. Still shipping.
Primary outcome
Shipped.
A reimagined Workday Learning experience — shipped, adopted, and part of the suite. Not a concept. A product.
Adoption outcome
200+
Enterprise customers adopted post-launch. Continues to grow.
What the engagement delivered
01
A learner-weighted discovery baseline — the research Workday still references when evaluating learning roadmap decisions.
02
Four behavioural personas, each tied to a distinct entry point, attention budget, and success signal — scaffolding the redesign was built on.
03
Six prototype rounds that turned a content catalogue into a personalised learning experience — validated before engineering started.
04
A consumer-grade home that respected enterprise constraints — permissioning, audit, buyer dashboards — without sacrificing the learner experience.
05
A durable product — the redesigned Learning App is live across the Workday suite with 200+ customers post-launch, still expanding.
§06 · Work With FutureProof
Shipping an enterprise product with a consumer-grade bar? That's a research and translation problem.
Bringing consumer UX patterns into enterprise contexts usually fails because the patterns don't survive translation. The ones that do require both halves of the skill set — and someone who's shipped on both sides.
We start with a $500 AI Readiness Audit. Five days. You'll come out with a clear view of where your experience breaks down and what it would take to fix it.