# Intent-Based Leadership Outperforms Permission-Based Leadership When someone says "I intend to" instead of "May I," they've already done the thinking. They've assessed the situation, considered their options, and formed a plan. The leader's role shifts from approving actions to confirming alignment. This single language change -- replacing permission-seeking with intent-declaring -- restructures who owns the decision. Marquet's "I intend to" framework on the USS Santa Fe didn't just change communication patterns. It forced every person in the chain to think before acting. You can't declare intent without understanding the situation well enough to form a plan. The language itself became a competence filter: if you couldn't articulate what you intended to do and why, you weren't ready to act. This maps directly to how distributed authority fails in open source BDFL models. In BDFL governance, contributors request permission from a single authority. The bottleneck isn't the contributor's competence -- it's the leader's availability and willingness to approve. Intent-based leadership removes this bottleneck. When contributors operate with clear intent and shared understanding of project goals, they don't need a single person to approve every decision. The leader-leader model is structurally incompatible with BDFL governance, which is why projects that scale beyond their founder eventually face a governance crisis. The practical test is what happens when the leader is absent. In permission-based systems, work stops or quality drops. In intent-based systems, the work continues because the decision-making capacity is distributed. As Marquet observed, when a unit's performance drops after an officer leaves, that's evidence of a leader-follower model -- not of good leadership. <!-- atomicity: 1 idea ✓ --> ## Why This Matters If you're building a team, a project, or a community, the question isn't "how much authority should I give people?" It's "how do I build the conditions where people can declare and act on their own intent?" The answer involves competence, clarity, and trust -- not permission slips. ## Links - [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] — applies-in: distributing intent reduces the market risk created when every consequential decision and trust judgment routes through one founder. - [[BDFL Litigation Necessarily Implicates Personal Corporate and Foundation Roles Because the BDFL Has Concentrated Them]] — contrasts: distributed intent and role clarity reduce the personal-corporate-foundation overlap that concentrated permission systems create. - [[3. Resources/Literature Notes/Untitled 1]] — evidence-for: its Trust Triangle ties credibility to transparent intent, empathy, and clear reasoning during a manager's first months. - [[3. Resources/Permanent Notes/The Merit Trap - Self-Worth in Systems of Singular Authority]] — contrasts: intent distributes judgment, while singular permission systems make one authority's approval the measure of both work and worth. - [[3. Resources/Literature Notes/BDFL and NAR - Parallel Structures of Charismatic Authority]] — contrasts: charismatic authority centralizes permission in a person instead of making purpose and decision boundaries explicit. - [[3. Resources/Permanent Notes/Competence Is the Prerequisite for Distributing Authority]] — constrains: intent can replace permission only when the person receiving authority has the competence to act on it. - [[3. Resources/Permanent Notes/Empowerment Without Clarity Is Abdication]] — extends: intent supplies the purpose and boundaries that let authority move outward without becoming leader abandonment. - [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] — contrasts: distributing intent and decision authority offers a structural alternative to institutions fused to one unaccountable leader - [[3. Resources/Permanent Notes/The Workhorse Trap Prevents Leadership Emergence]] — applies-in: intent-based delegation breaks the leader's dependence on doing every difficult task personally. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Leadership challenges. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under Leadership & Distributed Authority. ## Source - [[3. Resources/Literature Notes/Leadership and Distributed Authority - From Command to Intent - Literature Note]] - [[3. Resources/Readwise/Books/Drive by Daniel H. Pink|Drive by Daniel H. Pink]]