← Back to the courseAcademy · Lesson 3 of 7

Capture & connect knowledge

7 steps · 4 min

0 / 7 steps done

A process is more than a list of steps. The knowledge around it (which document applies, which standard bites, which system is needed, which site it happens at) attaches to the workflow itself instead of scattering across five tools.

Resource or location? The question comes up straight away, and the answer saves you hunting later: a resource is something you use: a caliper, a CRM system, a form. A location is where the work happens. So the meeting room is a location, not the resource standing in it.

The trick is the order: create things centrally once, then link them at the steps. That way you maintain a requirement in one place and it is correct everywhere. Those links are exactly what lets the AI help answer from your own knowledge later, instead of guessing.

Create resourcesTools, systems, documents: captured once, usable in every process.
Create locationsPlant, shop floor, branch: places get their own area: not what you use, but where you use it.
Create requirementsThe standard, the rule, the obligation: recorded once instead of re-explained everywhere.
Anchor it to the stepAttach the requirement to the node it belongs to, right where the question comes up.
Make order visibleBorder and fill colour per node: what belongs together reads at a glance.
The process mapCreate a new map: the layer above the individual workflows.
Place your processesModel how the workflows relate. Islands turn into one picture.