When Project Experience Becomes Strategy

Several years ago, I found myself asking what seemed like a simple question.

Why do smart organizations keep relearning lessons they already paid to learn?

It wasn’t a question about talent. The firms I work with are filled with thoughtful people who care deeply about the quality of their work. They invest in research. They mentor younger staff. They refine standards. They solve difficult problems every day.

Yet many of those same firms unknowingly solve some of the same problems again a few projects later. A product that performed well on one project isn’t considered on another. A specification that created unnecessary confusion quietly reappears. A lesson learned during certification never reaches the next project team.

The issue isn’t a lack of expertise. It’s that individual expertise and project information do not naturally become knowledge the entire organization can use.

It’s easy for a firm to assume that experience accumulates automatically: complete enough projects and the organization simply becomes better. Perhaps I once saw it that way, too. But while individuals naturally gain experience through their work, organizations only learn when they create a reliable way for what was learned on one project to inform decisions on the next.

That distinction has become increasingly important as firms have grown. Teams are larger, projects move faster, and responsibilities are distributed across more people than ever before. That’s a healthy evolution, but it changes the way knowledge moves through an organization. The architect who solved a difficult materials challenge three years ago may never work with the designer facing the same decision today. The project manager who understands why a particular specification evolved may have retired, changed roles, or simply be focused on another client. None of this represents failure. It’s simply the reality of a successful practice.

The question, then, isn’t whether firms have accumulated information and experience. Most have decades of both. The question is whether they can translate those resources into knowledge that is available when someone needs it.

What Project Documentation Can Teach

Every completed project leaves behind an enormous amount of information. Specifications document design intent, submittals record the products ultimately used, and certification and closeout documentation capture the decisions and outcomes that shaped the finished building. Together, these records reveal thoughtful choices, practical compromises, successful outcomes, and lessons that could benefit future teams.

Yet project documentation is typically treated as history rather than as a teacher. It is archived for its legal, contractual, or historical value and revisited when someone remembers a similar condition or product. More often, the project ends, the team moves on, and its experience remains attached to the work that produced it.

That does not reflect a lack of interest in learning. Every organization I’ve worked with wants greater consistency across offices, stronger project outcomes, and confidence that today’s decisions benefit from what the firm has already learned.

The challenge is not a need for more documentation. Firms already preserve enormous amounts of project information; learning begins when that information is understood and returned to the people making tomorrow’s decisions.

Tribal knowledge has long helped bridge that gap, but the experienced team leaders who carry it are not always available when someone needs their guidance—and they may eventually move into new roles, change firms, or retire. Project data can preserve evidence of what individuals and teams have learned, while ongoing feedback translates that information into knowledge others can apply. Like good coaching, it makes relevant guidance available while there is still time to inform a decision. 

Coaching Begins with Context

One observation has stayed with me for years.

Doc Rivers once said,

Average players want to be left alone. Good players want to be coached. Great players want to be told the truth.

Whether we’re talking about athletics or AEC professions, the underlying idea is remarkably similar. Even highly experienced professionals benefit from perspectives they can’t easily see for themselves. That’s what coaching provides.

Good coaching begins with listening. A coach cannot offer meaningful guidance without first understanding what someone is trying to accomplish, and the range of responses Doc Rivers describes reinforces that coaching is not a one-size-fits-all exercise. The same principle led us to think about sustainability in context: meaningful feedback must be grounded in a firm’s particular goals, priorities, and circumstances. A good coach respects those goals, recognizes patterns that may be difficult to see from within the work, and offers perspective while there is still an opportunity to act on it.

In the built environment, consulting can provide that same outside perspective. Its value lies in complementing the expertise and judgment teams already bring to their work while helping them see how their project decisions align with their stated goals.

Every completed project generates information that could help inform the next. Through an effective feedback loop, a consultant can help translate that information into knowledge that returns to the design process and supports future decisions.

When that knowledge fails to reach the next team, firms spend time and money solving problems they may have already solved. The cost is measured not only in missed opportunities, but in repeated research, avoidable rework, and decisions made without the benefit of the firm’s accumulated experience.

Before a project begins, feedback from previous work can help teams establish priorities, identify proven materials, and avoid specifications that have repeatedly created additional research or coordination. During design, timely feedback can reveal where stated goals and project documents are beginning to diverge, allowing teams to adjust before procurement or construction makes changes more expensive. After completion, feedback can confirm what performed as intended, capture lessons worth carrying forward, and strengthen the guidance available to future teams. Each stage has value, but the earlier insight reaches a project, the greater its potential to save time, reduce rework, and improve outcomes. 

Recognizing Patterns Across Projects

People sometimes ask whether firms need more project information to improve consistency. I don’t think they do. The building industry already produces extraordinary amounts of information through the documentation created across every phase of a project. The opportunity lies in bringing an experienced perspective to that body of information—one that can recognize patterns across projects and translate them into actionable data insights.

Over time, certain products consistently perform well. Certain substitutions repeatedly introduce unnecessary complications. Some specifications produce reliable results across many projects, while others require frequent clarification or revision. Those patterns don’t belong to a single project. They belong to the organization.

Without a reliable data feedback loop, these patterns are challenging to identify because they are spread across years of documentation and hundreds of individual decisions. That’s one reason I’ve become so interested in data feedback. It transforms dispersed project information into durable data insights that can be returned to teams as relevant feedback—without depending on who remembers the lesson or is available to explain it. As those insights inform decisions across projects, information becomes working knowledge the firm can continue to use as its people and teams change. 

From Information to Wisdom 

Information, knowledge, and wisdom are often treated as interchangeable, but they represent different levels of organizational learning. Information consists of the raw details gathered from documentation and assembled into a usable one-off project structure. Knowledge develops when a firm can recognize the relationships within that information and apply what it has learned. Wisdom is the ability to translate that knowledge quickly into strategy.

Every project has the potential to contribute to this progression. Each observation adds to the firm’s information, but its greater value emerges when observations can be understood across projects and used to guide future decisions.

Accumulating more documentation does not automatically move an organization from information to knowledge or from knowledge to wisdom. That progression requires a reliable way to preserve what projects are teaching, recognize patterns across years of work, and return those insights to the people who can act on them. An ongoing data feedback loop creates that connection, allowing the organization’s understanding to become more useful and more readily available with every project.

To me, this is one of the most encouraging opportunities in our profession. Firms already possess much of the information they need to improve; the next step is developing the knowledge to understand what it reveals and the wisdom to translate it into strategy.