<?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 Tom Wynne-Morgan on Medium]]></title>
        <description><![CDATA[Stories by Tom Wynne-Morgan on Medium]]></description>
        <link>https://medium.com/@tomwm?source=rss-714f6bcad32f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yYxaXkEldAi_txsm.jpeg</url>
            <title>Stories by Tom Wynne-Morgan on Medium</title>
            <link>https://medium.com/@tomwm?source=rss-714f6bcad32f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:19:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomwm/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[Government’s next design challenge isn’t the service. It’s the decision]]></title>
            <link>https://medium.com/@tomwm/governments-next-design-challenge-isn-t-the-service-it-s-the-decision-c10ae15d4a1a?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c10ae15d4a1a</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[mapping]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 22:18:40 GMT</pubDate>
            <atom:updated>2026-04-29T22:18:40.849Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing Morgan Maps — a tool for mapping digital decisions in public services</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6sXvHsNHmTELSg1eWqWww.png" /></figure><p>I have a hypothesis. The last 15 years of public service transformation were about digital transactions. The next 10–15 years will be about digital decisions.</p><p>Much of what we’ve built in digital government has been about putting services online: better forms, clearer journeys, reusable platforms, product teams, and modern delivery practices. That work mattered. It still does. But the next wave is less about how someone applies, books, pays or reports something and more about how government <em>decides.</em></p><p>Who is eligible. What evidence is trusted. What risk is acceptable. When human judgement is needed. How uncertainty is handled. How decisions are explained and challenged.</p><p>AI is clearly a catalyst here, and becomes more interesting when framed this way. Not as a chatbot bolted onto an existing process, or as a mechanism for efficiency gains. But as a reason to redesign the deeper machinery of government: policy intent, operating models, data flows, professional judgement, accountability and feedback loops.</p><p>If I’m right about this, we need new ways of mapping and thinking about decision systems. That’s the territory I’ve been exploring through a tool I built called a <a href="http://lab.tomwm.co.uk/morgan-map">Morgan Map</a>.</p><h3>What does it map?</h3><p>Morgan Maps look at services through two dimensions:</p><ul><li>Automation — how far a decision, or the elements around it, can be handled by software or machines</li><li>Criticality — how consequential a decision or element is to the quality of the outcome and public trust in it</li></ul><p>Plot a service’s elements across those two dimensions and something interesting happens. You stop seeing a journey and start seeing a constellation. Clusters of decisions, interfaces, evidence and execution that reveal the real structure of a service and where the hard questions live.</p><p>High automation + high criticality is where things get uncomfortable. That’s where you’re asking machines to make consequential calls. High criticality + low automation is where human judgement is load-bearing and probably under-supported. Low criticality + high automation is where you can probably just let it run. The map surfaces those tensions in a way that a process diagram or a service blueprint doesn’t quite manage.</p><p>I’ve cheekily called them Morgan Maps, in a head-nod towards the inimitable Simon Wardley, who showed us that the way you draw something shapes the way you think about it.</p><h3>What the tool does</h3><p>The tool is a browser-based canvas. You can:</p><ul><li>Add nodes representing elements of a service — decisions, evidence, execution steps, interfaces. These can alredy exist or be proposed.</li><li>Connect them through their relationships to each other — informs, triggers, constrains, transfers to, escalates</li><li>Position them by dragging across the automation/criticality axes</li><li>Filter by node type, organisation, tags, or axis ranges</li><li>Export and import as JSON</li></ul><p>There’s also a prompt you can use with any capable LLM to generate a JSON for a service using publicly available information that you can upload:</p><blockquote>“<em>Using the schema at https://tomwm-lab.vercel.app/morgan-map/schema.json and the guide at https://tomwm-lab.vercel.app/morgan-map/llm-guide.md, create a Morgan Map JSON file for [service name]. Use only publicly known information.</em>”</blockquote><p>It won’t be perfect, but it gives you something to react to which is often more useful than starting from a blank canvas.</p><p>I’ve recently I’ve added a public gallery. A place to publish maps and browse ones others have shared. It’s an experiment in whether there’s value in a shared library of service models. If you publish something, it gets a shareable read-only link so others can explore it without being able to edit it.</p><h3>Why bother?</h3><p>Because AI is forcing us to look at the machinery of decisions — and we don’t have great tools for that yet.</p><p>A service journey map will tell you what someone experiences. A Morgan Map tries to reveal what the system has to <em>decide </em>and where the risks are in how it does that. They’re complementary, not competing.</p><p>And as AI becomes a more serious part of public service delivery, the questions this surfaces become more urgent. Not “can we automate this?” but “should we, given how critical it is?” and if we do, what does accountability look like?</p><p>Try it at <a href="https://lab.tomwm.co.uk/morgan-map">lab.tomwm.co.uk/morgan-map</a><br>View gallery at <a href="https://lab.tomwm.co.uk/morgan-map/gallery">https://lab.tomwm.co.uk/morgan-map/gallery</a></p><p>Feedback welcome!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c10ae15d4a1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Organisational Rails of AI]]></title>
            <link>https://medium.com/@tomwm/the-organisational-rails-of-ai-65a4a829c1e3?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/65a4a829c1e3</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[organisational-design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 08:49:59 GMT</pubDate>
            <atom:updated>2026-03-02T09:43:17.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Railway lines at junction with stop sign" src="https://cdn-images-1.medium.com/max/640/1*UXQRQ2pYOQcmPGQKVxztdQ.jpeg" /></figure><h4><em>Why the standards being set now matter more than the technology setting them</em></h4><p>Before the railways, time was local.</p><p>Each town set its clocks by the sun. Noon in Bristol was not quite noon in London, and that didn’t matter because nothing moved fast enough between them for the difference to cause trouble. Time was contextual. Embedded. Agreed through proximity.</p><p>Then the railways arrived and distance began to collapse. What had been a harmless variation became an operational risk. A train could leave on time in London and arrive late in Bristol without slowing down. The problem wasn’t mechanical, it was conceptual. Different places were operating on different assumptions about reality.</p><p>Railway companies standardised time. Not because they had collectively agreed on a new philosophy of temporality. Because coordination demanded it.</p><p>Alignment came before agreement.</p><p>Most organisations run quite happily on local time. Different teams hold slightly different definitions of risk, of done, of acceptable error. These differences are rarely written down. They are absorbed, negotiated, smoothed over through experience and proximity. When work moves at human speed, tacit coordination is usually enough.</p><p>AI changes the speed and the connectivity.</p><p>It asks for clearer definitions. It exposes where thresholds were assumed rather than agreed. It has no tolerance for the ambiguity that experienced humans systematically absorb. And as AI systems begin operating across functions, small differences in interpretation start to compound. If one part of the organisation tolerates a five percent error rate and another treats one percent as unacceptable, whose standard is the model running on?</p><p>The friction that follows is rarely about the intelligence of the model. It is about misaligned assumptions contained by proximity and pace. AI connects those contexts at speed and makes their differences visible. Organisations are forced to align how they coordinate before they have fully agreed why. The behaviour changes because the system requires it. The cultural story catches up later, if at all.</p><p>This is the railway pattern playing out again.</p><p>Railways didn’t invent time. They revealed that local time could not scale. AI isn’t inventing organisational ambiguity. It is revealing how much of organisational life depends on shared but unexamined interpretation and forcing that interpretation into the open.</p><p>But there is something else happening underneath that.</p><p>Look at the pattern across technology transitions. Railways standardised time. Industrialisation standardised production. Computing standardised logic. The internet standardised connectivity. Each transition forced something previously implicit into an explicit shared standard and each time, that standardisation created a surface others could build on. The rails didn’t just move goods, they made mass manufacturing viable.</p><p>If that pattern holds, perhaps the more interesting question about AI is not what it automates, but what it standardises.</p><p>The strongest candidate is interpretation itself. Pattern recognition. The modelling of uncertainty. The normalisation of probabilistic reasoning in everyday decisions. If AI embeds those things into organisational infrastructure; into thresholds, escalation paths, definitions of done and good enough. It is not simply a tool sitting on top of existing systems. It is laying track.</p><p>The people laying railway track were not consciously constructing the foundations of globally synchronised time. They were trying to move goods more efficiently. The wider consequences only became visible in hindsight, long after the track was fixed.</p><p>Railway time wasn’t just an operational fix. It was a new relationship between humans and time itself. Within a generation, nobody remembered negotiating it.</p><p>The standards being written into AI systems now will not feel like infrastructure. They will feel like sensible defaults. But every default encodes a judgement about what normal looks like and whose interests it serves. Within a generation, nobody will remember negotiating them. The question is whether we are paying attention while there is still something to negotiate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65a4a829c1e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Computer Says Maybe]]></title>
            <link>https://medium.com/@tomwm/computer-says-maybe-b4fe98ff6cb5?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4fe98ff6cb5</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Sun, 15 Feb 2026 21:58:26 GMT</pubDate>
            <atom:updated>2026-02-15T21:58:26.083Z</atom:updated>
            <content:encoded><![CDATA[<h4>When certainty gives way to judgement</h4><p>For years, customer service had a kind of structural clarity. The system held the rules. The agent applied them. The outcome was binary.</p><p>“Computer says no” became shorthand for that world. It was blunt, sometimes infuriating, but clear. The decision lived inside the machine. The human delivered it.</p><p>You can see it in banking: a payment is blocked because it breaches a defined rule. In insurance: a claim is rejected because it falls outside policy. In licensing: an application is refused because a criterion is not met.</p><p>The system processed. The human explained.</p><p>Generative AI shifts that arrangement. Instead of hard-coded rules, we increasingly see probabilistic assessments.</p><p>In a <a href="https://www.linkedin.com/posts/sarahtgold_if-an-ai-flags-a-payment-as-potentially-fraudulent-share-7425132575284752384-6egP?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAADzROoB8yHFSq1M9dikogoDOG3L-BqpiJs">recent Linkedin post</a> after an event with Monzo, Experian and DeepMind, Sarah Gold from Projects by IF posed a simple question:</p><blockquote><em>If an AI flags a payment as potentially fraudulent with 63% confidence, who owns the decision that follows?</em></blockquote><p>That question matters because AI doesn’t just make things faster. It moves judgement around. It changes who decides, when humans step in, and who is accountable when things go wrong.</p><p>In the old model, the system made the decision and the organisation owned the rule. In the new model, the system generates a probability and hands it back to a human or another process. The ambiguity doesn’t disappear. It relocates, and that relocation is structural.</p><p>Take fraud prevention. Blocking a legitimate payment causes frustration and erodes trust. Allowing a fraudulent one causes financial loss and reputational damage. The work isn’t simply ‘processing transactions’, it is managing risk across millions of interactions.</p><p>Or take something like driver licensing in the context of medical conditions. On paper, it looks like a processing service: review the application, issue or refuse the licence. In reality, it balances the public safety risk of allowing someone unfit to drive against the personal and economic consequences of wrongly restricting someone’s independence. The system is constantly negotiating uncertainty.</p><p>Deterministic systems didn’t eliminate risk. They obscured it. By turning judgement into rules, organisations could tell themselves the problem had been processed rather than negotiated. The outcome looked objective, even though someone, somewhere, had already decided how much uncertainty was acceptable.</p><p>When AI enters the picture, that disguise falls away.</p><p>A model may suggest that a payment looks suspicious. It may classify a medical disclosure as higher risk. But it does not decide what level of false positives is tolerable. It does not determine how much inconvenience is acceptable in the name of safety. It does not set the organisation’s appetite for error.</p><p>Those are organisational choices.</p><p>“Computer says maybe” is what happens when probability replaces policy as the first response. The system no longer closes the question. It opens it.</p><p>That shifts what a job actually involves.</p><p>In a deterministic environment, being good at a job meant applying the rule consistently and escalating when necessary. In a probabilistic one, it’s about weighing the model’s suggestion against the organisation’s tolerance for error and deciding whether to follow it or override it. And then being able to explain why.</p><p>There’s something slightly ironic about this.</p><p>For years, we designed systems and services that treated humans a bit like machines. We stripped away discretion in the name of consistency. We encoded policy so tightly that the person on the frontline became an extension of the rulebook. Customer service often became the place where poorly designed processes ended up; absorbing frustration and enforcing decisions that had already been made elsewhere.</p><p>Now, as machines start to behave more like humans , making contextual assessments and generating recommendations rather than fixed answers, the human role should change again.</p><p>If the machine can model patterns and probabilities, the human can focus on judgement, explanation and trust. Customer service doesn’t have to be the bin for failure demand. It can become the voice of the organisation, the place where values are interpreted, where trade-offs are made visible, where risk is handled with context rather than hidden behind policy.</p><p>That only happens, though, if organisations are willing to design for it.</p><p>And here’s the problem Sarah points to: most organisations haven’t redesigned for that shift. The AI can score risk but it cannot decide who carries it.</p><p>“Computer says maybe” sounds softer than “computer says no.”</p><p>In reality, it is harder. Because it removes the comfort of certainty without removing the need for accountability, and that is the real work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4fe98ff6cb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sloppery Slope of AI]]></title>
            <link>https://medium.com/@tomwm/the-sloppery-slope-of-ai-d9ad5a4a65ea?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9ad5a4a65ea</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Mon, 29 Sep 2025 08:26:19 GMT</pubDate>
            <atom:updated>2025-09-29T08:58:23.706Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>We keep telling ourselves AI is making life easier. But what if it’s just making it emptier?</em></blockquote><h3>The great flattening</h3><p>Generative AI promises speed. What once took 10 steps now takes a single prompt. A journey becomes</p><p>…a jump.</p><p>But in all this collapsing of complexity, something is lost: texture. The pauses. The progressions. The little moments that made services feel considered, human, alive. We’re in danger of building things that are:<br>Helpful but hollow. Immediate but not intimate.</p><p>Flattened by speed. Stripped of ceremony. Delivered with “perfect” efficiency and zero resonance. Think of the Apple product box. The way it opens, the way it resists. That tiny friction says <em>this matters.</em></p><p>Or think of Miyazaki’s reaction to AI “slop.” When fans generated images in a Ghibli style, Miyazaki called it “an insult to life itself.” <a href="https://www.rollingstone.com/culture/culture-news/miyazaki-chatgpt-ai-slop-1235305906/">Rolling Stone</a> reported his objection and it underscores how much of what makes art and design meaningful is the layered conversation, craft, iteration, and collaboration. The long, collective journey behind the final image. Skip all that, and the result feels flat.</p><p>This is where the slope gets slippery. The more we normalise instant answers, the less we value the slow, textured processes that make experiences meaningful.</p><p>AI, in its rush to remove friction, risks removing meaning too.</p><h3>Liminal space needs limits</h3><p>The best experiences have edges. A film has credits. A painting has a frame. A journey has a beginning and end.</p><p>AI doesn’t like edges. It jumps. It blurs. Input in, output out, floating in a kind of ambient utility.</p><p>As John Maeda puts it, design has shifted <em>“from obstacle course to teleportation.”</em> <a href="https://johnmaeda.medium.com/autodesigners-on-autopilot-88c5b07609b9">Autodesigners on Autopilot</a></p><p>But teleportation removes the experience of movement; the friction, the reflection, the detours that matter.</p><p>Framelessness isn’t freedom. It’s disorientation.</p><p>And here’s the rub: design isn’t just about the end point anyway. It’s about the conversation that gets you there. The back-and-forth between a team as they make choices. The dialogue between a service and its users. The shared sense of <em>where are we heading? </em>That conversation is a frame too. It gives shape, context, direction.</p><p>AI often strips that out by arriving before you’ve even decided where you’re going. The jump replaces the journey and erases the dialogue that made the journey meaningful in the first place.</p><p>If we want AI-mediated experiences to mean something, we have to design for structure, thresholds and narrative arcs, even in micro-interactions. Memory and reflection that give a sense of place and progression. Without those, even the most intelligent service becomes unplaceable.</p><p>A void with a voice.</p><h3>Fake touch, real ick</h3><p>Worse than losing feeling is faking it. Too many AI services lean into “human-like” chatty tones, cartoon avatars, synthetic empathy.</p><p>But a wet handshake is worse than no handshake at all. I don’t want AI that <em>feels</em> more human. I want AI that feels more useful. More legible. More honest.</p><p>That’s the real opportunity: not to imitate us, but to support us. To give AI shape and texture so it feels trustworthy without pretending to be our friend. And to remember that the conversation is part of the work. Between teams in the room. Between services and their users. Between audiences and the things they love.</p><p>If AI skips straight to the answer, it robs us of that dialogue. And that’s the slope we should fear most: a slide into hollow efficiency, where nothing has edges, pauses, or meaning left.</p><p>However, if we design with care, with edges, with pauses, with space for conversation, then AI doesn’t have to flatten.</p><p>It can deepen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9ad5a4a65ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Purpose of Principles]]></title>
            <link>https://medium.com/@tomwm/the-purpose-of-principles-81413f742657?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/81413f742657</guid>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Fri, 08 Apr 2016 11:24:12 GMT</pubDate>
            <atom:updated>2016-05-12T12:08:05.401Z</atom:updated>
            <content:encoded><![CDATA[<h4>From strategy to guidelines.</h4><p>I’ve not been around all the blocks but I’ve certainly strolled up and down long enough to have seen my fill of strategies, tactics, guidelines, principles, ‘guiding principles’(!!), approaches and rules etc.</p><p>These words, amongst others, are used in various contexts to mean different things to different people and organisations. However, they really amount to one thing; our human need to make sense of the abstract world of concepts and ideas.</p><p>Principles are, for the most part, created with the best of intentions, often to refine a goal and provide the means of focus to achieve that goal. All very good stuff. Unfortunately, due to their conceptual nature, they are often poorly articulated and inaccurately contextualised; left open to misinterpretation or simply ignored due to their inefficacy.</p><p>In short, most people don’t really understand the purpose of principles. So I’d like to share a point on view on the purpose of principles within a design context. I’m first going to define what i think principles are useful for, then show how principles work structurally i.e. within broader strategy and tactical implementation.</p><h4>A few ground rules:</h4><p>Firstly, what I’m providing here is a point of view born out of experience, which I must credit in part to my time working with <a href="http://enginegroup.co.uk/">Engine</a>, and is by no means a perfect definition.</p><p>Secondly, when I use the word ‘design’, I mean it in the broadest sense which, to my mind, is best summed up by <a href="https://en.wikipedia.org/wiki/Herbert_A._Simon">Herbert Simon</a>:</p><blockquote>“Everyone designs who devises courses of action aimed at changing existing situations into preferred ones.”</blockquote><p>That being said, I assume the readership has at least some experience with the world of User Experience (UX), Customer Experience (CX), innovation, business design, service design, etc.</p><p>I’ve already suggested that the purpose of a principle is to define a goal and provide a focus to achieve that goal. In fact, at a high enough level, a goal is often expressed in principle terms. One of my favourites is by Spacex, the space exploration company started by Elon Musk of Paypal and, most recently, Tesla fame.</p><blockquote>“SpaceX designs, manufactures and launches advanced rockets and spacecraft…enabling people to live on other planets.”</blockquote><p>This defines what the company does and qualifies why they are doing that. A principle then is a statement that clarifies, and is clarified by, other statements. Simples. Sort of. In practice, the craft of creating principles (and it is most definitely a craft) is far more nuanced. There are a number of ways principles can be crafted and used.</p><h4>7 principles for creating principles</h4><ol><li><strong>Inspire and motivate</strong> — used generatively to elicit a response from a particular audience who are often internal stakeholders.</li><li><strong>Challenge assumptions</strong> — with the current state of play. Tools to examine and probe what already exists.</li><li><strong>Spot opportunities</strong> — in the current landscape arising from unmet and unarticulated needs.</li><li><strong>Stimulate ideas</strong> — building into opportunity areas.</li><li><strong>Provide focus and structure</strong> — to develop ideas appropriately.</li><li><strong>Evaluate and validate</strong> — to make a decision and make sure it’s right.</li><li><strong>Guide and direct </strong>— to stay on a chosen path as part of a broader strategy.</li></ol><p>Really well crafted principles should be effective across all 7 areas, although its likely that they will be created with a narrower focus in mind. For instance, an organisation may have a clear high level strategy and a steady operating model but lack the tools to innovate. In this instance they might create principles that inspire and enable them to spot opportunities and stimulate ideas. Essentially using principles as a tool to ask well framed ‘how might we?’ questions.</p><p>To explore how principles can be used at different levels lets take a semi-fictitious example of bank seeking to invigorate their mobile offer. Here we have 4 levels at which principles could be created with a couple of examples at each level.</p><p><strong>Strategy — </strong><em>Why</em> are we doing it<strong><br></strong><em>Examples:</em></p><ul><li>lead and innovate through mobile</li><li>support personal banking</li></ul><p><strong>Product/service principles — </strong><em>What</em> is it<br><em>Examples:</em></p><ul><li>focused on the basics</li><li>one app, many widgets</li></ul><p><strong>Design principles — </strong><em>How</em> do we make it<br><em>Examples:</em></p><ul><li>simplify obsessively</li><li>be recognisably brand x in all interactions</li></ul><p><strong>Design guidelines — </strong><em>How </em>will customers use/experience it<br><em>Examples:</em></p><ul><li>scrolling not click through or carousels</li><li>reflect colour pallet</li></ul><p>There is a clear hierarchy here — where ‘design guidelines’ reflect the higher order ‘design principles’ which in turn reflect ‘product/service principles’ and so on. Drawing out the connection between strategy and implementation is often the most valuable outcome of creating principles.</p><p>However, within the same order of principle there should be little or no hierarchy. Principles should conceptually interlock with each other to form a coherent whole that connects to the strategy or higher order principles above.</p><p>Creating a coherent whole does not mean that all principles bleed into one another. Apparent contradictions or differences between principles is perfectly normal and sometimes beneficial. For example, there might be a principle around being ‘swift’ as well as one around being ‘measured’ which, on face value, could be seen as contradictory.</p><p>It is often this contradiction or polarity that helps define the overall shape and tone of a strategy, service, product, etc. Much in the same way, a square has opposing corners but they all work together to define the very essence of squareness.</p><p>I should note that this strata and ordering of principles is not appropriate in all instances. As mentioned previously, there may already be a very clear strategy in place and all that is required is a set of design principles to help research and design teams to align better.</p><p>In all instances though the success of putting principles into practice relies on three main things:</p><p>- Exposing principles within an organisation while they remain in flux to sense check and iterate as well as help them become common parlance.</p><p>- Spending time getting the language right so that they both resonate and provide clarity for the intended audience.</p><p>- Testing principles by applying them to something more concrete e.g. running an ideation session with them to generate ideas for new product development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81413f742657" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seeing sense and serving civic society]]></title>
            <link>https://medium.com/@tomwm/sense-and-serving-civic-society-178d648a51bf?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/178d648a51bf</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Wed, 21 Oct 2015 21:37:57 GMT</pubDate>
            <atom:updated>2016-04-04T15:16:49.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLSFb2n-e8PG4c6N9BXGXQ.jpeg" /></figure><p>*disclaimer: deliberately grandiose title born out of a love of exuberant alliteration .</p><p>There are many wonderful things about the civil service. Not least the notion that there are a bunch of people living their lives in servitude of civic ideals.</p><p>There are also many highly frustrating things about the civil service. Not least the notion that 50% of what the civil seem to do is ask the other 50% what they are up to. (don’t quote me, it was a friend of a friend of a colleague who shan’t be named)</p><p>Leading on from that, some have postulated that you could cut the civil service by half and things would be ‘better’ and more ‘efficient’.</p><p>Im not sure that is entirely fair but one thing that has struck me recently is how myopic the view is of those inside the civil service walls. The ones who have dedicated the majority of their working lives, often for all the right reasons; passionate about civic service, making things better etc.</p><p>I have noticed that, for some, there is not the weight of responsibility with regard to being a direct cost to the tax payer. And i think this is less than ideal for them, for the work they do and of course for the tax payer.</p><p>Of course, it’s not their fault at all. For them to see sense (note: forced reference to opaque title) they need the right leadership, governance structures and, increasingly, the right tools to know if, when, where, how (and by how much) they are adding value.</p><p>By way of example I was recently at a cross government session on the future of analytics. One keynote was from a government team working with behavioural insights (otherwise known as ‘the nudge unit’). Much of their work is about analysing where value can be added in a service, introducing small changes and making users take ‘preferred’ actions, the better to release said value.</p><p>As part of the Q&amp;A an astute question was asked by <a href="https://twitter.com/eliotfineberg">a colleague</a> along the lines of:</p><blockquote>What is the cost of the work you do to unlock the value?</blockquote><p>And their response:</p><blockquote>Well, most of the work we do is done by an in house team. We don’t outsource very much.</blockquote><p>Granted, this is a very minor example. But it points to a truism within the civil service that ‘internal costs’ are generally not on the forefront of most civil servants minds. Outsourced people or tech are seen to be the more significant costs. Of course there are reasonable reasons for this and it is not too dissimilar from the commercial sector except of course for the source of funding.</p><p>My hypothesis is that the public would be best served by civil servants who have a good sense of what value they, and the work they do, brings to society. My proposal is that we should create tools, and utilise those that already exist, to make the evidence of value vs cost visible to individuals on a daily basis.</p><p>This is much easier said than done of course — I just said it and it’s still not done. Working out how much ‘bang you get for your buck’ is hard becuase you need to define what the bang is. It’s easy when the bang is a ‘thing’, like a call centre, or some software or a Mars bar. They map easily to bucks. It’s really hard when it’s more ephemeral like confidence or unlocking of potential.</p><p>However, I belive that even these more ephemeral qualities can be assigned a meaningful value. One suggestion is to take the same approach that a digital product team might do when estimating the backlog of work. For those that don’t know, a common approach is to size up items or tasks according to their complexity to develop/complete. This might be 1 to 9 point scale or a small/medium/large. It doesn’t really matter. What does matter is that the team does it consistently and regularly so that over time a reliable taxonomy is formed that presents relative value. Then, given a certain burn rate (the rate at which a team works through a backlog) more accurate delivery timescales can be made.</p><p>The net result being that a team, and individual members of a team knows quite explicitly what value they are adding every day.</p><p>Knowing what value you add can only be a good thing. Lets do it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178d648a51bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tales of tools]]></title>
            <link>https://medium.com/@tomwm/recently-i-was-at-hyper-island-in-manchester-an-independent-and-unique-academic-environment-de5089222e66?source=rss-714f6bcad32f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de5089222e66</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Tom Wynne-Morgan]]></dc:creator>
            <pubDate>Mon, 05 Oct 2015 13:54:33 GMT</pubDate>
            <atom:updated>2015-11-09T10:44:43.754Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I was at Hyper Island in Manchester; an independent and unique academic environment hailing from Sweden I believe. I was invited to give a little talk to the MA students there as I was in the area for a few days.</p><p>One of the students asked a question that I have been asked in various guises over the years:</p><blockquote>As a service designer what tools do you use most often or see as most valuable?</blockquote><p>Side note: while running a workshop at Microsoft, in Seatle, a few years ago I was asked by someone what tool I used to make the graphic drawings (Cartoons to you and I. You know, the type you get as part of customer journey maps or personas). “Oh, mostly Adobe Indesign” I answered. “No”, the chap retorted, “what do you use to make the drawings? ”. And then, with the most straight and unpatronising face I could muster I uttered “with a hand and a pencil”.</p><p>Back to Manchester. The idea of ‘tools’ has been around as long as design has a been part of our common parlance, and in particular business parlance. Elements of the design industry itself has used it as a metaphor to increase understanding (and sales). Im thinking of ‘method decks’ the idea of ‘tool boxes’ containing various design ethnography techniques or ‘kits of parts’ etc. The business world has models, design has ‘tools’. Same thing in practice.</p><p>So I’ve had to deal with the question of ‘tools’ for a while. When it comes from those outside the hallowed design community it’s often proxy for “how do I do what you do. . . Easily?” when it comes from those already on the inside it’s normally about a genuine desire to improve their craft. Both are reasonable.</p><p>Whilst I think ongoing discussion around the craft of designing — be it services, products, policy or anything else — is useful, the place I’ve arrived at over the last few years, and the answer I gave to the student is very simple. The tools I use most and are most useful are:</p><ul><li>Maintaining a vision</li><li>Being patient</li></ul><p>Maintaining a vision is much more easily said than done. Being patient helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de5089222e66" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>