Organisations rely on simplified representations and proxies to make frontline work understandable and manageable. Metrics, targets, checklists, and indicators reduce complexity into something actionable. These tools are essential for coordination and decision-making, but become limiting when we begin to treat them as if they fully capture the underlying context they stand in for. To improve frontline interventions, we first need to recognise what these proxies leave out, and how that missing context shapes performance in practice.
Why we simplify work
Organisations need to simplify work in order to manage it. No organisation can observe and account for every interaction, decision and variation that occurs across hundreds or thousands of employees each day. Instead, we create representations of work that make expectations visible and performance manageable.
Job descriptions define responsibilities. SOPs and processes describe how work should be performed. Competency frameworks describe what people need to know and be able to do. Training requirements establish what should be learned, while performance measures, experience requirements and service standards give organisations ways to assess whether expectations are being met.
These are not weaknesses in how organisations manage work. They are necessary.
This is particularly true on the frontline, where organisations need to create consistent performance across large numbers of employees, multiple shifts and locations, different managers and changing customer demands. Safety, compliance and operational requirements add further constraints. Without some form of standardisation, it would be extremely difficult to define what employees should know, what they should do and what good performance should look like.
But the usefulness of these representations comes partly from what they remove. A process cannot describe every condition in which it will be applied. A competency framework cannot capture every judgement an employee will make. A performance measure cannot explain everything that produced the result being measured.
The map has to simplify the territory. The problem begins when we forget that it is a map.
These simplifications do more than describe work. They shape how we think about what performance requires and, ultimately, where we choose to intervene when performance falls short.
So, before we design another training intervention, refine another process or introduce another performance measure, there is a more fundamental question worth asking:
Are the ways we describe and measure frontline work still telling us enough about what it takes to perform it well? To explore this question further, we should examine several underlying assumptions that shape how frontline work is currently understood and measured.
Frontline readiness: Knowing the job means being ready to do the job
Knowledge is one of the most obvious foundations of frontline performance. Employees need to understand the procedures they are expected to follow, the products or services they work with, relevant safety requirements and what the organisation expects from them. Without that knowledge, reliable performance becomes difficult.
It therefore makes sense that organisations invest heavily in transferring and assessing knowledge. We provide induction, product training, compliance courses and procedural instruction, then use assessments or observation to establish whether employees understand what they have learned. These activities provide useful evidence that someone has been prepared for the work.
The difficulty comes when evidence of knowledge becomes evidence of readiness.
A frontline employee may know exactly how a process should work under normal conditions. The work itself, however, rarely presents one requirement at a time. Customers interrupt. Priorities compete. Workloads change. Equipment creates problems. Time pressure increases. Employees must apply what they know while responding to what is happening around them.
This creates an important distinction. Knowledge can answer the question, “What should I do?” Frontline performance frequently requires an answer to a more immediate question: “What should I do now?”
The second question requires more than recalling the correct procedure. The employee may need to recognise which requirement applies, determine what takes priority, respond to an unexpected situation or know when to escalate. The knowledge remains essential, but its value is realised only through its application under the conditions in which the work occurs.
For L&D, completion and knowledge assessment can therefore tell us whether someone has learned something. Still, they provide limited evidence of whether that person is ready to perform reliably when conditions become less predictable.
Knowledge remains a foundation of frontline development. We need to be careful not to ask it to prove more than it can. Knowing the job is evidence of preparation. Readiness is demonstrated in how that knowledge is applied when performing the work.
Understanding frontline work: Documented work describes the work
Organisations need ways to describe those conditions and the work that takes place within them. Job descriptions establish responsibilities, process maps show how activities connect, and SOPs and workflows provide employees with a common understanding of how tasks should be performed. Without these representations, coordinating work across people, teams and locations would become extremely difficult.
They also give L&D something concrete to work from. When we need to determine what someone should learn, we naturally look at the tasks they perform, the processes they follow and the competencies associated with their role. These provide a practical starting point for deciding what knowledge and skills the work appears to require.
But documented work is necessarily a simplified version of performed work.
Consider a relatively straightforward frontline task such as checking a hotel guest into their room. The process can describe the required steps, information to collect, systems to use and service standards to follow. It cannot fully describe the conditions under which every check-in will happen.
One employee may perform the task during a quiet period with a returning guest. Another may perform the same documented task while several guests are waiting, the system is responding slowly, and a first-time visitor needs additional assistance. The task has not changed on paper, but what successful performance requires from the employee has.
Workload, interruptions, equipment, customer behaviour, coordination with colleagues and competing priorities are therefore not simply external factors surrounding the work. The conditions under which work is performed are part of the work itself because they influence how it must be performed.
Job descriptions, SOPs and process maps remain essential. The limitation lies in treating them as complete descriptions rather than useful representations. Understanding what someone is expected to do is not necessarily the same as understanding the work they must actually perform.
Once conditions become part of our understanding of work, another question follows. If those conditions change, how does an employee determine what the process requires in the situation at hand?
Process and judgement: Clear processes remove the need for judgement.
Processes exist partly to answer that question by removing uncertainty from work. They establish the correct procedure, define safety boundaries, clarify escalation paths and create common expectations about quality and performance. In many frontline environments, reducing unnecessary discretion is not only desirable but essential.
This is particularly important where mistakes have significant consequences. A safety procedure should not depend on an employee inventing an appropriate response in the moment. Compliance requirements, equipment operating procedures and financial controls may similarly require clearly prescribed actions. In these situations, the process deliberately limits variation.
But a process does not execute itself.
Someone still has to recognise the situation in front of them and determine how the process applies. Is this the situation covered by the procedure? Which requirement applies when two priorities compete? Is something unusual enough to require escalation? Does the employee have the authority to continue, or should the work stop?
Judgement is therefore often present even when the process is working exactly as intended. The employee interprets the situation, identifies the relevant requirement and takes the prescribed action.
This distinction matters because judgement should not be confused with unrestricted discretion. Exercising judgement does not necessarily mean departing from the process or choosing a preferred way of working. In safety-critical situations, good judgement may mean recognising that the procedure must be followed exactly, or that work cannot continue until someone with greater authority intervenes.
Judgement often sits between the situation and the appropriate application of the process.
Knowing whether employees can recall or demonstrate a procedure is therefore important, but it may not tell us whether they can recognise when and how that procedure should be applied. Processes can reduce the amount of judgement required without removing judgement from the work entirely.
If reliable performance depends partly on this ability to recognise, interpret and respond to different situations, the next question is how that judgement develops over time.
Experience and development: Experience is evidence of development
Experience is one obvious part of the answer. Repeated exposure gives frontline employees opportunities to practise, encounter different situations, recognise patterns and learn from the consequences of their decisions. Over time, this can produce better judgement and more reliable performance.
There is therefore good reason organisations use experience as an indicator of proficiency. Someone who has worked in a role for five years has usually encountered situations that a new employee has not. They may recognise problems earlier, anticipate what is likely to happen next and respond to familiar situations with greater confidence.
But time served measures exposure. It does not necessarily measure development.
Two frontline employees can spend five years in similar roles and develop very differently. One may have worked across different shifts, dealt with increasingly complex situations, received useful coaching and feedback, taken on additional responsibilities and learned from mistakes. Another may have spent much of that time performing familiar work in largely the same way.
Repetition itself can work in either direction. It can strengthen good practice and deepen understanding, but it can also make shortcuts, inefficient practices or poor judgement increasingly habitual. The number of times someone has performed an activity tells us little about which of these has occurred.
If years of experience become our measure of development, we may therefore overestimate some employees while overlooking the growth of others whose shorter experience has been more varied, challenging or developmental.
Experience creates an opportunity for development. It is not evidence that development occurred.
That does not make experience a poor indicator. It means we need to look beyond duration when trying to understand capability and performance. Feedback, increasing responsibility, exposure to different situations and observable changes in how someone performs can tell us more about what those years have produced.
The more useful question is not only, “How much experience does this person have?” It is, “What has that experience enabled them to become better at?”
This becomes particularly important when organisations try to create consistent performance across many employees with different levels and types of experience.
Standardisation and performance: Standardisation creates consistency
Standardisation is fundamental to managing frontline work at scale. Common processes and standards allow organisations to establish clear expectations across employees, shifts and locations while reducing unnecessary variation in how work is performed. For safety, compliance and quality, some variation should be eliminated.
A customer should not receive an unsafe service because they visited a different location. A critical procedure should not depend on which employee happens to be working. Organisations therefore have good reason to associate greater standardisation with more consistent performance.
But consistent performance does not necessarily require identical execution.
Frontline conditions vary. Customers arrive with different needs. Workloads fluctuate. Equipment fails. Priorities compete. Even where the required standard remains unchanged, the response needed to achieve it may differ.
Consider a hotel check-in. The information that must be captured, security requirements and service standards may be consistent for every guest. How an employee communicates may legitimately differ between a returning guest who knows the property and a first-time visitor who needs additional guidance. The standard has not changed. The employee has adapted within it.
Appropriate variation is not the same as unrestricted discretion. Some requirements are non-negotiable because variation introduces unacceptable safety, compliance or quality risks. Other parts of the work allow bounded judgement about how the standard should be applied as conditions change.
For L&D and operational leaders, the distinction matters because training for consistency can easily become training for sameness. If we focus only on reproducing identical actions, we may overlook whether employees understand what must remain fixed, where judgement is required and what boundaries govern their decisions.
Consistency does not necessarily mean sameness.
Good standardisation makes those boundaries clear. It controls variation that creates risk while allowing appropriate variation where reliable performance requires it. The objective is not simply to make everyone work identically, but to ensure that what matters remains consistent even when the conditions of work do not.
Taken together, these five assumptions now reveal something broader about how organisations understand frontline performance.
What the five assumptions have in common
Each assumption concerns something different: knowledge, documented work, processes, experience and standardisation. But each also involves something relatively visible and manageable being used to help us understand something that is harder to observe directly.
A pattern begins to emerge:
- Knowledge as a proxy for readiness
- Documented work as a proxy for work as performed
- Process compliance as a proxy for appropriate action
- Experience as a proxy for development
- Standardisation as a proxy for consistent performance.
There is nothing inherently wrong with these proxies. Organisations need practical ways to define expectations, coordinate work, assess employees and manage performance across large frontline workforces. We cannot observe every decision an employee makes or account for every condition under which work occurs.
The problem appears when the proxy stops being treated as an indicator and becomes mistaken for the thing it is intended to represent.
A completed assessment can demonstrate knowledge without demonstrating readiness. Following a documented process can demonstrate compliance without explaining whether the employee interpreted the situation appropriately. Years of service demonstrate exposure without showing what has developed through that experience.
What organisations choose to observe also influences where they intervene. If knowledge is the problem we can see, we train. If process compliance is the problem we can measure, we reinforce the process. If experience is our indicator of proficiency, we assume development will come with time.
Those responses may be entirely appropriate. But they may also address the representation of the performance problem rather than its underlying cause.
A proxy becomes dangerous when we stop treating it as a proxy.
The practical challenge is not to abandon these measures and representations. It is to recognise their limits and test whether they are giving us enough information to understand the performance problem before deciding how to address it.
Understanding work before trying to improve it
Organisations spend considerable effort trying to improve frontline performance. We introduce training, implement technology, refine processes, strengthen management practices and develop employee initiatives. Each intervention may have value, but each also rests on assumptions about what the work requires and what is preventing better performance.
That makes the quality of the diagnosis important. If our model of the work captures only what is easily documented, observed or measured, we may design an effective intervention for an incomplete version of the problem. More training will not necessarily address a problem of judgement. Tighter processes will not necessarily resolve changing operating conditions. More experience will not automatically produce development.
The answer is not to discard job descriptions, SOPs, competency frameworks, assessments or standards. Organisations need them to make work visible and manageable. But we should recognise them for what they are: useful representations of work, not the work itself.
Improving frontline performance therefore starts one step earlier than choosing the intervention. Before asking what training people need, what process should change or what technology might help, we first need to establish whether our understanding of the work is sufficient to diagnose what is affecting performance.
Are the ways we describe and measure frontline work still telling us enough about what it takes to perform it well?
