Who Owns Store Training?

Why 91 percent of L&D believes in continuous learning and 36 percent have built it

Summary. Almost everyone in learning and development now agrees that capability has to be built continuously. Very few organizations are structured to do it. The gap is not a belief problem, it is an architecture problem, and in retail it shows up as a question nobody owns cleanly: who actually gets to publish something to stores this week? This paper works through that question, answers the case for consolidating on one system, and gives you an audit you can run before buying anything.

The gap between what L&D believes and how it is built

LinkedIn’s 2025 Workplace Learning Report surveyed 937 L&D and HR professionals alongside 679 learners across North America, South America, Asia-Pacific and Europe. The findings describe a function that knows what it should be doing.1

Agree continuous learning is more important than ever 91 percent of L&D professionals
Concerned about employee retention 88 percent of organizations, with learning their top retention strategy
Say executives worry employees lack the skills to execute strategy 49 percent of L&D professionals
Qualify as career development champions with programs producing business results 36 percent
Have limited programs, no initiative, or are only starting 64 percent

Ninety-one percent believe in continuous learning and thirty-six percent have built something that delivers business results. That distance is the subject of this paper.

A gap that wide is rarely explained by effort or conviction. When almost everyone agrees and roughly a third succeed, the binding constraint is usually structural: something about how the work is organized prevents the belief from turning into a program.

Compliance systems are not broken. They are finished.

It is tempting to blame the learning management system, and it is the wrong diagnosis. An LMS is very good at the job it was specified for: housing durable content, assigning it, recording completion, and producing an auditable record. Those requirements are real, they are often legally required, and nothing described below replaces them.

The problem is that the specification is complete. A system designed around assigning courses and evidencing completion will always be organized around courses and completion, because that is what it was built to do well. Store capability is not a course. It is a stream of small, perishable, product-paced things that need to reach a workforce standing up, this week, before the product does.

Asking a compliance system to do that is not unfair to the retailer. It is unfair to the system.

“We should consolidate, not add another system”

Every technology leader has been burned by tool sprawl, and the instinct to consolidate is correct far more often than it is wrong. It deserves a real answer here rather than a brush-off.

The argument for a second channel rests on three things.

The two jobs have opposite success criteria. The compliance record must be immutable, complete, and retained for years. The store channel must be fast, disposable, and current. A single system optimized for both will be governed like the compliance one, because that is the requirement with legal consequences, and the store use case will lose every trade-off.

Consolidation is already failing in practice. Look at the audit below. If four to eight routes into your stores already exist, you do not have one system, you have one system and several unmanaged workarounds. The choice is not between one channel and two, it is between two deliberate channels and one plus a shadow estate nobody reports on.

The publishing populations are different people. Compliance content comes from a small number of authors on a slow cycle. Store content comes from merchandising, brand, visual, operations and loss prevention, weekly. Giving five departments author access to the system of legal record is a worse idea than giving them a channel designed for it.

Where the objection wins: if your store content genuinely amounts to a handful of items a month, and your existing system can get something published within a day, then a second channel is overhead you do not need. Run the audit before deciding, because the answer is a fact about your business rather than a matter of philosophy.

The question retail cannot avoid: who publishes?

In most retailers, the material stores actually need this week does not originate in HR. It comes from merchandising, from brand and marketing, from store operations, from visual, from loss prevention. Each of those functions has something urgent, each has its own idea of how important it is, and each will find a route to the store whether or not there is an official one.

That is why fleets end up with parallel channels: the formal system for compliance, plus email, plus a group chat, plus a printed pack in the back room, plus whatever a regional manager improvised. The associate is left to work out which of five inputs matters most, and the honest answer is usually whichever one their manager mentioned.

The structural fix is not to stop those departments publishing. It is to give them one channel with an explicit hierarchy, so that priority is a property of the system rather than a matter of who shouted last. That single decision does more for execution than any content improvement.

Run the channel audit first

This is the cheapest piece of analysis in the whole subject and almost nobody has done it. It takes a week and it usually settles the argument without a vendor in the room.

  1. Pick one store and one month. Ask the manager to list everything that arrived asking the team to know or do something, and where it came from.
  2. Add the routes head office knows about, then add the ones the store mentions that head office did not know about. The second list is the interesting one.
  3. For each route, record three things: who can publish to it, how long from decision to store, and whether anyone can tell if it was read.
  4. Count the items that arrived with a stated priority. In most audits this is close to zero, which means the store is doing the prioritization, without any of the context needed to do it well.

Two numbers come out of this. The count of channels, which is usually between four and eight, and the share of traffic with no confirmation of receipt, which is usually most of it. Neither is a purchasing decision. Both are governance findings, and they are the findings that determine whether any new tool will work.

What reinvention actually means

Five shifts, each of which can be made independently.

  1. From courses to a stream. Continuous does not mean more. It means smaller pieces arriving at the pace the business changes, rather than a curriculum refreshed annually.
  2. From assigning to publishing. Assignment is a compliance verb. Publishing is an editorial one, and it carries an editorial discipline: someone decides what goes out this week and what is held.
  3. From completion to comprehension. Completion says content was consumed. A short check says something landed, and the difference matters when the next conversation is with a customer.
  4. From HR reporting to field reporting. The person who can act on a weak result is a store or district manager. Data that reaches only the corporate learning team is an archive.
  5. From annual calendars to product calendars. Retail training should follow the buying and launch calendar, because that is when the knowledge is needed and when a gap costs money.

The second of those is the one that changes behavior fastest, and it is free. An editorial discipline means somebody holds a weekly decision about what stores will be asked to absorb, and says no to the rest. Without that, a new channel becomes the sixth unmanaged route rather than the replacement for five.

What should stay exactly where it is

Reinvention rhetoric usually overreaches, so it is worth being specific about what not to touch.

Compliance, safety, harassment, licensing and anything with an audit or legal requirement belongs in the system built to evidence it. Structured onboarding, where a new starter genuinely should sit down and work through material in order, belongs there too. So does anything that needs a permanent record attached to an individual for years.

The retailers who handle this well tend to run both deliberately rather than choosing. One global jeweler kept its LMS for compliance and onboarding and added a floor-focused channel alongside it, and describes the decision as an “and” rather than an “either or.”

Why this lands on store operations, not HR

If capability on the floor is measured by sales KPIs, then the function accountable for those KPIs has to own the tool that moves them. That is store operations.

This is not a reorganization argument. It is about who specifies the requirement. An L&D team asked to serve compliance and capability with one system will optimize for the one it is audited on, which is the correct decision given the incentives. Give store operations its own channel, with its own reporting, and both functions get to be good at their actual job.

It also resolves a budget question that otherwise stalls these programs indefinitely. Capability spend argued from an L&D budget competes with training for the whole organization. The same spend argued from store operations competes with other things that move store KPIs, which is the comparison it should be judged against and the one it tends to win.

The first move

Before changing any system, write down every route by which something reached your stores in the last month, and who sent it. Most retailers doing this exercise find between four and eight channels and no agreed order of priority. That list is the actual problem, and it is a governance decision rather than a purchase.

What to measure once the channel exists is a separate question, and worth settling before launch rather than after.

References

  1. LinkedIn, 2025 Workplace Learning Report. Survey of 937 L&D and HR professionals and 679 learners across North America, South America, Asia-Pacific and Europe. business.linkedin.com

Privacy Preference Center