Theory
The title trap
A role name hides the scope, authority, evidence, exceptions, and outcomes that determine whether work can move. Comparing the formal description with actual tasks and decisions yields a role decomposition into distinct work units. A title can stay useful for employment, identity, and accountability even when it is a poor automation unit.
Inputs
A named role, observed days of work, policies, systems, and people who receive its output.
Method
Compare the formal description with actual tasks, decisions, interruptions, handoffs, workarounds, and exception handling.
Output
A role decomposition that shows distinct work units and the reason each sits in the role.
Boundary
A title can remain useful for employment, identity, and accountability even when it is a poor automation unit.
Stop
Reject a role level automation plan when the underlying work and authority cannot be named.