What coordination knowledge does an operations manager hold?
An operations manager's knowledge is the gap between the process map and reality: who actually depends on whom, which orders can slip and which never may, what the December peak requires, and the dozens of informal arrangements with carriers, suppliers and clients that make the formal process work. The company only sees this web when the person holding it leaves — and things start quietly missing each other.
The anatomy of this knowledge
Coordination knowledge is distributed across hundreds of small certainties. Four clusters carry the weight:
The real dependency web
The process map shows the formal flow; the operations manager knows where it lies. Which step actually waits on which, where the buffer is hidden, which handover breaks when a particular person is on leave. Schedules built on the formal map alone fail in practice.
Seasonal and cyclical rhythms
What the December peak requires to be started in September. Which supplier gets slow in summer. When maintenance can be squeezed in. A year has a shape, and he knows it by heart while the calendar shows only dates.
The informal arrangement book
The carrier who holds a truck until 17:00 on a phone call. The client who accepts partial delivery if warned early. The supplier who prioritizes the company in a pinch because of history. None of it contractual, all of it operational capacity.
The priority judgment
When everything is urgent, which order really is: which client escalates, which penalty clause bites, which promise is sacred. Triage instinct built from years of consequences.
Why a standard handover misses it
Operations handovers transfer systems: the ERP, the planning tool, the dashboards. But the systems encode the formal process, and his job was precisely the informal delta on top. The successor operates the tools correctly and still gets worse outcomes — deliveries that used to be saved by a phone call now simply fail, and nobody can point at what changed.
What a MentX intake focuses on here
MentX is a personality-aware knowledge base: it captures the knowledge of a company's key person — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution. For an operations manager, the intake track walks the calendar and the network: the year's shape season by season, the arrangement book party by party, the triage rules case by case. Meeting ingest catches the daily planning meetings where this knowledge fires constantly. The graph makes the informal web explicit — and keeps it current as it evolves.
Who asks the DigiME — and what
Once the base has depth, the team converses with the expert's digital knowledge copy through DigiME. Three questions it answers for this role:
“The December peak is coming — what has to start now?”
The DigiME returns the September checklist that never existed on paper: temp staffing, packaging pre-orders, the carrier capacity call — with reasons and dates, sourced to intake and planning meetings.
“Client X's order will be late — how do we play it?”
His playbook for this client: warn early, offer partial delivery, call the plant engineer directly rather than purchasing — the relationship knowledge that turns a failure into a managed exception.
“Can we move the maintenance window forward a week?”
The dependency answer: only if supplier Y's delivery confirms first, because of the 2023 collision of exactly these two events — the kind of cross-dependency no planning tool holds.
