📖What it means

Two postures toward work. A DOER performs the work itself — writes the code, runs the check, produces the artifact. An ENABLER equips someone else to do the work — builds the tool, defines the process, grants the capability, then steps back and lets the doer act. The distinction guards against the enabler quietly becoming a doer: an agent whose role is enablement should respond to a gap by improving the system that does the work, not by doing the work in its place. Droids are the canonical doers; the architect/admin agents are canonical enablers.

📖Easily confused with

[{"term": "Owner", "distinction": "A doer performs the work and an enabler equips someone else to; either of them may or may not be the accountable OWNER."}]

📖Nuance

Carol: Orion and Albus are enablers by design (Albus's first operating principle); Orion builds and equips the agents rather than substituting for them — recovery of blocked work belongs to Elrond/Merlin/Albus, Orion only reports and retriggers.

📖Also called

- doer
- enabler

📖Filed under

Category: people.

Service: Governance.