The learning department gets some strange cred — since a whole lot of performance challenges often get downloaded right there.

Hear me out. Managers are not holding the conversations they were expected to hold. Employees are not consistently using the new process. Information is not moving properly between teams. A strategy that seemed perfectly sensible in the boardroom is producing only a faint impression in the places where the work actually happens. Yup, send it to learning. Because of course — someone wonders whether people have understood what is expected of them. Perhaps the communication was not clear enough. Perhaps the earlier training did not stick. Perhaps a refresher is required, preferably one that can be scheduled quickly and completed before the next reporting period.

The request usually sounds practical because it arrives with a solution already attached. What is less clear is whether anyone has adequately established the problem.

Organizations frequently make a quiet leap from observing that people are not doing something to concluding that they do not know how to do it. The leap is understandable. Knowledge and skill are easier to discuss than the many conditions that surround performance, and training is a visible intervention that can be commissioned, delivered and counted. It produces attendance records, completion rates and, with a little effort, reassuring charts.

Conditions are less accommodating. They are distributed across workflows, management habits, competing targets, technology, authority, workload, local norms and the small consequences people learn to anticipate after spending time inside an organization. They do not usually belong to one department, and they rarely fit neatly into a calendar invitation.

This helps explain why a circular hole identified as a capability deficit so often receives a square-peg learning response. The organization sees an outcome it dislikes, notices a behaviour that is missing, and moves directly toward instruction. The possibility that people may already possess the relevant capability, but operate in circumstances that make its use difficult or unwise, receives much less attention.

That possibility matters because employees are generally more observant than organizations sometimes imagine. They notice which priorities are discussed and which are measured. They notice whether a manager who follows the new process is supported or left exposed. They notice whether raising a concern produces action, delay or irritation. They notice when an expected behaviour takes more time but the performance target remains unchanged.

In many instances, the behaviour an organization dislikes may be entirely rational within the conditions it has created.

A manager may know how to conduct a difficult performance conversation but also know that senior leadership has previously reversed such decisions at the first sign of discomfort. A frontline employee may understand a new safety procedure but recognize that using it will interrupt production and produce an unpleasant exchange with a supervisor. A team may have been trained thoroughly in a new digital process while continuing to use an unofficial workaround because the approved system adds effort without improving the result.

In each case, more learning may be possible. It may even be helpful. But it is unlikely to resolve the problem because the problem is not simply that people have failed to absorb the lesson. The surrounding organization is teaching a more persuasive lesson every day.

Following the Problem in the Other Direction

One way to interrupt this reflex is to begin at the mission result and trace backward, rather than beginning with the proposed course and working forward.

I have been calling this the Conditions-to-Mission Trace. It is a simple way of testing whether an apparent capability problem is actually best explained by missing knowledge or skill, by the conditions surrounding performance, or by some combination of the two.

The Trace begins with the organizational result that is at risk. Customer concerns may be recurring. Quality problems may remain unresolved. Managers may be delaying necessary conversations. Employees may be failing to escalate emerging risks. The first task is to describe the result clearly enough that everyone understands why it matters beyond the learning function.

From there, the inquiry moves closer to the work. What operational consequence is contributing to the result? What is happening, or failing to happen, in the everyday process? Perhaps customer cases are being transferred without complete information. Perhaps supervisors are postponing difficult decisions. Perhaps small safety concerns are being managed informally until they become larger ones.

The next question is behavioural: what would people need to do differently for the operational consequence to improve? This sounds straightforward, although organizations often discover that their expectations are expressed through abstractions such as accountability, leadership, communication or ownership. These may be worthy aspirations, but they are difficult to diagnose until they are translated into observable behaviour.

A manager who is expected to “show accountability” may actually need to raise a specific concern within five working days, clarify the expected standard, agree on a next action and return to the conversation. An employee expected to “communicate better” may need to enter complete information before transferring a case and identify any unresolved risk. Precision matters because it becomes difficult to determine whether people have the necessary capability when the desired behaviour remains foggy.

Only then does the Trace ask whether people can actually do what is required.

The evidence may show that they cannot. They may lack important knowledge, skill, confidence or judgment, in which case a learning intervention is entirely appropriate. Training should not be treated as the villain in this discussion. It is simply one response among several, and it works best when directed toward a problem it can reasonably solve.

Sometimes, however, people can explain the process, demonstrate the skill or perform the behaviour successfully in certain circumstances. They may do it under one manager but not another, during quiet periods but not under pressure, or in a practice setting but not when the political or operational consequences become real. That variation should make us curious.

