What is a digital twin of an organization — and does a 20-person company need one?
A digital twin of an organization is a model of how a company works — its processes, roles, systems, data and rules — kept current enough to analyse a change before you make it. Large companies build one from process repositories, system data and simulation. A 20-person company rarely needs the simulation. It does need the foundation every twin starts from: an honest, owned picture of its core processes and the knowledge behind them. That foundation is useful on its own, today.
A short story
Before a merger, a family manufacturer was advised to build a digital twin of both companies. The proposal was full of simulation scenarios and dashboards.
The owners' real questions were simpler. Which processes work differently in the two companies? Who holds the knowledge of each? Which steps will break when the teams are combined? Answering them took process maps and conversations with the people who knew — not a simulation engine. And the answers were ready in time for the integration decisions. (An illustrative example, not a client case.)
What goes into a digital twin of an organization?
- the processes and their real variants;
- roles, owners and responsibilities;
- systems and how data moves between them;
- decision rules and exceptions;
- measures that show how each process performs;
- the knowledge and sources behind all of the above.
The last layer is the one most often missing. Without it, the model shows how work flows, but not why it flows that way — and not what to do when it doesn't.
What goes wrong when a small company starts with the model?
- Over-modelling: months go into a level of detail nobody will maintain
- System blind spots: the model is built from system data, so everything handled outside the systems is missing
- No recognition: the people who hold the knowledge see a model that does not match their work
- Ageing: the model goes stale, and decisions return to the same few people
Does a 20-person company need one?
Not the full version. What it needs is the foundation: a list of core processes with owners, the most critical ones mapped as they really run, and the rules, exceptions and data behind each step, with their sources.
If the company grows, that foundation grows with it and can connect to heavier tools later. Not to be confused with a digital twin of an expert, which is about one person's knowledge rather than the whole organization.
How is a digital twin of an organization different from process mining?
Process mining reconstructs how work flowed from the event data in your systems. A digital twin of an organization is broader: it combines processes, roles, systems, rules and measures into one model you can reason about. Mining can feed a twin, but both depend on system data — and in a small company much of the real process happens outside the systems.
For an SME, the people who do the work are usually the richest source. That is where the foundation starts.
How MentX helps
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
Mapping your processes and capturing your operations build exactly that foundation, from the people who do the work. Where a company later needs simulation or a full process repository, it builds on the same foundation with established solutions.
What to do this quarter
- List your core processes and their owners.
- Map the most critical one as it really runs.
- Record the rules, exceptions and data per step, with their sources.
- Note which systems hold which part of the process.
- Only then decide whether you need more than this.
