Information at the Point of Work
Why the Real Test of Information Is the Decision It Supports
A maintenance technician stands beside a machine that has stopped. The asset number is visible. The drawing exists. The work instruction and maintenance history are available. Yet before starting, the technician calls a colleague: “Which drawing applies to this machine?”
Nothing is necessarily missing. Several pieces of information must be connected before the technician can confidently decide what to do.
One record identifies the asset. Another contains the drawing. A third shows maintenance history. The technician still has to confirm the revision, check whether the configuration has changed and determine whether the instruction matches the equipment in front of them.
The factory has information. What it lacks is a reliable connection between information, context and action.
The real measure of information quality is not the document, dashboard or database. It is the decision the information is supposed to support.
1. The Factory Has More Information Than Ever
Modern manufacturing produces information continuously. Machines generate data; ERP and MES platforms store records; Maintenance holds work histories; Engineering maintains drawings; Quality and EHS manage inspections, procedures and permits.
The challenge is making relevant information useful when someone has to decide or act. A database can be complete, a dashboard accurate and a document current, while the task still contains uncertainty. Information connects People, Machines and Processes, but its value depends on whether the person performing the task can use it.
2. Start With the Decision
A useful shift is to start with what the person has to determine: What must they know? Where does it come from? In what form must it arrive? What happens after the decision?
This is different from asking, “Do we have the document?” A controlled procedure may still provide too much, too little or insufficient context. An operator may need one current parameter, not an entire manual; a technician may need the drawing for a specific asset configuration, not a folder of similar files.
HSE recommends fitting information, format, language and level of detail to the user, task and consequences of failure, using task analysis and user involvement to inform the design. HSE guidance on procedures.
The information system should be designed around the work it supports, not only around its repositories.
3. The Information-to-Action Test
Choose one recurring factory decision: selecting a spare, confirming a machine condition, checking whether maintenance can proceed or interpreting an abnormal indication. Trace it from the moment the need arises to the action that follows:
Decision → Information required → Source → Access → Interpretation → Action
Do not evaluate the employee; observe the system. Does the user search multiple systems, compare revisions, ask someone to interpret information or leave the task to find a record?
This reveals what BRIGS calls decision distance: unnecessary steps between useful information and the decision. It is not a formal performance metric, but a diagnostic lens for seeing where people perform integration work the system may need to handle better.
4. When Search Becomes Part of the Job
Factories often contain an unofficial process between “information requested” and “information found”. The formal process may say:
Verify the current specification.
The working process may become:
Find the specification → Identify the correct file → Confirm the asset → Check the revision → Determine whether it applies → Ask for confirmation.
Each step may seem reasonable. Together, they create additional work. Naming conventions, asset identification, document structure and separation between systems can make this an information-architecture problem rather than an accuracy problem.
Repeated searches become part of the job, even when they do not appear in the formal process.
Information design is therefore part of manufacturing process design.
5. Correct Information Can Still Be Difficult to Use
Accuracy matters, but it does not create usability by itself.
A technically correct manual may contain far more information than a worker needs. A dashboard may show every measurement but leave the user to decide which condition matters. An asset record may be complete yet hard to identify because its naming does not match the equipment.
A long document, dense screen or unfamiliar naming convention can increase the effort required to find what applies. A concise instruction may support one decision, while a full technical document remains necessary for another.
Information quality should be tested through use, not only through document control.
6. Context Is Part of the Information
Manufacturing information rarely makes sense in isolation. A number without machine identity can be ambiguous; a drawing without the applicable configuration can be incomplete; maintenance history without asset context can be difficult to interpret.
The same information may serve an engineer, technician and operator differently. This does not always require different information; it requires the right context.
Useful information should help the user establish:
- Which asset, process or condition does this relate to?
- Is it current and approved?
- Does it apply to the equipment in front of me?
- What decision or action should it support?
- What should happen if the condition does not match?
Context reduces unnecessary interpretation and helps prevent correct records from being applied to the wrong situation.
7. Factory UX: Information Is Part of the Human Interface
Information is encountered through the workplace: a label, display, instruction, alarm, visual indicator or machine screen. Factory UX examines how people see and understand it while interacting with machines, processes and the physical environment.
A clear machine identity connects an asset to its records; a well-designed display makes a condition recognisable; a concise instruction can reduce interpretation. Factory UX considers where information appears, whether it can be recognised from the working position and whether the person can act on it.
Factory UX makes the human-facing part of information clearer.
8. Factory OS: Information Must Move With the Workflow
Some information problems cannot be solved with better displays or documents. Maintenance may depend on approval status; a production change on the current engineering specification; an inspection on the latest quality requirement; a permit on the equipment, task and responsible people.
These are workflow relationships. Factory OS structures operational and safety activities, including information, workflows, maintenance-related processes and workplace controls. It is different from simply storing more information.
Factory UX addresses how information is understood. Factory OS addresses how information, workflow and control move together.
The person doing the work should not have to move between a machine, document repository, spreadsheet, supervisor and separate approval system to complete one ordinary task.
9. Connect the Information, Not Just the Systems
IT may manage platforms; Engineering, drawings; Maintenance, history; Operations, procedures; and EHS, safety information. Each function may work correctly. The difficulty appears when the person doing the work has to cross those boundaries.
The question is whether the sources work together around the person, machine and process involved. BRIGS begins by understanding the work and identifying the gap. The intervention may be digital, physical, visual, procedural or combined.
The information product should follow the requirement, not define it.
10. More Data Does Not Automatically Mean Better Decisions
As manufacturing becomes more connected, more data can become available without making decisions clearer. More sensors create signals, more dashboards create views and more records create information to search.
The useful question is not:
How much data are we collecting?
It is:
What becomes easier to control because this data is available?
Connectivity can improve visibility but increase complexity if information is added faster than workflows and interfaces are designed. A useful data point needs purpose, context and a person or process able to respond.
Technology is an intervention, not the starting point.
11. Designing Information Around the Factory
The BRIGS approach starts with the actual work.
SEE how people find, interpret and use information.
CONNECT it to the machine, process, person and decision.
DIAGNOSE whether the difficulty comes from missing data, poor access, weak context, inconsistent structure, disconnected workflow or usability.
DESIGN the information and workflow around the task.
IMPLEMENT through visual systems, improved documents, structured records, digital workflows, interfaces or workplace changes.
IMPROVE by observing whether the revised system supports the work more effectively.
There is no universal template. The intervention should follow the workplace, people, process and equipment involved.
BRIGS Perspective: Connect Information to the Work
At BRIGS, information is part of the relationship between People, Machines and Processes.
Factory UX addresses how it is seen and understood; Factory OS connects it to workflows, permissions, maintenance activities and operational controls. Machine and process safety depend on critical information being accurate and usable, while workplace improvement ensures the physical environment supports it.
The objective is a connected approach to how information works across the factory system.
A Practical Next Step With BRIGS
Choose one recurring factory decision. Start with the decision, not the dashboard, platform or document repository. Trace what the person needs to know, where the information comes from, how they access it, what interpretation is required and what follows.
Then ask:
Where is the factory forcing the person to connect information that the system should connect?
The gap may point to better equipment identification, clearer visual communication, improved document design, connected records, process redesign, a Factory OS workflow or a combination.
A BRIGS site assessment can extend the review across People, Machines, Processes, Information, Interfaces and Control.
The goal is not more information. It is a factory where information, people, machines and processes work together when decisions matter.
Have a similar challenge on your site?
Tell us what you are trying to improve and we will help you find the practical next step.