If a person can perform the behaviour somewhere, the organization needs to be cautious before declaring a general capability deficit.

The investigation must then turn toward conditions. Do people have the time, authority, information and tools required? Does the workflow accommodate the expected behaviour? Do managers reinforce it? Are performance measures aligned with it? What happens to someone who follows the new expectation, and what happens to someone who quietly continues with the old way?

This last question is particularly useful because it reveals the practical intelligence behind non-application. People may not be resisting change in any dramatic sense. They may simply have learned that the desired behaviour creates delay, conflict, visibility or risk, while the familiar behaviour allows the work to continue and attracts little consequence.

The organization may be asking people to behave differently while leaving untouched the reasons they behave as they do.

Making Conditions Visible to the Mission

The value of the Trace is not merely that it identifies barriers. Organizations already have many lists of barriers, usually stored somewhere near their lists of lessons learned. Its more important contribution is to connect conditions to the mission result in a way that leadership can see and act upon.

The core statement is intentionally simple: Because this condition exists, people tend to behave this way, producing this operational consequence and affecting this mission result.

Consider an organization concerned that supervisors are not responding promptly to employee safety concerns. The initial conclusion may be that supervisors require refresher training in reporting procedures. Yet a closer look might show that supervisors understand the process quite well. They also know that stopping work creates immediate production pressure, that authority to do so is unclear, and that leaders tend to scrutinize lost output more closely than delayed safety reporting.

The Trace might read: Because production interruption is immediately visible and negatively consequential, while delayed reporting attracts little attention, supervisors tend to manage concerns informally, which reduces early hazard visibility and increases the organization’s exposure to preventable incidents.

That statement does not absolve supervisors of responsibility, nor does it prove that capability is perfect. It does, however, present a more credible account of the behaviour than the assumption that everyone has forgotten (or messed up!) the training.

It also moves the issue into a different executive conversation. The question is no longer merely whether the course was effective. It is whether the organization’s operating conditions are suppressing the information and behaviour required to achieve an important safety outcome.

The same logic can be applied elsewhere. If managers delay performance conversations because they expect little organizational backing, the result may be persistent underperformance and larger employee-relations problems. If service staff omit important documentation because the system is cumbersome and speed is heavily measured, the result may be repeat work and poor customer resolution. If employees fail to raise emerging risks because previous escalation has produced blame rather than action, the result may be slower recognition of threats to strategy or operations.

In each case, the consequence makes the condition harder to dismiss as a learning department concern.

This is important because learning teams often have sight into the symptoms while possessing little authority over the causes. They are asked to build capability, yet the use of that capability depends on decisions made elsewhere: workload, systems, incentives, manager expectations, executive priorities and the consequences attached to action.

When results remain weak, the visible intervention is easy to invoke and blame. The course was delivered, people attended, and the desired behaviour did not appear consistently. It is tempting to conclude that the knowledge failed to transfer. Increasingly, the impacts of a single learning program can be tested/validated.

The Conditions-to-Mission Trace introduces a more demanding question: did the organization create the conditions in which transfer was likely, useful and rational?

That question does not require a large diagnostic exercise. A useful Trace may be completed through a short conversation, provided participants are willing to resist the convenience of the original explanation. What result is not improving? What is happening in the work? What must people do differently? What evidence shows that they cannot? Where are they already able to do it? What makes the desired behaviour difficult or costly? What small test might help distinguish a capability deficit from a conditions failure?

A small test is often preferable to a confident argument. One team might be given clearer authority, easier system access, stronger manager reinforcement or temporary relief from a conflicting target. If the desired behaviour improves without further training, the organization has learned something important about the cause of the problem. If it does not, the case for additional capability development may become stronger.

This is not a search for a tidy either-or answer. Many organizational problems contain both capability and conditions elements. People may need better skill while also requiring a workplace in which using that skill is supported. The purpose of the Trace is not to force a binary conclusion, but to prevent learning from becoming the entire explanation simply because it is the intervention most readily available.

There is a broader discipline in this. Organizations make better decisions when they improve the quality of the explanation that precedes the solution. A training request may ultimately remain a training request, but it should arrive there after the behaviour, capability and surrounding conditions have been considered, not before.

The next time an organization concludes that people need to learn something again, it may be worth pausing before the course is commissioned. The more useful first question may be whether people truly lack the capacity to act — or whether the organization has made the desired action harder than it realizes.