Most organizations pursuing a skills-based strategy are trying to make skills more visible.
They are building taxonomies, mapping skills to roles, introducing talent platforms, and asking employees to update profiles.
But on the frontline, skills have never been invisible.
Every shift depends on managers knowing who can operate a machine, complete a safety-critical task, train a new employee, handle an exception, serve a customer, or cover an unexpected staffing gap.
The frontline already runs on skills.
The challenge is making that knowledge more consistent, transferable, and useful across people, shifts, locations, systems, and changing business conditions.
That tension shaped our recent Skills Roundtable panel with Joe Dunlap of CJK Group and JD Dillon, author of The Frontline Enablement Playbook.
Our discussion surfaced an important lesson for any organization pursuing a skills-based strategy:
Skills are foundational—but the real goal is performance reliability.
Skills and capability are not the same thing
Organizations often use the words skill, capability, readiness, and performance interchangeably.
They are not the same.
Joe described skills as the foundation. Skills contribute to capability, but possessing a skill does not guarantee that someone will perform reliably under real working conditions.
Two employees may complete the same training and demonstrate the same basic skills. Yet one may consistently meet expectations while the other struggles when production pressure increases, equipment changes, an exception occurs, or the normal workflow breaks down.
As Joe explained:
“A skill is a skill, but it doesn’t mean that you’re capable.”
That distinction matters because many skills initiatives stop too early.
They measure:
- Training completion
- Knowledge
- Credentials
- Self-reported proficiency
- Exposure to content
But they do not establish whether someone is ready to perform a specific task, under specific conditions, to the required standard.
The better question is not:
Does this person possess the skill?
It is:
Can this person use that skill to produce the required outcome reliably?
The frontline has always been skills-based
JD challenged the assumption that organizations need to introduce skills-based thinking to frontline operations.
Managers have been making skills-based decisions for decades.
They use capability to determine:
- Who gets scheduled
- Who can operate particular equipment
- Who can cover another position
- Who needs cross-training
- Who is qualified for safety-critical work
- Who is ready for additional responsibility
- Who can help the operation adapt when something changes
The problem is that this knowledge is often informal.
It may live in a spreadsheet, on a certification board, in a scheduling system—or simply in the heads of experienced managers.
That creates risk.
When a knowledgeable manager leaves, the organization may lose its understanding of who can do what. A new manager inherits the same people and processes but lacks the capability insight needed to deploy the team effectively.
The opportunity is not to make the frontline skills-based.
It already is.
The opportunity is to capture and operationalize what frontline leaders already know so that the business does not depend on one person’s memory.
Start with the work—not the skills list
Many skills initiatives begin by selecting a library, building a taxonomy, or mapping skills to job titles.
Joe and JD argued for a different starting point:
Begin with the work and the outcomes it must produce.
Joe outlined a practical sequence:
- Define the expected performance outcome.
- Identify the capabilities required to produce that outcome.
- Determine the skills that support those capabilities.
JD described a similar approach through the lens of tasks.
Work can be understood as a series of tasks that must be completed to a defined standard. Instead of beginning with an abstract concept such as “customer service,” organizations can identify the moments that matter and define what effective execution looks like in each one.
A cashier, door greeter, equipment operator, housekeeper, and healthcare worker may all need customer service capability. But how that capability appears in the work is different for each role.
Employees often struggle to translate broad principles into action when the pressure is high.
Task-based enablement closes that gap.
It answers:
- What must the person do?
- Under what conditions?
- What decisions must they make?
- What exceptions are likely?
- What standard must they meet?
- What support will they need in the moment?
This makes skills more concrete—and more measurable.
Job titles often conceal major differences in the work
Even frontline jobs that appear standardized can vary significantly by location, equipment, product, workflow, and operating conditions.
Joe shared an example from the print and publishing industry.
A role may have the same title across multiple plants. But the employee may work with different equipment, produce different products, follow different workflows, and operate against different quality expectations.
The title is the same.
The capability requirements are not.
A generic enterprise skills model may look elegant while obscuring the differences that determine actual performance.
This is one reason local context matters so much in frontline skills work.
Organizations need enough consistency to make skills data transferable and useful. But they also need enough specificity to reflect how the work is truly performed.
The goal is not to document every possible variation.
It is to identify which variations meaningfully change readiness, risk, quality, productivity, or safety.
The SOP is not the work
Standard operating procedures provide an essential baseline.
But they rarely capture the full reality of frontline performance.
Real work includes:
- Equipment failures
- Staffing shortages
- Unpredictable customers
- Delayed deliveries
- Weather disruptions
- Quality problems
- Safety concerns
- Local operating differences
- Unusual exceptions
As JD noted, there is no “normal day” in many frontline environments.
Organizations can easily mistake the documented process for the lived reality. That creates training and support systems designed for conditions that do not exist.
Job trainers, experienced employees, and frontline managers are therefore critical sources of insight.
They know where the SOP needs context.
They understand the exceptions.
They recognize what “ready” looks like in a specific location.
And they can distinguish between someone who can demonstrate a task in a controlled environment and someone who can execute it reliably in the work.
Frontline managers are the connection point—and the constraint
Frontline managers connect corporate strategy to everyday execution.
They are expected to:
- Deliver production results
- Manage staffing
- Solve operational problems
- Coach employees
- Reinforce training
- Validate readiness
- Lead change
- Support corporate initiatives
Yet many are promoted because they were strong individual performers, not because they were prepared to manage people.
They are frequently thrown into the role with little warning or formal preparation.
JD described frontline managers as burned out, overwhelmed, and underprepared. Joe shared that in an internal study, more than 90% of managers were operating primarily in a firefighting mode.
This creates a critical design constraint.
Organizations cannot continue adding initiatives to managers’ workloads and assume they will activate them.
JD summarized the principle plainly:
“Don’t add something to the plate unless you’re taking something off the plate.”
Effective manager enablement should make the work easier.
That might include:
- Faster access to answers and guidance
- Better visibility into employee readiness
- Connections to experienced manager peers
- Tools that simplify staffing and cross-training decisions
- Support embedded into existing meetings and workflows
- Clear alignment between development activity and operational priorities
Structured programs may still have a role. But they cannot be the default solution for managers whose days are shaped by immediate production demands.
Skills data becomes valuable when it improves operational decisions
Collecting frontline skills data is not the objective.
The value comes from using that data to improve decisions.
Joe described how his organization is using capability information to support:
- Staffing
- Cross-training
- Movement between machines and work areas
- Succession planning
- Talent pipeline decisions
- Career mobility
- Targeted hiring and development
JD highlighted additional use cases involving risk mitigation and workflow control.
In some environments, employees cannot access equipment, systems, or particular assignments unless their certifications and readiness are current.
Capability data can also help managers answer simple but important questions:
- Who is qualified to perform this task?
- Who can safely cover this shift?
- Who has adjacent capabilities?
- Where are we dependent on one person?
- Where should we invest in cross-training?
- Which capability gaps create operational risk?
When skills data is connected to scheduling, staffing, workflow, certifications, mobility, and workforce planning, it becomes part of how the business operates.
When it remains trapped in an LMS or talent platform, its value is limited.
Cross-training is a business agility strategy
Cross-training is often positioned as a learning activity.
On the frontline, it is much more than that.
A worker who can perform several tasks gives the manager greater flexibility when someone calls out, demand changes, equipment fails, or priorities shift.
That is business agility in practical form.
But cross-training requires time and creates short-term disruption. Organizations may need to remove both the learner and trainer from productive work. In unionized environments, added capability may also affect pay, classification, or contractual obligations.
To justify that investment, HR and L&D must connect cross-training to operational outcomes.
The conversation is no longer:
Can we make time for training?
It becomes:
Will this investment reduce staffing risk, increase flexibility, improve productivity, or strengthen our talent pipeline?
As JD observed:
“We’re not talking about learning or training anymore. We’re talking about business agility and readiness.”
Define what “ready” means
One of the most important questions raised during the panel was:
How do we define ready?
Training completion does not automatically mean someone is ready to perform.
Readiness may require an employee to demonstrate that they can complete a task:
- Safely
- At the required speed
- At the required quality level
- Without assistance
- Under realistic working conditions
- While responding appropriately to common exceptions
The relevant measures are typically already defined by the business.
Depending on the environment, they may include:
- Safety
- Quality
- Productivity
- Waste
- Throughput
- Machine uptime
- Customer service
- Compliance
- Error rates
Skills and readiness measures should connect directly to those outcomes rather than creating a separate set of L&D metrics.
The hard work is often making tacit expectations explicit.
Managers may know readiness when they see it, but they may never have documented exactly what distinguishes a ready employee from one who still requires support.
That definition is essential if organizations want skills data that can be trusted and used at scale.
Frontline workers are not resistant to learning
Frontline employees are sometimes described as disengaged from learning.
The panel challenged that assumption.
Workers often want development, greater earning potential, mobility, and access to new opportunities.
But they are selective about what earns their limited time and attention.
A comment from the session captured the frontline prioritization test:
“Does it relate to my pay, or is it going to blow something up in my day today? If not, I can’t prioritize it.”
Employees may not object to learning.
They may object to irrelevant content, inaccessible systems, inconvenient timing, or training that creates no visible benefit.
JD drew an important distinction:
“There’s a huge difference between ‘I don’t want to learn’ and ‘I don’t want to complete the thing you’re asking me to do.’”
Organizations can improve engagement by:
- Connecting learning to real work and career opportunity
- Scheduling protected development time
- Using relevant, task-based content
- Embedding support into existing routines
- Providing access through technology workers can actually use
- Making the benefit clear to the employee and the operation
The answer is not always smaller or shorter learning. Some topics require time, practice, and sustained attention.
The larger principle is that learning must fit the operational context.
What HR and talent leaders can do next
The panel discussion suggests six practical starting points:
- Begin with one important outcome
Select a business outcome such as safety, quality, productivity, staffing flexibility, or time to readiness.
- Identify the work that produces it
Map the tasks, decisions, handoffs, exceptions, and local conditions that influence performance.
- Define readiness
Clarify what someone must be able to do, under what conditions, and to what standard.
- Work backward to capability and skills
Use skills to explain what supports reliable execution—not as the starting point or end goal.
- Make the data operational
Connect capability information to the systems and people making staffing, scheduling, development, risk, and mobility decisions.
- Reduce manager friction
Make it easier for frontline managers to support people and make decisions. Do not create another disconnected initiative.
Final takeaway
The frontline provides one of the clearest demonstrations of what skills-based strategy can become.
Skills are not theoretical.
They affect who works, what they can do, what they earn, how quickly the organization can adapt, and whether work is completed safely and reliably.
But skills are only one part of the performance system.
The organizations that make the greatest progress will not be those that build the largest taxonomies or collect the most data.
They will be the ones that connect skills to real work, define readiness clearly, support managers realistically, and use capability insight to improve the decisions that matter.
Because the real question is not whether skills exist.
It is whether those skills produce reliable outcomes in the work.
Join a Future Skills Roundtable
Each month, Richardson Consulting Group convenes HR, Talent, L&D, Workforce Planning, People Analytics, and business leaders for candid discussions about the practical realities of enterprise skills strategy.
These are not polished showcase presentations or vendor demonstrations. They are peer conversations about real work: what organizations are trying, where they are struggling, what they have learned, and what they would do differently.
View upcoming Skills Roundtables: https://richardsonconsultinggroup.com/skills-roundtables/
Leaders who would like early access to future sessions can also request to join the Enterprise Skills Advisory Circle, a curated peer community focused on the real work of scaling skills strategy.
There is no cost to participate.
Request access to the Advisory Circle: https://richardsonconsultinggroup.com/enterprise-skills-advisory-circle/