When Every Order Is a Project, Why Is Knowledge So Hard to Reuse?

“Haven’t we solved something like this before?”

If you have spent enough time in an equipment company where every order is a project, you have probably heard this question many times.

A customer requirement arrives. The engineering team begins evaluating possibilities. The proposal team starts preparing a response. Somewhere during the discussion, someone remembers that the company may have handled something similar in the past. Perhaps for another customer. Perhaps in another industry. Perhaps with slightly different specifications.

And yet, despite this feeling that “we have done something like this before,” teams often find themselves starting almost from scratch.

The proposal gets recreated. Engineering calculations are revisited. Design decisions are debated again. Lessons from earlier projects remain buried in folders, spreadsheets, emails, technical documents, or simply in someone’s memory. This is a surprisingly common challenge in growing equipment companies, especially in organizations where every order becomes a project and no two customer requirements are exactly alike.

Why does this keep happening?

The reason is simple: knowledge grows faster than the organization’s ability to reuse it.

Think about how much knowledge gets created in such companies. Every proposal creates knowledge about pricing, assumptions, and customer expectations. Every engineering challenge creates technical learning. Commissioning activities reveal practical issues that rarely appear on paper. Service teams learn recurring problems and workarounds. Customer interactions generate valuable understanding of operational realities.

Over the years, companies quietly build an enormous pool of expertise. They learn what works and what does not. They discover better ways of designing systems, estimating costs, handling operational challenges, and managing risks. In many ways, every project makes the organization smarter.

But there is one problem: most of this knowledge does not exist in a form that is easy to access or reuse.

Some of it sits inside proposal folders. Some knowledge lives in engineering drawings and reports, while some is hidden inside ERP systems, project documentation, commissioning reports, SOPs, spreadsheets, or shared drives. And a large part of it exists only in the minds of experienced employees; the people everyone depends on when a difficult situation arises.

This works reasonably well when the company is small. People know who to ask. Teams sit closer together. Finding information depends more on conversations than systems.

But as organizations grow, things begin to change. There are more projects, more customers, more employees, and more locations. Information increases rapidly, but accessibility does not grow at the same pace.

Imagine a proposal team responding to a customer requirement that looks somewhat familiar. They know the company may have submitted something similar three years ago. But where is that proposal? Which assumptions were used? What costing logic worked? Were there design challenges during execution? Did commissioning reveal issues that should be avoided this time?

Finding these answers often becomes harder than expected. Teams search folders, call colleagues, and depend on memory. Sometimes the right information is found. Often, it is not. And so, work gets recreated.

The hidden cost of forgotten knowledge

The impact of this is larger than it appears.

First, there is the cost of lost time. Skilled teams spend hours searching for information or recreating work that already exists. Second, inconsistency starts creeping in. Similar customer requirements may get approached differently simply because teams are unaware of earlier solutions.

Third, organizations become dependent on a few experienced individuals who become walking repositories of institutional knowledge. When they are unavailable or eventually leave, valuable expertise leaves with them.

And perhaps most importantly, innovation slows down. When teams spend time rediscovering yesterday’s answers, they have less time to improve upon them.

For many years, solving this challenge was easier said than done. Companies tried creating document repositories and structured databases, but maintaining them required significant manual effort. Documents needed categorization, tagging, updating, and discipline; something difficult to sustain in busy project-driven environments.

What has changed now?

Technology, especially Generative AI, is making it far easier to consolidate and access organizational knowledge.

Today, knowledge does not necessarily have to be manually recreated into one perfect system. Using connectors, information spread across different places such as proposal folders, shared drives, ERP systems, technical documents, SOPs, service records, commissioning reports, and project files can be brought together into a unified knowledge layer.

But the real shift is not just about storing information in one place.

It is about making it usable.

Instead of searching endlessly through folders or depending on someone’s memory, employees can access knowledge using natural language. A proposal manager may ask, “Do we have a similar proposal for this type of requirement?” An engineer may ask, “Have we faced similar operating conditions before?” A service team member may want to know, “What recurring issues were reported for similar equipment?”

Rather than hunting for documents, people can begin discovering answers from the organization’s own accumulated experience.

This does not replace expertise. Nor does it replace experienced people.

What it does is make existing expertise easier to find, reuse, and build upon.

Because perhaps the real challenge in growing equipment companies is not the lack of knowledge.

It is that valuable knowledge already exists, but remains difficult to access when it is needed the most.