Beyond ITSM: The ServiceNow and Microsoft Power Play
Impossible d'ajouter des articles
Désolé, nous ne sommes pas en mesure d'ajouter l'article car votre panier est déjà plein.
Veuillez réessayer plus tard
Veuillez réessayer plus tard
Échec de l’élimination de la liste d'envies.
Veuillez réessayer plus tard
Impossible de suivre le podcast
Impossible de ne plus suivre le podcast
-
Lu par :
-
De :
À propos de ce contenu audio
Microsoft is where intent is created: chats, emails, meetings, documents.
ServiceNow is where intent must become execution: routing, approvals, state, and evidence.
Workflows don’t fail in theory—they fail at org-chart boundaries. 🧠 Key Ideas & Mental Models 1. Digitally Rich, Operationally Fragmented Enterprises have plenty of tools but no shared operating layer. Work moves through inboxes, chats, portals, tickets, and spreadsheets—none of which own end-to-end state. The result is visibility everywhere and progress nowhere. Insight: The real problem isn’t tool sprawl. It’s workflow fragmentation. 2. Tickets Track Pain—Workflows Control Outcomes Tickets log problems. They don’t enforce solutions.
When tickets become the operating model, organizations optimize for logging instead of execution, and humans improvise the real process in side channels. Insight: Enterprises aren’t punished for missing visibility. They’re punished for missing execution. 3. Systems of Record vs Systems of Action
- Systems of record (ERP, HRIS) preserve truth
- Systems of action route work, enforce sequence, and capture evidence
- Microsoft owns engagement: where humans work and express intent
- ServiceNow owns execution: where work becomes a governed state machine
A real operating layer converts events into executable workflows, enforces decisions with identity and policy, and produces defensible outcomes. Insight: Read can be fast and forgiving. Write must be governed. 🧩 Real-World Scenarios Covered
- Employee onboarding without email chains or orphaned access
- Security incident response: Teams for war rooms, ServiceNow for control
- Finance approvals without policy erosion at quarter-end
- Major incidents & emergency change without turning chat into a control plane
- Copilot understands human context
- Now Assist understands operational state
- Workflow entropy (“temporary exceptions” that become policy)
- Shadow automation outside governance
- Permission drift through overscoped connectors and agents
- Microsoft = intent capture and collaboration
- ServiceNow = execution, routing, approvals, and evidence
- Start read-heavy, move to governed writes, then controlled agentic execution
It’s building an operating layer where human intent reliably becomes governed execution—every time, under pressure, with proof.
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.
Vous êtes membre Amazon Prime ?
Bénéficiez automatiquement de 2 livres audio offerts.Bonne écoute !
Aucun commentaire pour le moment