M365.FM - Modern work, security, and productivity with Microsoft 365 Podcast Por Mirko Peters (Microsoft 365 consultant and trainer) arte de portada

M365.FM - Modern work, security, and productivity with Microsoft 365

M365.FM - Modern work, security, and productivity with Microsoft 365

De: Mirko Peters (Microsoft 365 consultant and trainer)
Escúchala gratis

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.Copyright Mirko Peters / m365.fm - Part of the m365.show Network - News, tips, and best practices for Microsoft 365 admins Política y Gobierno
Episodios
  • The Designed Organization: Why Optimization is the Enemy of Performance

    The Designed Organization: Why Optimization is the Enemy of Performance
    Mar 29 2026
    Optimization feels like progress. It gives leaders measurable wins, cleaner processes, and a sense of control. But inside most organizations, optimization is exactly how performance becomes slower, heavier, and more political over time. Because optimizing individual parts without redesigning the system doesn’t create flow — it creates fragmentation. In this episode, Mirko Peters breaks down why modern organizations struggle to turn intelligence into action, why AI is exposing structural weaknesses, and how performance actually emerges from designing flow, not improving parts. ⚠️ The Core Argument You cannot fix performance by improving isolated components. Performance is not the sum of optimized teams, tools, or processes. It is the result of how well your organization is designed to move:decisionsdatacontextand authorityIf those flows are fragmented, optimization only strengthens the fragmentation. 🧠 The Optimization Trap Most organizations don’t fail because of bad decisions — they fail because of reasonable decisions made in isolation. Typical examples:Tightening governanceRolling out Copilot to a teamAutomating tasks with Power AutomateStandardizing SharePoint structuresEach move looks like a win locally. But systemically, these actions often:reinforce silosincrease handoffsfragment ownershipand slow down decision-making👉 The result:Local excellence, global drag 🏗️ What an Organization Really Is An organization is not:an org charta tech stacka governance modelThose are just the visible layers. The organization itself is a flow architecture — how things actually move. The 4 Core Flows 1. Decision Flow How signals turn into action:Who sees the issue?Who decides?How long does it take?👉 Strategy is executed through decision velocity, not intent. 2. Data Flow Where truth lives and how it moves:What is the source of truth?Who owns definitions?How many versions exist?👉 When truth fragments, decisions turn into negotiation. 3. Interaction Flow How context travels between people:Where is work discussed?Where is rationale stored?How is meaning preserved?👉 Coordination moves tasks.Connection moves meaning. 4. Power (Hidden Layer) Who can actually act:Who can override decisions?Who can delay work?Who really decides under pressure?👉 The real operating model = the power map, not the process map. 🏛️ Why Governance Doesn’t Fix It Governance is not an operating model — it’s a control framework. When the system is misdesigned:Governance adds friction, not clarityApprovals multiply without improving decisionsPolicies formalize confusionThis leads to:“default-no” behaviorescalation loopsshadow governance (side channels, informal decisions)👉 Governance should protect flow, not replace it. 📉 The AI Reality Check ~95% of generative AI pilots fail to create measurable business impact. Not because:models are weakprompts are badusers resistBut because:👉 Organizations cannot absorb the output AI generates answers in seconds. But organizations still need:days to validate contextmultiple approvalsrepeated data reconciliation👉 The constraint isn’t intelligence.👉 The constraint is architecture. ⚡ Decision Velocity: The Metric That Matters The most important performance metric today is: Decision Velocity Time from signal → action Not:dashboard updatesmodel accuracyactivity levelsBut:how fast the organization actually movesAI compresses analysis. If your system cannot convert insight into action:👉 You don’t have a technology problem👉 You have a design problem 🔄 Why Transformation Programs Fail Most transformation efforts stall because they:deploy tools without redesigning flowmap “ideal processes” instead of real behavioroptimize silos instead of the systemignore power and incentivesCommon failure patterns:Successful pilots that don’t scaleBeautiful process maps that don’t reflect realityIncreased activity without improved outcomesMore dashboards, more meetings, less clarity👉 Deployment ≠ transformation 🔍 The Hidden Reality Inside Organizations When you observe real workflows, you find:Decisions waiting for missing contextData being rebuilt multiple timesOwnership disappearing at handoffsWork moving through side channelsApprovals repeating without adding valuePeople compensate by:carrying context manuallycreating private trackersadding meetingsbuilding informal networks👉 Humans become middleware for a broken system 🛠️ What Actually Works: Redesigning Flow Performance improves when organizations redesign how work moves. Key changes: 1. Decision ClarityDefine clear decision ownersSeparate contributors from approversReduce unnecessary approvals2. Data OwnershipBecome 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.
    Más Menos
    1 h y 23 m
  • AI Won’t Fix Your Business — It Will Expose It

    AI Won’t Fix Your Business — It Will Expose It
    Mar 28 2026
    AI isn’t a repair layer for your business.It’s an exposure layer. In this episode, Mirko Peters breaks down a hard truth leaders keep missing: AI will not fix unclear ownership, messy access, or fragmented data —it will surface those weaknesses instantly. What looks like “AI transformation” is often something else entirely:a system-level audit of how your business actually operates. 🧠 Key Insight AI doesn’t transform — it amplifies.Strong structure → faster, clearer decisionsWeak structure → faster confusion and visible misalignmentAI is not intelligence applied to your business.It is your business, reflected back at machine speed. ⚠️ Why AI Rollouts Feel Successful (At First) Early signals are misleading:Meeting summaries look “good enough”Drafts feel productiveLow-risk use cases hide deeper issuesBut this is a false positive. Early success tests language generation — not operational readiness. 🔍 What AI Actually Exposes 1. Data Reality (Not Assumptions)Duplicate filesOutdated documentsConflicting versions of truthAI doesn’t “understand” your business —it retrieves what exists. If your data is fragmented, your answers will be too. 2. Permission ChaosOvershared folders become active contextOld access = present-day riskIrrelevant data enters decision-makingPermissions are no longer just security —they define relevance. 3. Missing ClassificationNo clear hierarchy of importanceStrategic vs. trivial data treated equallyLabels ignored or inconsistentResult:Generic, flattened, unreliable outputs 4. Unclear Ownership The most critical failure point. If no one owns the source:No one owns the answerNo one can act confidentlyAI exposes this instantly. 📉 The “Week 6–12 Stall” Most AI rollouts slow down here. Why?Early novelty fadesReal work beginsTrust gets testedWhat happens next:People verify instead of trustAI used for low-stakes work onlyAdoption looks stable — but confidence drops⚡ The Hidden Cost: Verification Before AI:Effort = finding + draftingAfter AI:Effort = checking + validatingIf verification becomes mandatory, AI isn’t saving time —it’s shifting the burden. 📊 The Only Metric That Matters Decision Latency Not:UsagePromptsLicensesBut: 👉 How fast can people move from question → confident action If AI speeds output but slows trust:your system is not aligned. 🧪 The Real Role of AI AI is not:A transformation toolA cleanup mechanismA replacement for structureAI is: An audit surface for your operating model It reveals:Where truth is unclearWhere ownership is missingWhere systems depend on human workaround🏗️ What To Do Instead Step 1: Expose RealityAsk real business questions in AICompare outputs to actual truthLook for:DriftContradictionsUser hesitationStep 2: Fix AccessAlign permissions with real responsibilityRemove legacy and inherited accessReduce context noiseStep 3: Reduce Data NoiseEliminate duplicatesArchive outdated contentDefine authoritative sourcesStep 4: Clarify Ownership For every domain:Who owns the source?Who owns the decision?Who updates it?Step 5: Reintroduce AI SelectivelyStart where structure is strongAvoid high-ambiguity workflows first🎯 Final Takeaway If your AI isn’t working: It’s probably not an AI problem.It’s a system problem. And that’s good news. Because systems can be:ObservedClarifiedRedesigned🔁 Closing Thought AI doesn’t create your business reality. It reveals it. So the real question is: Are you willing to see what it shows you? 📣 Call to Action If this episode changed how you think about AI:Follow the podcastLeave a reviewConnect with Mirko PetersShare the next topic you want unpackedBecome 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.
    Más Menos
    1 h y 23 m
  • The Permission Problem: Who Actually Has Power in Your Organization?

    The Permission Problem: Who Actually Has Power in Your Organization?
    Mar 27 2026
    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 StructuralRepeated friction is rarely about personalities—it’s a system outcomeOrganizations misdiagnose structural issues as “people problems”Work flows through access and context, not org charts2. Authority ≠ PowerAuthority = formal accountability (titles, roles)Power = ability to move work (access, context, trust)Decisions happen where context exists—not where authority sits3. Organizations Drift Over TimePermissions, ownership, and workflows accumulate historyGovernance reflects intent, but systems reflect reality“Temporary fixes” become permanent operating models4. Hidden Gatekeepers Control FlowCertain individuals become invisible infrastructureWork routes through them because they hold:ContextAccessTrustThis creates bottlenecks, burnout, and fragility5. Decision Latency Reveals PowerTime delays show where dependency existsMost delays are not approvals—they’re waiting for contextWhere work slows down = where power actually sits6. Permissions Define InfluenceEffective access ≠ intended governanceMisalignment leads to:Weak accountabilityHidden gatekeepingFalse confidence in control7. Communication Centrality = InfluencePower sits with people who:Bridge teamsTranslate contextAppear in every critical conversationThese are your informal decision brokers8. Content Ownership = Information PowerControl of SharePoint = control of truthIf leaders can’t access trusted content:Their authority becomes symbolicInformation gaps slow decisions more than approvals9. Shadow IT & Shadow AI Are SignalsNot rebellion—compensation for broken systemsPeople bypass governance to restore speed and clarityShadow behavior highlights unmet operational needs10. AI Amplifies Your Existing DesignAI doesn’t fix your organization—it reveals and scales itBad permissions → faster exposureMissing context → faster bad decisionsCopilot success depends on structural alignment⚠️ Why Copilot Pilots FailNot a technology problemA permission and access problemSymptoms:Uneven results between usersLack of trust in outputsIncreased dependency on human gatekeepers🔄 Two Failure Modes Over-Permissioned OrganizationsToo much access → confusion & weak accountabilityVisibility without ownership → poor decisionsLocked-Down OrganizationsToo little access → bottlenecks & slow executionControl 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 ≠ AccessAuthority ≠ ExecutionGovernance ≠ Reality🛠️ Practical Actions 1. Measure Decision LatencyTrack time from request → usable decisionIdentify where work waits and why2. Audit Access vs ResponsibilityCompare:Who is accountableWho actually has accessLook for:Stale permissionsHidden exceptionsMissing access for decision-makers3. Reduce Hidden DependenciesIdentify single points of failureAdd redundancy:Content ownershipWorkflow controlContext knowledgeDesign systems that don’t rely on heroics🧑‍💼 Executive Takeaway Digital structure is not IT hygiene—it is business design. Leaders must:Treat permissions as strategyAlign access with accountabilityBuild redundancy into systemsEnsure the environment deserves to be acceleratedBecome 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.
    Más Menos
    1 h y 22 m
Todavía no hay opiniones