Folded, aligned pieces of paperboard sit beside a metal right-angle guide with a blue face, resting in a wooden holder.

What to learn from a project that went well

A successful project helps us recognize ways of working worth carrying forward. Learning from it requires attention to everyday work, its adjustments, and what deserves care after the project ends.

Alejandro Mayorga9 min read

When a project ends well, it is understandable to want to let it end. There was work, decisions to be made, moments of fatigue, and, finally, something to feel satisfied about. Revisiting what happened can seem like an unnecessary way of prolonging it, as though joy had to undergo scrutiny before it could be legitimate. There is also a simpler reason to move on: what went well no longer demands attention. The next problem, by contrast, has a date, people responsible for it, and some urgency. Between that relief and the next task, a quiet opportunity can be lost: recognizing with enough precision which parts of the experience are worth taking with us.

The value of that pause lies in the experience the project still holds. Along the way, there were things people learned to do together, difficulties they came to understand, and ways of acting that found their place. Once the project is over, all of this fits all too easily into broad terms: commitment, collaboration, good communication. These are reasonable words, but they leave much unsaid. Two teams may use them to describe very different work. To learn something from success, we need to look more closely at what those words name: who was able to spot a difficulty in time, how that warning reached someone who could intervene, and what changed as a result.

There is evidence that it is worth extending our attention to these episodes. In a study by Shmuel Ellis and Inbar Davidi (opens in a new tab), published in 2005, soldiers carrying out successive navigation exercises improved more when they reviewed both their successes and failures than when they examined only their failures. This was a quasi-experiment in a military training setting, with defined tasks and outcome criteria; applying it without qualification to any organization would go too far. Over the course of the reviews, participants also developed richer explanations of successful episodes. The study thus provides a concrete basis for taking seriously what can be learned by examining a success.

In a project, preserving something can be a much less obvious decision than correcting it. An error gives us something we want to leave behind. A success requires us to choose within an experience that, for the moment, does not seem to need repair. That choice deserves care because not everything valuable takes the form of a new practice or a major decision. Sometimes it lies in a way of listening that made it possible to resolve a disagreement without damaging the working relationship. Or in the habit of sharing a doubt while it was still small. These details are easy to appreciate collectively and hard to recognize individually if no one stops to understand them.

The work we barely see

Consider a simple gesture: someone tells another person that a delivery will differ from what was planned, while there is still time to reorganize the work that follows. The change may be minor. The person receiving the warning adjusts the sequence of their work, clarifies a dependency, and carries on. In the end, there is no major delay or memorable argument. What did happen was that someone paid attention to another person’s situation and intervened in time. If all we remember is that the deadline was met, that part of the story is left out, precisely because it helped ensure that nothing conspicuous happened. Understanding the project requires making room for it without turning every exchange into a feat.

Two people spread blue fabric across a table: one aligns the edge while the other supports the overhanging section.

Asking what the person who gave the warning noticed and how the other person was able to respond brings our attention closer to what the Safety-II approach studies in the field of safety. EUROCONTROL’s 2013 paper From Safety-I to Safety-II (opens in a new tab) examines the adjustments people make in response to the actual conditions of their work. Developed particularly for air traffic management, it recognizes that these adjustments can contribute to both acceptable and adverse outcomes. Borrowing that perspective for a project requires retaining its caution: observing an adaptation helps us understand the activity better, but is not enough to consider it beneficial or recommend that it continue.

This attention changes our picture of an achievement. A plan organizes intentions, commitments, and dependencies; as work unfolds, people have to relate those expectations to what is happening. An instruction needs clarification, information arrives incomplete, two tasks move at different speeds. The quality of the work may also lie in how those differences are recognized and addressed. Seen this way, a satisfactory delivery contains a history of coordination that the final description of the product barely shows. Within it are small decisions, some shared and others made by someone who knew when consultation was necessary.

Looking closely also allows us to be fairer to the people who sustained the work. If someone quietly compensated for a difficulty for weeks, thanking them for their effort does not resolve what should be done about that difficulty. Making their availability a routine condition of the next project would be a poor way to recognize them. There may be something admirable in their response and something that needs to change in how the work is organized. Preserving what went well requires distinguishing the two: which capability deserves support and which burden should no longer be passed on to the same person. Satisfaction at having arrived does not require wanting to take the entire journey again.

Choosing what deserves to continue

The word preserve seems to mean leaving things as they are. In shared work, it usually calls for more active involvement. A relationship of trust may be lost through lack of contact; a careful way of coordinating may disappear when a different person takes on the role of sustaining it; a useful conversation may remain on the calendar long after it has lost its purpose. Choosing what deserves to continue means understanding what was alive in what worked. Sometimes a specific practice is worth keeping. At other times, what matters is a relationship that the practice helped sustain and that will need a different form over time.

If a brief meeting helped the team, for example, preserving its length and frequency says little about what happened in it. Perhaps it allowed a question to reach the right person before it became a problem. Perhaps two departments discovered there that they were using the same word differently. Recognizing that value changes the attention paid to the meeting: what matters is whether that conversation is still possible, who takes part, and what happens afterward. This does not call for recording every gesture or adding a layer of surveillance to the working day. It calls for enough understanding to keep a routine from surviving as an empty shell while what made it useful is lost.

Two people examine and feel a seam in a piece of linen laid across a workshop table.

It also calls for accepting that the project left people with different memories. In Learning from Samples of One or Fewer (opens in a new tab), James March, Lee Sproull, and Michal Tamuz examine how organizations learn from limited experience. One of the possibilities they describe is enriching our understanding of an event by attending to different interpretations. The same episode is experienced differently depending on one’s position in the organization. The authors also caution that these interpretations do not guarantee valid learning. Listening to them broadens what can be understood; it does not automatically turn them into a correct explanation.

That plurality matters even when everyone is satisfied with the outcome. For the person coordinating, what mattered most may have been that a decision came in time; for someone carrying out a task, that an objection was heard; for someone who joined later, that another person explained the purpose of what they were doing. These are different parts of shared work. Making room for them keeps the memory of the project from being reduced to what was visible from a single position. It also allows recognition to say something specific. Thanking someone for noticing a difficulty and explaining what their warning made possible expresses a kind of attention that general congratulations cannot reach.

Learning from a successful project can happen on that scale: a conversation that leaves us with a more precise understanding and a few things we no longer want to neglect. It need not take the lightness out of the ending or prolong it indefinitely. There is a time to celebrate and let the work end. But having finished it also gives us the chance to look at those who made it possible with attention that, while the project was underway, may have been focused on reaching the finish.

What deserves to continue may be modest: a way of asking, the care with which we hand our work over to someone else, the possibility of recognizing in time that we need help. A project that went well allows us to discover how much we depended on actions we had only just learned to name. After celebrating it, it falls to us to give them a place in the work ahead. Because we can also lose what made an achievement possible while we are still congratulating ourselves on having accomplished it.

References