<?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 Ben Cullimore on Medium]]></title>
        <description><![CDATA[Stories by Ben Cullimore on Medium]]></description>
        <link>https://medium.com/@ben_cullimore?source=rss-1e49117d8cdc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Up4peuiTypBxlqEZ.</url>
            <title>Stories by Ben Cullimore on Medium</title>
            <link>https://medium.com/@ben_cullimore?source=rss-1e49117d8cdc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:18:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ben_cullimore/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[How I Helped Set the Vision for a Re-Platforming Project]]></title>
            <link>https://medium.com/@ben_cullimore/how-i-helped-set-the-vision-for-a-re-platforming-project-32e743120ec5?source=rss-1e49117d8cdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/32e743120ec5</guid>
            <category><![CDATA[digital-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[strategic-design]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Ben Cullimore]]></dc:creator>
            <pubDate>Fri, 18 Oct 2024 13:58:35 GMT</pubDate>
            <atom:updated>2024-10-21T08:31:22.762Z</atom:updated>
            <content:encoded><![CDATA[<h3>Beyond re-platforming: how service design helped create a vision for strategic transformation</h3><h4>When you’re tasked with re-platforming a legacy product, there’s always more to it than just upgrading technology.</h4><p>I recently worked as a service designer on a project to move a 20-year-old product from a third-party platform to an in-house solution. In this post, I’ll share how I helped establish a clear vision and align it with strategic goals, despite the challenges of managing diverse stakeholder perspectives. This experience highlighted the importance of having a strong product vision.</p><p>Due to the sensitive nature of government work, I’ve omitted specific details, but I hope the approach I describe will still be useful.</p><h3>The challenge: more than just re-platforming</h3><p>We were responsible for more than just shifting the product to a new platform. The product had to be improved for accessibility, usability, consistency with other products in our ecosystem AND we were tasked with ensuring the product supported new ways of working, informed by extensive academic and behavioural research as well as aligning with the organisation’s evolving strategy.</p><figure><img alt="A drawing of a van with ‘digital moving van’ written on the side" src="https://cdn-images-1.medium.com/max/1024/1*LZxrw3AeQ4SWnJqYOP68IQ@2x.jpeg" /></figure><p>Whilst re-platforming the product was relatively straightforward, the real challenge was implementing these new ways of working and strategic goals. We had multiple stakeholders each owning different parts of the process, with their own interpretation of what the strategy looked like in practice and no unified definition of how our product could deliver that. The team needed clarity — a vision for how the product could support new processes and fulfil strategic goals.</p><figure><img alt="A drawing of a treasure map, with a ? to the left and a X on the right. In between are lots of messy lines." src="https://cdn-images-1.medium.com/max/1024/1*yvSkAP_T4-bcyIzwCAfIfQ@2x.jpeg" /></figure><h3>Defining the vision: a series of workshops</h3><p>I helped define the product vision through a series of workshops. Unfortunately, since stakeholders were spread across the UK with busy schedules, it was impossible to get everyone in the same room. We opted for a mix of remote and in-person sessions, each building on the last; testing ideas captured in previous sessions with each new set of stakeholders to maintain continuity, culminating in a final playback session to ensure consensus.</p><h3>Prepping for the sessions</h3><p>Before the workshops, we:</p><ul><li>Identified (and invited) stakeholders</li><li>Reviewed multiple policy documents, strategy presentations, business cases, and academic white papers — extracting key insights; theming and defining them.</li><li>Sketched out a diagram that illustrated my understanding of the product and how it supported practice; fundamental things— inputs, outputs, and steps it allowed users to achieve.</li></ul><figure><img alt="A drawing of post it notes and a pen" src="https://cdn-images-1.medium.com/max/909/1*8R6YZzeNDwYOf9SMl46PHQ@2x.jpeg" /></figure><h3>The workshop format</h3><p>Each session followed these three activities:</p><h4><strong>1. Reviewing the strategic themes</strong></h4><p>I presented back the 9 strategic themes we’d extracted from the documents to the group of stakeholders. For each theme I broke it down to cover:</p><ul><li>A problem statement; <em>what does the strategic theme aim to solve, and for who?</em></li><li>The expected outcomes; <em>what would happen if we met the strategic themes goal?</em></li></ul><p>As we debated each theme — discussing the problems it aimed to solve and the outcomes everyone expected — I captured live feedback on post-it notes, updating the definitions in real time. Once we reached agreement on our goals, I asked for practical ideas on how a digital product could help achieve those outcomes.</p><figure><img alt="A drawing of post-it notes, labeled; Strategic theme + Problem + Outcome + Idea" src="https://cdn-images-1.medium.com/max/1024/1*wpOZ7gpmpn6nXQdmZGWd8g@2x.jpeg" /></figure><h4><strong>2. Reviewing a theoretical model</strong></h4><p>I then walked the group through a high-level diagram outlining the fundamental workings of the product, focusing on inputs, user actions, and outputs — without getting into specific steps or features. Once again, I iterated and refined the design in real time, based on feedback in the room.</p><figure><img alt="a diagram of a theoretical concept — with inputs, outputs and ‘things’" src="https://cdn-images-1.medium.com/max/1024/1*htHkcONHW5yMfnHU4ExUKQ@2x.jpeg" /></figure><h4><strong>3. Aligning strategic themes to process</strong></h4><p>Once we had this common understanding of <em>the thing</em>, I drew up a table which had strategic definitions agree in the first activity in the left hand column and the basic process steps along the top. I then asked participants to add ideas ideas for how the product could support their strategic goals from the first activity and align them to the steps.</p><p>We spent time writing up post-it notes and aligning them to the strategic theme and step. We then grouped and ask stakeholders to present back their ideas.</p><figure><img alt="A drawing of a grid, with post-it notes. Labeled ‘idea board’" src="https://cdn-images-1.medium.com/max/1011/1*nHiQJOAhnCZh50ssb8LQyw@2x.jpeg" /></figure><h3>Overcoming challenges and reaching a consensus</h3><h4>Starting with a Visual Concept</h4><p>Starting with a visualised concept was crucial. Even if your initial idea is completely off, having something concrete to start discussions is invaluable. Stakeholders will quickly point out what doesn’t work, allowing you to refine it collaboratively.</p><figure><img alt="A nonsensical drawing of a weird shape labeled ‘this is the thing’." src="https://cdn-images-1.medium.com/max/943/1*PrV6TzIvaMG0wzKyLvYt6A@2x.jpeg" /></figure><h4>Aligning understanding</h4><p>Despite the product being in use for nearly 20 years, it became clear that not everyone had the same understanding of how it actually worked. This lack of shared clarity was a major barrier. Aligning strategic goals with the product required a common understanding of its purpose. Having a visual model I could reference and amend during sessions was key to getting everyone on the same page. Without a unified vision of how the product operated, how could we agree on how it should deliver the strategy?</p><h4>Navigating theoretical thinking</h4><p>Our stakeholders, primarily policy and practice leads, often thought in abstract and theoretical terms. This tendency can result in high-level debates, making it challenging to secure quick buy-in. As a designer, the ability to simplify and visualize a concept, present it clearly, gather feedback, and rapidly iterate in real-time is critical to bridging the gap between different perspectives. This approach accelerates collective understanding, paving the way for faster decision-making.</p><h4>Reaching consensus</h4><p>Walking stakeholders through our definitions and theoretical model generated plenty of debate. Each group brought its own unique perspectives, but having them challenge one another in an open forum was productive. It helped us reach consensus and, importantly, allowed stakeholders to gain a deeper understanding of different viewpoints.</p><h4>Facilitating with diplomacy</h4><p>As the facilitator, I had to lean heavily on my diplomatic skills to keep discussions focused. Ultimately, we managed to reach agreement on all key areas and even uncovered a new theme we hadn’t initially considered.</p><h4>Ideation with stakeholders: a pleasant surprise</h4><p>I was initially concerned about the ideation phase, fearing it would lead to a flood of wild and impractical ideas. However, by framing the session around their strategic goals, the ideas generated were much more sensible. Surprisingly, the stakeholders aligned on most suggestions. Asking the group to present their ideas helped filter out those that hadn’t been fully thought through, as many participants realised on their own that some concepts weren’t as viable as they had initially seemed.</p><h4>Addressing unrealistic expectations early</h4><p>This activity also addressed a common issue: stakeholders often hold onto certain ideas, and if those aren’t addressed, the final product may never meet their expectations. By surfacing and refining these ideas early on, we managed to prevent unrealistic expectations from lingering.</p><h3>Refining the vision and moving forward</h3><p>Following the workshops, I led my team through an analysis of the ideas we had gathered. We grouped duplicates and separated ideas that didn’t relate to the digital tool itself — stakeholders sometimes described practice; user actions instead of product features.</p><p>With a clear understanding of the stakeholder vision, I created a storyboard illustrating a “future day in the life of a user,” showcasing how the product would work; incorporating the ideas from our sessions. Applying the vision in a real-world context made it more tangible for stakeholders, allowing them to envision themselves using the product — especially since many had been users themselves. This perspective helped stress-test the vision, and they were quick to discard ideas that wouldn’t make practical sense in actual use.</p><figure><img alt="A drawing of a story board, illustrating a day in someones life. From left to right you’ve got a mug, a telephone, someone typing and someone walking. Beneath, post-it notes" src="https://cdn-images-1.medium.com/max/866/1*O5seSOAhvrm6hoVPqLE2NQ@2x.jpeg" /></figure><p>The storyboard became a valuable tool for validating the vision with stakeholders, ensuring it aligned with their strategy while remaining feasible.</p><p>With stakeholders aligned on the vision, the team used it to prioritise high-value, high-risk assumptions, which we systematically addressed through ideation, hypothesis development, prototyping, and user testing. The insights gained from testing allowed us to either validate the vision or identify areas needing improvement. We regularly played back these insights to the stakeholders, and as we had earned their trust by involving them early in the vision-setting process, they were open to iterating the vision based on the user feedback.</p><h3>Final thoughts: setting a vision in complex projects</h3><p>Setting a vision in large, complex projects isn’t about rigidly defining every detail — it’s about aligning stakeholders, providing direction, and ensuring your team has a north star to guide them.</p><p>The process I followed wasn’t perfect, but it allowed us to navigate multiple perspectives and deliver a vision that was both aligned with strategic goals and flexible enough to evolve based on user feedback.</p><figure><img alt="A sketch of the connect four board game. Withe 4 yellow discs aligned vertically." src="https://cdn-images-1.medium.com/max/883/1*sKV8eOgDqbOOxYnA6KzExw@2x.jpeg" /></figure><p>When working with stakeholders across various locations and perspectives, it’s crucial to structure the conversation, simplify and visualise concepts, present them clearly, and create space for challenges. Grounding the discussion in strategic goals helps keep it focused. With the right balance of preparation, visualisation, facilitation, and iteration, you can develop a vision that inspires confidence and drives the project forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32e743120ec5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Interaction to Service Design: My Journey and Tips for Those Considering the move]]></title>
            <link>https://medium.com/@ben_cullimore/from-interaction-to-service-design-my-journey-and-tips-for-those-considering-the-move-ae1fb441d5f5?source=rss-1e49117d8cdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae1fb441d5f5</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[service-design-tips]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ben Cullimore]]></dc:creator>
            <pubDate>Thu, 10 Oct 2024 16:30:13 GMT</pubDate>
            <atom:updated>2024-10-10T17:36:21.306Z</atom:updated>
            <content:encoded><![CDATA[<h4>Service design can seem like a mysterious discipline to those working in adjacent fields like UX or product design, but making the switch is more seamless than you might think.</h4><p>Having moved from interaction design to service design myself, I want to demystify the process and share how my journey unfolded, along with tips that might help if you’re considering making a similar move.</p><figure><img alt="A drawing of two different hats, one labeled interaction, the other service." src="https://cdn-images-1.medium.com/max/867/1*phyO-aKsJ2LGKfEXtVaxMg@2x.jpeg" /></figure><h3>Why I made the switch</h3><p>Like many interaction designers, I occasionally felt frustrated by not being involved in all aspects of the projects I worked on. There’s that classic refrain: “You don’t need to be in this meeting, go get your crayons out.” I’m naturally curious and always want to understand the bigger picture. I wanted to be part of the broader conversations that shaped the direction of the entire service, not just the digital interactions.</p><figure><img alt="A drawing of a crayola crayon." src="https://cdn-images-1.medium.com/max/702/1*ElO9id0H-Q5qP6MsTYqW4g@2x.jpeg" /></figure><p>I started exploring service design techniques on the side — things I’d read about, like service blueprints and journey mapping — and applied them to the product I was working on. Luckily, my product manager found these useful and that opened the door to experimenting with more service design approaches, such as problem-exploration workshops.</p><p>By the time a service design opportunity came up, I had enough case studies to put together a portfolio and make the official switch.</p><h3>The similarities (and differences) between interaction and service design</h3><p>Interaction and service design share a lot of common ground. In both roles, you start by trying to understand a problem and needs, then use your skills to sketch out how you think it should work, test your ideas with users (or stakeholders), take insight on board, and repeat the cycle. The major difference is scope.</p><p>In interaction design, you’re typically focused on the flow of a single product or feature. Service design zooms out to look at the wider ecosystem of interactions, which often includes multiple products, online and offline touch points, policies, practices, and technology.</p><p>Deliverables in service design tend to be bigger-picture — maps or diagrams that show how various elements interact with each other. I see blueprints as prototypes, which you test with stakeholders to ensure alignment with strategy and user needs.</p><p>The key shift is thinking beyond a single user journey and considering how various parts of a service fit together across multiple touch points. Because the scope is so broad, you often need to test ideas in workshops with a larger group of stakeholders.</p><figure><img alt="A drawing of a service design blueprint and a screen design." src="https://cdn-images-1.medium.com/max/873/1*knW9wqTcNEob9Jik6Ugbiw@2x.jpeg" /></figure><h3>Tips for switching to Service Design</h3><p>If you’re currently an interaction designer and thinking about transitioning to service design, here are some practical tips that worked for me:</p><h4>1. Shadow service designers; attend meetings and workshops</h4><p>Attend service design sessions to observe how ideas are shared and feedback is gathered. If possible, offer to help facilitate. Service designers are usually happy for an extra pair of hands!</p><figure><img alt="A drawing of a pair of binoculars." src="https://cdn-images-1.medium.com/max/387/1*doohpb-COcLFiGL8ET35PQ@2x.jpeg" /></figure><h4>2. Do some side work</h4><p>Create diagrams that explain how your screen flows fit into the bigger picture. The more you understand the wider context, the more you’ll be able to apply service design thinking to your work.</p><h4>3. Practice presenting your ideas</h4><figure><img alt="A drawing of a screen labeled presentation and a stick, labled ‘pointing stick’." src="https://cdn-images-1.medium.com/max/1024/1*_omiMUp-Rz39pVyr2jmO0g@2x.jpeg" /></figure><p>Whether it’s to stakeholders or colleagues, get used to presenting your work regularly. This helps you become more comfortable articulating your ideas and allows you to receive valuable feedback.</p><h4>4. Build a portfolio of case studies</h4><p>Like with any design discipline, having a few case studies to showcase your service design thinking will be invaluable when you apply for roles. Start collecting examples of how you’ve contributed to shaping services, not just digital products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*9GoCorGmSE0OrdsBH_JFSw@2x.jpeg" /></figure><h3>Resources that might help</h3><p>Here are a few links that I might be useful with starting as a service designer:</p><ul><li>[<a href="https://designnotes.blog.gov.uk/2022/08/25/a-day-in-the-life-of-a-service-designer-at-gds/">A day in the life of a service designer at GDS</a>] — A great look at the work of a service designer in the UK government.</li><li>[<a href="https://good.services/home">Good Services by Lou Downe</a>] — This book defines what makes a good service and provides useful techniques for service design.</li><li>[<a href="https://medium.com/full-stack-service-design/how-to-use-full-stack-service-design-model-da3fdd52ad70">Full Stack Service Design by Sarah Drummond</a>] — A series of blog posts that break down the components of a service.</li><li>[<a href="https://www.nngroup.com/articles/service-blueprints-definition/">NNgroups Service Blueprints: Definition</a>] — A pretty clear definition of service blueprints with examples.</li><li>[<a href="https://www.ideou.com/pages/design-thinking-resources">IDEO’s Design Thinking Resources</a>] — IDEO’s ideas and techniques for designing better services.</li></ul><p>Moving from interaction design to service design doesn’t have to be a daunting leap — it’s more of a shift in perspective. By taking small steps to widen your view and embracing opportunities to get involved in service design work, you can make the switch. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae1fb441d5f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>