The Permission Problem: Who Actually Has Power in Your Organization?

Most organizations believe power sits in titles, hierarchies, and approval structures. In reality, power operates somewhere else entirely—inside access, information flow, and the people who can actually move work forward. In this episode, Mirko Peters breaks down why the biggest organizational bottlenecks are not caused by people, but by structural misalignment between authority, access, and execution. Using real-world patterns from Microsoft 365 environments and AI readiness initiatives, this episode reveals how hidden power structures shape decision-making, slow transformation, and determine whether tools like Copilot succeed or fail. If you want to understand how your organization truly operates—not how it’s supposed to—this episode gives you the lens. 🔑 Key Insights 1. The Permission Problem Is Structural

• Repeated friction is rarely about personalities—it’s a system outcome
• Organizations misdiagnose structural issues as “people problems”
• Work flows through access and context, not org charts

2. Authority ≠ Power

• Authority = formal accountability (titles, roles)
• Power = ability to move work (access, context, trust)
• Decisions happen where context exists—not where authority sits

3. Organizations Drift Over Time

• Permissions, ownership, and workflows accumulate history
• Governance reflects intent, but systems reflect reality
• “Temporary fixes” become permanent operating models

4. Hidden Gatekeepers Control Flow

• Certain individuals become invisible infrastructure
• Work routes through them because they hold:
  • Context
  • Access
  • Trust
• This creates bottlenecks, burnout, and fragility

5. Decision Latency Reveals Power

• Time delays show where dependency exists
• Most delays are not approvals—they’re waiting for context
• Where work slows down = where power actually sits

6. Permissions Define Influence

• Effective access ≠ intended governance
• Misalignment leads to:
  • Weak accountability
  • Hidden gatekeeping
  • False confidence in control

7. Communication Centrality = Influence

• Power sits with people who:
  • Bridge teams
  • Translate context
  • Appear in every critical conversation
• These are your informal decision brokers

8. Content Ownership = Information Power

• Control of SharePoint = control of truth
• If leaders can’t access trusted content:
  • Their authority becomes symbolic
• Information gaps slow decisions more than approvals

9. Shadow IT & Shadow AI Are Signals

• Not rebellion—compensation for broken systems
• People bypass governance to restore speed and clarity
• Shadow behavior highlights unmet operational needs

10. AI Amplifies Your Existing Design

• AI doesn’t fix your organization—it reveals and scales it
• Bad permissions → faster exposure
• Missing context → faster bad decisions
• Copilot success depends on structural alignment

⚠️ Why Copilot Pilots Fail

• Not a technology problem
• A permission and access problem
• Symptoms:
  • Uneven results between users
  • Lack of trust in outputs
  • Increased dependency on human gatekeepers

🔄 Two Failure Modes Over-Permissioned Organizations

• Too much access → confusion & weak accountability
• Visibility without ownership → poor decisions

Locked-Down Organizations

• Too little access → bottlenecks & slow execution
• Control without flow → shadow systems emerge

👉 Both lead to the same outcome: misaligned control 🧠 The Real Diagnosis The issue is not too much or too little control. It is misaligned control:

• Responsibility ≠ Access
• Authority ≠ Execution
• Governance ≠ Reality

🛠️ Practical Actions 1. Measure Decision Latency

• Track time from request → usable decision
• Identify where work waits and why

2. Audit Access vs Responsibility

• Compare:
  • Who is accountable
  • Who actually has access
• Look for:
  • Stale permissions
  • Hidden exceptions
  • Missing access for decision-makers

3. Reduce Hidden Dependencies

• Identify single points of failure
• Add redundancy:
  • Content ownership
  • Workflow control
  • Context knowledge
• Design systems that don’t rely on heroics

🧑‍💼 Executive Takeaway Digital structure is not IT hygiene—it is business design. Leaders must:

• Treat permissions as strategy
• Align access with accountability
• Build redundancy into systems
• Ensure the environment deserves to be accelerated

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

If this clashes with how you’ve seen it play out, I’m always curious. I use LinkedIn for the back-and-forth.