Platform, not tool
ServiceNow should be governed as a strategic enterprise platform. When treated as "just ITSM tooling," organizations accumulate technical debt faster than they deliver value.
I help organizations treat ServiceNow as a strategic enterprise platform — not just a ticketing tool. My work starts with strong data foundations, platform governance, and architecture that scales.
I'm a ServiceNow architect with over 16 years of operational IT experience — from front-line L1 support through system administration to enterprise platform ownership. That path wasn't accidental. Understanding the real problems that service management platforms must solve is the only honest foundation for designing them.
Today I design enterprise-grade ServiceNow environments built on strong data foundations, platform governance, scalable architecture, and automation grounded in operational reality. I don't configure features and move on. I build platforms that remain coherent, governed, and valuable several years after go-live.
My conviction is simple: great platforms start with strong foundations. Most ServiceNow implementations struggle not because of missing features, but because of missing architecture. I exist to close that gap.
ServiceNow should be governed as a strategic enterprise platform. When treated as "just ITSM tooling," organizations accumulate technical debt faster than they deliver value.
Automation built on unreliable data creates unreliable outcomes at scale. CMDB health and CSDM alignment come first — everything else is downstream.
Quick wins are valuable; quick wins that erode platform integrity are liabilities. Every design decision should survive the next three upgrade cycles.
Designing ServiceNow instances as enterprise platforms — scoped, modular, upgrade-safe, and aligned with organizational service strategy.
Building configuration management databases that organizations actually trust — with clear data ownership, health metrics, and alignment to the Common Service Data Model.
Establishing platform governance that balances speed with control — review boards, instance strategy, update-set discipline, and scope management.
Extending ServiceNow beyond IT into HR, facilities, security, and business workflows — with shared architecture and consistent service design.
Designing automation that removes operational friction without creating new complexity — Flow Designer, Integration Hub, orchestration, and event-driven patterns.
Guiding platforms from initial implementation to enterprise-scale maturity — capability roadmaps, technical debt reduction, and continuous improvement frameworks.
Active participant in ServiceNow User Group events across the Nordics — sharing architecture patterns, governance lessons, and platform strategy insights with practitioners.
Regular attendee at Knowledge and CreatorCon conferences. These events aren't networking exercises — they're where platform ideas get pressure-tested against the global community.
Contributing to ServiceNow community forums and discussions. Sharing practical answers grounded in real implementation experience — not textbook theory.
Writing and speaking about platform governance, CMDB strategy, and the gap between vendor promises and operational reality. The ecosystem improves when practitioners share honestly.
I don't list job responsibilities. Here's what I actually solve.
Architecting ServiceNow as the enterprise service backbone for one of Denmark's largest financial groups. Building CMDB/CSDM foundations trusted by operations, establishing governance models that keep the platform scalable, and setting platform standards for long-term consistency. Designing integration patterns that connect ServiceNow to the broader enterprise ecosystem while supporting both internal operations and customer-facing service delivery. The challenge here is scale, data integrity, and long-term platform coherence across a complex financial organization.
Led the evolution from a legacy ITSM setup toward a governed, architecture-driven ServiceNow platform. Focused on operational alignment — ensuring that what was designed in architecture actually worked in daily service operations. Drove automation adoption grounded in real operational needs rather than theoretical efficiency gains, while establishing governance processes and a platform approach suited to high-complexity, multi-tenant enterprise environments.
I work with platform leaders, architects, and organizations that are serious about treating ServiceNow as a strategic enterprise platform. If you're scaling ServiceNow, building governance, or rethinking your platform architecture — I'd welcome the conversation.