← Back to Field Notes

Knowledge

February 17, 2026 · The Bloomfield Team

The Difference Between Documentation and Usable Knowledge

Every manufacturing operation we have walked into has documentation. SOPs in three-ring binders. Setup sheets in filing cabinets. Process instructions laminated and zip-tied to machine guards. Work instructions stored in the quality management system. Inspection protocols. Material specifications. Customer requirements files.

Every one of those operations also has a version of the same complaint: "We have the documentation, but nobody uses it. When something goes wrong, people ask the guy next to them."

The documentation exists. The knowledge does not flow. That gap is where most of the operational inefficiency in manufacturing lives, and it is a gap that more documentation cannot close.

What Documentation Actually Is

Documentation is information that has been written down and stored. An SOP for setting up a Haas VF-2 is documentation. A work instruction for incoming material inspection is documentation. A customer-specific packaging requirement saved in a folder on the shared drive is documentation.

Documentation answers the question: "Does the information exist somewhere in this building?" In most manufacturing operations, the answer is yes. The shop floor is not suffering from a lack of recorded information. Across the ERP, the file server, the quality system, the email archives, and the physical files, there are thousands of pages of documented knowledge.

The problem is that documentation, as it is typically created and stored in manufacturing, has three properties that make it functionally useless at the moment someone needs it.

It is organized by document type, not by situation. Setup sheets are filed with setup sheets. Quality procedures are filed with quality procedures. Customer requirements are filed by customer. When an operator needs to set up a job, they need information from all three categories simultaneously. Gathering it requires visiting three different locations, physical or digital, and assembling the relevant pieces.

It is static. An SOP written in 2021 reflects how the shop ran jobs in 2021. The tooling has changed. The machines have been updated. Customer requirements have evolved. The experienced operators already know which parts of the SOP are current and which parts need to be mentally revised. A new operator has no way to know this and follows the document exactly, which may or may not produce a good result.

It is disconnected from the work. Documentation lives in a system. Work happens on the floor. The distance between the two, sometimes measured in minutes of searching, sometimes in a walk across the building, sometimes in a phone call to someone in the office, is the gap where mistakes happen. When the cost of retrieving information exceeds the cost of guessing, people guess.

What Usable Knowledge Looks Like

Usable knowledge is information that reaches the right person, at the right moment, in a format they can act on without interrupting their work. It is the difference between a map filed in a drawer and directions spoken to you while you are driving.

In a manufacturing context, usable knowledge has four characteristics.

It is contextual. When an operator is about to set up Job #4417, the knowledge they need is specific to that job: the setup notes from the last time this part ran, the tooling that was used, the cycle time that was achieved, any quality issues that occurred, and the customer-specific requirements for this part number. Usable knowledge delivers all of this in one place, organized around the job, not scattered across six systems.

It is current. Usable knowledge reflects what happened last week, not what was written down three years ago. If the tooling approach changed on the last run, the knowledge system reflects that. If a new customer requirement was added after the last order, it is flagged. The information is alive.

It is searchable by symptom. When something goes wrong on the floor, the operator knows the symptom: chatter, surface finish degradation, dimensional drift, tool breakage. They may not know the root cause. Usable knowledge lets them search by what they are experiencing and returns the history of similar problems on similar parts, with the causes and solutions that were applied. Manuals organized by category cannot do this.

It is cumulative. Every job the shop runs generates knowledge. What worked. What failed. What the customer accepted. What they rejected. Usable knowledge captures this automatically from existing records, job travelers, inspection reports, quality deviations, and operator notes, and adds it to the body of knowledge that is available for the next similar job. The knowledge base grows with the operation.

A Concrete Example

A shop runs a family of hydraulic valve bodies for an industrial equipment manufacturer. The parts come in 14 configurations, ranging from simple two-port bodies to complex eight-port manifolds. The shop has run these parts for nine years, generating hundreds of job records.

Under a documentation approach, the setup sheets for these parts are filed in a binder organized by part number. The quality requirements are in a separate folder in the quality system. The last known tooling list is in the programmer's files. Any special notes about material behavior, fixturing challenges, or customer preferences are in the memory of the senior machinist who has run these parts since the beginning.

When a new order comes in for configuration 7B, the operator needs to pull from all of these sources. If the senior machinist is available, the setup takes 90 minutes. If he is on vacation or has retired, the setup takes three and a half hours because the operator follows the setup sheet literally, does not know about the fixturing modification that prevents chatter on the thin cross-section, and runs the first part at conservative parameters that the senior machinist would have overridden.

Under a usable knowledge approach, when Job #4417 for configuration 7B arrives on the floor, the system presents: the complete setup configuration from the last successful run, including the fixturing modification with a note explaining why it was adopted in 2022 after a chatter problem on the thin cross-section. The tooling list with current tool numbers and life remaining. The cycle time from the last run with a note that the programmer optimized the roughing path in 2024, reducing cycle by 12 minutes. The customer's inspection requirements, including the dimensional check they added after a rejected lot in 2023. The material note that heat lot variations from the current supplier occasionally require a feed rate reduction on the deep bore.

The operator, regardless of experience level, has everything they need to run the job correctly. The setup takes 90 minutes whether the senior machinist is there or not.

Where the Knowledge Already Lives

The good news is that most of the knowledge a manufacturing operation needs is already being generated. It lives in the ERP as job history, routing data, and cost records. It lives in the quality system as inspection reports, nonconformance records, and corrective actions. It lives in emails as customer communications, supplier quotes, and internal discussions. It lives on the floor as setup sheets, operator notes, and the institutional memory of experienced workers.

The knowledge exists. The systems that store it were not designed to deliver it contextually. The ERP was designed to manage transactions. The quality system was designed to ensure compliance. The email system was designed for communication. None of them were designed to answer the question: "What does the person doing this job right now need to know?"

That question is the one that matters. A custom knowledge system built around your operation's data connects these sources and organizes the information around the work being done. When an estimator opens an RFQ, they see pricing history and comparable jobs. When a programmer starts a new part, they see tooling selections and cycle times from similar parts. When an operator begins a setup, they see the complete context of every previous run.

The Return on Usable Knowledge

The financial impact of moving from documentation to usable knowledge shows up in three areas.

Setup time reduction: 15% to 30%. When operators have the full context of previous runs at the point of setup, they avoid the trial-and-error that consumes time on unfamiliar jobs. For a shop running two setups per machine per day across 15 machines, a 20% reduction in average setup time is worth 6 machine-hours per day. At a $125/hour loaded rate, that is $750 per day, or roughly $190,000 per year.

Scrap reduction: 20% to 40%. The majority of scrap in custom manufacturing comes from the first few parts of a run, when the setup is being dialed in and the operator is learning the behavior of the part. When the knowledge from previous runs is available, the learning curve compresses. First-article scrap drops. For a shop with $200,000 in annual scrap cost, a 30% reduction saves $60,000.

Knowledge retention: value compounds annually. Every retirement that would have cost $2.4 million in lost knowledge becomes a manageable transition when the knowledge is captured in a system. The new person still needs time to develop skill. But they have access to the accumulated experience of everyone who came before them, and that changes the ramp-up timeline from 24 months to 6 to 12 months.

The operation that treats knowledge as a living system rather than a filing obligation builds an advantage that compounds with every job it runs, every problem it solves, and every person it trains.