Engineering firms: the design rationale is the product
An engineering firm sells judgment: the ability to design things that work, on budget, without rediscovering old failures. That judgment concentrates in senior engineers, and almost none of it is in the drawings — the files show what was decided, never why, nor what was rejected. When a senior leaves, the firm keeps its archive and loses its ability to read it.
What knowledge is at risk in engineering firms
The knowledge at risk is the invisible layer above the archive:
- Design rationale per project — why this concept won, what was rejected and why — the graveyard of alternatives that makes the archive interpretable.
- The failure memory — which details cracked, which suppliers' materials disappointed, which clever optimizations failed in the field — a career of expensive lessons in one head.
- Calculation heuristics — where the standard method under- or over-estimates, which margins are load-bearing, when to distrust the simulation — the seniority itself.
- Client engineering culture — what client X's reviewers always challenge, which norms they interpret strictly, what documentation depth they expect — relationship knowledge with technical content.
- Norm and certification history — how past approvals were actually achieved, which interpretations were agreed with which body — knowledge that resurfaces as panic at renewals.
The typical trigger moment
The trigger that exposes engineering firms is the departure of a domain anchor — the one senior who carried a discipline (structures, thermal, controls) for twenty years. Projects in flight keep moving on momentum; the damage appears in the next generation of proposals and designs, where his review would have caught the issues nobody else sees. By then the connection to the departure is invisible.
What a Knowledge Space looks like 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. An engineering Knowledge Space connects design reviews and project meetings — where rationale is spoken aloud daily — and the intake track walks the portfolio: this design's story, what almost failed, what would you never do again, which margins matter. The graph links reasoning to specific projects, clients and norms, dated and sourced. Juniors then query DigiME during design work — getting the senior's reasoning at the moment it prevents the mistake, not in the post-mortem.
Questions we hear from engineering firms leaders
Our seniors review everything — isn't that how the knowledge transfers?
Review transfers verdicts, not reasoning: the junior learns that the weld detail was rejected, rarely the full why, and never the three alternatives the senior silently dismissed. Capture makes the reasoning itself available — including to the engineers the senior never happens to review.
We have design guidelines and calculation templates. What's missing?
Guidelines encode conclusions. The knowledge that leaves with a senior is what to do when guidelines conflict, when the template's assumptions don't hold, and which rules were written for a reason that no longer exists. That judgment layer is what the intake track targets.
How does this work with billable-hour pressure?
Capture rides on meetings that already happen — design reviews are the richest source. The intake sessions are the only added time, spread over weeks, and they are the highest-leverage hours a retiring senior can bill: every hour captured saves multiples downstream.
