Why You Should Separate Functional Leadership From Disciplinary Leadership
Functional and disciplinary leadership are two different jobs that classic leadership thinking blends together. Why the separation resolves the tension between administration and expertise, and how a Role Contract anchors it for human roles too.
Classic leadership thinking conflates two things that have nothing to do with each other: functional leadership and disciplinary leadership. Anyone who doesn't separate the two gives away a large share of their own impact in a self-organized, highly self-disciplined team, because they spend time on administration they could otherwise spend on expertise.
Anyone can, in principle, lead functionally
Functional leadership is expertise, understanding of the task, and the ability to make the right call in this specific moment. When an experienced subject-matter expert situationally takes charge of exactly the problem she knows best, the result is usually better than when every decision runs through the same formal channel.
That's not a drawback, it's an advantage most companies leave unused: specialists can take the lead on their topic in the moment, and on a different topic, someone else takes the lead. Functional leadership is bound to the task, not to a box on the org chart.
Functional leadership is bound to the task, not to a box on the org chart.
Disciplinary leadership is administration
Disciplinary leadership, on the other hand, is mostly legal and administrative: vacation requests, target agreements, formal approvals. The question that raises: why do you strictly need a manager for that, if at its core it's a clearly defined role?
The Peter Principle describes how this goes wrong: everyone gets promoted until they no longer meet the demands of the new level, a widespread and typical pattern in classically organized companies. Promoting a specialist several hierarchy levels purely for strong technical performance automatically hands her disciplinary duties she was never selected for and that have nothing to do with her actual strength.
Where Rocket Routine OS steps in
This separation is exactly the problem a Role Contract solves structurally, for human roles too, not only for AI operators. A Role Contract binds decision rights to the role and its boundaries, not to a level in the hierarchy. Who is responsible for what, which escalation triggers apply, and where approval is required is explicit, instead of implicitly hanging off a title.
When an organization has a high degree of freedom, that comes with the need for high self-discipline, so everyone still works toward the same larger whole. What that requires isn't an additional disciplinary layer, but clear roles and tasks in which everyone can do what they do best, keep developing continuously, and carry responsibility for their outcome, not for their position.
It's not about titles
It's not about positions, not about titles, not about power, but about enjoying the work, lifelong learning, and results that actually hold up. Everyone in the company needs to be enabled to take on responsibility, and that only works once functional and disciplinary leadership stop collapsing into one person and one title, and are treated as what they are: two different jobs with two different answers.