Learn Once, Remember Everywhere. How archival data can reconstruct the decision context behind your firm’s delivery expertise
NASA has not landed on the moon in 53 years and counting. The hard part about returning to the Moon was never remembering that rockets work.
NASA still had the drawings. It still has an archive of reports, calculations, photographs, and hardware. What it did not have, at least not in the same living form, was the full learned context of the Apollo program: the production instincts, supplier know-how, test-stand judgment, manufacturing workarounds, and hard-earned sense of what not to do.
That is the uncomfortable lesson of the Apollo program: despite having the original blueprints and vastly improved technology, it did not have the tacit knowledge. A blueprint can preserve the answer, but it rarely preserves the experience that produced the answer.
Engineering and architecture have always been trades of judgment. Yes, they are technical disciplines. Yes, they rely on codes, calculations, standards, models, and specifications. But the best practitioners know that the formal record is only part of the work. Real expertise often shows up as a pause over a detail. A warning in a redline. A quiet comment in a meeting: “We tried that once.” It is the ability to recognize a familiar risk before it announces itself as a problem.
That is tacit knowledge. Not a mystical concept. Not corporate jargon. Just the practical, lived expertise that accumulates when people solve hard problems over and over again in the real world.
Architecture and engineering firms are full of it. The principal who remembers why a façade detail failed in a coastal climate. The project manager who knows which permitting issue quietly drove a hospital renovation off schedule. The structural engineer who can look at a proposed solution and immediately see the field conflict hiding inside it. The civil lead who knows that a design is technically compliant but operationally doomed.
This is the knowledge clients actually pay for. And it is walking out the door.
The industry has talked for years about demographic change, retirement risk, staff turnover, and the shrinking window for mentorship. Those are real pressures. But the deeper issue is not simply that people leave. People have always left. The deeper issue is that, when experts leave, firms often lose the decision context that made those experts valuable in the first place.
The client deliverables remains. The lesson disappears.
Most firms already know this, which is why “knowledge management” has become a recurring agenda item in leadership meetings. The usual responses are familiar: lessons-learned templates, project closeout forms, internal wikis, lunch-and-learns, best-practice libraries, maybe a heroic SharePoint site with a naming convention that made sense to exactly three people in 2018.
These efforts are well-intentioned. They also tend to collapse under the weight of reality.
The people with the most valuable knowledge are usually the people with the least time to document it. They are reviewing deliverables, rescuing projects, mentoring staff, supporting pursuits, answering client calls, and being pulled into every situation that is too important to fail. Asking them to spend their spare time converting forty years of professional judgment into clean database entries is not a strategy. It is a fantasy with a steering committee.
We do not need to turn subject matter experts into monks.
The better opportunity is to give their work a memory.
Every project already produces a massive trail of context. Drawings. Models. Specifications. Emails. Meeting minutes. RFIs. Submittals. Markups. Comments. Photos. Cost estimates. Change orders. Addenda. Field reports. Closeout documents. Version histories. Collaboration threads. The daily exhaust of project delivery.
Individually, these artifacts look like administration. Together, they are the closest thing most firms have to a record of how their experts actually think.
The deliverable shows the decision. The collaboration record shows the thinking. This is where archival data gets a new life.
For decades, archives were treated as dead storage. Keep the files because contracts require it. Keep the emails in case there is a claim. Keep the drawings because someone may ask for them during a renovation. The archive was a defensive asset: necessary, expensive, and mostly inert.
Modern technology changes that equation.
With semantic search, metadata extraction, version history, knowledge graphs, and AI-assisted analysis, firms can start connecting disparate pieces of the project record into something more useful than a folder structure. Not just “find me the file.” Not just “search every PDF for this keyword.” But: show me similar problems, the decisions that resolved them, the context around those decisions, and the evidence of whether they worked.
That is a fundamentally different capability.
A young engineer should not have to know the name of the project where the firm solved a similar foundation issue twelve years ago. A project manager should not have to email six principals asking who remembers a phased healthcare renovation in Denver.
The firm should learn once.
Then it should remember everywhere.
This does not replace the expert. It elevates the expert.
The subject matter expert is still the hero of this story because their judgment is the original source material. Their decisions, comments, markups, warnings, and revisions are what give the archive value. Technology does not magically create expertise from old files. It reconstructs the trail of expert thinking so that more people can find it, learn from it, and apply it at the right moment.
The path to this outcome is not abstract. It is tactical.
First, connect and centralize all project data into a single repository. Drawings, reports, emails, models, photos, meeting notes—everything that reflects how work actually gets done. The goal is not perfection. It is completeness.
In parallel, construct a structured database of project data - client name, location, description, personnel involved, financial outcome. Information that would help inform the "who" and "what".
Second, use modern cloud tools to extract document metadata and context from that data. Turn unstructured files into structured knowledge without requiring manual tagging at every step. Then index these files for ‘linkages’ - where does a meeting note or email thread mention a drawing. Where is there mention of a warranty issue? In the tech space, this is called a “knowledge graph” and helps to address the “why” and the “how”.
Third, make that knowledge searchable to all employees - all the way down to the junior designers. (Within reason) do not gatekeep this information. Allow teams to ask natural questions and retrieve relevant past work, lessons, and patterns instantly. The system should surface context, not just documents.
This is how firms move from scattered archives to usable intelligence.
The Apollo Program lesson is not that documentation does not matter. Documentation matters enormously. The lesson is that documentation without context is incomplete.
A&E firms should take that seriously. The model, the drawing, and the specification are critical artifacts, but they are not the whole design. The whole design includes the decisions, debates, constraints, failures, revisions, and learned instincts that shaped the final answer.
Most of that context already exists.
It is sitting in the archive, scattered across deliverables, emails, meeting notes, markups, and collaboration systems. And notable, its is scattered across projects too. The opportunity now is to connect it, interpret it, and turn it into a searchable firm-wide memory.
Because the firms that win the next decade will not be the ones that simply store the most data.
They will be the ones that learn once - and remember everywhere.
About the Author
Nick Decker is the Global Segment Leader for Engineering at Egnyte. He is responsible for the growth and support of Egnyte’s engineering customers. Nick brings deep experience in the design and field technology space from time at Bluebeam and Dusty Robotics. He originally comes from the construction and engineering industry, having worked for large contractors Kiewit and AECOM Hunt. Nick holds a Civil Engineering degree and MBA from Purdue University.
