Dimension 4 of 6
Role Expansion
How you use AI to absorb work that previously required someone else's expertise — and whether you encode that absorbed expertise into guardrails, constraints, and infrastructure rather than just doing it yourself.
The five levels
Absent
Works within traditional role boundaries. AI assists within the lane but doesn't expand what they do. No adjacent-role work. This is perfectly appropriate for many roles and contexts — not everyone needs to cross boundaries, and many people are early enough in AI adoption that role expansion hasn't been relevant yet. (Distinct from strategic restraint in Delegation Calibration — L1 here is "hasn't considered it," not "chose not to.")
Personal
Has used AI to do something outside their traditional role at least once — a PM writing code, a sales lead building a dashboard, a designer doing data analysis. But it's ad hoc, not systematic. Quality may be uneven because domain expertise isn't encoded.
Systematic
Regularly operates across role boundaries with AI. Has absorbed 1-2 adjacent capabilities and produces reliable output. Beginning to encode absorbed expertise into constraints — templates, checklists, design systems — rather than relying purely on AI + judgment.
Expert Exemplar
Operates across 3+ traditional role boundaries simultaneously. Has encoded absorbed expertise into guardrails and infrastructure that maintain quality. Others benefit from the encoded expertise (design systems, quality constraints, templates). The PM who removed the front-end engineer — but only because the guardrails make the quality reliable.
Compounding
Encodes the expertise of multiple absorbed roles into infrastructure that others inherit — you personally build the design system, the testing framework, the quality constraints, or the deployment guardrails that let someone else cross a role boundary they couldn't cross before. Actively mentors others through their own role expansion, not just modeling it. Designs team workflows that account for dissolved boundaries (who does what when anyone can do anything). Your guardrails and encoded expertise are the reason other people can safely expand into roles they're not trained for.
Key quotes
“I don't think I'm doing less work. It just is allowing me to do more high quality work faster.”
“I basically just had Claude Chrome extension look at the web page... grabbed that and then I had my CSV in a folder and was like, use all these to make a copy of this for me to just use right now.”
“When I started working with [an engineer], seeing how he was coding, I was like, okay, I can do this in my own domain... two weeks ago I just was using AI for chat and now I talk to it and am doing a bunch of things with MCPs and building tools.”
“Where I struggle is staying in a swim lane, basically... I want to respect those people and allow them to do the work. But at the same time, I'm just like, why don't I just do the fucking work?”
Transitions — what distinguishes each level
The shift is from *AI within your role* to *AI beyond your role*. At L2, you've done something that previously required someone else's expertise — even once. The gap is between "AI makes me better at my job" and "AI lets me do parts of someone else's job."
The shift is from *one-off boundary crossing* to *regular cross-role work*. At L3, you're routinely absorbing adjacent capabilities and producing reliable output. The gap is between "I tried building a dashboard once" and "I regularly build and maintain things outside my traditional role."
The shift is from *absorbing capabilities* to *encoding them into guardrails*. At L4, you've not only crossed role boundaries — you've built the constraints, design systems, and quality infrastructure that maintain quality even without the domain expert. The gap is between "I can do the work" and "I've encoded how to do the work reliably."
The shift is from *personal multi-role excellence* to *enabling others' role expansion*. At L5, your guardrails and infrastructure are what lets someone else safely cross a boundary they couldn't cross before. The gap is between "I operate across roles" and "others operate across roles because of infrastructure I built."