A digital twin is a context-aware representation of a person, a role, a team or the whole organisation. It works from approved knowledge, inside boundaries somebody set deliberately, and it acts only through workflows that already exist.
A model has no idea who you are, what your team decided last quarter, or which customer must never be emailed on a Friday. So people re-explain their world every single time — and when someone leaves, everything they knew about how the work is done leaves with them.
A twin draws on sources somebody explicitly allowed. It cannot go looking for more.
What it may do is defined per twin: which workflows, which systems, which limits.
Context comes from the work happening in the Workspace, not from a questionnaire.
Colleagues get the context they would have asked you for, without waiting for you.
A role twin carries the working knowledge of the job to whoever takes it next.
The person a twin represents can read their own record. Nothing is built behind their back.
The routine half of a job, handed to something that already knows the context it needs.
Holiday and handover stop meaning that a whole area of knowledge goes offline.
A real answer, based on the work, instead of a guess and a hope.
Where decisions actually wait, and which dependencies nobody had named.
Who can see what, whether a person can read their own record, and what cannot be extracted even with administrator rights — these are decided in how the capability is built, not in how it is sold. A twin that employees cannot trust is a twin nobody will give context to, and a twin without context is worthless.
Start with one role or one team, on the work where losing context costs the most. Fourteen days, no card.