Systemizer

"Already made it a template"

"I already made it a template" — likes making everyone's work lighter.

Who is this type?

You convert individual craft into templates, workflows, and agents so anyone can get the same result — the rarest "converter" in the org.

Maintenance becomes its own goal, and unused systems pile up. A beautiful manual in storage helps only its author.

Grow your nose for "systems that get used". Backing out from the intended user prevents wasted maintenance.

▶ Class-up path: Institutional Designer (Systemizer × Sponsor) — when you can attach budget and authority to the systems

TodayInventory one of your own systems that isn't being used

2 weeksPick one user, run it together, and take feedback

1 monthMeasure "is it still used next week?" and iterate once

Templatize monthly reports so anyone can produce them at consistent quality.

Codify on-floor best practices into procedures/agents as org assets.

When a working system suddenly breaks, diagnose and design prevention.

"Their systems are easy to use" — relied on, though sometimes worried about "over-building".

Systemizers are maintenance pros, but a system that isn't used is nothing. Operators run them, Pioneers feed the pipeline.

Operator →The receiver who runs your system reliably. Turns your systems into on-floor results.

Pioneer →Supplies raw material (inventions). A Pioneer's new experiments become your systemization pipeline.