OSM is how Strategenz makes a service truly visible - described in terms that mean something to the real people who deliver it, not in org charts or rolled-up KPIs. A whole organisation, surfaced through the perspective of the service it actually provides.
A strategy deck tells you what the service should be. An org chart tells you which boxes report to which. A KPI dashboard tells you what last quarter looked like. None of them show the actual service - the thing the organisation produces - in terms the people who deliver it would recognise. OSM is the practice that makes that service visible.
An organisation’s service is rarely owned by one team. It is produced - every day - by the joint behaviour of many functions: product, ops, support, commercial, technology, the lot. When the service isn’t visible as a whole, the only thing left to manage is the org chart, and the service becomes whatever falls out of it.
OSM surfaces that whole. It gives leaders, and the people doing the work, a shared way to see what the service actually is - described in language they recognise, not in abstractions, hierarchies or quarterly numbers. Once a service is visible, it can be reasoned about. Until it is, it can only be reorganised.
It is a working practice, not a one-off model. The point is not to draw it once. The point is to keep it in view.
OSM holds together because each perspective only works if the others are honest. Define without Resource is a brochure. Resource without Connect is a head-count plan. Connect without Run is a wiring diagram. Run without Define is a treadmill.
Service catalogue, customer outcomes, the promise behind each one.
Roles, skills, capacity, technology, suppliers - the shape, not just the count.
Hand-offs, contracts, shared data, the seams that hold the service together.
Operating rhythm, decisions, escalations, leading signals - the daily operation.
OSM uses the same vocabulary across every engagement. These are the recurring practices - the things a leadership team actually does to manage the service over time.
A one-paragraph statement of what this service exists to do, for whom, on what terms - owned by the leadership team, not a function.
Four to seven principles that resolve the trade-offs the Promise cannot, and that every function commits to.
The cross-functional mix of skills, modes and capacity needed to deliver the service, expressed as a profile rather than a count.
The minimum set of systems, data and suppliers the service depends on, owned at the organisation level.
Explicit, named agreements at every boundary where the service crosses a function.
The cadence of decisions, reviews and signals that keep the service honest week to week.
A short list of leading indicators across the four perspectives - not a dashboard.
The condition under which the service definition itself must be reopened, and who has the authority to do so.
Every engagement is built to end. The measure of our work isn’t how long we stay - it’s whether your team can run the service after we’ve gone. OSM is not a deliverable. It is the practice through which an engagement is run - diagnose the service, redraw what is missing, rehearse it against reality, then hand it back to the organisation.
A close investigation of how the service is actually defined, resourced, connected and run today - across functions, not within them. Findings that matter, not recommendations.
A working session with the leadership team to redraw the perspectives that need it.
We run the redrawn service against real decisions, real weeks, real edge cases. Most "designs" never survive this step. The ones that do are the ones the organisation will actually use.
The leadership team owns the practice. Strategenz leaves a credible operating manual with checkpoints that allow self assessment. No retainers, no embedded consultants, no 400 page incomprehensible document - you can operate the model yourself.
A short conversation usually tells us. We'll be honest if it doesn't fit.