# Competence Is the Prerequisite for Distributing Authority You can't give someone decision-making authority they don't have the knowledge to exercise. Marquet's framework makes this explicit: control, competence, and clarity are a triad. Push control downward without matching competence upward, and you get bad decisions made faster. That's worse than the centralized model you were trying to escape. This is where most "empowerment" initiatives fail. A leader announces that the team now has more autonomy, but doesn't invest in the training, context, or technical depth required for that autonomy to produce good outcomes. The team makes mistakes. The leader pulls authority back. Everyone concludes that distributed authority doesn't work -- when the real failure was skipping the competence step. Azzarello reframes delegation in the same terms: delegation isn't offloading tasks, it's building value in your team. When you delegate effectively, the person receiving the work becomes more capable over time. The authority transfer is permanent because the competence transfer is real. When you just hand off tasks without development, you've created a dependency that snaps back the moment something goes wrong. The open source parallel is instructive. Projects with strong onboarding documentation, mentorship pipelines, and graduated responsibility paths produce contributors who can eventually maintain the project independently. Projects where the founder holds all context in their head produce a bus-factor-of-one situation. The competence wasn't distributed, so the authority can't be either. <!-- atomicity: 1 idea ✓ --> ## Why This Matters Distributing authority is not a values statement. It's an investment. You have to build the competence infrastructure first -- documentation, training, mentorship, graduated responsibility -- or the distribution will collapse under its own weight. The sequence matters: competence first, then control. ## Links - [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] — applies-in: intent-based control works only when people have the competence to act on the stated intent - [[3. Resources/Permanent Notes/Empowerment Without Clarity Is Abdication]] — extends: competence and clarity are separate prerequisites for authority that does not collapse back to the leader - [[3. Resources/Permanent Notes/The Workhorse Trap Prevents Leadership Emergence]] — evidence-for: leaders who keep doing the work deny others the practice through which competence grows - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — applies-in: distributing DevRel authority without role knowledge and support shifts overload rather than building capacity - [[3. Resources/Readwise/Articles/The Wired Word for 7262026]] — evidence-for: a leadership vacancy exposed capacity among more than seventy lay participants that formal leadership had not made visible. - [[3. Resources/Permanent Notes/A Capability Transfer Is Proven by Absence Not by a Handoff]] — because this supplies the test for whether the prerequisite was met: if the work collapses in the holder's absence, competence was never built and the authority transfer was nominal. - [[3. Resources/MOCs/Open Source Governance MOC]] — because it sets the precondition every delegation and succession design in this MOC depends on: authority handed to someone without the competence to use it returns as a bottleneck. ## Source - [[3. Resources/Literature Notes/Leadership and Distributed Authority - From Command to Intent - Literature Note]] - [[3. Resources/Readwise/Books/Engineering Management for the Rest of Us|Engineering Management for the Rest of Us]] - [[3. Resources/Literature Notes/Responsibilities of a Code of Conduct Responder]] — incident-response authority depends on trained communication, documentation, empathy, and conflict judgment