# Empowerment Without Clarity Is Abdication Marquet's sharpest insight isn't that leaders should give more control. It's that empowerment without competence and clarity is incomplete -- and worse, it's still a top-down act. The leader "empowers" the follower, which means the power still originates from the top. The follower receives permission rather than possessing capacity. Real distributed authority requires clarity about purpose, goals, and decision criteria. Drasner calls this the manager's primary obligation: creating clarity where none exists. When a team knows what outcome they're driving toward and what values guide their decisions, they don't need to ask for permission. They have what they need to act. When that clarity is absent, "empowerment" just means people make decisions in the dark -- and the leader blames them for the bad outcomes. This is why "specify goals, not methods" works as a leadership mechanism. Goals provide direction; methods provide constraint. When you specify the goal but leave the method open, you've given people real autonomy -- bounded by shared understanding of what success looks like. When you specify neither goals nor methods but call it empowerment, you've abandoned your responsibilities as a leader. The same pattern appears in open source governance. Projects that articulate clear contribution guidelines, architectural principles, and project vision can distribute decision-making to maintainers and contributors effectively. Projects that say "everyone can contribute" without defining what good contribution looks like generate conflict, rework, and maintainer burnout. The invitation without the framework is abandonment disguised as openness. <!-- atomicity: 1 idea ✓ --> ## Why This Matters If you're a leader saying "I trust my team to make decisions" but haven't articulated what those decisions should optimize for, you're not empowering anyone. You're offloading responsibility while retaining the right to second-guess. Clarity is the difference between delegation and abandonment. ## Links - [[3. Resources/Literature Notes/Your First 30 Days in a New DevRel Role]] — applies-in: a shared definition and stakeholder map create the purpose clarity a new DevRel practitioner needs before acting independently. - [[3. Resources/Literature Notes/Untitled 1]] — applies-in: the Trust Triangle's logic component supplies the clear rationale and expectations that keep managerial trust from becoming unbounded delegation. - [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] — extends: intent gives people a clear purpose within which they can act without waiting for permission. - [[3. Resources/Permanent Notes/Competence Is the Prerequisite for Distributing Authority]] — constrains: clear intent cannot make distributed authority safe when the recipient lacks the skill to act on it. - [[3. Resources/Permanent Notes/Values Alignment Predicts Team Performance Better Than Process Compliance]] — evidence-for: shared values supply the decision criteria that keep empowerment from becoming directionless delegation. - [[3. Resources/Literature Notes/BDFL and NAR - Parallel Structures of Charismatic Authority]] — contrasts: concentrated authority often calls compliance clarity while withholding the purpose and boundaries required for genuine empowerment. - [[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/Engineering Management for the Rest of Us|Engineering Management for the Rest of Us]]