Share technical knowledge so more people can put it to work.

Start with a category of work that makes the business distinctive: a difficult fabrication, a product adapted for a dealer or a combination of supply and specialist support. Frequency matters, but so do commercial fit and the direction you want the business to take.

Review a few accepted and declined requests with colleagues from sales, preparation and delivery. Why was one attractive and another unsuitable? What information changed the decision? A declined job can reveal an important boundary more clearly than a successful one.

An old proposal records the offer. A drawing describes the finished item. Neither necessarily explains the options rejected, the uncertainty discussed or the special agreement made with the customer.

For a representative job, add a short account of five things:

• What the customer was actually trying to achieve.
• What made the work technically or commercially unusual.
• The decision and the reasoning behind it.
• The conditions that made the commitment practical.
• What the delivery team learned afterwards.

Connect this account to the job and documents people already use. Agree who updates it when experience changes the original understanding. If branches work in different languages, make sure product terms and document versions still refer to the same specification. Useful knowledge needs a shared meaning, not just a translated file.

For example, “This modification is possible” is not enough. “This job used material variant B after review of drawing version 3; the previous delivery estimate cannot be reused” tells a colleague what needs checking. Record the source, date and who can explain the decision. A changed specification should also make it clear when an earlier example needs reviewing.

Previous work provides a reference, not automatic permission. Available capacity, a specialist’s availability or a material specification may have changed.

Separate reusable experience from information that must be checked again. People need to see which is which. That distinction lets them apply judgement instead of copying a decision made under different circumstances.

Then establish what they can actually do. Can the employee prepare an option, discuss it with the customer or make a commitment? The decision-authority framework helps make those boundaries practical. Better access to information alone will not remove a queue for approvals.

A searchable job record may be enough. In other situations, drawings, technical notes and customer commitments need to be brought together. AI may provide a useful way to find relevant material or prepare a comparison.

A suggested answer should point back to the job and version on which it relies. An experienced colleague should assess whether the comparison is meaningful. A confident answer does not give permission to make a new customer commitment.

For confidential business knowledge, our preference is to assess a suitable open model in a private environment. It must handle the required comparison well; choosing a larger and more expensive model is not an objective in itself. Finding and explaining information does not automatically call for an agent acting independently. Our private AI approach explains the distinction.

Ask a colleague to prepare a new request using the available material. Did they ask the right questions? Could they identify what remained uncertain? Could the customer move forward with a well-founded next step?

Those questions tell you more than whether the search returned results. They show whether knowledge is becoming usable commercial capability.

More people can then contribute the expertise customers come to you for, while experienced specialists focus on the decisions that need their judgement most.

At a building materials supplier, we work on established applications with product-specific logic and support internal developers. Knowledge transfer means preserving the reasoning behind those rules through technical change. A new developer needs to understand the business agreement represented by a rule.

To explore which knowledge your team needs to take on more, start with business process analysis. We connect the work you want to win with the decisions needed to deliver it.