The Demiurge · Part 03 of 04

The Demiurge at Work

Nobody on the team is wrong. They are just not the Demiurge, and that is the problem.

5 min readUpdated Shadow of The Creator
The Demiurge · 4 parts

The Demiurge is often the most skilled person on the team and the hardest to work under. They see the better version of everything: the slide, the sentence, the architecture of the whole product. So they fix it. The colleague arrives in the morning to find their work redone overnight, better, and with no note about why.

After a few rounds, the team adjusts. People stop finishing things, because finished things get redone. They stop proposing, because proposals get rebuilt. The Demiurge reads the quiet as a lack of talent and takes on more, until they are doing six jobs at a standard nobody asked for and the launch has moved for the fourth time.

01The pattern

How the loop runs at work

The work loop ↻ and again
01
The handover
A colleague delivers their part
02
The redo
Fixed overnight, no explanation
03
The withdrawal
They stop finishing things
04
The takeover
The Demiurge does it all, late

The loop ends with the Demiurge alone with the whole project and a moved deadline, which proves to them that nobody else could have done it. The team that could have done it left at stage three.

02Recognition

What it looks like

  • →Rewriting a colleague's deliverable instead of sending it back with notes
  • →A launch date that has moved more than twice for reasons only you can see
  • →Collaborators who go quiet, then leave, without ever arguing
  • →Being the only person who touches the final version of anything
  • →Describing every team you have worked with as not quite good enough
03Origin

Why work brings it out

At work the Demiurge's name is on things, and a thing with the Demiurge's name on it is the Demiurge. A colleague's merely adequate slide in a shared deck is exposure, and redoing it is self-protection dressed as diligence. It feels urgent in a way the colleague cannot understand, because for them it was only a slide.

The second driver is the vision. The Demiurge can see the finished product in full, and a team is a group of people who cannot see it. Every handover is a gap between the vision and what arrived. Closing the gap by hand is faster than explaining the vision, until the people who would have learned it are gone.

04What helps

What actually helps

  1. 01

    Define done before the work starts

    Write down, with the team, what finished means for this project: the standard, the date, the person who signs off. A standard set in advance can be met. A standard that lives in your head moves.

  2. 02

    Send it back instead of redoing it

    When a colleague's work falls short, return it with three specific notes and a deadline. It takes longer than fixing it yourself, once. It takes less time than doing every job on the team forever.

  3. 03

    Let one deliverable ship below your bar

    Pick something low-stakes and let it go out as the colleague made it. Watch what happens. Usually nothing, and that nothing is the evidence the Demiurge has never collected.

  4. 04

    Explain the vision once, in full

    Spend an hour showing the team the finished thing you can see. The Demiurge skips this because it feels slower than doing it. It is the only step that lets anyone else do it.

05 · Journal prompts

Three questions to sit with

  1. 01Whose work did I redo this month, and what did they learn from that?
  2. 02Which deadline have I moved, and what was I protecting by moving it?
  3. 03What would I have to accept to let someone else finish this?
More shadow work prompts ›
06Questions

Frequently asked questions

Why do I end up doing everyone's work myself?

The Demiurge redoes work that falls below its bar, and colleagues learn fast that finishing is pointless. The workload that follows feels like proof that nobody else is capable. It is the result of the redo rather than the reason for it.

Is the Demiurge just a high standard?

No. A high standard is a bar the team can be told about and reach. The Demiurge's bar moves as the work gets close, lives in one person's head, and is enforced by takeover rather than feedback. The standard is real. The way it is applied is the shadow.

Why do my collaborators keep leaving?

People leave a Demiurge quietly because arguing changes nothing; the work gets redone either way. From their side, nothing they finish survives contact, so the only move left is to stop finishing and, eventually, to go. Few of them say why on the way out.

How do I know if the Demiurge is my shadow?

The free Archemap test names your archetype and your shadow in about ten minutes, with no signup. A workplace check first: count the deliverables this year that went out exactly as a colleague made them, without your hands on the final version.

Is the Demiurge your shadow?

Take the free test to discover your archetype and the shadow pattern running quietly underneath it.

Take the free test ›