Positions Are Not Roles

Find yourself in this page first. The model is easiest to grasp from the job title you already hold.

A position is a job title — PM, Designer, Engineer, QA. A role is something narrower: the kind of contribution you make right now, defined by what you want from the work. Pre-AI, a position was one fixed bundle — one motive, one object, one angle — because production was scarce and focus was finite:

• PM framed the product.
• Engineer built the code.
• Designer built the UX.
• QA evaluated the quality.

One title, one job. That held because nobody had spare capacity to do a second kind of work well.

What AI changes

With delegates supplying production, the bundle comes apart. Each position can now act as more than one motive, and reach past its default object. The title becomes a default, not a boundary.

flowchart LR
  P["A position<br/>(one title)"] --> BUNDLE["was: one bundle<br/>one motive · one object · one angle"]
  BUNDLE --> NOW["now: a default, not a boundary"]
  NOW --> M1[intend]
  NOW --> M2[generate]
  NOW --> M3[structure]
  NOW --> M4[accumulate]
  NOW --> M5[evaluate]

One position used to be one bundle. With delegates supplying production, it fans out into several motives.

Position	Default bundle (object · motive)	Motives AI now opens
PM	product · intend	Build a prototype with a delegate; encode product knowledge for reuse
Designer	product · build the UX	Own the why; own the design system; own the design corpus
Engineer	product · build the code	Structure the codebase; own conventions; reach into process and toolchain
QA	product · evaluate quality	Own acceptance criteria; curate golden sets; probe adversarially

The motives named here — intend, build, structure, accumulate, evaluate — are the four actors and their two faces. This table is just the door into them.

QA is the sharpest case

QA’s default is evaluation — the trained quality specialist whose whole job is judging the product. When delegates write the checks, QA stops being the one who writes tests and becomes the one who owns the acceptance contract and curates the corpus it draws from. The motive didn’t change — it was always about the product working. What changed is that production got cheap, so the scarce, valuable part — deciding what “good” means and guarding it — is now the whole job.

Two things the old org chart no longer says

There is no Gatekeeper position

Judging isn’t a job someone owns — it’s what any expertise does when you turn it backward on a result. Every position reviews whatever it touches. Review is everyone’s part-time act, not one person’s title. (More in Two faces and the gate.)

The title is a starting point, not a fence

An Engineer who notices three features each rolling their own auth and extracts one shared path has stepped into a structuring motive — same person, different role, same minute. The model lets you name that without a promotion or a re-org.

---

Next: The four actors →