About this series This is part of a series exploring Organisational Service Management (OSM) - a new lens I’ve developed for understanding how Services actually work, how they fail, and how we can make them meaningful again. OSM is not just a methodology - it’s a psychology, a model of thinking that puts people, context, and accountability back at the heart of Service delivery. If you’ve ever sensed something’s not quite right in how Services get delivered, managed, or measured, this series is for you.
Where effort and experience part ways
We all recognise cognitive bias - a well-documented phenomenon explored in countless books, journals, and training sessions. We try to tame it, to retrain the quirks of our human psychology in pursuit of better, more pragmatic decision-making. But awareness doesn’t eliminate bias - it merely gives us a name for it. And yet, in the world of Services - from repairing a leaky tap to deploying a cutting-edge technology platform - we continue to ignore how bias seeps into our models and measures. We still conform to legacy metrics and outdated assumptions, often forgetting the very people the service is meant to support. In an attempt to give these people a voice we make them stakeholders, or interested groups. We solicit requirements, use cases, all the standard methods to realign what the Service needs to be in a language that is designed to represent it in structured terms. We encourage thinking functionally in silos, gather requirements, construct user stories, formulate epics, ask consumers of the Service to define their outcomes in metrics that reflect process measures. That’s the Service Blind Spot in action - where internal alignment with legacy indicators sets out to mask the external, lived reality.
We acknowledge the bias - then embed it into the very systems we design.
Just as naming a bias doesn’t remove its influence, naming experience gaps won’t close them - unless we have the tools to see, frame, and redesign around them. So, with nothing better to guide us, we define what we can - and justify what we must. More often than not, we’re defining fragments - small elements of a broader picture. And that broader picture? It either gets ignored or assumed to be someone else’s job. It’s assumed that someone else is providing the answer to the most important question. Is this actually providing value for the people who need it? We assume someone else is doing it … so no one is. It’s the gap between what’s measured and what’s experienced. A disconnect between internal confidence and external reality. As an example Conway’s Law identified a pattern, not a path. It revealed the influence of structure, but offered no way to fix it. And like cognitive bias, naming it doesn’t mean escaping it. In all honesty Conway’s Law is not alone, it’s just a single example of an attempt to define something in the hope that defining it will help us avoid it. Diagnosis is fine, avoidance is better. We have an abundance of things that will measure the damage, contain the sprawl, or minimise the impact. What we need to do is avoid it in the first place.
Metrics that Measure nothing
We built our organisations for control, not coherence.
Most organisations were never designed to deliver coherent Services. They evolved in functions, silos, and hierarchies - structures optimised for control, not cohesion. We carved the work up so it could be delivered efficiently. We created departments to manage expertise. And then we put metrics and owners in place to make those silos ‘accountable.’ But Services - real, lived, human Services - don’t follow those lines. They cross them. They weave through them. And they fall apart in the gaps between them. We’ve been conditioned to believe that what gets measured gets managed. But too often, the wrong things are measured - and the right things are left invisible. Dashboards tell us that things are happening as we expected them to - and we all live comfortably with that lie. We celebrate ‘green’ metrics while people struggle. Because the human effort, the emotional friction, and the experience gap aren’t being tracked. Dashboards measure the things we’re most comfortable knowing - not necessarily what matters. The things that we expect to see, things that we have convinced ourselves give a ‘proxy’ for the truth. Who hasn’t worked in an organisation where a Service boasts 98% compliance - while users escalate, shoulder-tap, and silently bypass the system just to get things done?
Human-Centric without Design
Too much of Service Management (as a formal discipline) has been obsessed with process, compliance, and control. But people don’t experience services through frameworks. They experience them through emotion, interaction, and outcome. When we design services around checklists instead of connection, we create systems that might work on paper - but fail in practice. We need to put humans back at the centre. Not just as customers, but as collaborators, contributors, and carriers of the service itself. People can make a bad process work, but a bad process will never make people work.
Good people. Bad patterns.
No one sets out to design a fragmented service. But when ownership is function-based, metrics are internal, and success is defined by SLA compliance, fragmentation becomes invisible - until it fails. We don’t see Services. We see tickets, reports, escalations. We see handoffs, dashboards, and governance meetings. All the machinery of service, but none of the meaning.
Tools Without Transformation
It’s tempting to think that buying a better tool will fix the problem. And while tools are necessary, they’re never sufficient. Yet still we chase the next shiny tool - and mistake the flurry of implementation effort for real progress. After the ‘joy of launch’ subsides, we’re left with the same issues - just with a shinier cog. So we turn to a different sort of tool - the Outsource. Outsourcing is just another shiny wrapper. We assume someone else must know better - but the same bias-driven models persist, just with a new badge - and the flurry continues with no real progress. You can have a new shiny tool. You can Outsource a function. You can automate a Process. But unless your internal culture shifts to support the new way of working, you’ve just outsourced the surface - not the substance. True Service transformation doesn’t come from implementation - it comes once you deliver to people, it comes from the introspection. It comes from understanding the true definition of what you are trying to deliver, the Service that humans will consume - and most importantly how you are adding your unique capability to the overall outcome.
Data, Data everywhere, but not a drop to think with.
The modern organisation is drowning in data. Yet we still struggle to answer basic questions: What Services do we actually provide? Who owns them? Are they working? Who are they for?
That’s because data without structure is noise. And structure without insight is just bureaucracy. We’re drowning in data, clinging to the fallacy that just a bit more ‘insight’ will make it all make sense. We convince ourselves that with just the right dashboard, the problems will become obvious - and the service will magically align. But knowing isn’t the same as changing. So when we have such an abundance of data it’s just like white noise, great for filling a space but it doesn’t carry a tune.
Structural Problem
At the heart of the Service Blind Spot is a structural issue - the way we divide, manage, and govern work. Silos exist for a reason. They create focus, specialisation, and accountability. But they also create isolation, fragmentation, and obfuscation. Each silo has its own metrics, owners, and reporting lines. But no one owns the whole experience. No one sees the service as a system of interdependent parts. And when things fail, they fail quietly. Everyone was doing their job. But the outcome still missed the mark.
Invisible Cost
What lives in the Blind Spot isn’t just poor experiences or broken processes - it’s the slow erosion of belief. It’s the moment when a team delivers exactly what was asked, yet still hears it wasn’t enough. It’s the dashboard that says ‘solved’ while the user is still chasing answers. It’s the project that has a delivery party, but no one is celebrating. It’s the quiet drift of a customer who never complains, just leaves. And it’s the weariness that sets in when people realise that no one owns the whole, that their care and concern won’t change the system. The real cost? It’s the disengagement, the emotional fatigue, the loss of energy and will. When people stop believing they can make it better, they stop trying - and once that faith is gone, the road back is long.
Not a Spot - more a Black Hole.
The Blind Spot? It’s a Black Hole.
It pulls everything into its core, and once you are caught in its pull you are destined for the same results. The only escape is awareness, and the courage to chart a different path. We need a new map. A new legend. A new way to navigate.
OSM: A different way to see
Organisational Service Management (OSM) is my response to this entire problem space. It’s not just a methodology. It’s a psychology. A new lens to understand how services are delivered, experienced, and improved. OSM helps : Make Services visible in dimensions that matter Centre the human experience Connect data with context Create ownership with influence Shift from functional compliance to outcome confidence Build credibility not just in what we know - but in knowing where those limits are
The Service Blind Spot is just the starting point. Because once we define a problem, we can start to fix it. OSM starts by challenging the assumption that Services can be understood functionally. It rejects the idea that SLA/XLA’s, burn rates, financial ratios alone define quality. It questions whether we have clarity on what it is we want to deliver. Instead, OSM asks: What’s the real shape of the Service as experienced? Where is effort being spent vs where value is being felt? What patterns of fragmentation or distortion are at play? What are influences on the outcomes What do we truly know When do we have enough to be credible ?
And critically - how can we make the invisible visible again?
Building Service literacy
You can’t fix what you can’t see. And you can’t lead what you don’t understand. OSM introduces models and frameworks to help leaders see Services as integrated, evolving, human systems - not just technical or operational components. This isn’t about more data. It’s about more meaning. Making the Services credible. Credibility isn’t about data completeness. It’s about the confidence that a service will do what it promises - in the eyes of those who depend on it. Credibility is that ‘gut instinct’ that the Service will deliver its outcome to support people. The credibility to instil trust and faith in the Service, not just a green light on a dashboard that says we are meeting the metrics which no one has faith in. A business cannot survive just on this ‘gut instinct’ - it’s a reasonable human litmus test to start with but it’s not a permanent solution. We need a way of rendering the complex into the graspable, not through seeing every moving part but through having a credible representation we can trust and visualise. The Service Intelligence Base (SIB) is my response to this. It’s not just a smarter data repository, it’s a structured, federated model that connects the dots between Service data, Operational context, Design prediction and lived experience. It’s a credible representation - structured enough to model reality, human enough to guide real decisions.
What’s next?
In future articles, we’ll dive deeper into the thinking that drove me to structure OSM. The SIB will reappear during this journey as the structure to hold our representation. I’ll also share how I’m applying OSM to myself - a practical testbed for the same ideas. Where I can, I’ll highlight organisations on this journey too, and how they’re realising OSM in their own ways. Because the Service Blind Spot isn’t a failure of intent. It’s a failure of design. And design can change - when we lead with the courage to redesign, not just reframe.
Sharing this is part of my own journey in building Strategenz and driving a new way of thinking - and if something here resonated, sparked a thought, or challenged how you see things, I’d love to hear it. Drop a comment, follow along, or share it with someone navigating their own transformation.