<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ross Williamson on Medium]]></title>
        <description><![CDATA[Stories by Ross Williamson on Medium]]></description>
        <link>https://medium.com/@rosswilliamson-strategenz?source=rss-c3460ef8481f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0AYk2ZN_6lbiP2t4KgadXw.jpeg</url>
            <title>Stories by Ross Williamson on Medium</title>
            <link>https://medium.com/@rosswilliamson-strategenz?source=rss-c3460ef8481f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:12:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rosswilliamson-strategenz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Nothing Is Ever Overwritten]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/nothing-is-ever-overwritten-4933dbcb5e86?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4933dbcb5e86</guid>
            <category><![CDATA[management-services]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[it-service-management]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 00:00:24 GMT</pubDate>
            <atom:updated>2026-08-17T23:23:37.293Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Decision You Can No Longer Defend</h3><p>Someone is going to ask you why you did that.</p><p>Not today. In about eighteen months, in a meeting you didn’t expect to be in, in front of people who weren’t there the first time. The question will be perfectly reasonable, and it will be asked in a tone that suggests the answer is obvious.</p><p>Eighteen months ago you stood down the investment. The capability was peripheral — everyone said so, the assessment said so, and the money was needed somewhere it would do more good. You made the call on the evidence in front of you. It was the right call on that evidence.</p><p>The capability is not peripheral now. It is on the critical path of something that matters, and the assessment in front of you today says exactly that. In a calm, confident voice. With no indication that it has ever said anything else.</p><p>So you go looking for the version that justified you. It isn’t there. Not missing, not deleted, not lost in a migration — it was <em>updated</em>. Somebody did the responsible thing and brought the record in line with reality, and in doing so removed the only evidence that reality used to be different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_OzElJSYIxsbXzr_" /><figcaption>Photo by <a href="https://unsplash.com/@silverkblack?utm_source=strategenz&amp;utm_medium=referral">Vitaly Gariev</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You made a defensible decision. You can no longer demonstrate that it was defensible.</p><p>And the organisation comes off worse than you do, because it is about to learn the wrong lesson. It will conclude that someone was careless. The actual lesson — that the assessment moved, and nobody noticed it moving, and no decision was ever revisited when it did — is the one nobody can see, because the evidence for it was tidied away one field at a time.</p><h3>Keeping It Current Is How You Lose It</h3><p>Every model we build asks one question. <em>What is true?</em> Then it stores the answer.</p><p>When the answer changes we replace it, and we call that maintenance. Data quality. Keeping the record accurate. It sounds so obviously correct that it takes an effort to notice it is a choice, and a strange one: we are running systems whose defining behaviour is to destroy their own past.</p><p>First, a word about <strong>true</strong> — because it is about to do more work than it should, and it is not quite the word we mean.</p><p>Nothing in this argument requires a claim to be accurate, verified or exact. It does not require it to be right. When this piece calls something true, it means only that it is the best account anybody currently has: made by someone who was in a position to know, bounded to the part they can actually speak for, and good enough that a reasonable person would act on it.</p><p>That is credibility, and credibility is not precision.</p><blockquote><em>A field filled to four decimal places by somebody who was guessing is precise and worthless. “I can’t tell you what it costs, but I can tell you it’s the part that breaks first” is imprecise and immediately useful.</em></blockquote><p>Read <em>true</em> that way for the rest of this piece — the best we know, trusted enough to decide from — and notice that it has to be a lower bar than accuracy. Set the bar at accuracy and almost nothing clears it, which is <a href="https://www.strategenz.com/articles/contribution-without-consensus">exactly how a model ends up empty</a>.</p><p>There is a better question, then, and it has the useful property that the first one can be recovered from it.</p><p><em>What has been claimed, about what, by whom, and when?</em></p><p>Answer it and you can always derive what is true now — take the claims, apply precedence, read off the result. But it does not work in reverse. From the current answer you cannot recover when it arrived, what it replaced, or whether it has been quietly reversed twice since spring.</p><p>Overwriting is lossy in exactly one direction. It is the direction we have been going for forty years.</p><blockquote><em>A record that is always current can never tell you when it wasn’t.</em></blockquote><p><a href="https://www.strategenz.com/articles/the-myth-of-the-single-source-of-truth">The Myth of the Single Source of Truth</a> argued that the authoritative view should be composed on demand from layers, rather than negotiated into a single stored row.</p><p>Follow that one step further than it went.</p><p>If there is no single row, then “update the record” is not a coherent operation. There is nothing to overwrite. There are layers, each saying what it has an opinion about, and every one of those claims already carries a date — the moment somebody made it. The date is not metadata bolted onto the side. It is part of what the claim <em>is</em>.</p><p>Which means the answer you get today is the composition evaluated at today. That is all “current” has ever meant. Ask the same question with a different date and you get a different answer, assembled the same way, equally real, equally authoritative for its moment. And not one field of it. Every claim in the model carries a date, so the entire composition evaluates at that date — you are not retrieving an old value, you are standing in the model as it stood.</p><p>History stops being a feature you add to the model. It becomes the model. What we have been calling the current state turns out to be a query — one among many, with no special status except that it happens to be the one we ask most often.</p><p>Nothing has to be discarded for this to work, because nothing was ever being replaced. It was only ever being added to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wHCDkgRm0rtrX_ta" /><figcaption>Photo by <a href="https://unsplash.com/@afafa?utm_source=strategenz&amp;utm_medium=referral">Andreas Fickl</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What You Can Ask a Model That Remembers</h3><p>Three questions become available. None of them can be answered by a system that keeps itself tidy, and none of them is idle — behind each one is somebody with a decision in front of them and a date by which it has to be made.</p><p><strong>When did this become true?</strong> Not whether it is true — when it started being true.</p><p>The person asking is deciding whether to act at all. A cost that has been climbing steadily for two years and a cost that jumped last week are the same number today and two completely different problems, needing two completely different responses. One is a trend you have been ignoring; the other is an event you have just discovered. A model that only holds today’s answer flattens both into a single confident present tense and leaves you to guess which you are looking at — usually wrongly, and usually in the direction that requires less work.</p><p><strong>What did we believe when we committed?</strong> This is the one that would have saved the meeting we opened with.</p><p>The decision here isn’t about the past at all. It is whether to trust the same process again. A commitment can only be judged fairly against the evidence available when it was made — and if that evidence no longer exists in the form it had at the time, every past decision gets judged by present knowledge. Competent people look reckless. Lucky people look wise. And the organisation, quite rationally, stops making bold calls, because the record has quietly made boldness indefensible after the fact.</p><p><strong>Where did intent and delivery part company?</strong> The gap between the service you designed and the service you are running is not a number. It is a shape over time.</p><p>The decision this feeds is where to spend next. A gap that opened in one month usually has a cause sitting right next to it in the timeline — a reorganisation, a supplier change, a budget round. A gap that widened slowly over two years is a design problem, and no amount of remediation will close it. Same gap today, different money entirely. A snapshot tells you the size and hides the shape, which means it can tell you that something is wrong but never what to do about it.</p><p>That is the pattern in all three. The model is not being asked to be a record. It is being asked to be <strong>something you can commit on the strength of</strong> — and a claim you cannot date is a claim you cannot weigh.</p><h3>Credible Is Not the Same as Correct</h3><p>We set the terms earlier: credible, not accurate. It is worth following that to the place it actually leads, because most people accept the definition and then flinch at the consequence.</p><p>A claim can be credible — properly sourced, honestly bounded, made by exactly the right person — and still turn out to be wrong.</p><p>That is not a flaw in the idea. It is the point.</p><p>Whole fields have moved forward on theories the world eventually refused to match. The theory was never worthless — it was the best available claim, held honestly, and the fact that it could be seen to fail is precisely what produced the next one. Progress did not come from being right first time. It came from being wrong in a way that was visible, dated and attributable.</p><p>A model that overwrites cannot do this. When the wrong claim is replaced by the right one, the organisation gains a corrected field and loses the entire lesson. There is no record that anybody believed otherwise, no record of how long they believed it, and no way to ask the only question that would have been useful: <em>what were we reasoning from, and why did it look right at the time?</em></p><blockquote><em>Being visibly wrong is worth more than being quietly corrected.</em></blockquote><p>An organisation that cannot see itself having been wrong cannot calibrate anything. It cannot tell you which of its sources have earned confidence and which have merely never been checked. Every claim arrives wearing the same face.</p><h3>Nobody Has to Be Right the First Time</h3><p>So far the cost of forgetting has been the organisation’s. There is a personal one too, and it is the reason the model ends up thin in the first place.</p><p><a href="https://www.strategenz.com/articles/contribution-without-consensus">Contribution Without Consensus</a> argued that people stop contributing what they know because contributing exposes them — put your name to something and wait to be quietly overruled by someone with more seniority and less proximity.</p><p>Time is what finally removes that risk.</p><p>If nothing is discarded, a correction is not a deletion. Someone else’s later claim does not replace yours; it sits beside it, both dated, both attributed. If theirs wins on precedence, yours is still on the record saying exactly what you said, on the day you said it, with the reasoning intact.</p><p>Which means the worst outcome of contributing is that you were right about your patch at the time and something changed afterwards. That is not a professional risk. That is just what happens to true things.</p><h3>The Timeline Doesn’t Stop at Today</h3><p>Everything so far has looked backwards. It doesn’t have to.</p><p>If a claim is an event with a date on it, then a claim about a date that has not arrived yet is exactly the same kind of object. A contract that lapses in March. A supplier exiting in June. A capability being stood down at year end, a team being restructured, a licence that will not be renewed. Each of these is known now and true later — a claim with a future validity date, sitting in the model alongside everything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WwYRndcgWjB2cRVL" /><figcaption>Photo by <a href="https://www.pexels.com/@towfiqu-barbhuiya-3440682">Towfiqu barbhuiya</a> on <a href="https://www.pexels.com/">Pexels</a></figcaption></figure><p>So ask the model the same question, dated March.</p><p>Not a forecast, and not a guess. The same composition, evaluated at a date that hasn’t happened yet, returning what the service will look like given what has <em>already been decided</em>. The commitments you cannot currently see are the ones nobody has connected to the thing they will land on.</p><p>That is the difference between reacting to a change and seeing it coming — and it is not sophistication or analytics or a maturity level. It is whether the claims in your model carry a date.</p><h3>Why We Don’t Do This</h3><p>It is not storage. Storage has been effectively free for two decades, and anyone who has priced it knows the “we can’t keep all that” storage argument is a reflex rather than a calculation.</p><p>There is a better objection, and it has actually been earned.</p><p>Most organisations have already tried keeping everything once, and it went badly. The archive nobody could navigate. The warehouse that quietly became someone’s second job. The shared drive holding fourteen versions of the same document with no way to tell which one anybody acted on. The lesson taken from that wasn’t <em>we stored too much</em> so much as <em>stored information rots</em> — it ages, it detaches from whatever it described, and every additional pile is one more thing to govern, secure and eventually explain to somebody. Collecting more starts to look like pouring fuel on a fire you are already fighting.</p><p>That objection is right about what it saw. It is wrong about what caused it.</p><p>Those things rotted because they were kept <em>somewhere else</em>. A copy lifted out of the system that gave it meaning is an orphan the moment it lands: no owner, no relationship to the thing it describes, no way to tell whether it still applies. It has to be managed separately precisely because it <em>is</em> separate. That is what turns volume into fuel.</p><p>A claim that was simply never removed is in no such position. It is still attached to the part of the service it speaks about and the person who made it, still bounded by what they said they knew, still sitting in the same structure as everything else. Nothing needs curating, because nothing was ever extracted.</p><blockquote><em>You are not building an archive alongside the model. You are declining to delete from it.</em></blockquote><p>Which is worth being exact about, because the two get confused constantly. Hoarding is copying data out and hoping it proves useful later. This is the opposite: nothing moves, nothing is duplicated, and the past is reachable by the same query that reaches the present.</p><p>So it isn’t cost, and it isn’t sprawl. The real reason is less comfortable than either.</p><p>A model that remembers is a model that can be checked. Checked against the world, which most organisations would accept. But also checked <em>about itself</em> — how often it has been wrong, how long it stayed wrong, which sources keep needing correction, and which decisions were made in the window while it was wrong.</p><p>That is a genuinely exposing thing to build, and the discomfort is real rather than irrational. It is also the entire value. A model whose reliability cannot be examined is not a safer model. It is one whose unreliability is simply unmeasured, being used to make commitments anyway.</p><p>Every organisation that has ever said “we need a single, accurate view” has been asking for a model that can be examined about itself, while believing it asked for one that is simply accurate about the world.</p><h3>The Challenge</h3><p>Pick a decision your organisation made about eighteen months ago. A real one, with money or people attached.</p><p>Now try to reconstruct what made it credible at the time — not the minutes, not the paper that went to the committee, but the state of the world the paper was drawing on. What the assessments said that week. What was believed about the dependencies, the cost, the criticality.</p><p>You will find one of two things. Either you cannot reconstruct it at all, or you can only reconstruct it from someone’s personal archive — a saved deck, an exported spreadsheet, an email thread that survived because one person happens not to delete things.</p><p>Which means you can no longer show the decision was credible when it was made. Only that it was made.</p><p>Then notice what that means about the decision you are going to make this quarter.</p><p><em>Originally published at </em><a href="https://www.strategenz.com/articles/nothing-is-ever-overwritten/"><em>https://www.strategenz.com</em></a><em> on August 18, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4933dbcb5e86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contribution Without Consensus]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/contribution-without-consensus-d2be8b8b2300?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2be8b8b2300</guid>
            <category><![CDATA[management-services]]></category>
            <category><![CDATA[it-service-management]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 00:00:42 GMT</pubDate>
            <atom:updated>2026-08-06T23:11:58.545Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Field You Cannot Honestly Fill In</h3><p>You know one true thing about a service. You have known it for two years. This morning you finally go to put it in the system.</p><p>The form has thirty-one fields. Four of them are mandatory, and you have no idea what belongs in any of them. Business criticality. Recovery tier. Data classification. Upstream owner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DOZiQoGFb1b2nBWS" /><figcaption>Photo by <a href="https://www.pexels.com/@mikhail-nilov">Mikhail Nilov</a> on <a href="https://www.pexels.com/">Pexels</a></figcaption></figure><p>You know one of those thirty-one things. You are being asked to have an opinion on all four of the ones you don’t.</p><p>So you do what everybody does. You guess, or you hedge: <em>TBC</em>, <em>under review</em>, <em>no idea</em>. The guess is a fabrication the record has no way to detect. The hedge feels like the honest option and does more damage in its own way — it fills the space, so the field reads as answered and nobody ever comes back to it. Either way your one true fact lands wrapped in three non-answers indistinguishable from it.</p><p>Or — the more likely outcome — you close the form and walk away. The organisation stays exactly as ignorant as it was before you tried, and it has no idea it just lost anything.</p><p>Now take the other route. You skip the form and go to the person who owns that record, because it’s really their system, not yours. Which means a conversation, which becomes a meeting, which becomes a standing meeting — because once two people have to agree, someone has to book the room. Your one true fact is now an agenda item.</p><p>Neither of these is a tooling problem. It’s the same tax collected at two different counters, and the tax is <strong>agreement</strong>.</p><h3>The Cost Is the Agreement, Not the Typing</h3><p>Every organisation that has watched its model go stale blames the interface. It was too clunky. Nobody had time. We’ll do a data quality drive next quarter.</p><p>The interface is not what stopped you. What stopped you is that the record is <strong>singular</strong> — there is one row for that service, and it can only say one thing at a time. Everything painful follows from that one design choice:</p><ul><li>Because there is one record, it needs <em>all</em> its fields filled — so contributing means having an opinion on things you don’t know.</li><li>Because there is one record, it already belongs to somebody — so contributing means taking something from them.</li><li>Because there is one record, only one answer can stand — so contributing means winning, and winning means a meeting.</li></ul><p>Three barriers, and all three are the same shape. You are not being asked for what you know. You are being asked to <em>first</em> become someone who knows the whole thing, and <em>then</em> to negotiate with everyone else who thinks they already do.</p><p>Almost nobody clears that bar. So the knowledge doesn’t vanish — it just goes somewhere cheaper. A spreadsheet. A private note. A thing someone says out loud in incident calls that has never once been written down.</p><p>And all the while, the dashboard says this is going well. Coverage is up. Completeness is up. The population rate has climbed three quarters running — every knowledge metric on the slide pointing the right way.</p><p>Those numbers are lying, in precisely the way <a href="https://www.strategenz.com/articles/measuring-what-matters">Measuring What Matters</a> warned about. A completeness score counts fields that contain <em>something</em>, not fields that contain <em>knowledge</em>. The guess scores. The hedge scores. Walking away — the only fully honest option on offer — is the one thing the metric punishes. It is measuring occupancy and reporting it as understanding, and it climbs fastest exactly where people were least able to tell the truth. Credible over complete was the whole point; we built the dashboard the other way round.</p><blockquote><em>The consensus requirement isn’t slowing your model down. It’s why your model is empty.</em></blockquote><h3>Partial Knowledge Is the Normal Case</h3><p>Here is the assumption buried under the singular record: that somewhere there exists a person who knows the whole thing, and our job is to find them and give them the form.</p><p>There is no such person.</p><p>The network engineer knows how traffic reaches that service and has no idea what it costs. Finance knows exactly what it costs and could not tell you what it does. The architect knows what <em>should</em> happen — the intended design and the reasoning behind it — and almost never sees what actually does. The service desk lead knows exactly what does happen, what breaks and in what order, and has never seen the architecture diagram. Each of them is genuinely authoritative about one facet and genuinely ignorant of the rest.</p><p>That ignorance is not a gap to be closed. It is <strong>correct</strong>. It is what specialisation looks like from the inside, and the fact that your finance analyst has no view on recovery tiering is a sign the organisation is working, not failing.</p><p>We built systems that treat a partial answer as an incomplete one. It isn’t incomplete. It’s precise — and we made precision impossible to submit.</p><p>That precision is exactly what makes it <strong>credible</strong> — and credibility here has two sides that need each other. On the inside, it is how far the contributor actually trusts their own information: not whether it holds true for the whole model, only whether it holds in their own context. On the outside, it is that the edge of that context is visible, so anyone reading it knows how far to carry it. The network engineer is entirely right about routing and says nothing whatever about cost — and because you can see exactly where that frame ends, you know exactly how far to trust it.</p><p>Credibility isn’t certainty and it isn’t coverage. It is a bounded claim that somebody is willing to stand behind. Confidence with no stated limits is just assertion; a limit with no confidence behind it is noise.</p><p>A completed record has no such property. Filled end to end, it cannot tell you which fields were known and which were guessed, which is why the coverage number climbs while your confidence in it falls. <a href="https://www.strategenz.com/articles/knowledge-isnt-a-story">Knowledge Isn’t a Story</a> argued that what we need is knowledge we trust enough to act on now. This is the mechanism underneath it: bounded precision beats unbounded assertion, and credibility — not completeness — is the only measure of a model worth reporting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rH0Ioqbutxrys2vz" /><figcaption>Photo by <a href="https://unsplash.com/@sloppyperfectionist?utm_source=strategenz&amp;utm_medium=referral">Hans-Peter Gauster</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Silence Is an Answer</h3><p>Let people say only what they actually trust their own information on, and nothing at all about the rest.</p><p>Not <em>unknown</em>. Not a blank. Not a sensible default. <strong>Nothing.</strong></p><p>The distinction sounds like pedantry and it is the whole mechanism. “I don’t know” is still a claim — it’s a claim about the state of your knowledge, and it lands in the record as a value that occupies the space. A blank field is worse: it overwrites what was there with emptiness, and now the organisation knows less than it did before you helpfully filled the form in.</p><p>Silence isn’t a value. It’s the absence of a claim. And in a composed model — where the answer to any question is assembled on demand from whatever layers have something to say — a layer that stays silent about a facet simply <strong>lets a lower layer show through</strong>, untouched.</p><p>That’s what makes contributing safe. You cannot damage what you don’t speak to.</p><h3>A Worked Example: Two People Who Never Met</h3><p>Take a payments service. Sanitised, generic, but you’ll recognise both halves.</p><p>The <strong>security analyst</strong> knows exactly one thing about it: it touches regulated data, so it falls inside a particular control regime. That’s it. The analyst has no view on who runs it, what it costs, how many people depend on it, or whether it’s healthy this morning.</p><p>The <strong>service desk lead</strong> knows something entirely different and equally true: when this service starts to fail, the first sign is never monitoring. It’s a specific, oddly-worded complaint that shows up two or three hours before anything goes red.</p><p>Today, neither fact reaches the model.</p><p>The analyst can’t record that one fact without owning — and therefore fabricating — the other thirty, so the route is a ticket raised against whoever owns the record: a wait, and then a checkbox landing three weeks later with the reasoning stripped off. The desk lead’s fact is worse off still, because there is no field for it at all. Creating one is a governance change, which is a working group, which is next quarter. So it stays in one person’s head, in a chat thread, and in the goodwill of whoever happens to be on shift that night.</p><p>Now let each of them contribute a layer that speaks only for itself.</p><p>Each adds one thing and stops. They have never met. They have not agreed on anything, because there was nothing to agree about — neither one said a word about the other’s facet. Nobody reviewed anything. Nobody was overwritten.</p><p>And the composed view of that service now carries a regulatory boundary <em>and</em> an early-warning signal that the organisation has always possessed and never once been able to write down.</p><h3>Nobody Is Overwritten, So Nobody Resists</h3><p>It’s worth being honest about why the review gates exist. They aren’t bureaucracy for its own sake. When there’s one record, your fact landing means someone else’s fact leaving — so the gate is protection against loss, and the people defending it are defending something real.</p><p>But the fear runs in both directions, and this is the half nobody says out loud. Contributing doesn’t only risk taking someone else’s answer away. It exposes yours. The moment your fact is visible, anyone with more confidence, more seniority or <a href="https://www.strategenz.com/articles/truth-vs-turf">a different lens</a> can correct it to their own assumed truth — and in a singular record, correcting means <strong>replacing</strong>. Yours is simply gone, with nothing left to show you ever said otherwise.</p><p>So contributing carries a personal risk and no personal upside. You put your name against something you actually know, and then wait to be quietly overruled by someone who was never as close to it as you were. People learn this exactly once. The engineer who watched their assessment flattened by an architect’s assumption does not make that mistake twice — and the organisation has just trained its best-informed people into silence, then gone looking for a better form.</p><p>Take the loss away and you take the fight away with it. A contribution adds a layer; it removes nothing. If it turns out to be wrong, or thin, or less authoritative than something else, it loses on precedence and sits harmlessly underneath — and it is still there, still attributable, still available to anyone who later wants to know what you said and when you said it. Nothing in this model is ever destroyed, which is a bigger idea than this piece can hold and gets one of its own.</p><p>The correction you were bracing for stops being a deletion, too. Someone else’s claim doesn’t edit yours; it lands in its own layer beside it, both attributed, both readable. If theirs wins on precedence, yours is still on the record saying exactly what you said — and the fact that the two of you disagreed is now visible information rather than an argument settled by whoever spoke last.</p><p>The gate was never really about quality. It was about scarcity — one record, one winner. Composition ends the scarcity.</p><h3>A Disagreement Is a Finding</h3><p>And then the fear turns inside out. The contradiction you dreaded attracting is the most useful thing you could have handed the organisation.</p><p>A gap tells you nobody knows something. A conflict tells you something worse and far more useful: two people who are each genuinely authoritative both believe they know, and their answers don’t match. That happens for only a few reasons — the design was never implemented the way it was drawn, or it drifted and nobody noticed, or the two of them are answering different questions using the same word. Every one of those is a finding, and none of them surfaces anywhere else.</p><p>So when the architect says traffic reaches that service one way and the network engineer says it reaches it another, the valuable output is not a ruling about who to believe. It is the discovery that the intended service and the running service have come apart — and that nobody spotted it, because the record only ever had room for one of them.</p><blockquote><em>Reconciliation doesn’t settle a disconnect. It deletes it — along with the only evidence that it existed.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*obdrnbd1nP_6AkEg" /><figcaption>Photo by <a href="https://unsplash.com/@shvedkriss?utm_source=strategenz&amp;utm_medium=referral">Kristina Shvedenko</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>More Contributors, Not More Meetings</h3><p>Watch what this does to the arithmetic.</p><p>Under consensus, every person you add is another person who has to agree. Coordination cost rises with each one, and the knowledge your organisation can hold is capped — not by what people know, but by how many of them you can get to sign the same sentence.</p><p>Under composition, every person you add contributes what they know at no coordination cost at all. They didn’t have to convince anyone, or be right about anything except their own patch.</p><blockquote><em>Under consensus, every extra contributor makes the model slower. Under composition, every extra contributor makes it richer.</em></blockquote><p>That is the difference between a model that decays the moment the programme ends and one that gets better on its own — because contributing to it is finally cheaper than keeping your own spreadsheet.</p><h3>Why This Falls Out of Composition</h3><p><a href="https://www.strategenz.com/articles/the-myth-of-the-single-source-of-truth">The Myth of the Single Source of Truth</a> answered the case where two layers disagree: don’t negotiate, set a precedence rule once and let the answer show its work.</p><p>But disagreement is the <em>rare</em> case — rare in how often it happens, and, as we just saw, disproportionate in what it tells you when it does. Most of the time two layers aren’t fighting over the same facet at all; they have nothing to do with each other. Precedence handles the overlap. Silence handles everything else, which is nearly all of it.</p><p>Between them there is no point left in the system that requires anybody to agree with anybody up front. That’s the second half of the machine: the first half made truth composable, and this half makes it <em>contributable</em>.</p><p>And it is what turns credible knowledge from a principle into something an organisation can actually accumulate. You will never hold knowledge you trust enough to act on while the people who have it can’t get it in the door.</p><h3>The Challenge</h3><p>Go and find someone who knows one true, useful thing about a service and has never put it anywhere. You will not have to look hard — ask anyone who has worked a service desk for more than a year.</p><p>Then ask them why not. You’ll get one of two answers: <em>“there’s no field for it”</em>, or <em>“that’s not my system to change.”</em></p><p>They sound like different problems. They’re the same one, and neither of them is about the person, and neither of them is about the tool.</p><p>Then look at the end of a project, where the loss is easiest to see. A delivery team spends months finding out how the thing really behaves under pressure, and almost none of it has anywhere to go. The clearest case is the risks still open on the day the project closes. They were real enough to review every week while there was a project to review them in. Then the project ends, the register is archived, and they simply stop existing — not accepted, not mitigated, not handed to anyone. Nobody made a decision. There was just no layer left standing that could hold them.</p><p><em>Originally published at </em><a href="https://www.strategenz.com/articles/contribution-without-consensus/"><em>https://www.strategenz.com</em></a><em> on August 7, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2be8b8b2300" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Myth of the Single Source of Truth]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/the-myth-of-the-single-source-of-truth-03c88861def8?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/03c88861def8</guid>
            <category><![CDATA[management-services]]></category>
            <category><![CDATA[it-service-management]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Mon, 06 Jul 2026 00:00:23 GMT</pubDate>
            <atom:updated>2026-07-29T00:59:50.800Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Meeting Where Two Systems Disagree</h3><p>The asset register says the server was decommissioned in March. Monitoring says it served four thousand requests this morning.</p><p>Someone asks the question that launches a thousand projects: <em>which one is the source of truth?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TsUWDJb5RJy75LeP" /><figcaption>Photo by <a href="https://unsplash.com/@a_chosensoul?utm_source=strategenz&amp;utm_medium=referral">A Chosen Soul</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It feels like the responsible question. It is actually the wrong one — and asking it is how organisations end up spending years, and fortunes, chasing a record that never arrives.</p><p>Because the honest answer nobody in the room wants to hear is: <strong>both are.</strong> The register is telling the truth about the <em>decision</em>. Monitoring is telling the truth about the <em>traffic</em>. Neither is wrong. They are answering different questions and being forced to share one row.</p><h3>The Golden Record That Never Arrives</h3><p>The Single Source of Truth is the project that is permanently six months from done.</p><p>Every organisation has one running. A programme to reconcile the systems, retire the duplicates, and crown one authoritative record that everyone will finally trust. It is always underway, always nearly there, always quietly slipping.</p><p>It slips because it rests on two assumptions, and both are false:</p><ul><li>that there is <strong>one right answer</strong> waiting to be found, if we just clean the data hard enough</li><li>that everyone will <strong>agree to defer</strong> to it once we do</li></ul><p>You can pour years and a fortune into the first and the register will <em>still</em> disagree with monitoring — because you were trying to legislate agreement between two things that are each telling the truth. And the second assumption never survives contact with reality: the moment one system is declared the winner, everyone whose truth got overwritten quietly reopens their own spreadsheet.</p><h3>Truth Has More Than One Author</h3><p>The reason the golden record never arrives isn’t poor discipline or the wrong platform. It’s that different parts of the organisation are <strong>legitimately authoritative about different facets of the same thing.</strong></p><p>In <a href="https://www.strategenz.com/articles/truth-vs-turf">Truth vs Turf</a> I called these <em>lenses on one graph</em>: Operations owns current state, Enterprise Architecture owns intended state, the PMO owns the money, security owns the posture. Each is right about its own facet. The turf war starts when every lens insists its view is <em>the</em> view.</p><p>A Single Source of Truth doesn’t end that war. It just picks a winner and overwrites the losers. And the overwritten truth doesn’t vanish — it goes underground, into side files, footnotes, and the caveats people add out loud in meetings because they no longer trust the record to carry them.</p><blockquote><em>A single source of truth doesn’t end the turf war. It just decides whose truth has to go underground.</em></blockquote><h3>Stop Declaring Truth. Compose It.</h3><p>Here is the shift the whole series turns on.</p><p>The mistake is believing the authoritative view is a thing you <strong>store</strong>. It isn’t. It’s a thing you <strong>compose</strong> — assembled the moment you ask, from whatever layers have something to say, each contributing only what it is authoritative about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_ygXTAJdiZ_UIXgk" /><figcaption>Photo by <a href="https://unsplash.com/@techivation?utm_source=strategenz&amp;utm_medium=referral">Techivation</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Nothing is negotiated up front. There is no golden record to keep in sync, because there is no single record at all. When two layers speak to the same question, a <strong>precedence rule</strong> decides which one wins — set once, applied the same way every time, and visible in the answer.</p><p>The authoritative answer to <em>“is this server live?”</em> isn’t kept in any one system. It’s composed, on demand, from the layers that know — with a known rule for who wins when they overlap.</p><h3>A Worked Example: The Network Says Yes, Security Says No</h3><p>Take a single service endpoint.</p><p>The <strong>network layer</strong> knows it’s up and routable — packets reach it, the port answers. The <strong>security layer</strong> knows a policy blocks that port for anyone outside a named group. Ask <em>“can a user reach this service?”</em> and you get two answers that are both entirely true.</p><p>In the old world, this is a fight. Which system is the source of truth — the network monitor or the policy engine? You either argue it out, or you anoint one system the winner and bake the other’s reality into a footnote. Either way, someone’s truth is now wrong on the record, and the person who knows it’s wrong stops trusting the record.</p><p>In a composed world, you don’t choose. Both layers keep their own truth intact. The answer to the <em>composite</em> question — can a user actually reach it — is composed, with a precedence rule that says the security layer wins on reachability. Result: <strong>reachable, no.</strong></p><p>And the answer arrives carrying its reasoning: <em>network says yes, security overrides, here’s the rule.</em> You didn’t get a flattened fact you have to take on faith. You got a <strong>resolved view that shows its work.</strong></p><h3>Precedence Beats Consensus</h3><p>This is the quiet superpower, and it’s worth saying plainly.</p><p>Consensus is a meeting you hold forever. Precedence is a rule you set once.</p><p>You no longer need everyone to <em>agree on the truth</em>. You need them to agree only on <strong>who wins where they overlap</strong> — a far smaller agreement, and a far more durable one. Reachability defers to security; cost defers to finance; intended state defers to EA. Each of those is a one-time decision, not a standing argument.</p><p>And because the rule is explicit, disagreement stops being a failure to suppress and becomes <strong>information</strong>. When a lower-precedence layer contradicts the winner, that contradiction is visible — a signal worth looking at, not an error to reconcile away. The record stops hiding its own seams.</p><h3>Why This Is the Service Information Base in Miniature</h3><p><a href="https://www.strategenz.com/articles/knowledge-isnt-a-story">Knowledge Isn’t a Story</a> made the case that we don’t need perfect data — we need <strong>credible knowledge</strong>, information we trust enough to act on right now. Composition is <em>how</em> you get it.</p><p>A composed view is current by construction: there is nothing to keep in sync, because it’s assembled at the moment you ask. And it’s trustworthy by construction: it shows the layers it drew from and the rule that resolved them. That is the core move of the Service Intelligence Base — and almost everything else in this series is a consequence of it. History, accountability, commitments, even modelling the future — each turns out to be composition pointed at a different question.</p><p>Once you stop trying to <em>declare</em> the truth and start <em>composing</em> it, the reconciliation programme doesn’t get easier. It disappears.</p><h3>The Challenge</h3><p>Pick one fact two of your systems disagree about right now — the register versus monitoring, the CMDB versus the cloud console, the plan versus the actual.</p><p>Resist the reflex to ask <em>which one is right.</em> Ask instead: what is each of them genuinely authoritative about, and which should win where they overlap? Write that precedence rule down.</p><p>You’ve just composed your first authoritative view — and you may notice you never needed the reconciliation meeting at all.</p><p>If this changed how you look at your next “single source of truth” programme, I’d love to hear it — comment, follow, or share it with whoever owns the reconciliation project that’s always six months from done.</p><p><em>Originally published at </em><a href="https://www.strategenz.com/articles/the-myth-of-the-single-source-of-truth/"><em>https://www.strategenz.com</em></a><em> on July 6, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03c88861def8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SLA: A Promise With Nothing Behind It]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/sla-a-promise-with-nothing-behind-it-70f638a66a8d?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/70f638a66a8d</guid>
            <category><![CDATA[it-service-management]]></category>
            <category><![CDATA[management-services]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Sun, 05 Jul 2026 00:00:48 GMT</pubDate>
            <atom:updated>2026-07-29T00:56:45.417Z</atom:updated>
            <content:encoded><![CDATA[<h3>The SLA Was Met. The Service Failed.</h3><p>The report is unambiguous. <strong>99.7% against target.</strong> Green for the quarter, green for the year.</p><p>And yet the client is quietly furious, the team is exhausted, and two of your best people are updating their CVs.</p><p>Both things are true at once. The number was hit. The Service let everyone down.</p><p>How does an organisation hold both of those in the same hand and not notice the contradiction?</p><p>Because it measured the <strong>promise</strong> — and never looked at what was behind it.</p><h3>An SLA Is Just a Promise</h3><p>Strip away the acronym and the penalty clause, and a Service Level Agreement is a promise: <em>we will respond within four hours</em>, <em>we will be available 99.9% of the time</em>, <em>we will resolve this by Friday</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZcuC1DNOjXP8U9NR" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So is an OLA. So is a pledge in a kickoff deck. So is the line a manager says in a steering meeting to make the tension go away.</p><p>They are all the same shape — a <strong>declaration, made by one party to another, about future behaviour</strong>. This is the useful lens from Promise Theory: a promise is voluntary, it is about <em>your own</em> conduct, and it only means something when someone is relying on it.</p><p>Once you see SLAs as promises rather than paperwork, the interesting question stops being <em>“did we hit the number?”</em> and becomes something far more revealing:</p><blockquote><em>What, exactly, is keeping this promise?</em></blockquote><p>Most organisations have never asked it.</p><h3>The Unbacked Promise</h3><p>Here is the failure almost nobody maps.</p><p>A promise lives in one place — a contract, a policy, a slide. What actually <em>delivers</em> the promise lives somewhere else entirely — a process, a Service, a person, a piece of infrastructure. And in most organisations, <strong>nothing connects the two.</strong></p><p>The promise floats free. It has been made, it is being reported on, and if you go looking for the thing that keeps it, you find… a gap. Or worse, you find a single overworked person and a rota held together by goodwill.</p><p>Take a sanitised example. A client is promised <em>Tier-1 response within four hours</em>. The commitment is signed, tracked, and reported green every month. Ask the harder question — <em>what delivers this?</em> — and the answer is one experienced engineer who happens to check her phone on weekends. There is no second person. There is no documented path. There is a <strong>promise with nothing behind it</strong>, and the org has been quietly relying on luck and heroics to keep it.</p><p>A commitment with nothing delivering it is not a commitment. It is a hope with a deadline.</p><h3>Why the Dashboard Can’t See It</h3><p>The dashboard measures the promise. It cannot measure what backs it.</p><p>You can hit four hours for eighteen straight months on the strength of one person’s diligence, and every single month the report will say green. The metric is telling you the truth about the <em>outcome</em> and nothing at all about the <em>exposure</em>. The gap is invisible right up until the day she takes leave, or leaves, and then it is a catastrophe that “came from nowhere.”</p><p>It did not come from nowhere. It was an unbacked promise the whole time. The green just hid it — because <strong>green measures whether the promise was kept, never whether anything was keeping it.</strong></p><p>This is the same illness as the watermelon metric: green on the outside, red in the middle. But the cure isn’t a better number. It’s making the promise itself into something you can inspect.</p><h3>Make the Promise a Thing</h3><p>The shift is small and it changes everything: stop treating a commitment as text buried in a document, and start treating it as a <strong>first-class object in your model of the organisation</strong> — something you can point at, question, and trace.</p><p>When a promise is a thing in its own right, four questions become answerable that were previously rhetorical:</p><ul><li><strong>Who made it?</strong> (Not the logo on the contract — the actual accountable party.)</li><li><strong>Who is it made to?</strong></li><li><strong>What Service or Outcome does it promise?</strong></li><li><strong>What delivers it?</strong></li></ul><p>That last one is the whole game. When the commitment is connected to the thing that delivers it, an unbacked promise stops being invisible. It shows up as exactly what it is: a promise with a dangling end, pointing at nothing. You don’t discover it during the incident review. You see it the moment it’s made.</p><p>You don’t need a new tool to start thinking this way. You need to stop accepting a promise as delivered simply because it has been <em>written down</em>, and start asking — for every commitment that matters — <em>show me what’s behind this.</em> If the answer is a name and a hope, you have found a risk that no register captured, because no register knew the promise existed as a distinct thing.</p><h3>Unbacked Promises Are Faith Debt</h3><p>There is a human cost underneath the operational one.</p><p>Every promise your organisation makes is a small deposit or withdrawal on trust. A promise kept builds <strong>faith</strong> — the quiet confidence that lets people use the official path instead of routing around it. A promise broken withdraws it, and faith returns far more slowly than it leaves.</p><p>An unbacked promise is worse than a broken one, because it corrodes trust twice. First when it fails — suddenly, “inexplicably.” And again when everyone realises there was never anything holding it up, and starts to wonder what <em>else</em> is being reported green with nothing behind it.</p><p>A promise met by heroics is borrowed faith. A promise with nothing behind it is a debt you simply haven’t been billed for yet.</p><h3>The Challenge</h3><p>Your dashboard is telling you which promises were kept.</p><p>It is not telling you which ones are being kept by luck, by one person, or by nothing at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tbA66FdwQkspijb7" /><figcaption>Photo by <a href="https://unsplash.com/@a_chosensoul?utm_source=strategenz&amp;utm_medium=referral">A Chosen Soul</a> on <a href="https://unsplash.com/?utm_source=strategenz&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Go find one commitment that matters — an SLA, a pledge, a line in a plan — and trace it to the thing that delivers it. If you can’t, you haven’t found a reporting gap. You’ve found the next crisis, early enough to do something about it.</p><p>If this piece changed how you look at a green dashboard, I’d love to hear it — comment, follow, or share it with someone who owns an SLA they’ve never questioned.</p><p><em>Originally published at </em><a href="https://www.strategenz.com/articles/a-promise-with-nothing-behind-it/"><em>https://www.strategenz.com</em></a><em> on July 5, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70f638a66a8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finance Without Fog]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/finance-without-fog-2dbfb1214d56?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dbfb1214d56</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 02:05:58 GMT</pubDate>
            <atom:updated>2026-01-20T02:05:58.313Z</atom:updated>
            <content:encoded><![CDATA[<h3>When Cost Models Meet Reality — Bringing Finance onto the Service Graph</h3><p>In earlier articles, we established a simple but uncomfortable truth:</p><p><strong>Services are the unit of value.</strong></p><p>Not projects.<br>Not teams.<br>Not systems.</p><p>Services.</p><p>This article explores what inevitably happens when finance is <em>not</em> organised around that same truth.</p><h3>Finance in the Fog</h3><p>The finance committee meets quarterly.</p><p>Slides are polished. Business cases are compelling. Everyone is prepared.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OlCSIUVaACAj64og" /><figcaption>Photo by <a href="https://unsplash.com/@pietyo?utm_source=medium&amp;utm_medium=referral">Patrick Mueller</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Project A promises 20% efficiency gains.<br>Project B will “transform the customer experience.”<br>Project C is “critical infrastructure renewal.”</p><p>All three sound important. All three need funding.</p><p>But when someone asks the simplest questions, the room goes quiet:</p><ul><li>Which services will this actually improve?</li><li>What do those services cost today?</li><li>How will we know whether the investment worked?</li></ul><p>Not because the numbers are wrong.</p><p>But because the numbers aren’t connected to anything real.</p><p><strong>Finance operates in a fog.</strong></p><h3>The Spreadsheet Temple</h3><p>Most organisations don’t treat financial planning as sense-making.<br>They treat it as ritual.</p><p>The PMO maintains elaborate cost models:</p><ul><li>CapEx vs OpEx allocations</li><li>Project portfolios</li><li>Resource forecasts</li></ul><p>Finance tracks spending with discipline:</p><ul><li>Cost centres</li><li>GL codes</li><li>Purchase orders</li><li>Variance reports</li></ul><p>Governance demands business cases that justify every dollar:</p><ul><li>ROI calculations</li><li>NPV projections</li><li>Payback periods</li></ul><p>All rigorous.<br>All defensible.<br>All structurally detached from the services the business actually delivers.</p><p>This is the <strong>Spreadsheet Temple</strong> — a parallel world where financial truth exists independently of operational reality.</p><p>The issue isn’t diligence.<br>It’s <strong>disconnection</strong>.</p><h3>Cost Without Context</h3><p>Most organisations don’t have a cost problem.<br>They have a <strong>visibility problem</strong>.</p><p>Ask:</p><blockquote>“What does our Customer Onboarding service cost to run?”</blockquote><p>No clear answer.</p><p>Because the cost lives everywhere except where the service does:</p><ul><li>HR (recruitment)</li><li>IT (provisioning)</li><li>Facilities (workspace)</li><li>Learning &amp; Development (training)</li><li>Finance (billing setup)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s4aCkc7MMU9LV-5d" /><figcaption>Photo by <a href="https://unsplash.com/@blankerwahnsinn?utm_source=medium&amp;utm_medium=referral">Fabian Blank</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Each tracked separately.<br>None attached to the service outcome.</p><p>Just as experience metrics fail when they’re detached from lived reality, <strong>cost fails when it’s detached from the service it describes</strong>.</p><p>Finance can show spending.<br>It cannot show <strong>cost of delivery</strong>.</p><h3>The Structural Disconnects (Not New — Just Exposed)</h3><p>None of this is new.<br>It’s the same structural failure showing up in a financial form.</p><h3>1. Cost Categories vs Services</h3><p>Finance organises spend by:</p><ul><li>Department</li><li>Category</li><li>Project</li><li>Ledger code</li></ul><p>But customers don’t consume departments.</p><p>They consume <strong>services</strong>.</p><p>When cost is not anchored to services, every meaningful question requires translation — and translation always loses truth.</p><h3>2. Run vs Change Is a False Boundary</h3><p>Every organisation tries to separate:</p><ul><li><em>Run the business</em></li><li><em>Change the business</em></li></ul><p>We’ve already seen how this breaks accountability when <strong>projects</strong> are treated as the unit of change.<br>Finance simply inherits that distortion — and amplifies it.</p><p>The same work is:</p><ul><li>“Run” to one group</li><li>“Change” to another</li></ul><p>The distinction becomes political, not structural.</p><p>And almost nobody tracks whether <strong>change actually improved the run</strong>.</p><h3>3. Business Cases Without Memory</h3><p>Business cases are still treated as approval artefacts.</p><p>They win funding — then disappear.</p><p>Which means:</p><ul><li>Assumptions aren’t tested</li><li>Benefits aren’t validated</li><li>Learning doesn’t compound</li></ul><p>This isn’t a finance failure.<br>It’s a governance failure.</p><p>Control without sense-making.<br>Approval without feedback.<br>Process without learning.</p><h3>The Invisible Cost of Change</h3><p>Here’s a question most organisations still can’t answer:</p><p><strong>“What did it cost to change this service last year?”</strong></p><p>Not just the project budget — the <em>total</em> cost:</p><ul><li>Design and planning</li><li>Testing and rework</li><li>Operational disruption</li><li>Adoption and training</li><li>Coordination overhead</li></ul><p>These costs are real.<br>They’re just structurally invisible.</p><p>Without visibility of cost-of-change:</p><ul><li>Investment decisions rely on narrative</li><li>Fragile services absorb repeated funding</li><li>Finance remains reactive instead of predictive</li></ul><h3>This Isn’t About Finance Capability</h3><p>Finance teams aren’t failing.</p><p>They’re operating exactly as the model allows.</p><p>Finance speaks in:</p><ul><li>Budgets</li><li>Allocations</li><li>Variance</li></ul><p>Operations speaks in:</p><ul><li>Services</li><li>Flows</li><li>Capabilities</li><li>Outcomes</li></ul><p>Both are rational.<br>Neither is sufficient on its own.</p><p>This is not a people problem.</p><p>It’s a <strong>model problem</strong>.</p><h3>Cost Is an Overlay, Not a System</h3><p>Here’s the reframe that resolves the tension:</p><blockquote><strong>Cost is not a separate system.<br>It is an overlay on the service graph.</strong></blockquote><p>Services are the unit of:</p><ul><li>Value delivery</li><li>Customer experience</li><li>Operational risk</li><li>Change impact</li></ul><p>Cost does not exist independently of these.<br>It is a property of how services are constructed, operated, and evolved.</p><p>Which means finance doesn’t lose rigour — <br>it gains <strong>context</strong>.</p><h3>The Structural Anchor: The Service Graph</h3><p>Every organisation already has an implicit service graph:</p><ul><li>Services consume platforms</li><li>Platforms consume infrastructure</li><li>Teams operate components</li><li>Vendors sit on critical paths</li></ul><p>The issue has never been absence.</p><p>It’s fragmentation.</p><p>Without a shared structural truth:</p><ul><li>Cost floats</li><li>Change disconnects</li><li>Decisions degrade into storytelling competitions</li></ul><h3>The Service Intelligence Base (SIB)</h3><p>The OSM: Service Intelligence Base is not a reporting layer.</p><p>It is the <strong>structural spine</strong> that allows multiple perspectives — including finance — to coexist coherently.</p><p>It establishes:</p><ul><li>Authoritative service entities</li><li>Stable identifiers across finance, PMO, and operations</li><li>Relationship intelligence that shows dependency and impact</li></ul><p>It does not replace finance systems.<br>It connects them to reality.</p><h3>Common IDs: Where Alignment Actually Starts</h3><p>The most important capability is also the least glamorous:</p><p><strong>Shared service identifiers.</strong></p><p>When finance, delivery, and operations all refer to the same service:</p><ul><li>Costs remain visible over time</li><li>Business cases don’t “die”</li><li>Change history accumulates</li><li>Outcomes can be assessed honestly</li></ul><p>This is where fog starts to lift.</p><h3>Run and Change as Views, Not Silos</h3><p>On the service graph:</p><ul><li><strong>Run</strong> is the steady-state cost of delivery</li><li><strong>Change</strong> is the episodic cost of altering delivery</li></ul><p>Same services.<br>Same dependencies.<br>Different questions.</p><p>This removes politics and reveals signals:</p><ul><li>Fragile services cost more to change</li><li>Stable services deliver predictable ROI</li><li>Chronic rework becomes visible early</li></ul><h3>Business Cases That Stay Accountable</h3><p>When business cases remain structurally linked to services:</p><ul><li>Assumptions stay visible</li><li>Predicted vs actual outcomes can be compared</li><li>Run-cost impact is no longer a surprise</li><li>Organisational learning compounds</li></ul><p>The question shifts from:</p><blockquote>“Why is this service expensive?”</blockquote><p>To:</p><blockquote>“What changed — and was it worth it?”</blockquote><p>That’s a materially better conversation.</p><h3>What Changes in Practice</h3><p>When finance lives on the service graph:</p><ul><li>Budget conversations become concrete</li><li>Portfolios become service bets, not project lists</li><li>Run-the-business becomes honest</li><li>Change-the-business becomes credible</li><li>Governance gains memory</li></ul><p>Evidence replaces storytelling.</p><h3>The Real Test for Finance</h3><p>The challenge isn’t transparency for its own sake.</p><p>It’s relevance.</p><p>The old model allows everyone to say:</p><ul><li>“We followed the process.”</li><li>“We allocated correctly.”</li><li>“We tracked spend.”</li></ul><p>All true.<br>All insufficient.</p><p>Because the only question that ultimately matters is:</p><p><strong>Did the business get value?</strong></p><p>And that question can only be answered when cost lives where value lives — on the service graph.</p><h3>From Fog to Focus</h3><p>This isn’t about turning finance teams into engineers.</p><p>It’s about shared structural truth.</p><p>When cost, change, and delivery operate on the same service model:</p><ul><li>Strategy becomes executable</li><li>Investment becomes accountable</li><li>Services become financially legible</li></ul><p>Not in spreadsheets.<br>Not in decks.</p><p>But where value actually exists.</p><h3>The Question That Anchors Everything</h3><p><strong>Can you connect a dollar spent<br>to a service delivered<br>to a value created?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lh_HFfKdKVHCzKpx" /><figcaption>Photo by <a href="https://unsplash.com/@alinnnaaaa?utm_source=medium&amp;utm_medium=referral">Alina Grubnyak</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If not, finance hasn’t failed.</p><p>It’s simply been asked to operate without structure.</p><p>OSM offers a way out of the fog — <br>not by reducing financial discipline,<br>but by connecting it to reality.</p><p>Cost becomes an overlay, not a temple.<br>Investment becomes evidence-based, not story-based.<br>Finance becomes strategic, not just compliant.</p><p>And the organisation finally gets credible answers to the questions that matter:</p><ul><li>What does this service cost?</li><li>Is it worth it?</li><li>If we invest again — will it actually improve?</li></ul><p>—</p><p>If this resonates, follow along for more on Organisational Service Management, service flow, and human-centred transformation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dbfb1214d56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring What Matters: Human-Centric Metrics]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/measuring-what-matters-human-centric-metrics-77b802de8320?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/77b802de8320</guid>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 22:10:35 GMT</pubDate>
            <atom:updated>2026-01-13T22:10:35.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Friction, Flow, and Faith — The Dimensions We Ignore</p><p>The dashboard is green.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vP7QmdG7OtYDxbjx" /><figcaption>Photo by <a href="https://unsplash.com/@dengxiangs?utm_source=medium&amp;utm_medium=referral">Deng Xiang</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Every metric within threshold. Every SLA met. Every ticket closed on time.</p><p>The board is happy. The exec team is celebrating.</p><p>And yet, people are struggling.</p><p>They’re working around the system. Creating shadow processes. Emailing colleagues instead of using the official channels. Building spreadsheets because the “approved” process doesn’t fit their reality.</p><p><strong>The metrics say everything is fine.</strong><br><strong>The humans say it’s broken.</strong></p><p>Who’s right?</p><h4>The Tyranny of the Measurable</h4><p>We’ve been conditioned to believe that what gets measured gets managed.</p><p>But we rarely ask the harder question: <strong>Are we measuring the right things?</strong></p><p>Most service metrics were designed for control, not insight:</p><ul><li>Request volume (activity, not outcome)</li><li>Processing time (speed, not quality)</li><li>Compliance rates (contractual coverage, not real satisfaction)</li><li>Service availability (presence, not usability)</li></ul><p>These aren’t bad metrics. They’re just incomplete.</p><p>They tell us what the <em>system</em> is doing.<br>They don’t tell us what <em>people</em> are experiencing.</p><p>And when we optimize for incomplete metrics, we get perverse outcomes — because these metrics aren’t insight, they’re concealment.</p><p>Like hiding behind a window, we think the display of measurement protects us from admitting we don’t really understand what’s happening. We can see out (sort of), but we convince ourselves no one can see in. Except they can. The customers can. The teams can. Everyone can see we’re measuring activity while value slips away.</p><ul><li>Tickets closed quickly but problems unresolved</li><li>Services “available” but unusable</li><li>SLAs met while trust erodes</li><li>Everything green while morale collapses</li></ul><p>We measure noise and miss signal.</p><h4>What We’re Actually Measuring</h4><p>Let’s be honest about what traditional service metrics really capture:</p><h4>Activity Masquerading as Progress</h4><p>“We processed 10,000 requests this month!”</p><p>Great. How many of those created real value vs. people completing forms because they had to?</p><p>In HR, it’s applications processed. In Finance, it’s transactions cleared. In Legal, it’s contracts reviewed.</p><p>But volume measures <strong>engagement with the system</strong>, not <strong>value delivered to humans</strong>.</p><p>It’s like measuring hospital admissions and calling it healthcare.</p><h4>Speed Without Quality</h4><p>“Average processing time: 2.4 hours!”</p><p>Brilliant. How many of those outcomes actually worked?</p><p>In procurement: How many purchase orders had to be corrected?<br>In onboarding: How many new hires needed follow-up support?<br>In customer service: How many cases got reopened?</p><p>Speed metrics measure <strong>completion</strong>, not <strong>resolution</strong>.</p><h4>Compliance Without Trust</h4><p>“99.9% SLA compliance!”</p><p>Wonderful. Do people trust the service?</p><p>Because compliance is a contractual floor, not a ceiling.<br>You can hit every SLA and still have a service nobody wants to use.</p><p>Meeting SLAs measures <strong>defensive success</strong>, not <strong>positive impact</strong>.</p><h4>Availability Without Usability</h4><p>“Five nines uptime!”</p><p>Fantastic. Can people actually do what they need to do?</p><p>A service can be “up” and still be:</p><ul><li>Too slow to be useful</li><li>Too confusing to navigate</li><li>Too fragmented to complete a task</li><li>Too frustrating to trust</li></ul><p>Uptime measures <strong>technical availability</strong>, not <strong>human effectiveness</strong>.</p><p>These metrics aren’t lies. They’re just incomplete truths.</p><p>And incomplete truths, when treated as complete, become dangerous fictions.</p><h4>The Human Dimensions We Ignore</h4><p>So what are we missing?</p><p>If traditional metrics capture system behavior, what would <strong>human-centric metrics</strong> look like?</p><p>OSM introduces three core dimensions that most organisations never measure:</p><h4>Friction: The Effort Tax</h4><p>Friction is the invisible cost of getting things done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XxTwhy6wUu-AFxDA" /><figcaption>Photo by <a href="https://unsplash.com/@heritagetax1?utm_source=medium&amp;utm_medium=referral">Rebekah Roy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s not about whether the service works — it’s about <strong>how hard people have to work to make it work</strong>.</p><p>Friction shows up everywhere:</p><ul><li>In HR: The unofficial “ask Jenny” channel because the HRIS doesn’t cover edge cases</li><li>In Sales: The spreadsheet that reconciles what CRM says vs. what actually happened</li><li>In Finance: The manual journal entries fixing what the system can’t handle</li><li>In Legal: The email chain explaining what the contract management system obscures</li><li>In Operations: The tribal knowledge about which supplier to actually call</li></ul><p><strong>Friction isn’t failure. It’s tax.</strong></p><p>A tax on time, energy, trust, and credibility.</p><p>And unlike technical debt, we rarely acknowledge it — let alone measure it.</p><p><strong>How to detect friction:</strong></p><ul><li>Time spent outside the “happy path”</li><li>Frequency of escalations and exceptions</li><li>Shadow systems and unofficial processes</li><li>Knowledge that exists only in people’s heads</li><li>Requests that require “someone who knows how it really works”</li></ul><p>When friction is high, people survive — but they don’t trust.</p><h4>Flow: The Movement of Value</h4><p>Flow is about whether value is actually moving through the system.</p><p>Not activity. Not busyness. Not tickets being shuffled.<br>But <strong>real progress toward real outcomes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X4ZLvn4Eac9lOFTY" /><figcaption>Photo by <a href="https://unsplash.com/@bruno_nascimento?utm_source=medium&amp;utm_medium=referral">Bruno Nascimento</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Flow asks:</p><ul><li>Is work moving forward, or looping?</li><li>Are decisions being made, or deferred?</li><li>Are handoffs smooth, or causing rework?</li><li>Is the service creating momentum, or drag?</li></ul><p>We’ve covered this before: activity without flow is just exhausting theatre.</p><p><strong>How to detect flow (or the lack of it):</strong></p><ul><li>Work in progress that never completes</li><li>Decisions revisited multiple times</li><li>Deliveries that require heroic effort</li><li>Services where “done” keeps changing</li><li>Teams that are busy but making no visible progress</li></ul><p>When flow is broken, effort multiplies but outcomes don’t.</p><h4>Faith: The Belief That It Will Work</h4><p>Faith is the most human metric of all.</p><p>It’s not about satisfaction surveys or NPS scores.<br>It’s about <strong>whether people believe the service will actually help them</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_rl10vwlJF-yWcTg" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=medium&amp;utm_medium=referral">Tim Mossholder</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Faith is what makes someone:</p><ul><li>Use the official process instead of working around it</li><li>Trust the system instead of calling a colleague who “knows how it really works”</li><li>Try the service again after it failed them once</li><li>Recommend it to a peer</li></ul><p><strong>Faith isn’t blind optimism. It’s earned credibility.</strong></p><p>And it erodes silently:</p><ul><li>One unresolved ticket at a time</li><li>One ignored escalation at a time</li><li>One “we’re working on it” that never delivers</li></ul><p><strong>How to detect faith (or the loss of it):</strong></p><ul><li>Declining service adoption (people voting with their feet)</li><li>Rising exceptions (people bypassing the system)</li><li>Shadow systems and workarounds (people building their own solutions)</li><li>Silence in feedback channels (people have stopped expecting change)</li><li>Cynicism in conversations (people have given up)</li></ul><p>When faith is lost, no amount of compliance can restore it.</p><p>You can’t SLA your way back to trust.</p><h4>Why Traditional Metrics Can’t Capture This</h4><p>Here’s the uncomfortable truth:</p><p><strong>Friction, flow, and faith can’t be measured the way we measure uptime.</strong></p><p>They’re emergent properties of complex human systems.</p><p>You can’t instrument them directly.<br>You can’t put a probe on “trust” or set a threshold for “belief.”</p><p>But you <em>can</em> detect their presence — or absence — through signals:</p><ul><li>Conversations people have (or avoid)</li><li>Decisions people make (or defer)</li><li>Paths people take (or work around)</li><li>Energy people invest (or withdraw)</li></ul><p>This requires a different kind of measurement:</p><p>Not <strong>precision</strong>, but <strong>pattern recognition</strong>.<br>Not <strong>dashboards</strong>, but <strong>sensemaking</strong>.<br>Not <strong>single metrics</strong>, but <strong>coherent stories</strong>.</p><h4>The Multi-Dimensional Truth</h4><p>Here’s where it gets harder.</p><p>Human-centric metrics are <strong>multi-dimensional</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AkhOJxE4xwldxb1l" /><figcaption>Photo by <a href="https://unsplash.com/@loganvoss?utm_source=medium&amp;utm_medium=referral">Logan Voss</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You can’t optimize for one without affecting the others.</p><ul><li>Make it faster → might increase friction (less care, more rework)</li><li>Remove friction → might slow flow (more approvals, more coordination)</li><li>Increase compliance → might erode faith (people feel controlled, not supported)</li></ul><p>These trade-offs are real.<br>And they matter.</p><p>That’s why OSM treats services as <strong>dynamic ecosystems</strong>, not atomic units.</p><p>Everything co-exists in a web of influence:</p><ul><li>Speed affects quality</li><li>Quality affects trust</li><li>Trust affects adoption</li><li>Adoption affects demand</li><li>Demand affects speed</li></ul><p>Life is not linear. Experience is messy.</p><p>Any model that flattens this complexity risks doing more harm than good.</p><p>Simplicity is valuable — but only when it honors the richness of what it represents.</p><h4>What Human-Centric Measurement Looks Like in Practice</h4><p>So how do you actually measure friction, flow, and faith?</p><p>Not with dashboards. With <strong>rituals, signals, and stories</strong>.</p><h4>Rituals: Create Space for Reflection</h4><p>Build lightweight, recurring moments where teams surface what traditional metrics miss:</p><ul><li><strong>Flow replays:</strong> Once a fortnight, walk through one real request end-to-end. Where did it stall? Where did someone have to intervene? What would have happened if they hadn’t?</li><li><strong>Friction audits:</strong> Monthly, ask: “What’s one thing people are working around?” Not to fix everything — just to acknowledge it exists and decide if it matters.</li><li><strong>Faith checks:</strong> Quarterly, ask the people who actually use the service: “Do you believe this will help you?” Not a survey. A conversation.</li></ul><p>These rituals don’t produce charts.<br>They produce <strong>awareness</strong>.</p><p>And awareness, in complex systems, is often more valuable than certainty.</p><h4>Signals: Watch What People Actually Do</h4><p>Human behavior reveals what surveys hide:</p><ul><li>Are people using the service, or working around it?</li><li>Are escalations rising or falling?</li><li>Are the same issues being reopened?</li><li>Is tribal knowledge becoming more concentrated or more distributed?</li><li>Are teams building shadow systems?</li></ul><p>You don’t need new tools. You need new questions.</p><p>Look at:</p><ul><li>Request patterns (repeated issues, frequent follow-ups)</li><li>Exception trends (are people trusting the standard process?)</li><li>Workaround frequency (how often do people bypass the official route?)</li><li>Manual intervention rate (how often does someone need to “fix” what the system did?)</li><li>Adoption rates (are people choosing to use this?)</li><li>Time-to-value (how long before someone gets actual benefit?)</li></ul><p>These aren’t perfect measures.<br>But they’re <strong>honest ones</strong>.</p><h4>Stories: Listen to the Narrative</h4><p>The most revealing metric is often qualitative:</p><p><strong>What story do people tell about the service?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zZtMrHswVtrp__eP" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Not in the boardroom. In the hallway.</p><ul><li><strong>In HR:</strong> “Just call Maria, she knows who to talk to in payroll.”</li><li><strong>In Finance:</strong> “The system will reject it, so prepare the manual workaround first.”</li><li><strong>In Sales:</strong> “Put the real notes in the email, not the CRM — no one reads the CRM.”</li><li><strong>In Legal:</strong> “The workflow is for show; the real approvals happen in the coffee queue.”</li><li><strong>Everywhere:</strong> “I gave up and built a spreadsheet.”</li></ul><p>These aren’t complaints to be dismissed.<br>They’re <strong>signals of system health</strong>.</p><p>When the story is cynical, compliance won’t fix it.<br>When the story is one of workarounds, automation won’t solve it.<br>When the story is about people, not process, no framework will save you.</p><h4>The OSM Approach: Credible Over Complete</h4><p>OSM doesn’t demand perfect measurement.</p><p>It demands <strong>credible measurement</strong>.</p><p>Measurement that’s:</p><ul><li><strong>Honest</strong> about what it knows and doesn’t know</li><li><strong>Contextual</strong> to the service and the people who use it</li><li><strong>Dynamic</strong> enough to adapt as the service evolves</li><li><strong>Human</strong> enough to capture what actually matters</li></ul><p>The Service Intelligence Base (SIB) supports this by creating a living model where:</p><ul><li>Friction points are tagged and tracked (not hidden in tribal knowledge)</li><li>Flow breaks are visible (not buried in backlogs)</li><li>Faith trends are documented (not dismissed as “soft” data)</li></ul><p>It’s not about measuring everything.<br>It’s about measuring <strong>enough</strong> to act with confidence.</p><h4>The Courage to Measure Differently</h4><p>Here’s the challenge:</p><p>Human-centric metrics require vulnerability.</p><p>They surface uncomfortable truths:</p><ul><li>The service people celebrate internally might be the one users hate</li><li>The metrics we’re proudest of might be the least meaningful</li><li>The places we feel most in control might be where trust is most fragile</li></ul><p>Traditional metrics protect us from these truths.</p><p>They let us say “everything’s fine” when it’s not.<br>They let us optimize for appearances instead of outcomes.</p><p>Human-centric metrics don’t allow that luxury.</p><p>They ask:</p><ul><li><strong>Are people getting value, or just activity?</strong></li><li><strong>Is the service building trust, or eroding it?</strong></li><li><strong>Are we making it easier or harder to get things done?</strong></li></ul><p>And those questions don’t have green-light answers.</p><p>They have <strong>honest</strong> answers.</p><p>Which is why most organisations don’t ask them.</p><h4>What Changes When We Measure What Matters</h4><p>When you start measuring friction, flow, and faith:</p><ul><li><strong>Priorities shift.</strong> You stop celebrating processing volume and start investigating why people need so many interventions in the first place. Why are so many HR requests exceptions? Why do so many purchase orders need manual correction? Why do sales reps maintain shadow spreadsheets?</li><li><strong>Conversations change.</strong> Governance meetings stop being compliance theatre and start being genuine service improvement sessions.</li><li><strong>Ownership becomes real.</strong> Service owners can finally see what’s actually happening, not just what the dashboard says.</li><li><strong>Investment decisions improve.</strong> You fund the things that reduce friction and restore faith, not just the things that look impressive in a roadmap.</li><li><strong>Trust rebuilds.</strong> People notice when you measure what they care about, not just what’s easy to measure.</li></ul><p>This isn’t soft. This is strategic.</p><p>Because in the end, services succeed or fail based on human adoption and trust — not technical compliance.</p><h3>The Question We Need to Ask</h3><p>So here’s where we land:</p><p><strong>Are your metrics helping you see truth, or just helping you sleep at night?</strong></p><p>Because dashboards full of green lights might feel reassuring.</p><p>But if people are struggling, working around the system, and losing faith — those green lights are lies.</p><p>Not malicious lies. Just incomplete ones.</p><p>And incomplete truths, when we treat them as gospel, become the most dangerous kind of fiction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77b802de8320" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ownership Without Authority]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/ownership-without-authority-18d1115bbdbe?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/18d1115bbdbe</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 03:21:18 GMT</pubDate>
            <atom:updated>2026-01-07T03:21:18.410Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to take ownership of Services we can not own.</h3><p>We’ve all heard it:</p><p>“You’re accountable for the service.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EeAuiC4CE9hYzOiO" /><figcaption>Photo by <a href="https://unsplash.com/@tobiastu?utm_source=medium&amp;utm_medium=referral">Tobias Tullius</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Great. Now explain how that works when you don’t control:</p><ul><li>the infrastructure it runs on</li><li>the team that builds it</li><li>the budget that funds it</li><li>the decisions that shape it</li></ul><p>This is the accountability trap: responsibility without power.</p><p>We’ve encountered this before — it’s organisational theatre.</p><p>The rituals, titles, and frameworks that look like meaningful action but achieve very little. In this case, handing someone accountability without enablement, then wondering why they can’t deliver. It’s the organisational equivalent of giving someone a steering wheel with no connection to the wheels.</p><p>And it’s everywhere.</p><h3>The RACI Delusion</h3><p>RACI matrices promise clarity: Responsible, Accountable, Consulted, Informed.</p><p>In theory, beautiful.<br>In practice, a game of organisational hot potato.</p><p>Because when something goes wrong, everyone points to their box:</p><ul><li>“I’m just <em>consulted</em> — not my call.”</li><li>“I’m <em>informed</em> — I didn’t know I was supposed to act.”</li><li>“I’m <em>responsible</em>, but I don’t have authority to change anything.”</li></ul><p>And the person marked <em>accountable</em>?<br>They’re holding the bag for a system they don’t control.</p><p>RACI doesn’t create ownership. It creates plausible deniability.</p><p>It maps reporting lines, not influence.<br>It shows structure, not flow.</p><p>Real ownership can’t be assigned in a spreadsheet.<br>It has to be <em>enabled</em>.</p><h3>Authority Is Not Control</h3><p>Here’s the uncomfortable truth: most services cross multiple boundaries.</p><p>They span:</p><ul><li>technology stacks</li><li>business units</li><li>vendor contracts</li><li>geographic regions</li><li>governance frameworks</li></ul><p>No single person controls all the moving parts.</p><p>So when we say someone “owns” a service, we’re usually lying.</p><p>What we mean is: “You’re the person we’ll look too to fix it when it fails.”</p><p>Or more simply — who we can blame.</p><p>That’s not ownership. That’s a scapegoat with a job title.</p><p>Real ownership is about <strong>influence</strong>, not control.</p><p>It’s the ability to:</p><ul><li>see what’s happening across boundaries</li><li>coordinate the people who <em>do</em> have authority</li><li>make informed decisions even when you don’t hold all the levers</li><li>create accountability through visibility, not hierarchy</li></ul><p>You don’t need to control everything to own the outcome.<br>But you do need to <em>see</em> everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wTi7ZiaX1A7rTtJb" /><figcaption>Photo by <a href="https://unsplash.com/@jenniferfjy?utm_source=medium&amp;utm_medium=referral">Jennifer Feng</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And that’s where most organisations fail.</p><h3>The Accountability Trap</h3><p>Let’s talk about what happens when we create accountability without enablement.</p><p>A “service owner” gets handed:</p><ul><li>a title</li><li>maybe a budget (if they’re lucky)</li><li>responsibility for uptime, performance, user satisfaction</li></ul><p>But they don’t get:</p><ul><li>access to the teams that fix issues</li><li>authority to prioritise changes</li><li>visibility into dependencies</li><li>influence over architectural decisions</li></ul><p>They’re expected to answer questions like:</p><ul><li>“Why is this service slow?”</li><li>“When will that feature be ready?”</li><li>“What’s the risk if we deprecate this component?”</li></ul><p>And the honest answer is: <em>“I don’t know — because I can’t see it, and I can’t change it.”</em></p><p>That’s the trap.</p><p>We’ve given them accountability for an outcome they have no power to shape.</p><p>So what do they do?</p><p>They spend their time in meetings.<br>Negotiating. Escalating. Pleading.<br>Trying to create influence through sheer force of personality.</p><p>Exhausting. Ineffective. Unsustainable.</p><h3>What Real Service Ownership Looks Like</h3><p>Real service ownership isn’t about control.<br>It’s about <strong>coherence</strong>.</p><p>An owner doesn’t need to make every decision.<br>But they do need to:</p><ol><li><strong>See the whole service</strong> — not just their part, but the entire flow from request to outcome</li><li><strong>Know the dependencies</strong> — what influences the service, and what the service influences</li><li><strong>Coordinate across boundaries</strong> — bring the right people together at the right time</li><li><strong>Make trade-offs visible</strong> — when priorities conflict, expose the choice clearly</li><li><strong>Own the narrative</strong> — be the authoritative voice on service health, direction, and risk</li></ol><p>Notice what’s missing: direct authority over people, budget, or infrastructure.</p><p>Because ownership is a relationship with the <em>service</em>, not a position in the hierarchy.</p><p>When the service is visible, ownership becomes possible.<br>When it’s fragmented across silos, ownership becomes fiction.</p><h3>OSM: Making Ownership Real</h3><p>This is where Organisational Service Management (OSM) changes the game. OSM doesn’t pretend services can be owned by one person with total control.</p><p>Instead, it creates the <strong>conditions for ownership</strong> by making services visible, connected, and navigable.</p><h3>The Service Intelligence Base (SIB)</h3><p>The SIB is OSM’s answer to the visibility problem.</p><p>It’s a living model that shows:</p><ul><li>what the service actually is (not what we hoped it would be)</li><li>who consumes it, who depends on it, who supports it</li><li>what components enable it, and what risks threaten it</li><li>where changes are happening, and what their impact might be</li></ul><p>This isn’t a static diagram.</p><p>It’s a dynamic, federated view — constantly updated by events, signals, and real operational data.</p><p>When a service owner can <em>see</em> the service — truly see it — they don’t need authority over every component.</p><p>They can:</p><ul><li>spot issues before they escalate</li><li>coordinate responses across teams</li><li>make informed trade-offs</li><li>communicate credibly with stakeholders</li></ul><p>Visibility creates influence.<br>Influence enables ownership.</p><h3>Ownership by Experience, Not by Org Chart</h3><p>OSM flips the traditional model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5GN1Tg79uE8cwVrm" /><figcaption>Photo by <a href="https://unsplash.com/@acerin?utm_source=medium&amp;utm_medium=referral">Aleš Čerin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Instead of asking “Who reports to whom?”, it asks “Who experiences this service?”</p><p>Ownership follows the <strong>service boundary</strong>, not the reporting line.</p><p>That means:</p><ul><li>the owner is accountable for the <em>outcome</em>, not the <em>components</em></li><li>teams contribute to the service, but don’t own fragments of it</li><li>decisions are made in the context of service flow, not departmental priorities</li></ul><p>This is a fundamental shift.</p><p>It requires organisations to stop treating services as collections of tickets, projects, or infrastructure — and start treating them as <strong>living systems with identifiable outcomes</strong>.</p><p>When we do that, ownership becomes coherent.</p><h3>The Influence Model</h3><p>So how does ownership without authority actually work?</p><p>Through <strong>structured influence</strong>.</p><p>An effective service owner in the OSM model:</p><h4>Creates Sightlines</h4><p>They ensure the service is visible to everyone who needs to see it.<br>Not buried in tribal knowledge or scattered across systems — but represented in a shared, credible model.</p><h4>Facilitates Coordination</h4><p>They bring the right people into the conversation — not through endless meetings, but through <strong>service-centric rituals</strong> that focus on flow, health, and outcomes.</p><h4>Exposes Trade-Offs</h4><p>When priorities conflict (and they always do), the owner makes the choice explicit:<br><em>“We can have speed or stability — which matters more right now?”</em></p><h4>Owns the Story</h4><p>They are the authoritative source on service state.<br>Not because they control everything, but because they <em>see</em> everything.</p><h4>Builds Trust Through Transparency</h4><p>They admit uncertainty.<br>They share what’s known, what’s assumed, and what needs to be learned.<br>That credibility earns influence.</p><p>This is ownership as <strong>stewardship</strong>, not dominion.</p><h3>What This Means in Practice</h3><p>Let’s ground this with an example.</p><p>Imagine a “Customer Onboarding” service.</p><p>It involves:</p><ul><li>a CRM system (owned by Sales)</li><li>an identity platform (owned by Security)</li><li>a provisioning workflow (owned by IT)</li><li>training content (owned by Learning &amp; Development)</li><li>a billing integration (owned by Finance)</li></ul><p>No single person controls all those pieces.</p><p>In a traditional model, the “service owner” spends their life chasing updates:</p><ul><li>emailing teams for status</li><li>sitting in five different governance meetings</li><li>trying to predict impact when something changes</li></ul><p>In an OSM model with a SIB:</p><ul><li>The service is modelled as a single entity with visible dependencies</li><li>Each component team updates their part in real-time (via automation or lightweight input)</li><li>The service owner sees the whole picture in a <strong>single, living view</strong></li><li>When a change is proposed (e.g., Security wants to upgrade the identity platform), the SIB immediately shows:</li><li>which services are affected</li><li>who needs to be involved</li><li>what the downstream impact might be</li></ul><p>The owner doesn’t need authority over Security.<br>They just need to see the dependency and coordinate the conversation.</p><p>That’s influence.<br>That’s ownership.</p><h3>The Hard Truth About Accountability</h3><p>Here’s what organisations don’t want to hear:</p><blockquote><strong>If you give someone accountability without visibility and influence, you’re setting them up to fail.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IoQsr81XIc-PE4Ho" /><figcaption>Photo by <a href="https://unsplash.com/@herrond?utm_source=medium&amp;utm_medium=referral">Daniel Herron</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And when they fail, it’s not because they weren’t capable.<br>It’s because the system was designed to obscure truth and fragment responsibility.</p><p>That’s not poor performance.<br><strong>That’s poor design.</strong></p><p>OSM doesn’t magically solve every organisational dysfunction.</p><p>But it does make one thing clear:</p><p><strong>If you can’t see the service, you can’t own it.</strong></p><p>And if you can see it — really see it — then ownership becomes possible, even without authority.</p><h3>The Path Forward</h3><p>Ownership without authority is not a paradox.<br>It’s a choice.</p><p>It requires:</p><ul><li>making services visible</li><li>designing for influence, not control</li><li>measuring coherence, not compliance</li><li>building trust through transparency</li></ul><p>OSM provides the model, the language, and the tools to make it real.</p><p>But it also requires something harder:</p><blockquote><strong>The willingness to stop pretending hierarchical authority equals service ownership.</strong></blockquote><p>Because it doesn’t.<br>And it never did.</p><p>—</p><p>If this resonates, follow along for more on Organisational Service Management, service flow, and human-centred transformation.</p><p>And if you’re navigating the accountability trap in your own organisation — I’d love to hear your story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18d1115bbdbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lighthouse, Not a Map]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/lighthouse-not-a-map-ed18548033ee?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed18548033ee</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 17:21:49 GMT</pubDate>
            <atom:updated>2025-12-15T17:21:49.762Z</atom:updated>
            <content:encoded><![CDATA[<p>Rethinking strategy, certainty, and how organisations navigate change</p><h3>Strategy as Insurance</h3><p>Tier One strategy firms don’t really sell strategy anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TbTwAa4Ll7Bbdak9" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>They sell insurance.</p><p>For decades, the Tier One firms were the symbol of elite strategy.</p><p>Boardroom alchemy. Razor-sharp thinkers. The best brains money could buy.</p><p>When something was truly hard, truly consequential, you brought them in.</p><p>I grew up professionally in organisations where a Tier One engagement still meant something.</p><p>It signalled intent. It said: <em>we are prepared to be challenged</em>. Not just validated.</p><p>Somewhere along the way, though, the product changed.</p><p>It stopped being insight.</p><p>It stopped being transformation.</p><p>What emerged instead was something safer, more subtle — a <strong>strategy-as-cover industry</strong>, built around defensibility rather than direction.</p><p>Today, when many boards call Tier One advisors, it isn’t because they want a bold answer. It’s because something has already gone wrong.</p><p>Sales are falling.<br>A new technology is looming.<br>AI has arrived and the executive team doesn’t quite know what to do with it.</p><p>I’ve sat in those rooms. The tension is familiar. People are not looking for the <em>right</em> answer — they are looking for a <em>defensible</em> one.</p><p>You don’t bring in Tier One advisors to fix the problem.<br>You bring them in to spread the risk.</p><p>The strategy-as-cover industry isn’t always hired to be right.<br>It’s hired to be defensible.</p><p>Translation: <em>If this fails, it won’t be our fault.</em></p><p>This is strategy by plausible deniability.</p><p>And it works — politically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xdL6W6L83Rk-AT9V" /><figcaption>Photo by <a href="https://unsplash.com/@oommiidd?utm_source=medium&amp;utm_medium=referral">omid roshan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Break‑Even Deck</h3><p>Hiring a top‑tier strategy firm now buys three things:</p><ul><li><strong>Time</strong> — to stall hard decisions</li><li><strong>Borrowed Credibility</strong> — to calm investors and boards</li><li><strong>Cover</strong> — to shield individuals from blame</li></ul><p>And for many, that’s enough.</p><p>I’ve watched entire programmes exist purely to maintain that cover. Months of activity, endless workshops, beautifully structured decks — all optimised to avoid committing to anything that might expose an individual leader.</p><p>Not a bold roadmap.<br>Not an uncomfortable truth.<br>Just someone credible to stand beside them when the hard questions arrive.</p><blockquote>The irony is that real strategy is inherently risky.</blockquote><p>It demands ownership.<br>It creates exposure.<br>It forces leaders to place a stake — not just approve a deck.</p><p>Instead, much of what passes for “strategy” today is built from familiar components: best practice, turf protection, risk avoidance, and transformation theatre.</p><p>I’ve helped organisations unwind years of these accumulated decisions. Each one made sense at the time. Each one was defensible. And collectively, they locked the organisation into a future nobody would have consciously chosen.</p><p>These elements get wrapped into a single, reassuring concept called <em>Strategy</em> — and an entire industry has grown wealthy delivering it.</p><p>But using what has been, simply because it is defensible, is no different from playing cards with a loaded deck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qx84HbmE1cqJD8eW" /><figcaption>Photo by <a href="https://unsplash.com/@richwilliamsmith?utm_source=medium&amp;utm_medium=referral">Rich Smith</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Not a deck that helps you win.<br>Not even one that guarantees you lose.</p><p>A deck designed to break even.</p><p>Breaking even feels safe.<br>It also guarantees irrelevance.</p><h3>Stakes, Not Plans</h3><p>True strategy is not about certainty. It’s about intent.</p><p>It’s about taking a <strong>stake</strong> — a conscious decision about where you are heading — and then paying close attention to how reality responds.</p><p>Every meaningful strategy I’ve seen succeed started this way. Not with a master plan, but with a directional bet and a willingness to learn in <strong>public</strong>.</p><p>Strategy is <em>directional</em>.<br>Plans are <em>mechanical</em>.</p><p>Confusing the two is one of the most damaging habits in modern organisations.</p><p>A strategy does not need to be grounded in execution detail. It can begin as a vision, a belief, even a wish. What matters is whether, at this moment in time, you can credibly say you are on your way.</p><p>That <strong>credibility</strong> comes from signals, not documents.</p><p>From decisions made.<br>From trade‑offs accepted.<br>From behaviours that align with intent.</p><p>This is why strategies that take nine months to “complete” are usually obsolete before they are approved.</p><p>I’ve lived through those cycles.</p><p>By the time alignment is reached, the market has moved, the people have changed, and the opportunity has expired.</p><p>When we take too long to decide where we are going, we pass the point at which the decision is useful.</p><h3>The ‘Strategic Plan’ break from sanity</h3><p>There is no such thing as a <em>strategic plan</em>.<br>They are two fundamentally different things.</p><p>Plans explain how.<br>Strategy explains why — and where.</p><p>Plans can be delegated.<br>Strategy cannot.</p><p>Putting the two together and claiming a win is just racing to failure.<br>I have been around far too many organisations that claim they ‘have’ a strategic plan, which amounts to a gantt chart equivalent of things that they want to achieve. Nothing says ‘why’, nothing forms a glue that aligns people, they just become arbitary boxes to tick off to claim momentum</p><h3>OSM a Lighthouse on the Shore</h3><p>This is where Organisational Service Management (OSM) comes in — not as another framework, but as a different way of <em>seeing</em>.</p><p>OSM acts like a lighthouse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A-dpP_mazppY4LNR" /><figcaption>Photo by <a href="https://unsplash.com/@evgenit?utm_source=medium&amp;utm_medium=referral">Evgeni Tcherkasski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A lighthouse doesn’t illuminate the entire coastline.<br>It doesn’t provide a step‑by‑step route.<br>And it certainly doesn’t guarantee safe passage.</p><p>What it does is provide a <strong>fixed point of reference</strong>.</p><p>A signal that says: <em>this is where you are and where you are pointed in relation to where you’re trying to go.</em></p><p>That distinction matters.</p><p>Most organisations try to manage uncertainty by pretending it doesn’t exist. They create ever more detailed plans, more milestones, more artefacts — as if precision can substitute for direction.</p><p>OSM works the other way around.</p><p>It accepts uncertainty as a given and focuses instead on <strong>orientation</strong>.</p><p>It asks:</p><ul><li>What services actually exist today?</li><li>Who consumes them, who depends on them, and who is impacted when they fail to deliver?</li><li>Where are we investing energy that no longer aligns with intent?</li><li>Where are signals emerging that reality is diverging from strategy?</li></ul><p>Rather than forcing alignment through documents, OSM exposes alignment — or the lack of it — through observable service behaviour.</p><p>This is why it doesn’t try to “light up” the whole organisation.</p><blockquote><strong>OSM doesn’t tell leaders what decision to make — it makes it harder to pretend a decision hasn’t been made, and even harder to hide behind indecision.</strong></blockquote><p>Trying to see everything at once is what leads to paralysis.</p><p>Instead, OSM creates just enough visibility to support decision‑making: clear sightlines between intent, services, and outcomes.</p><p>When leaders can see how strategy is (or isn’t) showing up in the services their organisation actually delivers, they don’t need insurance.</p><p>They can navigate.</p><p>Not with certainty.<br>But with awareness.</p><p>And awareness, in complex systems, is far more valuable than confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ej9Fmb542dbonGS3" /><figcaption>Photo by <a href="https://unsplash.com/@fallonmichaeltx?utm_source=medium&amp;utm_medium=referral">Fallon Michael</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Leadership with Credible Uncertainty</h3><p>Leadership is not about eliminating uncertainty.<br>It is about managing it honestly.</p><p>Real leaders are clear about what they know, what they don’t know, and what they are choosing to learn next. They don’t hide behind complexity, delay, or the comfort of external authority.</p><p>Credible uncertainty is not indecision.</p><p>It is the ability to say:</p><ul><li><em>This is our intent.</em></li><li><em>This is what we understand today.</em></li><li><em>This is where the signals suggest we may be wrong.</em></li><li><em>And this is how we will adjust if reality proves us wrong.</em></li></ul><p>I’ve seen leaders lose trust not because they were wrong, but because they pretended they weren’t unsure. Certainty theatre might feel reassuring in the moment, but it erodes credibility over time.</p><p>This is where the insurance model of strategy ultimately fails.</p><p>Cover delays accountability.<br>Decks replace dialogue.<br>And leadership becomes something performed, rather than practiced.</p><p>But real leaders don’t need cover.</p><p>They need clarity.<br>They need ownership.<br>And often, they need the courage to act before the market forces their hand.</p><p>Because strategy was never meant to protect you from failure.</p><p>It was meant to help you choose what you are willing to risk.</p><p>—</p><p><em>If you enjoyed this post, follow me for more thinking on Organisational Service Management, Service Flow, and the human side of transformation and leadership.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed18548033ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation — oh really?]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/digital-transformation-oh-really-5aa2f7322b8a?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aa2f7322b8a</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 03:51:48 GMT</pubDate>
            <atom:updated>2025-12-01T03:51:48.566Z</atom:updated>
            <content:encoded><![CDATA[<h3>Digital Transformation — oh really?</h3><p><em>Most organisations are just doing tech cosplay</em></p><h3>Acceptable Lies</h3><p>Digital transformation has become the safest, most socially acceptable lie in modern business. Say it with confidence, throw a budget at it, hire a vendor — and suddenly we’re all pretending we’re reinventing the organisation.</p><p>We’re not.</p><p>We’re renovating.</p><p>Rebranding old behaviours with new tools.</p><p>Hoping technology will politely fix the parts of the organisation we refuse to touch.</p><p>Here’s the uncomfortable truth:</p><blockquote><strong>“Digital” without behavioural change is just tech cosplay.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wNorjYg3oDtOadYK" /><figcaption>Photo by <a href="https://unsplash.com/@shubhro_?utm_source=medium&amp;utm_medium=referral">Shubhro Jyoti Dey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Binary Fantasy</h3><p>Slap “digital” in front of anything and people instantly treat it like a binary switch:</p><ul><li>off/on</li><li>legacy/modern</li><li>broken/fixed</li></ul><p>It’s comforting. It’s simple. It’s also nonsense.</p><p>Technology changes fast.<br>People, incentives, culture, decision structures, habits — those change at glacial speed.</p><p>So swapping out one system for another without shifting how the organisation actually behaves is like <strong>bolting a rocket engine to a horse</strong>.</p><p>Impressive hardware.</p><p>Same animal.</p><h3>The Roadmap Delusion</h3><p>Let’s talk about roadmaps — the corporate security blanket.</p><p>A roadmap looks authoritative. Structured. Serious.<br>But most roadmaps are just a collection of guesses given PowerPoint privileges.</p><p>And yet, they all follow the same tired pattern:</p><ol><li><strong>Where we are</strong> — document it endlessly</li><li><strong>Where we want to be</strong> — describe it vaguely</li><li><strong>How we’ll get there</strong> — guess</li></ol><p>The problem isn’t the structure — it’s the weight we put on Step 1.</p><p>Months mapping every inconsistency.<br>Endless workshops cataloguing every pain point.<br>As if documenting the past more aggressively will create a better future.</p><p><strong>Spoiler:</strong> it won’t.</p><p>You don’t need perfect knowledge of the present to move.<br>You just need <strong>credible</strong> knowledge. Enough to act.</p><p>Completeness is paralysis.<br>Credibility is progress.</p><h3>The Chessboard Nightmare</h3><p>Designing a future is like playing chess on a board that expands every time you move a piece.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xdwhG0dG1T0zjuqP" /><figcaption>Photo by <a href="https://unsplash.com/@hpzworkz?utm_source=medium&amp;utm_medium=referral">Hassan Pasha</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Every step explodes into more steps.<br>Every decision creates ten more decisions.</p><p>It’s overwhelming. Uncertain. Messy.</p><p>So what do organisations do?<br>They retreat back to safety.</p><p>Document. Analyse. Re-document. Re-analyse.<br>Polish the current state until the future feels too risky to attempt.</p><p>The map becomes more important than the journey.</p><p>Thats where transformation dies — on the side of the road.</p><h3>Enter OSM: The Anti-Illusion</h3><p>Organisational Service Management (OSM) doesn’t buy into the fantasy of perfect knowledge.<br>It’s built for the real world — the one full of ambiguity, shifting priorities, and incomplete information.</p><p>OSM prioritises: — movement over certainty</p><ul><li>learning over planning</li><li>structure over noise</li><li>coordination over heroics</li><li>outcomes over artefacts</li></ul><p>In OSM, the future isn’t a destination. <strong>It’s a hypothesis.</strong></p><p>You set Stakes — intentions, outcomes, constraints.</p><ul><li>You take a step.</li><li>You learn.</li><li>You adjust.</li><li>You keep going.</li></ul><p>The model expects change.<br>It rewards interaction.<br>It grows with you.</p><p>This is what actual transformation feels like.<br>Not perfect. Not linear. Not safe. <strong>But real.</strong></p><h3>The One View That Matters</h3><p>The aim isn’t to replace project management, architecture, service management, product thinking, or strategy.</p><p>It’s to stop them competing.</p><p>OSM gives you a single coordinated view — credible enough to make decisions, clear enough to expose what matters, honest enough to show when you have too little information, and ruthless enough to show when you have far too much.</p><p>Because transformation is not about designing the perfect plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UpXkLURl1twrufOm" /><figcaption>Photo by <a href="https://unsplash.com/@heyquilia?utm_source=medium&amp;utm_medium=referral">Kenny Eliason</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s about building the organisational capability to move forward when the plan inevitably changes.</p><h3>The Challenge</h3><p>So before the next executive meeting that starts with “our digital transformation journey…”, ask one simple question:</p><p><strong>Are we actually transforming — or just upgrading tools and calling it bravery?</strong></p><p>—</p><p><em>If you enjoyed this post, follow me for more thinking on Organisational Service Management, Service Flow, and the human side of transformation.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5aa2f7322b8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSM: Risk, Investment, and What’s Really at Stake]]></title>
            <link>https://rosswilliamson-strategenz.medium.com/osm-risk-investment-and-whats-really-at-stake-ca7bbddc95f6?source=rss-c3460ef8481f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca7bbddc95f6</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Ross Williamson]]></dc:creator>
            <pubDate>Tue, 25 Nov 2025 04:18:12 GMT</pubDate>
            <atom:updated>2025-11-25T04:18:12.585Z</atom:updated>
            <content:encoded><![CDATA[<h4>From avoiding blame to making deliberate, stakeful decisions</h4><blockquote>Continuing the journey through Organisational Service Management — and how to reframe Services to serve people.</blockquote><h3><strong>Reframing the Conversation</strong></h3><p>When we treat every potential negative event purely as a “risk,” we unconsciously bias our decision-making toward avoidance. But businesses don’t grow through avoidance — they grow through intentional, well-understood investments.</p><p>The language we use shapes the behaviours we adopt:</p><ul><li>Calling something a <strong>risk</strong> frames it as a threat to be controlled.</li><li>Calling it an <strong>investment</strong> frames it as a choice about how we allocate time, money, and attention.</li></ul><p>This isn’t about being blindly positive or pretending everything is an opportunity.</p><p>It’s about recognising that:</p><ul><li>Every opportunity contains risk (you might lose).</li><li>Every risk contains opportunity (you might win).</li></ul><p>They are two sides of the same coin: <strong>uncertainty plus choice</strong>.</p><p>The real work is to evaluate that uncertainty with clarity rather than fear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-C1mJfpG2e6ZILwm" /><figcaption>Photo by <a href="https://unsplash.com/@thetonik_co?utm_source=medium&amp;utm_medium=referral">Tonik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One practical way to think about it:</p><ul><li>Risk is what could be lost.</li><li>Investment is what you’re choosing to stake for a potential gain.</li></ul><p>Underneath both labels is the same thing:<strong>a stakeful decision under uncertainty</strong>. Healthy organisations need to be fluent in both sides of that conversation.</p><h3><strong>Why We Default to “Risk” Language</strong></h3><p>Most of us don’t wake up in the morning excited to be blamed. Our psychology and our organisational systems both encourage <strong>defensive thinking</strong>.</p><p>A few forces overlap here:</p><ul><li><strong>Human negativity bias</strong> — We are wired to notice and remember bad things more than good ones. Historically, that kept us alive. Your brain is a superb “danger detector,” not an “opportunity maximiser.</li><li><strong>Accountability fear —</strong> In many organisations, the person associated with the incident or failed change becomes the story. Even if the decision was reasonable at the time, nobody wants to be the name on the post-incident review.</li><li><strong>Compliance and audit pressure</strong> — Risk frameworks, controls, and checklists are often written in the language of avoidance: prevent, mitigate, restrict. The easiest way to pass an audit is not to do anything new.</li></ul><p>So we build mechanisms like risk registers. On the surface, they are logical and necessary.</p><p>Underneath, they can quietly encourage behaviours like:</p><ul><li>Pushing risks onto someone else (“Can we assign this to another team?”).</li><li>Inflating risk ratings so nobody can say you missed something — or accuse you of not raising it.</li><li>Designing controls that make change harder than staying still.</li></ul><p>It’s all perfectly rational — and it’s all <strong>avoidance-driven</strong>.</p><p>The old joke applies:</p><blockquote>If we’re being chased by a bear, I don’t have to outrun the bear, I just have to outrun you.</blockquote><p>In service terms: it doesn’t mean the service is great; it just has to look slightly less risky than the alternative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p4aZi7nFArvP4lqf" /><figcaption>Photo by <a href="https://unsplash.com/@hansjurgen007?utm_source=medium&amp;utm_medium=referral">Hans-Jurgen Mager</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>What Happens When Everything Becomes a Risk</strong></h3><p>When every uncertain event is captured only as a risk, several things tend to happen:</p><ol><li><strong>The horizon shrinks.</strong> Teams optimise for the next quarter’s audit or the next board report, rather than the next 3–5 years of capability.</li></ol><p>2. <strong>Innovation is quietly discouraged.</strong> New ideas are born as risk items: “Risk: new platform may be unstable.” That risk is real — but the upside rarely makes it into the same conversation with the same weight.</p><p>3. <strong>People play not to lose.</strong> Decisions are judged more harshly by outcomes than by the quality of reasoning. So the safest move is often to say no, defer, or ask for one more review.</p><p>The result is a kind of organisational drift.</p><p>Services may remain “safe,” but they get older, more brittle, and less relevant.</p><p>We prevent outages but also prevent progress.</p><p>Worse, the focus becomes all about mitigating risk. Available capacity gets sucked into <em>addressing risks</em>. That can quietly build a culture of gaming the system — making sure there are ‘official’ risks on the register that defend the service or change you’re trying to push through.</p><p>When everything becomes a risk, <strong>everything</strong> is a risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VNQYNWldmKU7TIYs" /><figcaption>Photo by <a href="https://unsplash.com/@josephjtwo?utm_source=medium&amp;utm_medium=referral">Joseph Two</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Seeing the Investment Inside the Risk</strong></h3><p>Reframing doesn’t mean ignoring downside. It means bringing <strong>both sides of the equation</strong> into view.</p><p>Take a simple example:</p><blockquote>“Risk: Migrating our core service to a new cloud platform may cause instability and outages.”</blockquote><p>That’s true. But what’s the investment decision hiding inside it?</p><blockquote>“Investment: Allocate capital and capacity to modernise our platform so we can scale, deliver features faster, and reduce long-term operating costs.”</blockquote><p>Same situation, different framing. Once we treat it as an <em>investment</em>, better questions become possible:</p><ul><li>What are we actually staking? (Budget, reputation, customer trust, people’s time.)</li><li>What is the potential upside, and over what timeframe?</li><li>What scenarios exist between “complete success” and “total failure”?</li><li>What small bets or experiments could give us more information before we commit fully?</li></ul><p>We can now talk in terms that boards and executives understand intuitively: <strong>return on investment, portfolio, options, and time horizon</strong>, rather than only red-amber-green risk ratings.</p><h3><strong>A Simple Pattern: From Risk Item to Investment Thesis</strong></h3><p>Here’s a lightweight pattern you can apply directly to your existing risk register.</p><p>For any risk item, ask the team to complete four steps:</p><p>1. <strong>Name the situation neutrally.</strong></p><p>Strip away the fear-laden phrasing. Instead of “Risk of catastrophic outage due to legacy database,” try “Choice: continue on legacy database vs. invest in modernisation.”</p><p>2. <strong>Write both sides explicitly.</strong></p><ul><li><em>Downside (risk):</em> What might be lost if we act or don’t act?</li><li><em>Upside (opportunity):</em> What might be gained if this plays out well?</li></ul><p>3. <strong>Describe the stake and horizon.</strong></p><ul><li>What are we putting at risk?</li><li>Over what timeframe does this pay back — or hurt us?</li></ul><p>4. <strong>Choose a posture.</strong></p><p>Not every situation deserves the same response. For each one, decide whether you will:</p><ul><li><strong>Avoid</strong> — The potential loss is too great relative to the upside. We consciously choose <em>*not*</em> to make this investment now.</li><li><strong>Insure</strong> — We’ll go ahead, but we’ll offset or share the risk (contracts, architecture, contingency plans).</li><li><strong>Experiment</strong> — We’ll make a small, reversible bet to learn more before committing.</li><li><strong>Commit</strong> — We believe the upside justifies a significant, visible investment.</li></ul><p>Documenting this doesn’t need a new tool. It could simply be new columns in your existing register:</p><ul><li>Opportunity / upside</li><li>Investment posture (avoid / insure / experiment / commit)</li><li>Smallest next bet</li></ul><p>The goal is not more process; it’s <strong>better conversations</strong>.</p><h3><strong>Why This Matters for Modern Service and Technology Management</strong></h3><p>Traditional ITSM thinking has hardwired us into defensive postures: prevent incidents, reduce outages, eliminate vulnerabilities. These are all important — and they will always matter.</p><p>But if that’s the whole story, we drift into a world where:</p><ul><li>Change is guilty until proven innocent.</li><li>The safest service is the one that never evolves.</li><li>Technology teams are seen as cost centres to be controlled, not strategic partners to be backed.</li></ul><p>Modern service organisations need a more balanced model.</p><p>Instead of maintaining only a <strong>risk register</strong> full of “things to avoid,” imagine maintaining an <strong>investment register</strong> full of “choices to consider.” For each significant risk item, there is a paired investment entry asking:</p><ul><li>What capability might this give us if we lean into it?</li><li>How would we know it was paying off?</li><li>What’s the minimum viable stake we could put down to test the idea safely?</li></ul><p>This encourages teams to think like portfolio managers:</p><ul><li>Some investments will be low-risk, low-return (improving stability, removing toil).</li><li>Some will be higher-risk, higher-return (new products, new platforms).</li><li>The job is to shape the <em>*mix*</em> — not to avoid every possible loss.</li></ul><p>It also:</p><ul><li>Encourages ownership rather than avoidance.</li><li>Invites strategic thinking rather than fear-driven reactions.</li><li>Connects operational decisions with business outcomes and value.</li><li>Over time, this can change how governance works.</li></ul><p>Risk boards and change advisory forums can start asking:</p><ul><li><em>What investment are we making here?</em></li><li><em>What return are we seeking — financial, strategic, experiential?</em></li><li><em>What have we done to limit the downside without destroying the upside?</em></li></ul><p>This doesn’t abolish traditional risk language. It simply refuses to let it dominate.</p><p>We still care about confidentiality, integrity, availability, safety, and compliance. But we also care about momentum, relevance, and impact.</p><h3><strong>Practical Prompts for Teams</strong></h3><p>If you want to experiment with this in your own context, here are a few prompts you can start using in meetings and reviews:</p><ul><li>“If we treated this as an investment, what are we actually buying?”</li><li>“What’s the smallest safe bet we could place to learn more?”</li><li>“If we <em>don’t</em> act, what risk are we implicitly accepting?”</li><li>“What would make this risk worth taking?”</li><li>“In two years, will we regret being too cautious or too bold here?”</li><li>“Whose Stake are we touching with this decision — customers, staff, partners, regulators?”</li></ul><p>Used regularly, these questions shift the tone of conversation from <em>”How do I avoid blame?”</em> to <em>”How do we create value, safely enough?”</em></p><p>So far we’ve talked about risk and investment in general.</p><p>In OSM, we go one step further: we treat both as views of the same underlying thing — <strong>Service Stakes</strong>.</p><h3><strong>OSM: Human-Centric Services</strong></h3><p>The OSM (Organisational Service Management) lens starts with a simple yet critical idea: <strong>services are constructs that deliver to humans</strong>. They are ways we organise people, tools, rules, and information so that real human beings can get something done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ndwXRB-mR3wP0anI" /><figcaption>Photo by <a href="https://unsplash.com/@dylu?utm_source=medium&amp;utm_medium=referral">Jacek Dylag</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If we see services only through a risk lens, we tend to design them as <strong>shields</strong>:</p><ul><li>Shields against incidents.</li><li>Shields against complaints.</li><li>Shields against being blamed.</li></ul><p>The work becomes “chasing” — chasing tickets, chasing metrics, chasing compliance. Everyone is busy, but the service doesn’t necessarily feel better for the people who use it or the people who run it.</p><p>When we bring the investment lens into OSM, the service construct looks different. A service is no longer just a bundle of processes and SLAs; it’s a <strong>portfolio of bets</strong> we’re making on better human outcomes:</p><ul><li>Bets that certain roles, skills, and tools will make work smoother.</li><li>Bets that certain policies will make things safer without strangling initiative.</li><li>Bets that certain experiences will build trust with customers and partners.</li></ul><p>Instead of asking, “What could go wrong and who will get in trouble?” we start asking:</p><ul><li>“Who is this service really for?”</li><li>“What are they trying to achieve?”</li><li>“What are we willing to stake to make that easier, safer, and more human centric?”</li></ul><p>In that frame, risk management becomes part of <strong>designing for better outcomes</strong>, not just <strong>covering our arses</strong>. Controls, reviews, and escalation paths still matter — but they are tuned toward learning and improvement, not just self‑protection.</p><p>We stop chasing issues after the fact and start shaping the service construct so that better results are the default.</p><p>The point of the OSM view is to make that explicit: every risk decision is also a design choice about what kind of service, and what kind of working life, we are building.</p><h3><strong>OSM: Service Stakes</strong></h3><p>In the OSM SIB (Service Information Base) language, we give this idea a specific name: <strong>Stakes</strong>.</p><p>A <em>Stake</em> is the underlying thing we are putting on the line when we make a decision about a service. It might be money, time, reputation, trust, safety, attention, or energy. Whatever form it takes, a Stake represents a <strong>meaningful consequence for real people</strong> if the service goes well or goes badly.</p><p>At the OSM level, we can represent every service as a <strong>portfolio of Service Stakes</strong>, each with clear human outcomes attached.</p><ul><li><strong>Risk language</strong> zooms in on the <em>threat</em> to those Stakes.</li><li><strong>Investment language</strong> zooms in on the <em>potential return</em> on those Stakes.</li></ul><p>The underlying object is the same: the <strong>stakeful decision</strong> about how this service will show up for people.</p><p>When we map Stakes, we can see that projects, bets, experiments, options, promises, policies, guarantees, risks, and investments are all specific framings of the same underlying thing:</p><blockquote><strong>Positions we take in an uncertain world, with something at Stake.</strong></blockquote><p>Stakes are not static. As services evolve, the Stakes change:</p><ul><li>Financial Stakes shift as costs, contracts, and scale change.</li><li>Trust Stakes shift as customers and staff accumulate experiences, good and bad.</li><li>People Stakes shift as roles change, teams restructure, and new skills are needed.</li><li>Safety and compliance Stakes shift as regulations change or new technologies land.</li></ul><p>Because Stakes move, OSM is interested in <strong>how we observe and measure them over time</strong>. Later in this series I’ll connect Stakes to metrics: what we choose to measure, and how we read the signals.</p><p>By thinking in terms of Stakes, we:</p><ul><li>Stop biasing ourselves before we start (by calling everything a “risk” or, alternatively, blindly calling everything an “investment”).</li><li>Make more powerful and insightful connections between decisions that previously lived in different boxes (projects vs risks vs policies).</li><li>Give ourselves a more honest, human-centred way to ask: <em>“What are we really putting at Stake here, and is that the right choice for this service and these people?”</em></li></ul><h3><strong>From Outrunning the Bear to Choosing the Path</strong></h3><p>Remember the bear story from earlier — our psychology will always nudge us in that direction: if something dangerous is chasing us, we just need to run a bit faster than the person next to us. Many organisations operate exactly like that — trying to look slightly less risky than the alternative.</p><p>But that’s a very limited notion of success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SA9oYP77Daf_sIJ8" /><figcaption>Photo by <a href="https://unsplash.com/@juzwe?utm_source=medium&amp;utm_medium=referral">Julian Zwengel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A more useful image is this:</p><blockquote><strong>we are not just running from a bear; we are choosing which path our organisation will take through uncertain terrain.</strong></blockquote><p><em>Risk</em> thinking helps us see the cliffs and the loose rocks.</p><p><em>Investment</em> thinking helps us see the vantage points, the shortcuts, and the places worth reaching.</p><p><strong>We need both.</strong></p><p>In OSM terms, that’s the shift: using risk thinking to see where service outcomes may suffer, and investment thinking to decide how we’ll change the service so their experience actually improves — while deliberately outsmarting the bear, not just outrunning someone else.</p><p>Let’s stop merely running from danger and start deliberately choosing where we want to go — and what we’re willing to stake to get there.</p><p>—</p><p><em>If you enjoyed this post, follow me for more thinking on Organisational Service Management, Service Flow, and the human side of transformation.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca7bbddc95f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>