How we learn from work and what we often miss

In most workplaces, outcomes travel faster than understanding. A project concludes, results are noted, and the organisation moves on. Success is celebrated, failure is reviewed, and both are quickly absorbed into the next cycle of execution. The underlying assumption is rarely questioned: that outcomes, by themselves, contain lessons. Recent research discussed in MIT Sloan Management Review suggests otherwise. The idea of “learning from execution” challenges the tendency to treat results as self-explanatory and argues that without deliberate analysis, both success and failure can mislead. At the centre of this argument is a deceptively simple distinction. Achieving a goal is not the same as understanding why it was achieved. Falling short is not the same as understanding what went wrong. Yet in practice, these two are often conflated.

Consider how success is typically handled. A campaign performs well, a client approves a proposal, and a target is exceeded. The immediate response is to scale. More resources are allocated, similar strategies are replicated, and the approach is institutionalised. The logic appears sound: something worked, so it should be repeated. What is often missing, however, is clarity on causation. A campaign might succeed because it coincided with favourable timing. A proposal might be accepted because it aligned with a decision already in motion. A target might be met due to external conditions rather than internal execution. When these variables are not examined, success becomes difficult to reproduce. What appears to be a reliable strategy may in fact be an isolated outcome.

Failure follows a different, but equally problematic, trajectory. When an initiative does not deliver, the response is usually corrective. Reviews are conducted, accountability is assigned, and attention shifts toward preventing repetition. While this process is necessary, it often stops short of identifying what remains useful within the failure. An unsuccessful project can still contain elements worth preserving. An idea may be sound but poorly framed. A strategy may be viable but mistimed. A process may reveal insights about constraints or audience behaviour. When failure is treated as a closed case rather than a source of information, these elements are lost.

The framework emerging from the Sloan discussion attempts to bring discipline to this ambiguity. It suggests that outcomes fall into four broad categories. Some are true “hits” – successful and clearly understood. Others are “lucky” – successful, but without clarity on causation. Some are “learning” outcomes – unsuccessful, but rich in insight. And finally, there are “defeats”, where neither success nor understanding is achieved. This distinction matters because it introduces discipline into what is often an instinctive process. Instead of reacting to outcomes, it requires organisations to pause and examine them. A true hit can be scaled with confidence. A lucky outcome calls for restraint, not enthusiasm. A learning outcome deserves deeper attention, not dismissal. A defeat signals the need to rethink more fundamentally.

What follows from this is not just interpretation, but action. The research outlines a structured approach called DIRS: Decompose, Interpret, Reward, Scale. Decomposition requires breaking work into its components, rather than treating it as a single outcome. Interpretation focuses on identifying which of those components actually drove results. Rewarding shifts attention away from outcomes alone and toward behaviours that generate insight. Scaling, crucially, comes last, once there is confidence in what is being repeated. This sequence challenges a common instinct in workplaces, where scaling often happens immediately after success. By placing it at the end, the framework introduces a pause between outcome and replication. That pause is where clarity is built.

For individuals, particularly those in the early stages of their careers, this has practical consequences. Much of professional growth is assumed to come from exposure. The more one does, the more one learns. Yet exposure without interpretation has limits. Take a common scenario. A presentation is well received. The presenter may conclude that their approach was effective. But without analysing the structure of the argument, the sequencing of information, or the specific moments that engaged the audience, the success remains difficult to replicate. The next presentation may follow a similar format without achieving the same result. Conversely, when a presentation fails to resonate, the instinct may be to attribute it to nerves or insufficient preparation. While these factors may play a role, they do not fully explain the outcome. A closer examination might reveal that the central argument lacked clarity, or that the supporting data did not align with the audience’s expectations. Without identifying these factors, the lesson remains incomplete.

The distinction between outcome and understanding becomes particularly important over time. Professionals who rely on outcomes alone may improve their efficiency, but not necessarily their judgment. They complete tasks faster, yet continue to encounter similar challenges. Patterns remain unrecognised, and improvement becomes incremental.

This process does not require elaborate systems. It begins with asking more precise questions. After completing a task, instead of settling for a general assessment, it is more useful to identify specific drivers. What element had the greatest impact on the result? At what point did the direction of the work shift? Which assumption proved inaccurate? Such questions shift attention from results to reasoning. They transform experience into something that can be applied, rather than simply recalled. Documentation further strengthens this process. In environments where tasks move quickly, insights can fade just as quickly. Without personal reflection, feedback addresses only part of the picture. When combined with self-analysis, however, it becomes more precise and actionable. As such, growth depends on how experience is processed.

In many organisations, learning is described as a priority. Yet it often exists as an abstract goal rather than a structured practice. The idea of learning from execution suggests that learning must be embedded into the way work is reviewed. It must be treated as a process, not an assumption. For young professionals, this offers a clearer path to development. The value of work lies not only in its completion, but in the insight it generates. Two individuals may share similar experiences, but the one who examines those experiences more closely will progress further. Work, in this sense, is no longer a sequence of tasks. It is a series of opportunities to understand how decisions shape outcomes. Without that understanding, experience accumulates without direction. With it, experience becomes a source of deliberate growth.