<?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 Veron WK Lai on Medium]]></title>
        <description><![CDATA[Stories by Veron WK Lai on Medium]]></description>
        <link>https://medium.com/@norev517?source=rss-4cbbd453d346------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-cBOz2cJQpMgY-H143qtAQ.png</url>
            <title>Stories by Veron WK Lai on Medium</title>
            <link>https://medium.com/@norev517?source=rss-4cbbd453d346------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:48:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@norev517/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[The many shapes of service design: In Conversation with Justin Kim, Service Design Lead at…]]></title>
            <link>https://norev517.medium.com/the-many-shapes-of-service-design-in-conversation-with-justin-kim-service-design-lead-at-6c5933f21cbf?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c5933f21cbf</guid>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:35:13 GMT</pubDate>
            <atom:updated>2026-11-16T14:35:13.309Z</atom:updated>
            <content:encoded><![CDATA[<h3>The many shapes of service design: In Conversation with Justin Kim, Service Design Lead at University of the Arts London</h3><p>Justin Kim and I met at Engine in 2017. At the time, very few agencies in the world specialised in service design. Justin has now worked in service design for about fifteen years, across a boutique consultancy, an in-house role at <a href="https://www.sainsburys.co.uk/">Sainsbury’s</a>, the <a href="https://www.bcg.com/about/overview?utm_source=search&amp;utm_medium=cpc&amp;utm_campaign=brand&amp;utm_description=paid&amp;utm_topic=none&amp;utm_geo=lon&amp;utm_content=brand_search_other-parameter&amp;gclsrc=aw.ds&amp;gad_source=1&amp;gad_campaignid=23891865547&amp;gbraid=0AAAAACKyBhpkB6s-T740pXqlpFN-ycXBZ&amp;gclid=Cj0KCQiAnsvXBhCqARIsAHKgGNYnO5QzQQqs9EwuZ8ZwKdM3Bo2YVaUIoV2aE222kWLnLTbiyvucg68aAsLGEALw_wcB">Boston Consulting Group (BCG)</a>, and now the <a href="https://www.arts.ac.uk/">University of the Arts London</a> (UAL).</p><p>I invited him to the third <em>In Conversation</em> event at London College of Communication because of a question I hear from students every year. When you study service design, you all learn a very similar process and way of thinking. Then you go into industry, ask three service designers what they do, and get three different answers. Why does the job look so different from one place to the next? Is it the industry, the organisation, or something else? That question ran through our whole conversation.</p><h3>From product designer to service designer</h3><p>Justin studied <a href="https://www.arts.ac.uk/subjects/3d-design-and-product-design/undergraduate/ba-hons-product-and-industrial-design-csm">product design at Central Saint Martins </a>and worked as a product designer for a few years. Around 2009 or 2010 he started to ask himself, “Is that it? Is my creativity being used in this way forever?” That question took him to an MA at Goldsmiths, where he learnt about service design, and then to Engine around 2011, when the term was still not widely recognised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LLYrqgfozB3MzhYuv7V3Hw.jpeg" /><figcaption>Justin Kim, Service Design Lead at University of the Arts London, talking about his 15 years in service design.</figcaption></figure><p>He stayed there for seven and a half years. Because it was a boutique agency, he worked with a wide range of clients, from car makers and airports to retail and utility companies, across the UK, Europe, the US and East Asia. He found that something quite common in one part of the world can have a big impact when you bring it somewhere else.</p><p>He then moved in-house to Sainsbury’s to look after a consistent experience across digital and in-store channels. Covid arrived soon after, bringing a wave of digital transformation. Next came BCG, where he spent three and a half years, mostly building AI products for UK government and for private clients such as an aviation company. When I asked why he went back to consulting after working in-house, he said he had noticed that clients respected the big consultancies more, and he wanted to understand why. He also felt he was missing one skill: numbers. He was confident delivering customer-centred solutions and influencing the right people, but not with numbers, and that is what firms like BCG are known for. After a few years of long hours, he wanted a better balance for his family. UAL’s vision of becoming a more student-centred organisation caught his attention, and he joined seven months ago.</p><h3>Service design is about changing the story</h3><p>I asked Justin how he would define service design after 15 years of practising it in different places, on projects of all sizes. He said there is no right or wrong definition, but he holds one core principle that he learnt early on: service design is about changing the story of the organisation you work for.</p><p>He referred to <a href="https://www.ynharari.com/book/sapiens/">Yuval Noah Harari’s <em>Sapiens</em>,</a> which argues that what makes humans different from other animals is our ability to believe in the same story. Every organisation believes a story about itself: this is what we deliver to our customers, and this is the value we add. That story may be wrong, or there may be room to improve it. The role of a service designer is to come in as a storyteller, help people see that the story holding the organisation together isn’t working as well as they think, and bring user-centred stories in to change the narrative.</p><h3>How the focus shifts as you grow</h3><p>The role of a service designer doesn’t only change from one organisation to another. It also changes with your level of experience. I asked Justin what he focused on in his first few years. He said it was two things: what are the key problems, and how do I deliver the right solution? He tried different methods and tried to be as creative and user-centred as possible. His questions were about the work itself. Am I using the right tool? Is this journey map backed up by the right data? Is the solution good?</p><p>As he became more senior, his focus changed. A good solution is now a given. What matters is who needs to own it, who he needs to influence, what they care about, and how to turn a good piece of service design into something that actually gets implemented. “It’s a lot more of people skills.” We come back to what he means by people skills later in this post.</p><h3>What has changed for designers starting out today</h3><p>I asked whether expectations for junior and mid-level designers have changed since he started. Justin said they have, for two reasons.</p><p>The first is maturity. 10 to 15years ago, most organisations didn’t have a clear idea of what service design was, so a lot of the work was about introducing and educating. Now they do have expectations, but he isn’t sure that is a good thing. They have seen deliverables elsewhere, personas for example, and assume they know what those mean, while someone else in the same room understands them quite differently.</p><p>The second is AI, and he gave both a pessimistic and an optimistic view. The pessimistic one: when he was a junior designer, the typical time to produce a journey map, including the research was about two weeks. Today he expects his junior team members to take a lot less time and reach similar quality, because the assumption is that AI tools speed things up. That means more pressure and shorter timelines. The optimistic one: if you become good with these tools, you can do much more than a junior would normally be expected to. To illustrate a future experience, you can now make short AI videos that help people imagine something better. Ten years ago, that meant hiring a video team, or an illustrator who could draw about six scenes a day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4AhOWzM_qa-SCpcUN9rB9g.jpeg" /><figcaption>Justin and I at the third In Conversation event, talking about why service design looks so different from one organisation to the next.</figcaption></figure><p>I also wanted to add an international view, because many of my students are international students; they might come from countries where service design is still quite new. What we in the UK saw between 2010 and 2015 at large corporates may be what you see where you come from in 2025 or 2027. Back then, consultancies spent a lot of time selling the value of the process, and many clients were testing their appetite for service design rather than committing to implement it. In the UK today, very few clients will pay for a year-long programme just to see what happens. When they bring in service design, they expect implementation.</p><p>Justin agreed, and shared something he noticed early in his career. Many consultancies put their effort into small pieces of work first and built trust over time. A big project rarely arrives on reputation alone. It usually starts with a small one. Once that is proven and stakeholders feel comfortable, it leads to a slightly bigger project, then another, and eventually the big one. He sees the same pattern in-house. At UAL, he and his team are earning trust with stakeholders step by step. Propose something too big too early and people become defensive. How much service design an organisation is ready for depends on its context, its timing and where it is in the world.</p><h3>Consultancy or in-house?</h3><p>Students early in their careers often ask me whether they should go into consultancy or in-house, and what the difference is. So I asked Justin what surprised him about each.</p><p>Consultancy suits you if you want variety and might get bored working on one project for more than six months. It also gives you a special power: in the first month, you can play dumb. You can ask very obvious questions, and that is powerful because it helps the organisation rethink its own story. “Why are we actually not doing this?”</p><p>The downside is that your work becomes your baby, and once you deliver it, you lose sight of it or watch it get spoiled. On one project with a large tech company, Justin’s team created a strategy and implementation plan the client was excited about. The client then decided to hold on to it until a competitor moved first. In the client’s own words, the work became “ammunition” rather than something to implement. After all that research, and the confidence that it would work, that was painful.</p><p>Justin said In-house gives you ownership, and your colleagues see you as an equal peer rather than an outsider. When Justin started in-house, he was shocked by the level of data he could now access, compared with what he could see as a consultant working with the same organisation. If service design is storytelling, data and insight are the key ingredients of the story. People also start to see how you can help with their goals, and you build long-term relationships.</p><p>The downside of in-house is that it can be slower, with more bureaucracy and established frameworks you have to challenge, gently. He described service design as “a very nosy job”. You look at the end-to-end experience, talk to lots of people and dig into the front and back end. If people aren’t used to that, they will ask why you are asking questions about their job. Politics exists everywhere, agencies included, but in-house politics tends to be more complex, and you have to learn to navigate it.</p><p>Choosing between agency and in-house isn’t a final decision. What you learn in an agency can serve you very well in-house, and sometimes it is the opposite: habits that worked in one place need unlearning in the other. Justin’s own career has moved between both. If you can, grow your experience by working in different kinds of places. Each one teaches you something the other can’t.</p><h3>The artefact is a small part of the actual work</h3><p>I have this conversation often with students, especially those working on their dissertations. Learning how to use a tool is one thing. Knowing when to use it, and when to choose not to, is another. The artefact is only a small part of the work and effort in a design process. Most of it is the conversations, the politics, understanding the dynamics, influence and storytelling. When you are learning, it is easy to see the artefact as the whole thing.</p><p>Justin shared how he sees design tools being used in the real world, with journey maps as his example. They all carry the same name, but they serve very different purposes. The level of detail depends on your audience. For the operational teams at one of his previous clients, he made one of the most detailed maps he has ever made: evidence from store visits, different paths showing user needs and pain points, and benchmarks of what other brands were doing. He said he doesn’t like things that detailed, but that audience needed every detail, and they wanted to see what competitors were doing. At UAL, for a very senior audience, he made a simple end-to-end view of the student journey that highlights only the key pain points.</p><p>On another project, the brief was to improve how the operations team handled a new service, and the audience was both the leadership team and operations. He needed something visual and quick to understand, but backed up by data. The leadership team only needed the key problems along the journey. The data team, the delivery teams and operations each needed to see their part represented. So he brought them in and asked colleagues from those teams to present parts of it themselves.</p><p>Future journeys can take many forms: an illustrated story, a step-by-step scenario, or a foresight scenario that lets stakeholders interact with a future customer. Justin also showed a quick AI prototype of a better experience for UAL applicants, though he was clear it isn’t being implemented. In each example, he uses the artefact to start a conversation and bring the important questions about priorities to the table.</p><h3>What a good outcome looks like</h3><p>I asked Justin when an artefact has backfired and when it has made a difference. A bad outcome, he said, is something beautiful that nobody owns. “If your audience doesn’t feel like it’s their work, then you fail.” A good outcome doesn’t have to look beautiful. It can be a boring Excel spreadsheet, as long as the stakeholders feel it is theirs and want to talk about it.</p><p>He said one of his most successful projects, with the biggest impact, was the operations project he mentioned earlier. The data team and the delivery teams were not happy at first, because they felt they were already doing that work. Instead of competing with them, he made sure each team was represented so nothing was duplicated, and kept repeating that it was not his work or his team’s work: “It’s our work.” When it came to presenting, colleagues from data, delivery and operations talked it through. It became their work, they were proud of it, and it worked. He sees a lot of beautiful artefacts made with AI in the name of service design these days, often with little real content behind them.</p><h3>From good to great</h3><p>The last part of our conversation was the one many students were waiting for, especially those starting job searches: what separates good service designers from great ones?</p><p>From working with great service designers throughout his career, he sees three traits.</p><p><strong>They notice what is easily overlooked.</strong> On a home interview, a good service designer captures what they hear. A great one also captures the context. That is how you find the real need behind what people tell you. The same applies to stakeholders: look beyond what they ask for and understand their motivation.</p><p><strong>They are imaginative.</strong> They bring ideas from other industries or other parts of the world and mix them. The solution still has to be realistic, but it pushes the boundaries.</p><p><strong>They enable other people.</strong> “It’s not about me, it’s not about service.” Justin tells his team to go into workshops with ideas in their back pocket, and when a stakeholder is about to say something, help put the words in their mouth so the idea becomes theirs. He sees service designers as architects behind the scenes: they see the whole thing and plan it, but the people on stage need to feel they own it.</p><p>On mentoring, he tries to stay curious and learn from team members with less experience but different approaches. He is also aware of his own biases: “Your bias is your expertise, but your bias is the blocker of trying new things.”</p><h3>People skills sit underneath everything</h3><p>Earlier, Justin described how his focus moved towards people as he became more senior. He called people skills the most difficult part of the job, and something he is still learning. Part of it is storytelling: like any good storyteller, know what your audience needs, how they want to hear it and which medium works best. The other part is understanding the dynamics. If you work with a general manager, who influences their decisions? What are their personal goals, such as a promotion? This is harder in-house, because you become part of the system yourself.</p><p>You earn trust by understanding what people need from you, providing it, and starting small. Once you have earned it, things become much easier. He said he isn’t asking all designers to become a politician. But if you promise an outcome, you need to understand the broader picture to get there.</p><h3>Five quick questions</h3><p>I like to end each In Conversation with a few quick questions, so I gave Justin five!</p><p><strong>What service design is not?</strong> A magic wand. People will come with all kinds of expectations, and some will think service design can solve everything. It can solve many things, but only with the right time, resources and money. Manage expectations from the very beginning.</p><p><strong>What is the most overrated artefact?</strong> A future journey map without implementation. Everyone is excited after the workshop, then goes away and nothing happens.</p><p><strong>What is the most underrated skill?</strong> Listening to a sensible colleague who disagrees with you. As he becomes more senior, he is more aware that he can be a little stubborn.</p><p><strong>Most organisations think service design is… but actually it is…</strong> Most organisations think service design is done only by service designers. In reality, it is done by everyone from the very beginning. Otherwise there is no service design.</p><p><strong>What is the biggest lesson you have learnt?</strong> Whatever is agreed in a successful workshop won’t necessarily be implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kp7fm6a0kLXm0cF3WIGYhw.jpeg" /><figcaption>Years after we worked together, and still talking service design.</figcaption></figure><h3>What Justin would like you to take away</h3><p>Service design is about changing the story an organisation believes about itself. The artefact is only a small part of that. Choose your tools and level of detail for your audience. Earn trust with small steps. Make sure the work belongs to the people who need to carry it forward. And if you can, learn from working in different kinds of places.</p><p>Thank you so much, Justin, for your time, for sharing work from across your career, and for speaking so openly about the realities of consultancy and in-house life. It was lovely to sit down with you again after all these years.</p><p><em>This post is written from the recording of In Conversation, a series of events where I sit down with leaders to talk about design. If you would like to take part, or know someone you would like to nominate, please get in touch.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c5933f21cbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring Social Value: In Conversation with Mo Gutale, Head of Business Insights at GLL]]></title>
            <link>https://norev517.medium.com/measuring-social-value-in-conversation-with-mo-gutale-head-of-business-insights-at-gll-bd7f834cbc62?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd7f834cbc62</guid>
            <category><![CDATA[impact-measurement]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[social-value]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:27:15 GMT</pubDate>
            <atom:updated>2026-11-16T14:27:15.772Z</atom:updated>
            <content:encoded><![CDATA[<p>Earlier in October, I sat down with Mo Gutale, Head of Business Insights at <a href="https://www.gll.org/">Greenwich Leisure Limited (GLL)</a>, the UK’s largest staff-owned social enterprise that runs Better leisure centres and libraries across the UK. Mo and I first met a couple of months before, and ended up talking for hours about social value and impact. What I found from our conversation is that design and data don’t actually hold opposite views on impact at all. There is a lot of nuance in where they differ and where they share common ground. As service designers, we are used to capturing how people feel: “I feel better”, “I feel more connected”. But what does that look like as a number? And when does a story count as evidence? Our conversation changed how I think about data, so I invited Mo to the <em>In Conversation</em> event I hosted at <a href="https://www.arts.ac.uk/subjects/business-and-management-and-science/postgraduate/ma-service-design-lcc">London College of Communication, University of the Arts London</a>. I hoped it would open up new ways for designers to look at data and design.</p><h3>From the leisure centre floor to head office</h3><p>Mo has been with GLL for more than 15 years and has worked across the UK, including a year in Falmouth, Cornwall. Before moving into data, he was a national projects manager looking after innovation. He told us that many leisure centres still share the same 1970s layout: two squash courts, a sports hall, two studios and a gym. The business relied on about 30% of the floor space while the rest sat quiet, so his team trialled things like virtual reality and gamification to see whether a squash court could become a multi-use space. Virtual group cycling came out of that kind of thinking.</p><p>He now leads the data team at head office. Over four or five years, he led the move to a modern cloud infrastructure, so the whole organisation now works from one unified set of data. His job title is Head of Business Insights rather than Head of Data, and he said that is deliberate. More on that later.</p><h3>What social value actually means</h3><p>Social value is a big subject with a long history in economics, and there are many definitions. When I asked Mo how he would define it, he said it is the positive difference an organisation makes to people and places, environmentally, economically and socially. “Fundamentally, it boils down to one word, and that’s wellbeing.” In other words, how satisfied people feel with their lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*sD7mRhVTi3UFg_68ERaKww.png" /><figcaption>The ROAMEF cycle: rationale, objectives, appraisal, monitoring, evaluation and feedback. Source: HM Treasury, The Green Book (2026), Figure 1. © Crown copyright 2026.</figcaption></figure><p>He walked us through why this matters so much in public services, through the lens of GLL. <a href="https://www.legislation.gov.uk/ukpga/2012/3">The Social Value Act 2012</a> means public bodies buying services have to consider social value, not just cost. GLL bids for contracts to run leisure centres for local authorities, so demonstrating social value is a core part of every bid. <a href="https://www.gov.uk/government/publications/the-green-book--2">HM Treasury’s Green Book</a> then introduced the <a href="https://www.happierlivesinstitute.org/the-wellby/">WELLBY</a>, a way of turning wellbeing into money. You ask people a simple question, how satisfied are you with your life, before an intervention and again after it. One point up on that scale, for one person over a year, is valued at £13,000 in 2019 prices, within a range of £10,000 to £16,000. With inflation, the figure is higher today. The Procurement Act 2023, in force since February 2025, then changed the wording from the “most economically advantageous tender” to the “most advantageous tender”. Dropping “economically” gives more room to weigh social value, and authorities must also have regard to a national policy statement that includes it.</p><h3>Borrow a framework before you build one</h3><p>Design and procurement often work in the opposite order. As designers, we start with research: we spend time in the community and understand the problem first, then co-create what to deliver. A public tender asks you to commit to what you will deliver first, before you have the contract or the chance to explore the problem. So I asked Mo how designers can find a middle ground between design and delivery, and how to use a framework when you don’t have all the evidence yet.</p><p>Mo was honest that social value can be messy and hard to navigate. He compared it to accounting, where everyone knows what a P&amp;L or a balance sheet is. Social value has no common standard, so every industry builds its own framework. GLL created its own <a href="https://www.healthclubmanagement.co.uk/health-club-management-press-releases/new-research-finds-leisure-services-in-enfield-deliver-14-million-in-social-value-GLL/363946">Social Value Calculator</a> for sport about 15 years ago, covering things like physical activity, crime and educational attainment. While the Social Value Calculator works well for GLL, Mo was also honest that he isn’t suggesting everyone build their own. A framework you create yourself may not be trusted by funders, so it can be less helpful than you might think.</p><p>His advice is to borrow before you build. Look at what already exists, from organisations like <a href="https://www.stateoflife.org/">State of Life </a>to databases that list outcomes with proxy values attached. If your project reduces a building’s energy use, someone has already worked out the value of each unit of carbon saved. Use it, rather than inventing your own method. Years of research sit behind those figures, and they help you explain value in a language others already recognise. Then think through your project as a chain: what are you trying to influence, which framework can you refer to, and what will you measure?</p><h3>What’s easy to measure, and what matters</h3><p>If data matters so much in procurement, I expected GLL to have a big data team. Mo told us it is fewer than ten people, which surprised me for an organisation of that size that relies so heavily on winning contracts. So I asked him what his team actually focuses on gathering and measuring. Do they go for what is easy to capture, or what matters?</p><p>“What’s easy is what pays the bills.” He said his team works mostly on the leisure centre side of the business. An organisation like GLL has systems full of transactions, visits and income, and those numbers are the facts you have to work with. Even then, you can’t look at everything. GLL focuses on around ten key measures: more people through the door, more income, happier employees, and so on.</p><p>The hard part is what those numbers mean to people. “Two identical people swimming in the same pool, two lanes next to each other, have different feelings.” One is recovering from a health problem. The other is keeping up a daily routine. You only learn that by going out and asking, and that takes time and effort. In Mo’s view, the organisations that do well spend more of their time on this harder part.</p><p>The harder part Mo describes is what researchers and service designers do every day. I agree with Mo that the organisations able to show both evidence and impact are the ones that have invested in building capability in both quantitative and qualitative data. In service design, we are proud of having a strong and rigorous process for gathering qualitative data. GLL has built and invested in its strength on the quantitative side, while recognising the value of going out and asking people, the harder part. For designers, that is a useful reminder: the stories we gather are one half of the picture, and the numbers are the other. Learning to work with both, and with the people who hold each, is where the value is.</p><h3>Starting from nothing</h3><p>Investing in both may seem like the obvious answer, but in today’s economy not every organisation has the money to do that. Many of our students and alumni work in charities and small organisations with no data team, no Salesforce and no dashboards. So I asked Mo: if you had to start from scratch, especially coming from a more qualitative background, what is the minimum?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*_10Mr9DgvlWGzSHThAhMFg.jpeg" /><figcaption>Mo and I taking questions from the audience at In Conversation.</figcaption></figure><p>His answer was to start with a question. Without a clear question, you end up swimming in data. From there, be clear about the problem you want to solve and the intervention you will put in place. Take a baseline measure before, and a follow-up measure after. The change between the two is what you are trying to show, and it can be as simple as a survey. “When it comes to measurement, the simplest is really the easiest.”</p><p>I then asked whether the same approach applies at his organisation at this scale. He said pretty much: the principle is the same at GLL’s scale, just with more layers. Leadership sets an aspiration, which becomes the KPIs. His team then translates those down to the source systems that hold the data, and to the thousands of people in different roles who need it. Even then, he kept stressing that you need to keep it simple. A general manager at a leisure centre should know the 10 things they need to pay attention to, not 55. Two of those are how many people come through the door and how much income comes into the till.</p><h3>Are stories evidence?</h3><p>After so much talk about data, I turned to the question I had been waiting to ask. As designers, we collect a lot of stories. From his point of view, when does a positive experience or a story count as evidence?</p><p>Mo doesn’t see subjective data as weaker than objective data. That surprised me as the Head of Business Insights who has built his team around quantitative data. “Somebody’s cholesterol level is not more important or more factual than how they feel about themselves.” You need both. But one story is one signal. Think about how many signals you need, and look for numbers that strengthen what people tell you.</p><p>His example was <a href="https://www.better.org.uk/what-we-offer/activities/healthwise">GLL’s Healthwise programme</a>, where GPs and other health professionals refer people to the gym. At any time there are around 20,000 people on it, on subsidised prices for a 12 week programme, often for diabetes or heart conditions. He could show that around 70% graduate, with follow-ups at 6 and 12 months. But it is stronger when he also shows the case studies: where people started, how they feel, and what they can do now. “For every data point, there is a story behind it.”</p><h3>Building a data culture</h3><p>After data and impact, I moved the conversation on to data at scale, and to Mo’s own journey over the last five years, building GLL’s data team from the ground up.</p><p>I was interested in this because, while data and design might seem like very different disciplines, they have a lot in common in how they sit within an organisation. Both are the new kids on the block. An organisation might be over a hundred years old and have had a data department for less than 10 years. The same is true for many design teams, especially in the public sector. So how do you bring a new way of working into an established organisation?</p><p>Mo said people expect him to answer with technology, but looking back over the last five years, it has very little to do with tech. Technology helps, because a survey that once took months can now go out by text and come back the same day. But his focus has been on adoption, and what he wants people to get from data is insight and action. When someone looks at a report, what do they take away, and what do they do next?</p><p>GLL runs over 240 leisure centres and 120 libraries across the UK, and his small team serves all of them. Before Covid, with the old infrastructure, the same work would have needed a team of more than 50 people. The infrastructure does the heavy lifting now, which leaves his team free to design what people see with intention. Instead of more than 20 different measures, a manager gets a short narrative: this is going well, keep doing it; this isn’t, do less of it. Managers used to spend hours pulling member counts out of a CRM. The most common feedback now is relief at not having to do that, so they can spend their time on customers.</p><p>“Data is just a fact. It doesn’t tell you anything.” When organisations say they are data driven, he thinks what they should mean is that they take educated insight from data. That is why, he said, GLL deliberately named his role and his team after insights, not data.</p><p>I think this applies just as much to design teams in the public sector, who often face the same challenge as a newer discipline inside an established organisation. Mo’s lesson is that the tools matter less than adoption. A journey map or a blueprint won’t change much on its own. What changes things is making the work easy for colleagues to use, and clear about what they should do next. Like data, design earns its place when it turns into insight people across the organisation can act on.</p><h3>Data for the future, not just looking back</h3><p>A lot of conversations about data are about reporting: looking back at what has already happened. For Mo, that isn’t where the biggest impact lies. The real value is in using that history to see what is coming. He gave us an example. Gym membership follows a cycle. People join in January, drop off around April, come back a little in summer, and spike again in September. What you gain in September you tend to lose by November. GLL has no minimum contract beyond a month, so the pattern is clear: wherever membership sits in August is roughly where you will start the next January.</p><p>Knowing the normal cycle means you can spot when behaviour changes. Because people pay by direct debit, a weaker January shows up in income for the rest of the year. So his team warns the business early, puts a number on the risk, and joins the conversation about what to do, such as putting marketing effort where there has been growth rather than where people aren’t coming in. “We don’t make decisions. We present the facts.”</p><h3>Four quick-fire questions</h3><p>This is the second event in my In Conversation series, and I like to end each one with a few quick-fire questions. The aim is to leave the audience with something to think about, rather than ask the speaker to explain or elaborate. So I closed with four.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52Rezc0vITkrpN58OKQcOw.jpeg" /><figcaption>Mo answers my quick-fire questions to close the conversation.</figcaption></figure><p><strong>What should organisations stop measuring?</strong> Things that don’t matter, Mo said. Fewer measures usually give you a clearer direction. People love flashy dashboards with hundreds of numbers, but they drown the message. He also half-remembered a saying, better known as Goodhart’s law: when a measure becomes a target, it stops being a good measure. His example: a KPI of a million visits doesn’t by itself mean you have made anything better.</p><p><strong>What should organisations measure more?</strong> Follow-up. Once a financial period closes, everyone moves on. The same happens with projects. What was the long-term impact? You will be surprised what you learn when you go back.</p><p><strong>One piece of advice for demonstrating social value?</strong> Get your chain right: inputs, activities, outputs, outcomes, impact. The most common mistake he sees is mixing up outcome and impact. If someone tells him they created a million pounds of social value, his questions are: what changed, what outcome did you achieve, and do you have stories to go with it?</p><p><strong>Can everything that matters be measured?</strong> “No.” The more you try, the more you get lost in detail. Start simple.</p><h3>What Mo would like you to take away</h3><p>Start with a question. Borrow a framework before you build your own. Take a baseline, and always follow up. Pair your numbers with stories, and your stories with numbers. Measure fewer things, and turn them into insight people can act on.</p><p>Thank you so much, Mo, for your time, for making data feel approachable to a room of designers, and for staying to answer so many questions.</p><p><em>This post is written from the recording of In Conversation, a series of events where I sit down with leaders to talk about design. If you would like to take part, or know someone you would like to nominate, please get in touch.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd7f834cbc62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Listening to Staff Voice in Higher Education: Inside Making Connections]]></title>
            <link>https://norev517.medium.com/listening-to-staff-voice-in-higher-education-inside-making-connections-ae31c9e4809a?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae31c9e4809a</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[higher-education]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Thu, 15 Jan 2026 09:43:27 GMT</pubDate>
            <atom:updated>2026-01-15T09:49:26.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpyWoCqBUM6-SKlpdHO6kw.png" /></figure><p>Earlier this year, we spent nine months on a project that started with a simple question: how does staff voice actually travel through a university? Not what’s on paper, but how it really feels. Where does it get stuck? What happens to it once someone speaks up?</p><p>The project was called Making Connections. It ran from January to September 2025, and brought together colleagues from the <a href="https://servicefutures.co.uk/">Service Futures Lab </a>and the Social Purpose Lab at UAL. We were asked to look at how informal staff voice connects, or doesn’t connect, to decision-making and governance, especially around equity, inclusion and sustainability.</p><p>What followed was not neat. It was messy, relational, and sometimes uncomfortable. It reminded us that listening takes care and requires structure.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIkOpJD82vbI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIkOpJD82vbI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIkOpJD82vbI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6899da26777bf29c7fadcbca804c4c9c/href">https://medium.com/media/6899da26777bf29c7fadcbca804c4c9c/href</a></iframe><h3>Starting with trust, not solutions</h3><p>From the beginning, we made a deliberate choice: this would be collaborative research, not consultancy. That might sound like a small difference, but it changed everything.</p><p>We didn’t arrive with a ready-made solution or some “best practice” model to roll out. We came as embedded researchers, staff looking at our own institution, alongside colleagues whose daily working lives are shaped by the very systems we were examining, and this mattered.</p><p>Staff voice is tangled up with power, risk and vulnerability. Many people have spoken up before and felt ignored. So before we could ask anyone to share their experiences, we had to create conditions where honesty felt possible.</p><p>That meant going through proper ethics approval, being clear about how we’d use the data. It meant keeping people’s own words, not smoothing them out. And it meant working in the open, sharing what we were finding as we went, rather than disappearing for nine months and coming back with a polished answer.</p><h3>Being in the room mattered</h3><p>A big part of this project happened face-to-face. We as a team really can’t overstate how much that mattered.</p><p>We spent time physically moving across campuses, listening to staff talk through their experiences of committees, networks, forums and informal workarounds. These weren’t formal interviews; they were conversations.</p><p>In our co-design workshops, we brought together people who don’t usually sit in the same room: academic staff, professional services colleagues, technical staff, network members, managers and leaders. We sent out email invitations weeks before, but sign-ups were low. So we did something simpler. We walked around campus, floor by floor, department by department, knocking on doors and inviting people to join us on the day. We had conversations with them, answered their questions about the purpose and intended outcomes. And the number of people who turned up was significant. In a way, that was already making connections.</p><p>Throughout the research and co-design, we mapped systems together. We surfaced frustrations. We asked people to visualise where their voice actually goes once it leaves their mouth, or their inbox.</p><p>What became clear very quickly was this: <strong>staff voice isn’t missing. People care deeply. They speak up in all sorts of ways, through networks, grassroots initiatives, informal conversations, and unpaid labour that often happens on the edges of already overloaded roles.</strong></p><p>The problem wasn’t a lack of participation. It was fragmentation.</p><h3>Voice exists, but pathways don’t</h3><p>Across workshops, interviews and mapping exercises, the same questions kept coming up:</p><ul><li>Where does this go?</li><li>Who’s responsible for responding?</li><li>Is this being heard, or just recorded?</li></ul><p>Staff described a landscape of committees, forums, champions and consultations that felt hard to navigate, and even harder to understand. Remits were often unclear. Feedback loops were weak or invisible. Decisions seemed to happen “somewhere else,” with no transparency about how input had shaped outcomes.</p><p>Over time, this created fatigue.</p><p>People told us they were tired of repeating the same points in different spaces. Tired of giving time they didn’t really have. Tired of not knowing whether their participation made any difference. This is where the word <em>tokenism</em> came up, not as an accusation, but as a feeling. Effort and impact didn’t seem aligned.</p><h3>Method as care</h3><p>You will see in our report that our methodology combined service design, co-design and research-through-design. That included desk research, literature reviews, survey analysis, governance mapping, interviews, workshops and iterative prototyping.</p><p>In reality, it also involved a lot of care.</p><p>We created multiple ways to contribute, in person, asynchronously, anonymously, because not everyone feels safe speaking in the same spaces. We acknowledged contributions publicly where people wanted recognition, and protected anonymity where they didn’t.</p><p>As a team, we stayed aware of our own positionality. We’ve all experienced precarious contracts at different points. We sit at different places in the hierarchy. We’re insiders, which gave us access and trust, but also meant we had to keep questioning our own assumptions and blind spots.</p><h3>What kept surfacing</h3><p>Across all phases, five tensions came up again and again:</p><ol><li><strong>Unclear remits:</strong> people didn’t know what different forums or committees were actually able to do</li><li><strong>Weak feedback loops:</strong> contributions often disappeared into silence</li><li><strong>Limited transparency:</strong> decision-making pathways weren’t visible or easy to follow</li><li><strong>Lack of time and resources:</strong> social purpose work was often unpaid, squeezed in around everything else</li><li><strong>Under-supported local action:</strong> energy was there, but structures didn’t always enable it</li></ol><p>None of this was about individual failure. These were systemic conditions shaping behaviour and processes.</p><h3>From insights to prototypes</h3><p>Rather than jumping straight from findings to recommendations, we worked through co-design and prototyping. Over time, this led to twelve concepts. These concepts might not seem like big transformations or feel particularly innovative. But they are practical interventions designed to make staff voice more visible, valued and actionable.</p><p>Some focused on clarifying governance and accountability. Others explored how meetings could become more meaningful, or how consultation could be done with greater care. Several addressed recognition, not as a reward culture, but as acknowledgment of labour that already exists.</p><p>We tested these concepts with staff and discussed them with senior leaders. Four proposals were prioritised for further development. What mattered most to us wasn’t which ideas “won.” It was that staff could see their experiences reflected back in something tangible.</p><h3>A starting point, not a finish line</h3><p>Making Connections doesn’t offer a neat solution. What it offers instead is a reframing: staff voice as an ongoing relationship, not a mechanism to optimise. A reminder that listening needs infrastructure, not just good intentions. And trust takes time and consistency to rebuild.</p><p>For us, this project reinforced in higher education and in organisational work that participation is not free. It draws on emotional, cognitive and temporal resources, often from those already carrying the most.</p><p>If staff voice is going to matter, it has to be met with clarity, reciprocity and follow-through. Otherwise, opting out becomes an obvious and rational choice.</p><p>If you’d like to find out more about the project, <a href="https://servicefutures.co.uk/2025/01/07/making-connections/">please go to our website to download the full report</a> to explore the research, methods, insights and proposals in detail.</p><p>We’ll also be presenting this research at the <a href="https://www.advance-he.ac.uk/programmes-events/conferences/equality-diversity-and-inclusion-conference">Advance HE Equality, Diversity and Inclusion Conference in Manchester on 25–26 March</a>. This year’s theme is “Embedding EDI in Higher Education: Tradition Retold, Borrowed Insights, and Bold Innovations,” If you’re there, do come and say hello. We’d love to continue the conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae31c9e4809a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Happened When We Brought Drama Therapy into MA Service Design]]></title>
            <link>https://norev517.medium.com/what-happened-when-we-brought-drama-therapy-into-ma-service-design-2fb8788086a8?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fb8788086a8</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[drama-therapy]]></category>
            <category><![CDATA[design-education]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 16:30:29 GMT</pubDate>
            <atom:updated>2025-12-15T16:30:29.762Z</atom:updated>
            <content:encoded><![CDATA[<p>This year at <a href="https://www.arts.ac.uk/subjects/business-and-management-and-science/postgraduate/ma-service-design-lcc">MA Service Design at UAL</a>, we brought drama therapy into the course, with a drama therapist leading two three-hour sessions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1146610755%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1146610755&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2096112328-093cdd8fa746668128d3a86493b58a35b6c7c556c49e72d4518a6b92d735b8ec-d_1280%3Fregion%3Dus&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/73828316a78f7a80eeb5d4bfbab61365/href">https://medium.com/media/73828316a78f7a80eeb5d4bfbab61365/href</a></iframe><h3>Act One: An Unexpected Introduction</h3><p>I’ve been teaching MA Service Design at UAL for several years now. In my Ways of Working unit, we already explored collaboration, reading group dynamics, and working with uncertainty. But I’ve been curious about whether approaching these things differently, through a completely different discipline, might offer students new perspectives.</p><p>Last summer, I met Alex, a drama therapist. To be honest, I knew nothing about drama therapy before I met him, so I had no expectations, just curiosity about a role I’d never encountered.</p><p>As Alex described his work, I kept having these small moments of recognition. “Oh,” I kept thinking, “that’s exactly what happens in a co-design workshop.” The more we talked, the more I noticed the similarity between our disciplines. Drama therapy works with embodiment, the idea that our bodies hold knowledge our minds haven’t processed yet. It creates safe spaces to practice being uncomfortable. It uses role-play to develop genuine curiosity about different perspectives.</p><p>All of this felt like it could add something different to what I already explore in class. So I applied for funding to bring Alex in. To my surprise and slight nervousness, we got it.</p><h3>Setting the Stage</h3><p>Two sessions. Three hours each. Thirty MA Service Design students who had no idea what they were walking into.</p><p>I wasn’t in the room. Alex and I had discussed how the presence of your teacher changes how you show up, so I stepped back. Before the sessions, I briefed Alex over coffee at a café in Brockley, on a sunny autumn afternoon. We’d planned for two hours, but the conversation stretched longer, followed by many audio notes exchanged over the next few days. Alex didn’t just come to deliver sessions; he took time to really understand the role of service designers, the challenges they face in academic and industry settings, and the dynamics at play.</p><p>What impressed me was how well Alex articulated the connections after just those few hours at our chat at Brockley. He put it so clearly: “The similarity between service design and actually acting is going into new environments where no one knows you, where you have to prove yourself, and potentially antagonistic environments.” I’m grateful for that depth of understanding.</p><p>After the first session, I interviewed students on camera to capture their immediate reflections. What they shared was remarkable.</p><h3>Discoveries in Motion</h3><p>One student described how the exercises worked: “What was very interesting is that it kind of enabled us to wear different kinds of hats in terms of emotions, in terms of qualities or characteristics of a person. I think that’s something that’s always going to be helpful, especially in a field like service design.”</p><p>The embodied nature of the work surprised several students. One shared: “I was surprised by myself at how far I could act. I really embodied the feeling. I felt it and it was quite prominent through my facial expressions, body language. I pushed myself. I got out of my comfort zone, and that was really nice.”</p><p>What I found particularly interesting was how the exercises revealed patterns students hadn’t noticed before. One reflected: “I realised that some dynamics, functional, dysfunctional, those are very situational. So I learned today to ask why more, why are you reacting, and I uncovered underlying layers, and that helped me understand a little bit more.”</p><h3>Playing the Same Role Differently</h3><p>While we do explore these themes in my unit, including collaboration, reading emotion, noticing what’s unsaid, and working through discomfort, what Alex brought was a completely different methodology for engaging with these ideas.</p><p>Where I might lead a discussion or reflection exercise, he had students physically mirror each other’s movements. Where we might analyse stakeholder dynamics, he had students literally arrange themselves in space to represent a play, with everyone becoming different parts of the system, showing through their positions who was at the centre and who was at the margins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOOSCHfLIG-8OhF-4sj58A.png" /></figure><p>Students talked about going outside their comfort zones but feeling safe doing it. Alex created what I’d consider as “safe enough space”, which is not perfectly safe, but safe enough to take risks. When something felt too vulnerable, there was permission to pause, to say “not yet.”</p><p>I like how the session framed the unfamiliar as play, as “let’s see what happens” rather than as a test you might fail.</p><h3>Reading Between the Lines</h3><p>Students kept mentioning exercises where they were assigned emotions and asked to exaggerate them. The impact was profound, particularly for students who found emotional expression challenging.</p><p>One student shared: “I always keep the emotion and feeling by myself. I won’t share it to others, so it’s really difficult for me to show my feelings and emotions, but through this process I think it’s really good to show more information about myself or my feeling to my teammates to build our bond between each other.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ooXhXgUTmeeDXZ5TNYBXIQ.png" /></figure><p>This resonated deeply. In service design, we’re constantly interpreting what people tell us, but words are just one layer. The drama work gave students permission to trust their intuition, not to make assumptions, but to get curious about mismatches between what’s said and what’s felt. To develop the skill of pausing and thinking: “Something feels off here, let me ask more questions.”</p><p>This feels particularly important for students from different cultural backgrounds, and we have a mostly international cohort. Communication norms vary enormously. Drama exercises can’t teach you every cultural context, but they can teach you to notice your own interpretations, to hold them lightly, to get curious about what else might be true.</p><p>One student captured the progression beautifully: “You know, the first time we were asked to describe how we were feeling, it was more quiet and reserved, and I think as the session went along, at one point we were all screaming, so that was, you could see the progression of openness.”</p><h3>After the Curtain Falls</h3><p>A different approach to familiar themes, through embodied practice rather than discussion or a live project, gave students new ways of understanding. The drama sessions didn’t solve everything. Six hours total doesn’t transform someone’s capacity for collaboration or emotional awareness. But it planted something. It showed students that these capacities can be practiced, not just hoped for.</p><p>I’m sharing this because I think we need more conversations in design education about different ways of approaching the relational, emotional, and embodied skills that matter so much in practice.</p><p>What I learned is that sometimes the most valuable teaching happens between disciplines, between head and body, between what we can explain and what we can only experience.</p><p>If you’re curious about how drama therapy can be used and applied in design education or in your design team, feel free to reach out. I’m working on some ideas on how we can bring drama therapy into the design industry, so I’m up for any connection and conversation. Do connect with me on <a href="https://www.linkedin.com/in/veron-wk-lai-3b302a8/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fb8788086a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Find Your Unique Excellence: Why Generic Skills Lists Hold Back Your Design Career]]></title>
            <link>https://norev517.medium.com/find-your-unique-excellence-why-generic-skills-lists-hold-back-your-design-career-8a77e2693b12?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a77e2693b12</guid>
            <category><![CDATA[higher-education]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 13:22:59 GMT</pubDate>
            <atom:updated>2025-09-23T18:34:46.611Z</atom:updated>
            <content:encoded><![CDATA[<h3>Find Your Unique Excellence: Why a Generic Portfolio May Hide Your True Strengths</h3><p><strong><em>Note:</em></strong><em> This blog is adapted from notes taken during the MA Service Design portfolio session. I’m sharing it with students who attended, as well as prospective students who want to understand what we do beyond </em><a href="https://www.arts.ac.uk/subjects/business-and-management-and-science/postgraduate/ma-service-design-lcc"><em>MA teaching here at the London College of Communication, UAL</em></a><em>. This should give you a sense of how we focus on employability alongside academic work.</em></p><p><em>I’ve also written a more comprehensive blog about the </em><a href="https://norev517.medium.com/from-ma-to-industry-your-service-design-portfolio-translation-guide-dbafb61d3066"><em>transition from MA to industry</em></a><em>, from which this session and blog drew content.</em></p><p>Picture this: you’re a hiring manager looking at 50 portfolios in a day. Portfolio after portfolio reads exactly the same: “I conduct user research, facilitate workshops, create journey maps, and build prototypes.”</p><p>By portfolio number 30, they all blur together. The hiring manager can’t distinguish between candidates, so they default to picking whoever has something that stands out — often for reasons that have nothing to do with design ability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpRPnQgY8GsYxEO7_yfUrg.jpeg" /></figure><p>This is the reality of today’s design job market. It’s competitive — there are opportunities, but there are also many very talented designers looking for jobs, plus professionals from other fields transitioning into design. When most designers present themselves using the same templates and formats, it makes it impossible for employers to see what makes them special but also relevant to their business needs.</p><p>Getting reference and templates from other portfolios is what people usually start with, but it shouldn’t be how you finish.</p><h3>The Problem With Looking Like Everyone Else</h3><p>When every designer claims the same skills using the same language, employers find it hard to make decisions. They filter out applications that don’t match their specific task list, but here’s the problem — you might have unique skills that don’t fit their job description but are incredibly relevant to their business needs.</p><p>I’ve been working with students and coaching designers who use templates or copy formats from other portfolios and website guides. These templates limit what they think they should showcase, and worst of all, they fall exactly into these cookie-cutter formats. The result? Portfolios that look identical, even when the designers behind them have completely different strengths.</p><p>Meanwhile, some talented designers get overlooked because they haven’t learned to articulate what makes them different. They have unique approaches, innovative solutions, and distinctive ways of thinking (and working) — but their portfolios read like everyone else’s. And when I spoke with them, they said they take portfolio templates and just fill them up with their work, rather than creating a format that shows their skills and excellence.</p><h3>The Generic Skills Trap</h3><p>Here’s where some people get it wrong. They create portfolios that read like this: “I do workshops. I create journey maps. I prototype. I do user research.”</p><p><strong>So does everyone else in this room.</strong></p><p>The question isn’t whether you can do these things — it’s whether you can do something better than anyone else. What’s your unique excellence? What have you created that no one does quite like you?</p><p>I remember working with a graduate who was getting nowhere with applications. Her portfolio was technically perfect but forgettable. Then we dug into her major project, and I discovered she’d developed a completely novel approach to running co-design sessions with participants going through very challenging times for their health. She’d written detailed guides, tested it multiple times, and had evidence of real impact.</p><p><strong>That was her gold.</strong> Not the fact that she could facilitate workshops — that she could facilitate workshops with the level of care and approach that actually worked when others failed.</p><p>This isn’t about limiting yourself to one narrow skill — it’s about having at least one thing you do exceptionally well that makes employers think, “We need that person.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A3K2r76uP9ZVdvzIYbdNpA.jpeg" /></figure><h3>Discover Your Hidden Gold</h3><p>Right now, think about a project where you created something unique. Maybe it’s a super clever way you synthesized information, a unique technique you developed for storytelling, or what’s particularly interesting is how you used AI strategically and meaningfully in your design process.</p><p>Ask yourself:</p><ul><li>What approach did I develop that others don’t use?</li><li>What problem did I solve in a way that surprised people?</li><li>What technique do colleagues ask me about?</li><li>What part of my process consistently yields better results?</li></ul><p>The key is specificity. Instead of saying “I’m good at stakeholder management,” you might say “I developed a visual stakeholder mapping technique that helped a 50-person project team align on priorities in one session instead of weeks of back-and-forth emails.”</p><h3>Turn Excellence Into Portfolio Gold</h3><p>Here’s what this means for your portfolio: when you’re looking at your case studies, you need to build a story where the climax is your unique excellence and why that excellence matters.</p><p>Maybe you excelled in how you handled co-design — thinking deeply about user needs, not just running workshops. That yielded high-quality outcomes, and you have your own tools to demonstrate that impact. But what does that mean for your project? What was the actual impact? You need to capture this in your story.</p><p>Yes, you’ll still need the basics of the project process, but you’re not using those as your key content. Your unique approaches are — and it could be 2 to 3 things, depending on how you tell the story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCbU5Dmq3b9UlX__xlQeDQ.jpeg" /></figure><p><strong>Instead of this:</strong> “I conducted user research, ran workshops, and created prototypes.”</p><p><strong>Write this:</strong> “My approach to co-design with vulnerable users led to insights that completely changed the service direction — and it was the first time our service partner had live tested their service with this user group.”</p><p>That’s not just process — that’s impact driven by your unique excellence.</p><h3>The Excellence Audit</h3><p>Look at your current portfolio and ask:</p><ul><li>Could any of my classmates have written this exact case study?</li><li>Am I showcasing process or proving impact?</li><li>What would make someone think “I need this person on my team”?</li><li>Where do I demonstrate something no one else can do?</li></ul><p>If you can’t answer these questions clearly, you haven’t found your unique excellence yet. Keep digging.</p><h3>Why This Matters More Than Ever</h3><p>In a market where everyone looks the same, being memorably excellent at something specific is your ticket to standing out.</p><p><strong>The goal isn’t to be perfect at everything. It’s to be memorable to someone who needs exactly what you offer.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ysS0nzMPCmeyGlNuTedn0g.jpeg" /><figcaption>Sep Portfolio Session with 3 cohorts of MA students together</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a77e2693b12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From MA to Industry: Your Service Design Portfolio Translation Guide]]></title>
            <link>https://norev517.medium.com/from-ma-to-industry-your-service-design-portfolio-translation-guide-dbafb61d3066?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbafb61d3066</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 10:53:39 GMT</pubDate>
            <atom:updated>2025-09-19T07:27:12.902Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I want to start with a huge thank you. Over the last six months, so many of you, former MA students now out there in the world, have sat with me (virtually and in coffee shops, restaurants and Mercato Metropolitano!) to share your journeys. You’ve been so open about the messy bits, the wins, the “why did nobody tell me this?” moments. Those conversations? They’re the heart of this blog. Every struggle you shared, every “aha” moment you described, every piece of wisdom you offered — it all shaped what I’m about to share. Thank you for sharing your stories with me.</blockquote><h3>Here’s Where We Are</h3><p>It’s that time of year again. I’m sitting across from <a href="https://www.arts.ac.uk/subjects/business-and-management-and-science/postgraduate/ma-service-design-lcc">MA students</a>, laptops open, portfolios ready, eyes full of questions. Next week marks my 10th year running these career sessions on helping MA students get ready for their job search, and honestly? The questions haven’t changed much, but the world around them has.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmwBbnGny7vjPr_tKawAQw.jpeg" /><figcaption>One of the career sessions back in 2019</figcaption></figure><p>LinkedIn is now filled with helpful portfolio tips and career guidance. Social media has brilliant creators sharing interview strategies and practical advice. There’s so much good content out there from talented experts. So I wondered, do we really need another voice in this conversation?</p><p>But then I realised something. Having lived this double life — teaching at university while working as a Head of Design, and now as a design coach. I’ve been fortunate to see both sides of the transition. The gap between how we teach and how we hire. That perspective might offer something useful.</p><p>Then last week, a student said something that touched my heart: “I feel like I spent a year learning a language nobody in industry speaks.”</p><p>Oh…yes… I remember that feeling so well.</p><p>So let’s talk about something I haven’t seen covered much — not another list of portfolio tips, but the real work of translating between your MA academia and the industry. Because here’s what I’ve learned after a decade of living between worlds: your MA isn’t preparing you wrong. You’re just speaking two different languages, and nobody’s given you the dictionary yet.</p><h3>Living in Two Worlds And Finding the Bridge Between Them</h3><p>For the past ten years, I’ve been fortunate to live this double life — teaching at university while working as a Head of Design, and now continuing that teaching work alongside my role as a design coach. It’s been a privilege to sit on both sides of the table: guiding students through their MA journey and also reviewing portfolios, running interviews, and building teams.</p><p>This double life has taught me something I wish I’d known back when I was doing my own MA in Service Design in 2010: the gap between academia and industry isn’t about one being right and the other wrong. It’s about translation. And what breaks my heart is seeing students trying so hard to hide their academic work, thinking it’s not “industry enough.”</p><p>Let me tell you something I wish someone had told me back in 2010.</p><p>Your academic depth isn’t a weakness to overcome. It’s a strength waiting to be articulated.</p><p>I’ve watched brilliant students struggle to explain their MA projects to hiring panels. I’ve seen the disappointment when they realise their passion for design justice, circular economy, climate change, or speculative futures doesn’t match any job description they can find. Some even feel lost, “Why did I study this if nobody wants it?”</p><p>But here’s what took me years to understand: You don’t need to abandon your academic identity. You’re learning to become bilingual, and that takes time and practice.</p><h3>The Language Gap: Two Worlds, Both Valuable</h3><p>Let me share what I’ve learned from sitting on both sides — marking student work, and also hiring teams and making the case for new roles to leadership.</p><p><strong>In academia</strong>, when I’m marking your work, we celebrate depth. You spent months exploring the philosophical implications of climate change on community design. You grounded your work in the Design Justice framework. You can cite fifteen sources on speculative futures. Your tutor? We’re thrilled. Your external examiner? Impressed.</p><p><strong>Your future employer?</strong> When I’m hiring or trying to justify a new headcount to leadership, they’re looking for something different.</p><p>Not because your work isn’t valuable, it absolutely is. But because they’re listening for different signals. While you’re explaining your theoretical framework, they might be wondering: “Could this person handle our messy stakeholder workshop next Tuesday?”</p><p>I hear this struggle often from students: “The theories and concepts I’m learning don’t match any job description I see.” I really understand where that feeling comes from. I felt it myself back in 2010. But here’s what took me years to realise: your MA isn’t just about preparing you for the job market today. It’s an education that sets your direction for many years to come.</p><p>Some of what you’re learning needs translation for today’s roles — that’s the practical work we’ll do together. But other parts? They’re seeds you’re planting in your mind for your future. You need to understand which is which.</p><p>Remember all that “impractical” academic research you’re doing? Industry eventually catches up. Take AI as an example, everyone’s excited about ChatGPT like it’s brand new. Meanwhile, Alan Turing was asking, “Can machines think?” back in 1950. The first AI workshop? 1956. By the 1980s, over 80% of academic disciplines were already deep in AI research, while industry was just beginning to build its first website.</p><p>Your speculative design project about climate-adaptive cities that feels “too out there”? It won’t take 70 years like Alan Turing’s work did. Look at the circular economy, which started as an academic theory in the early 2010s is now standard practice, with companies like Ellen MacArthur Foundation partnering with major brands. User experience design itself went from academic research in the 1990s to becoming essential for every business by the 2010s. Design justice frameworks you’re studying now? They’re already shaping policies in progressive organisations.</p><p>The seeds you’re planting now often bloom faster than you think.</p><p>Academia runs ahead of industry. That’s where big conversations start, where ideas get explored before they’re ready for the market. So when you’re wondering if your research topic matters — trust me, it does. You’re just early to the conversation.</p><p>The key is thinking strategically about your translation: which parts to communicate when, what’s relevant to whom, and in what context. Not every employer needs to hear about your theoretical framework, but they might need to know you can navigate complexity. Not every role requires speculative thinking, but they all value someone who can see beyond the immediate problem.</p><h3>Finding Your Voice in Both Languages</h3><p>Something I notice often when I am hiring: students spending lots of time explaining their academic research methodology in an interview or in their portfolio, which I understand because that’s key to how I assess your work academically. But when I’m wearing my Head of Design hiring hat, what I really want to understand is: “Tell me about a time something went wrong and how you handled it.”</p><p>This isn’t about simplifying your work. It’s about highlighting different facets of the same diamond.</p><p><strong>Instead of:</strong> “My project was grounded in participatory design theory and explored the methodological frameworks for co-creation with marginalised communities…”</p><p><strong>You might try:</strong> “I worked with a community group who’d been excluded from previous design processes. Here’s how I built trust, created safe spaces for their input, and turned their lived experiences into design decisions…”</p><p>Same project. Different story. Both true.</p><p>Your academic report might run 15,000 words with 50 references. Your portfolio needs to tell that story in 3 minutes. Not because one is better than the other, but because they serve different purposes. Think of it like this — your academic work is the full symphony. Your portfolio is the melody that invites people to hear more.</p><h3>The Impact Question And Why We’re All Measuring Different Things</h3><p>In your MA, excellence looks like theoretical rigour, critical thinking, and pushing boundaries; these all reflect your MA learning objectives and assessment criteria for all the work you do. But when you’re job hunting, everyone asks about “impact.” And I see students worry, “But I didn’t increase any conversion rates! I didn’t save anyone money!”</p><p>Let’s reframe this together.</p><p>You’re not going to revolutionise the NHS in a 12-week project. Nobody expects you to. But what DID you do?</p><ul><li>Did you help a difficult stakeholder group find common ground?</li><li>Did you help a community see their challenge in a new way?</li><li>Did you create a conversation that didn’t exist before?</li><li>Did you make something complex feel more approachable?</li></ul><p>That’s impact. Real, meaningful impact.</p><p>And here’s something we don’t talk about enough — what was the impact on YOU? How did this project change how you see design? What did you learn? What did you unlearn? Your growth as a designer is also an impact worth sharing.</p><h3>Let’s Talk About the Messy Reality</h3><p>When I’m on the hiring side, I’m always curious when students present these perfectly smooth MA projects. Every workshop went great! All stakeholders were engaged! The process was linear and logical!</p><p>But here’s what I know from years of teaching: that’s not usually how it goes, is it?</p><p>In units with industry collaboration, I’ve seen it all. Stakeholders can’t commit to an 8-week collaboration due to unforeseen team changes or organisational issues. Users can’t make the workshop because life happens. Your perfect research plan needs rethinking when the organisation restructures mid-project.</p><p>And you know what? That’s not because it’s “just a student project.” That’s every service design project I’ve experienced in the industry too.</p><p>Here’s what’s interesting. When I speak with peers who are also on the hiring side, they often have the perception that MA students might be too sheltered for real-world messiness. But I think about all the challenges you’ve already navigated. You’ve been handling complexity all along! Maybe you’re just not sure if it’s okay to talk about it.</p><p>It is. It really is.</p><p>That time you had to completely pivot your research approach because stakeholders couldn’t give you user access? That’s exactly the kind of problem-solving we need. When you facilitated a workshop with zero budget and borrowed post-its? That’s resourcefulness. When your project sponsor changed three times and you still delivered? That’s resilience.</p><p>The messy parts of your story? They show your real skills.</p><h3>Finding Your Framework And Building Bridges Between Worlds</h3><p>Here’s something practical that one of our alumni, <a href="https://www.linkedin.com/in/eri-hirose-043414109/">Eri Hirose from Japan</a>, shared with me. She’s now Lead Service Designer at Digital Health and Care Wales. She didn’t have the traditional UX background many of her peers did, but she noticed something — public sector roles kept mentioning the GDS (Government Digital Service) framework.</p><p>So she mapped her MA project to GDS principles. Same work, new framing. Suddenly, hiring managers could see exactly how her academic project prepared her for their challenges.</p><p>If you’re interested in public sector work, explore the GDS framework. Curious about Tech? Understand how design fits into product organisations — maybe a path to Product Management resonates more than Product Designer, or perhaps you’re drawn to Design Operations. Your service design lens gives you a unique perspective on product thinking that many organisations need.</p><p>You’re not changing your work. You’re creating bridges for understanding.</p><h3>Beyond the Expected Path (Your MA Prepared You for More Than You Might Think)</h3><p>When I was looking for ideas for this blog, I caught up with <a href="https://www.linkedin.com/in/pierre-rault/">Pierre Rault</a>. He is one of the past students from France. Pierre worked in advertising in Paris, then after the MA moved to Vietnam, heading up Innovation Programs for <a href="https://www.theschoolab.com/en/">Schoolab</a>, a French consultancy. His role combined business development, workshop facilitation, user research management, and creating toolkits for design thinking — essentially building innovation capacity for SMEs and startups across Vietnam.</p><p>When I spoke with Pierre for this blog, he shared something valuable: “Service design isn’t just about org design and business architecture — it helps build coherent brand experiences. It’s essentially operations and branding skills combined.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0ZAglOzNSOta_k8Cv-emA.png" /><figcaption>Last day Pierre visited LCC before moving to Vietnam back in 2019</figcaption></figure><p>After Schoolab, Pierre co-founded <a href="https://saynopa.com/">Nopa</a> in Vietnam, leveraging design and branding to encourage sustainable behaviours. Their first product, Nopa Move, is a stylish modular bottle that rewards commuters for choosing reusable options. From advertising to service design to sustainable entrepreneurship, it is not the path anyone would have predicted, but exactly the kind of journey your MA makes possible.</p><p>Your MA in Service Design isn’t just preparing you for service design roles. It’s teaching you to see systems, understand complexity, facilitate change, and build bridges between worlds. These aren’t just service design skills — they’re leadership skills. Innovation skills. Change-making skills.</p><p>You might find your path in unexpected places. Perhaps you’re exactly what that sustainability startup needs as a strategic lead. Or what that healthcare organisation needs as an innovation manager. Or what that social enterprise needs as a systems thinker.</p><h3>A Moment of Truth</h3><p>As someone who was in your position back in 2010, then spent years on both sides of teaching and hiring, here’s what I want to share with you:</p><p>You haven’t wasted your time in academia. You haven’t learned the “wrong” things. You’re not behind your peers who went straight to industry.</p><p>You’ve been doing deep work. Thinking work. Questioning work. The work that pushes boundaries and imagines futures. That’s not separate from “real” design work — it IS real design work, just with a different accent.</p><p>Yes, learning translation skills takes time. Yes, you’ll need to practice telling your story in different ways. But please don’t apologise for your academic depth. Your critical thinking is valuable. Your research skills matter.</p><p>The industry needs what you’re bringing. Sometimes they just need help understanding it.</p><h3>Your Translation Toolkit</h3><p>If it helps, here are some practical things you might try:</p><p><strong>1. The 3-Minute Version</strong> <br>Take your MA project. Can you explain it in three minutes using everyday language? Practice until it feels natural — it took me ages to get comfortable with this!</p><p><strong>2. The Problem-Solution-Impact Framework</strong> <br>For each project, consider articulating:</p><ul><li>What problem were you solving? (In real-world terms — if it’s for a specific sector like the public sector, try framing it through GDS design principles)</li><li>How did you approach it? (Focus on decisions and actions)</li><li>What changed because of your work? (Even small changes matter)</li></ul><p><strong>3. The Learning Story</strong> <br>Pick one challenge from each project in your portfolio. How did you handle it? What did you learn? These stories often resonate in interviews.</p><p><strong>4. The Translation Dictionary</strong> <br>Maybe create a list of your academic terms and their industry equivalents:</p><ul><li>“Design Justice framework” → “Inclusive engagement that considers power dynamics and marginalised voices”</li><li>“Systems thinking approach” → “Understanding how different organisations and communities need to be part of the change”</li><li>“Critical design intervention” → “Challenging assumptions through prototypes”</li><li>“Speculative design futures” → “Exploring what-if scenarios to inform today’s decisions”</li></ul><h3>Telling Your Story (The Real One)</h3><p>It’s about telling people the skills you’ve built and finding the right translation. If there are industry frameworks that help — like GDS for public sector or product thinking for tech, use them to articulate your learnings. Show your critical thinking in ways the hiring side can see you’ll make an impact.</p><p>Don’t shy away from your ability to manage difficult situations. All those messy parts matter — that’s everyday life in the industry. The missing user group session because people couldn’t come, the venue changed last minute by stakeholders, the timeline shifted. Most of your MA had industry partners; you didn’t design in a silo. The skills that matter aren’t just how well you conduct research or visualise concepts, but how you navigate real-world complexity.</p><p>Those topics that feel impractical? Think about how you managed that uncertainty, your ability to learn and translate. Your hiring manager might not need speculative design futures right now, but they need someone who can manage people dynamics, who brings creativity to scoping issues when everything feels too big.</p><p>And here’s what I’ve learned: as you explore and grow your career, those unclear, ambitious research topics often become your everyday challenges.</p><p>Let me share one last story. Back in 2010, my MA thesis explored how designers could drive collaboration and build innovation capability in local authorities — how councils could develop design capacity within their organisations. There were no service design roles in the industry, let alone in local authorities. This was the year before GDS even started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bw2hZA8t0I0Aeqa3c-XUnw.jpeg" /><figcaption>My late-night research on organisational change and building design capability in the public sector, 2010.</figcaption></figure><p>Like you, I questioned: if there are no service designers as a job in most places, why bother exploring how we could have a role and make an impact there?</p><p>Fast forward to today — local authorities are now one of the main employers of service designers in the UK. Banks and retail companies have their own service design teams. The “impractical” became essential.</p><p>You’ve spent months (maybe years) learning to question, think systematically, research deeply, and imagine different futures. That’s not separate from industry skills — that’s exactly what good design needs.</p><h3>Let’s Keep Talking</h3><p>If you’re an MA Service Design student at UAL, I’m looking forward to speaking with you all in our upcoming session. If you’re reading this and thinking “Yes, but…” that’s perfectly okay. Every situation is unique.</p><p>If you’re not from UAL but facing similar challenges, or if you graduated a few years back and are still navigating this translation work, <a href="https://www.linkedin.com/in/veron-wk-lai-3b302a8/">feel free to reach out</a>. I offer coaching services for designers, and we can talk about your specific journey.</p><p>Because here’s what ten years of these conversations has taught me: every path from academia to industry is different, and that’s what makes them beautiful.</p><p>You’re not behind. You’re not ahead. You’re not under-prepared. You’re learning to be bilingual in a world that needs translators.</p><p>And that translation work? It’s valuable work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bsw9ueIbo9BfQ4Mu" /><figcaption>First alumni meetup at Mercato Metropolitano back in June 2025</figcaption></figure><p><em>To all former MA students from LCC, UAL now thriving in industry — remember those moments of doubt? Look at where you are now. Maybe share this with someone who needs to hear it today.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbafb61d3066" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rewriting the Chatter: What Swimming taught me about Coaching]]></title>
            <link>https://norev517.medium.com/rewriting-the-chatter-what-swimming-taught-me-about-coaching-6faaa2cb60a5?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/6faaa2cb60a5</guid>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 17:47:17 GMT</pubDate>
            <atom:updated>2025-08-20T17:47:17.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration by Jasleen Ashta, created for this blog." src="https://cdn-images-1.medium.com/max/600/1*LlsNNhz_lWnAa8-JHCwMsQ@2x.png" /><figcaption>Illustration by Jasleen Ashta, created for this blog.</figcaption></figure><p>For years, I’ve had a complicated relationship with swimming. I’ve always loved watching people in water, the joy of effortless gliding that looks so beautiful. But getting in the pool myself was a different story entirely.</p><p>“You will drown.” Not might. Will.</p><p>That’s what my brain has been telling me since childhood, after a couple of frightening moments in the water — twice in the open sea, actually. That voice has been rehearsing this line for decades. Quiet, constant, and very convincing.</p><p><a href="https://en.wikipedia.org/wiki/Chatter:_The_Voice_in_Our_Head">I recently read psychologist Ethan Kross’s book</a> about what he calls “chatter”: the internal monologue that loops when we’re stressed or vulnerable.</p><ul><li><em>You’re going to mess this up.</em></li><li><em>They know you are not good enough.</em></li><li><em>This is going to go badly.</em></li></ul><p>Even Simone Biles, one of the greatest athletes in history, has spoken openly about the mental blocks that made her step back from competition. She described that relentless inner dialogue that can erode confidence, no matter how accomplished you are.</p><p>Instead of what most people will say (oh just don’t think about it), Kross’s approach is different. He doesn’t suggest fighting this voice. Instead, he talks about naming it and reframing it. Because that chatter isn’t usually about the present moment, it’s echoing something from the past. A time we felt judged, unsafe, or simply not enough.</p><p><strong>Back in the water (again)</strong></p><p>Over the past few years, I’d dipped in and out of swimming classes, mostly group sessions. I made some progress, but the more I swam, the louder the fear became. Eventually, my confidence slipped to the point where I couldn’t go swimming alone and wanted to give up, even though I knew I’d come a long way.</p><p>Earlier this year, I decided to try once more. Not with grand expectations, just curiosity.</p><p>I found a swimming teacher who changed how I understood water. What I noticed was how often he asked, “How do you feel?” after every single new movement he taught me. That simple question made me pause and notice what was happening in my body, not just the narrative in my head.</p><p>It reminded me of coaching — that process of slowing down to really notice what’s there.</p><p>After a few months of lessons, I realised something I hadn’t understood in all my previous attempts. I’d been trying to push through the fear, to swim over it, to pretend it wasn’t there like many people like to suggest: ‘just don’t think about it’. But fear doesn’t like being ignored.</p><p>What my swimming teacher showed me was different. He paused, acknowledged the fear. He allowed me to speak the old narrative out loud, and then, bit by bit, we began to rewrite it.</p><p><strong>Finding your stroke</strong></p><p>This is what I’ve come to understand coaching really is — not giving advice, but creating space for reflection. Helping you notice the stories you’re telling yourself and supporting you to write new ones.</p><p>When a client comes to me anxious about presenting to senior leadership, we don’t start with presentation techniques. We begin with:</p><ul><li><em>What’s your inner voice saying right now?</em></li><li><em>Where did that story come from?</em></li><li><em>What would you like it to say instead?</em></li></ul><p>Because real confidence isn’t about eliminating fear. It’s about recognising it and consciously choosing a different narrative.</p><p><strong>A different kind of deep end</strong></p><p>Whether you’re preparing for that interview, presenting to the board, or standing at the edge of your own version of the swimming pool, remember that the voice in your head isn’t always telling the truth. Often, it’s just replaying an old story.</p><p>The swimming pool taught me something I thought I already understood from coaching. But there’s a difference between knowing something intellectually and experiencing it physically. Standing at that pool edge, heart racing, and choosing to get in 4 times a week, practising one small drill each time and over time swimming a bit further, floating a bit longer, the narrative shift happened.</p><p>One of the most valuable things I learned wasn’t just how to move through water, but how to meet fear with more patience and presence. To slow down, breathe, and gently question whether that inner voice is protecting me or just keeping me stuck.</p><p>The truth is, I still feel that flutter of old fear sometimes when I am swimming alone. But now I have a different conversation with it. Now I know that rewriting our inner narratives isn’t a one-time event: it’s a practice and it is a skill to learn.</p><p>If this resonates and you’re curious about exploring coaching. <a href="https://www.linkedin.com/in/veron-wk-lai-3b302a8/">Connect with me on LinkedIn, and I’d love to hear from you</a>.</p><p>And even if you’re not looking for coaching right now, I’d still love hearing your thoughts or your own version of the swimming pool story. We all have one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6faaa2cb60a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Story of Health: Why Storytelling belongs in Healthcare]]></title>
            <link>https://norev517.medium.com/the-story-of-health-why-storytelling-belongs-in-healthcare-907a4c169e0a?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/907a4c169e0a</guid>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Tue, 12 Aug 2025 09:05:23 GMT</pubDate>
            <atom:updated>2025-08-12T09:05:23.317Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in 2015, I was sitting in a workshop with people living with psoriasis. We were there to co-design a communication tool to help them talk to their doctors, and I was watching one participant examine our prototype. She looked up and said something that’s stayed with me ever since: “<em>This feels like how I want to be heard, not just about the cream, but about me</em>.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqvXnfNu35mH5M1llpc-SA.png" /><figcaption>Images from workshop with people living with psoriasis, by the Author</figcaption></figure><p>That moment crystallised something I’d been sensing throughout my career as a service designer. Healthcare conversations often narrow down to symptoms, test results, diagnoses. But what gets lost in all that clinical precision is the story — the human narrative that gives meaning to the experience of being unwell, and more importantly, of being well.</p><p>Most people think of health as simply the absence of disease, it is something we only notice when it breaks. But after two decades working across healthcare and education sectors, I’ve come to believe we need to flip that narrative. Healthcare design shouldn’t just focus on fixing what’s broken. It should help shape stories about what being well actually means, what it feels like to thrive rather than just survive.</p><h3>The Missing Story in Healthcare</h3><p>My friend and colleague Daniel Steenstra recently highlighted <a href="https://danieliao.substack.com/p/why-decentralised-healthcare-is-inevitable">the lack of design thinking in our healthcare systems</a>. He makes a compelling case for design-led, human-centred frameworks that can handle complexity and uncertainty. We desperately need flexible infrastructure and community-rooted care models. But there’s another design tool we’ve been overlooking: storytelling.</p><p>We see this everywhere else. In business, storytelling drives everything from branding to customer loyalty. In education, it’s the difference between information that sticks and facts that fade. Design teams map entire user journeys through stories. Therapists help people rewrite their life narratives.</p><p>Before writing, we had stories. They weren’t entertainment — they were survival tools, teaching groups how to stay safe, where to find food, how to work together. Stories help us remember more, connect more deeply, and even change our behaviour. Yet healthcare, this deeply human space, somehow remains one of the last places where storytelling is genuinely valued.</p><h3>Why Healthcare Pushes Back on Stories</h3><p>I get why healthcare pushes back on Stories. Let’s be honest about the reality on the ground. Healthcare professionals are dealing with overwhelming patient loads, chronic understaffing, and systems stretched to breaking point. When you’ve got fifteen minutes per patient and a waiting room full of patients, storytelling can feel like a luxury you can’t afford.</p><p>During the pandemic, we saw this pressure amplified to an extreme. Healthcare workers were making life-and-death decisions hourly, following rapidly changing protocols, managing scarce resources. In that environment, asking someone to pause and consider narrative approaches might seem absurd — even insulting.</p><p>The clinical process prioritises data, diagnostics, and evidence-based protocols. This rigour saves lives. But somewhere along the way, stories were seen as too soft, too anecdotal, too unscientific. When you’re already drowning in demands, anything that seems “fluffy” gets pushed aside.</p><p>But perhaps the real issue is that we’re only dealing with the fires in front of us. The dominant healthcare story has become crisis management — putting out fires of ill health, then moving to the next emergency. Stories could actually give us space to step back and ask: what does being well even mean? What narrative do we want to tell ourselves about health beyond just managing illness?</p><p>I’m not suggesting we need storytelling in A&amp;E. But there must be space somewhere in the system for people to explore what wellness means to them, to imagine health as more than just the absence of disease. When the only story is crisis and recovery, we miss the chance to shape a different narrative entirely.</p><p>Patients’ health experiences are not numbers on a chart. They feel pain, worry, the endless waiting to know when and how being well might become reality again — this is part of their lived experience, and these experiences are stories. Rita Charon’s narrative medicine shows how storytelling builds empathy between doctors and patients and actually saves time in the long run by improving communication. In oncology, patient stories support shared decision-making, leading to better treatment choices. But these remain exceptions rather than the norm, partly because the system doesn’t create space for them to flourish.</p><h3>When Stories Go Wrong</h3><p>Like any tool, storytelling can backfire when used carelessly. During COVID-19, we saw exactly how wrong it can go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*BZXqtp4AEuCLYG_M.jpg" /><figcaption>“Can you look them in the eyes?” — one of the UK government’s COVID-19 public health posters during the pandemic. <em>Source: HM Government campaign, image via Campaign Live.</em></figcaption></figure><p>Those UK government adverts — <a href="https://www.newstatesman.com/politics/uk-politics/2021/01/new-covid-19-ad-campaign-blames-public-government-s-failures">“<em>Can you look them in the eyes</em>?” with disturbing images of patients</a>. Social media dividing us into “anti-vaxxers” versus responsible citizens. The obesity messaging that placed moral responsibility on individuals while ignoring systemic health inequities.</p><p>That shame-based storytelling backfired. We saw how it pushed people further away, made them withdraw rather than engage. Fear and shame might grab attention, but they break trust. Instead of helping people imagine better outcomes, these stories trapped them in narratives of helplessness.</p><h3>Stories Our Grandmothers Knew About Health</h3><p>In Design, we use stories to shape reality, not just describe it. We constantly ask “<em>What if?</em>” and “<em>How might we?</em>”. Stories help people see a different version of themselves and believe in it.</p><p>I’ve seen this shift happen in my own family. Growing up in Hong Kong, I watched a different way of thinking about health. For my grandmother, it wasn’t something you only dealt with when you got ill, it was part of everyday life. She made soups to moisten the lungs in autumn, cooling teas in the summer, Tai chi every morning in the park with neighbours. Every food had a property. Every season had a rhythm. It wasn’t called self-care — it was just what you did. These stories weren’t about medicine, they were about maintenance. They were about tending to the body like you’d tend to a garden.</p><p>But I watched that story shift. By the time it got to my parents’ generation, going to the hospital had become the proper thing to do. My mum would still make the cooling soup, but she’d say, almost apologetically, “Of course we’ll see a doctor if it gets worse.” Traditional ways became “old remedies,” and Western medicine became the default.</p><p>This isn’t unique to Chinese culture. Similar shifts happened globally as modern healthcare expanded. The dominant narrative became crisis intervention and pharmacological solutions. Traditional practices — whether Chinese medicine, Ayurveda, or Indigenous healing got pushed to the margins, reframed as “alternative” to the new “real” medicine.</p><p>Modern medicine has given us remarkable breakthroughs. I’m not romanticising the past or dismissing the lives saved by hospitals and pharmaceuticals. But when crisis intervention becomes our only story, people disconnect from the everyday practices that build resilience. They stop trusting their own role in health. They wait to get sick rather than actively staying well.</p><h3>Imagining Wellness: The Story We Live Into</h3><p>When we only wait to get sick instead of staying well, something fundamental changes in how we actually experience health. Because here’s something that fascinates me: the stories we tell ourselves about our bodies literally change how our bodies function. What some call manifestation is actually neuroscience.</p><p>Emily Balcetis at NYU discovered that when people visualise their goals as being physically closer, they actually behave differently. They walk faster, push harder, persist longer. The story they tell themselves about distance literally changes how their body moves through space.</p><p>This is exactly what’s missing in healthcare. We’re excellent at describing illness — its stages, symptoms, treatments. But we rarely help people visualise and embody wellness. When someone gets diagnosed with diabetes, they receive detailed stories about disease progression, medication regimens, and potential complications. But who helps them imagine and feel what thriving with diabetes looks like? What their energised morning could feel like? How their body might move with strength rather than limitation?</p><p>Remember that woman from my 2015 workshop? Her insight about wanting to be heard “not just about the cream, but about me” — that’s exactly what happened when we moved to the co-design phase. We started designing a tool to help them talk to their doctors, but the conversation quickly moved somewhere else. They spent a long time just sharing what a good day looked like. Not a symptom-free day, that wasn’t the point. It was more like: if the weather’s dry, I wear this. If my skin flares up, I do that. It was so practical. So ordinary, but also really hopeful.</p><p>They were building on each other’s stories with small tips and little wins, and you could feel something shift. They weren’t just talking about what was hard. They were showing each other what was possible. Not “how to fix it,” but “how I live with it.” What really stuck with me was how their language changed. It moved from “I can’t do that because of my skin” to “I’ve found a way to…” and that small shift in language also felt like a shift in posture, even in how they sat and spoke. It wasn’t about pretending the condition had gone. It was about reclaiming some control. Setting a new baseline on their own terms.</p><p>I think we forget that this kind of storytelling the everyday conversation has power. It helps people imagine themselves in a different light. It’s about recognising that the stories we rehearse shape how we inhabit our bodies. If the only story you know is breakdown, you’ll move through the world expecting to break. But if someone helps you imagine and rehearse a story of capability, even with limitations, you start moving toward that instead.</p><p>Our brains don’t distinguish much between vividly imagined experiences and real ones. Mental rehearsal creates neural pathways. So when healthcare only provides narratives of pathology without narratives of possibility, we’re literally wiring people for worse outcomes.</p><p>Without the ability to imagine what’s possible, this becomes a kind of health literacy and health inequality. The literacy to know what’s within your power, the inequality of not having access to imagine what’s possible. This isn’t just healthcare — it applies in education too, where young people who have access to resources believe they have the power to change their own future. The same principle applies to health.</p><h3>Where Stories Make Real Impact</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*zT-QJq1jDNyMQSvjo62KNQ.jpeg" /><figcaption>A Friendship Bench Grandmother sitting with her client on simple wooden park bench in Zimbabwe. Credit: Freidnship Bench</figcaption></figure><p><a href="https://www.friendshipbench.org/the-team">The Friendship Bench in Zimbabwe</a> shows what’s possible when care, culture and conversation come together. Trained community members, often older women, offer talk-based support on benches in public spaces. It’s not formal therapy, it’s problem-solving in everyday language — nothing fancy, just someone listening and helping you work things through. But it works. It’s reduced depression and anxiety, and now it’s being adopted in other countries. What I find powerful is how resourceful it is, by using what’s already there, and how it makes support feel local, familiar and safe. That’s health access. That’s health literacy. And it doesn’t come from more services, but from different stories about what care can look like.</p><p>This same principle shows up in different contexts. In Canada, <a href="https://www.firstnations.org/stories/amplifying-native-communities-through-the-power-of-digital-storytelling/#:~:text=Recognizing%20the%20power%20of%20storytelling,in%20the%20digital%20communications%20strategies.">First Nations youth have been using digital storytelling to explore mental health and cultural identity</a>. They’re making short films, taking photos, recording voice notes, and through that process, they’re seeing themselves differently. It’s not just expression. It’s about shaping how they imagine who they are, and who they might become. The way storytelling helps people see a future they didn’t think was possible. It’s not just about looking back. It’s about rehearsing something forward. That’s the imaginative part of health we don’t talk about enough.</p><p>And here in the UK, <a href="https://www.patientvoices.org.uk/">Patient Voices</a> has been collecting digital stories from people using health services and sharing them with healthcare staff. These stories get used in training and even inform policy. It’s a way to help staff see beyond the diagnosis, to really understand what care feels like from the other side. The frustration, the small kindnesses, the waiting, the feeling of being invisible or heard. It’s not about data. It’s about being human. And that’s often what gets forgotten.</p><p>None of these are just communication tools. They show what changes when people are given the space to create, not just comply. When the story isn’t written for them, but with them.</p><h3>Where Do These Stories Belong?</h3><p>The problem isn’t that story lacks value, it’s that our systems aren’t designed to recognise or support that value. Current evaluation frameworks favour quantifiable clinical outcomes, overlooking the social and emotional dimensions of care. When everything is measured in discharge rates and medication adherence, where’s the metric for “feeling heard” or “understanding my condition”?</p><p>But crucially, this isn’t about adding more burden to healthcare professionals. They’re already fighting fires daily. Instead, it’s about creating spaces — both within and alongside the clinical system, where different stories about health can emerge. Spaces where wellness isn’t just recovery from illness, but something we actively cultivate.</p><p>Community storytelling initiatives often generate deep local impact but face structural barriers to scale. Without stable funding, systemic integration, and new evaluation frameworks that value ownership and agency alongside clinical outcomes, they remain promising but fragile.</p><p>The opportunity is to make storytelling feel essential rather than optional. A different kind of infrastructure that supports both patients and professionals in imagining health beyond crisis management.</p><h3>Building a Different Story</h3><p>So maybe the next chapter in healthcare won’t come from policy papers or boardrooms. Maybe it starts in kitchens, schools, youth groups, park benches — the places where people already live and talk about life, not just illness. The stories are already there. What’s missing is the space to tell them and the belief that they matter.</p><p>As designers, our role isn’t to collect stories like data points. It’s to make space. To build conditions where people feel safe enough to say what being well means to them. Not when things go wrong, but when they’re trying to live their lives — raising kids, getting through school, managing pain, finding a bit of joy in the middle of it all.</p><p>Because when people don’t believe they have the power to imagine being well, that’s not just a personal gap. That’s a health inequality. If you grow up without being shown what thriving could look like for you, how can you move towards it?</p><p>The stories we tell shape what we think is possible. And right now, too many people are stuck in a system that only gives them stories about breakdown and crisis. We need to change that. Not by telling people what to think, but by helping them see they can shape the story too.</p><p>The radical act is believing that everyone’s story matters. That the teenager managing anxiety, the elder navigating multiple conditions, the parent juggling family health — they all hold pieces of wisdom the system needs. And most importantly, they all have the power to rewrite their story.</p><h3>References</h3><p>Abdullahi, A.A. (2011) — Trends and challenges of traditional medicine in Africa</p><p>Balcetis, E. &amp; Dunning, D. (2010) — Wishful seeing: More desired objects are seen as closer</p><p>Bandura, A. (1997) — Self-efficacy: The exercise of control</p><p>Charon, R. (2006) — Narrative Medicine: Honoring the Stories of Illness</p><p>Chibanda, D. et al. (2016) — Effect of a primary care-based psychological intervention on symptoms of common mental disorders in Zimbabwe</p><p>Gottschall, J. (2012) — The Storytelling Animal: How Stories Make Us Human</p><p>Green, M.C. &amp; Brock, T.C. (2000) — The role of transportation in the persuasiveness of public narratives</p><p>Greenhalgh, T., Jackson, C., Shaw, S. &amp; Janamian, T. (2016) — Achieving research impact through co-creation in community-based health services</p><p>Hardy, P., &amp; Sumner, T. (Eds.). (2015). Cultivating compassion: How digital storytelling is transforming healthcare (2nd ed.). Kingsham Press.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=907a4c169e0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Months In: Starting My Coaching Practice]]></title>
            <link>https://norev517.medium.com/3-months-in-starting-my-coaching-practice-2e363b253a38?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e363b253a38</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 08:34:31 GMT</pubDate>
            <atom:updated>2025-08-08T08:42:22.477Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started my coaching practice back in April, alongside teaching and consulting, I honestly didn’t know what to expect.</p><p>So what made me start? I kept thinking about my own path over the last 20 years. The moments when I had incredible managers and mentors who knew exactly when to push and when to support. And those other moments — when I felt completely alone, trying to figure out whether my struggles were normal, if I was on the right path, or I was just ‘not good enough’. I wished I’d had someone who could sit with me and say: “<em>What you’re experiencing? I’ve been there. Let’s work through this together.</em>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*iIWn75fRc4WN37DtufuVnw@2x.png" /><figcaption>Illustration by Jasleen Ashta, created for this blog.</figcaption></figure><p>My journey has taken me everywhere, from being the sole designer at startups (exciting and terrifying in equal measure), to freelancing with my life packed into a suitcase for two years — literally living between train stations and client offices across the UK, then bringing Design to some of the country’s most traditional organisations, and building and scaling design at two successful scale-ups. Each role taught me something different about confidence, about leadership, about staying true to yourself when everything around you is changing.</p><p>But here’s what I’ve been reflecting on: We spend so much energy on what we’re designing for others, but how often do we intentionally design our own path?</p><p>I thought coaching would be about me sharing what I’d learned. What I didn’t expect was how much I would learn in return.</p><p>Over these past months, I’ve worked with such a diverse group of client:</p><ul><li>The sole designer at a startup, trying to establish design culture while managing endless ambiguity — I remember that pressure so well.</li><li>Designers within massive IT infrastructure organisations, working to make design valued in engineering-heavy cultures.</li><li>Senior designers taking the leap into freelance life — that mix of excitement and fear about leaving the safety.</li><li>Designer who’ve spent years in one sector, now wondering if it’s possible to pivot without starting from scratch.</li><li>First-time manager, suddenly responsible for others while still figuring out their own approach.</li></ul><p>One conversation particularly stayed with me. A client with over 10 years’ experience said: “<em>No one’s ever asked me what kind of designer I want to be. And what kind of designer would make me feel aligned?</em>”</p><p>We get so focused on moving up that we forget to ask if we’re moving in the right direction. Or if the way we’re moving feels authentic to who we are.</p><p>The tools and frameworks I developed while shaping the <a href="https://ualshowcase.arts.ac.uk/c/london-college-of-communication-ma-service-design"><em>Ways of Working unit at UAL</em> </a>have found new life in these conversations. Yes, we work on the practical things — interview preparation, promotion cases, client pitches. But the real shift happens when my client starts to trust their own voice. When they stop minimising their achievements. When they realise their different perspective isn’t a weakness. I particularly felt this myself as someone from Hong Kong, who studied in Australia, and now working in the UK. That balancing act between fitting in and being yourself, then learning how to lead others while staying authentic.</p><p>Whether it’s helping someone shape design culture in a three-person startup or supporting a designer in a 300-person organisation, I keep seeing the same need: <em>How do I grow and evolve without losing what makes me me?</em></p><p>Something that’s really encouraged me: several clients have secured professional development funding from their companies for our work together. It tells me organisations are beginning to see coaching not just as a nice-to-have, but as genuine investment in their people’s growth.</p><p>The question of purpose comes up often. Sometimes designers feel they have to choose between doing meaningful work and staying in design. I’ve wrestled with this myself. But I’ve learned that purpose and design aren’t mutually exclusive; we just need to be more intentional about how we weave them together, whether that’s through the projects we choose, the teams we build, or the problems we decide to tackle.</p><p>As September approaches, I’m opening up more space for new clients. This work energises me in ways I didn’t anticipate. It connects everything I’ve learned about design, education, and leadership into something that feels genuinely meaningful.</p><p>In the coming months, I’ll be sharing more reflections here — insights from coaching conversations, lessons from my own journey, and honest thoughts about navigating this profession we love (even when it drives us mad at times!).</p><p>If any of this resonates, if you’re navigating change, seeking clarity, or simply want to explore your next step, <a href="https://www.linkedin.com/in/veron-wk-lai-3b302a8/">Connect with me on LinkedIn, and I’d love to hear from you</a>.</p><p>All sessions are remote, which means I can work with designers anywhere in the world. Having made my own journey from Hong Kong, Melbourne to London, I love the possibility of connecting across cultures and contexts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e363b253a38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Our Designer Series — Simon Castillo]]></title>
            <link>https://norev517.medium.com/meet-our-designer-series-simon-castillo-46d0e5176a65?source=rss-4cbbd453d346------2</link>
            <guid isPermaLink="false">https://medium.com/p/46d0e5176a65</guid>
            <dc:creator><![CDATA[Veron WK Lai]]></dc:creator>
            <pubDate>Wed, 03 Jul 2024 10:05:53 GMT</pubDate>
            <atom:updated>2024-07-03T10:05:53.722Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet Our Designer Series — Simon <strong>Castillo</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdzqK2ACpCIUygiQ5Y3-sg.png" /></figure><p>Hello everyone! I’m <a href="https://www.linkedin.com/in/veron-wk-lai-3b302a8/">Veron</a>, the Head of Design at Accurx. In our second “Meet Our Designer” series, I had the pleasure of sitting down with <a href="https://www.linkedin.com/in/castillosimon/">Simon</a>, one of our Product Designers here in the Accurx Design Community. Simon joined us last summer, and prior to Accurx, he worked in the government at the Home Office and Ministry of Justice. Like many designers in the industry, Simon didn’t study Design at university, he studied Mechanical Engineering at University College London. Always fascinated by how things work, Simon realised his true passion lies in Design, and later started his first designer role in 2016. After six years in government, he made the leap to Accurx. It’s been less than a year now, and everything still feels new. I asked him to share his reflections on his experiences, insights from his work in designing for the public sector, and the changes he’s noticed since transitioning from government to a scale-up product company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2tZ-7kKbzWJYasTzd3UoRg.jpeg" /><figcaption>Simon joined us last summer, and prior to Accurx, he worked in the government at the Home Office and Ministry of Justice.</figcaption></figure><p><strong>Veron:</strong> Since the beginning of your design journey, you’ve mostly focused on designing for the public sector, working at the Home Office, Ministry of Justice, and now for the NHS. What are some of the common challenges you’ve encountered when designing for the public sector?</p><p><strong>Simon:</strong> One of the main challenges is that you’re designing for a wide range of people, because many public-facing services are meant to cater to everyone. While it’s definitely challenging, making sure that accessibility is at the forefront of the design process is crucial, and that’s something I’ve found really rewarding. When you’re designing for such a broad audience, you have to consider the needs of people you might not have direct experience with, or you have to gather a lot of context about their needs. And also, when you’re designing for the public sector, it isn’t just about the public; you’re also designing for the staff, the civil servants. They’re often under a lot of pressure to deliver services efficiently and might not have the time to learn complicated systems. So, making something that’s easy for them to use and supports their day-to-day operations is crucial.</p><p><strong>Veron:</strong> I’m really interested in something you mentioned about designing for users. The distinction between the definition of customers versus users is quite intriguing. In a B2C scenario, we usually refer to customers as users. But in your case, you’re talking about users as both the general public and civil servants. How does this shift affect your approach to design?</p><p><strong>Simon:</strong> As a customer, when you’re purchasing a product or service, you have a choice. You’re more inclined to consider the different options that meet your needs. But in the public sector, you don’t really have a choice of using different digital services to renew your passport or book a GP appointment in the case of the NHS. And for the civil servant-facing side of those services — they also don’t have as much choice but they still need to do their jobs effectively. So there’s less focus on attracting and retaining customers and a strong focus on helping users complete their tasks efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVQS8d8CKZDD5N49c8dVWg.png" /></figure><p><strong>Veron:</strong> We’ve touched on the challenges designers face when designing for users in the public sector. Now, let’s delve into the day-to-day challenges product teams encounter in these diverse contexts. What have you observed as common challenges in your experience?</p><p><strong>Simon:</strong> From my time in government, one big challenge is tackling problems holistically. For example, when I was working on a product related to criminal convictions at the MOJ, it was clear that the policy around it is handled by multiple government departments. Understanding how the different parts fit together is one challenge. And then another challenge is when you identify areas for improvement but struggle to rally cross-government efforts to address them collectively. Figuring out how to solve the different pieces and link them together across such large organisations is quite difficult.</p><p><strong>Veron: </strong>Absolutely, I can relate to that even in our context at Accurx. Despite being a product company, influencing how communication flows between GPs and patients for referrals requires understanding how hospitals and pharmacies operate too. It’s a holistic approach indeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*BfBIFRED1MMoM-YJ75wlHQ.png" /><figcaption>Veron (left) had the pleasure of sitting down with Simon (right), one of our Product Designers here at Accurx Design Community to talk about his experience in designing for the public sectors.</figcaption></figure><p><strong>Veron:</strong> Shifting from challenges, let’s talk about the aspects you find enjoyable or rewarding. What key elements have you found fulfilling when designing for the public sector over the years?</p><p><strong>Simon:</strong> I think it’s the chance to design something impactful and beneficial for many people. Solving a problem well can significantly enhance people’s experience with the public sector — a lot of the time they’re using these services in difficult or stressful circumstances, like when someone has a legal or health problem, and that sense of making the whole process easier for them is really rewarding.</p><p><strong>Veron: </strong>Definitely, that sense of impact resonates here at Accurx too. People are passionate about improving healthcare communication. Regardless of the problem’s scale, we know that solving it effectively can gradually transform how healthcare professionals work and how patients access care. Now, let’s talk about your recent transition from an in-house role within a government team to working for a product company serving the NHS. What similarities have you noticed, and what are the key differences?</p><p><strong>Simon: </strong>When I first joined here, I found that the product team setup is exactly the same as the ones I experienced in the government, which was quite reassuring. There’s often this perception that government might lag behind, but that’s not always the case. Government departments have the same digital product team structure as a young product company like here. The relationships and ways of working are very transferable. In terms of challenges, I’d say the speed of change is definitely different. Here in a product company or scale-up, you can really see the company’s ambitions driving how people work. It’s quite common for a product company to quickly pivot and change to meet its goals and mission, which is less likely to happen for a product team in government. What’s interesting for me is that in a product company, you can clearly see how the work you do contributes to the company’s overall mission and goals, whereas in government, you might not have that direct connection because it passes through so many layers.</p><p><strong>Veron:</strong> That’s a very insightful reflection. I hadn’t considered it from that angle, but it makes perfect sense. Considering the size of our company or organisation, with around 10–12 product teams and 250 staff at Accurx, compared to government departments, we’re much smaller, which naturally affects the pace.</p><p><strong>Simon:</strong> Another common aspect I’ve noticed is that when you’re working as a designer in a digital product team, whether in government or at Accurx, you’re using the latest technologies in your day-to-day work and surrounded by people who are tech-savvy or regularly use products on different devices. However, this doesn’t always reflect the end users. So it’s essential for your team to understand if the product you’re designing will truly meet users’ needs, in their context and with their experience.</p><p><strong>Veron:</strong> That’s a valid point, especially considering our earlier discussion on designing for users with varying needs and digital literacy levels. With your extensive experience in the public sector over almost six years, have you noticed any changes in digital literacy and people’s comfort in using digital government services?</p><p><strong>Simon:</strong> It’s not very clear, I’d assume digital literacy is improving but regardless of any shifts in the population’s comfort level, the goal is always to make services that are as inclusive as possible. I think that’s a good fundamental principle of service design in government.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVQS8d8CKZDD5N49c8dVWg.png" /></figure><p><strong>Veron: </strong>After discussing the design challenges and similarities, what everyday differences have you noticed between working in government and a product company? I understand it’s been a relatively short time, less than a year, since you’ve been here.</p><p><strong>Simon:</strong> One thing that’s been quite interesting, and something I didn’t expect, is how quickly as a designer or as a team, you can change and adapt your ways of working here at Accurx. Even in less than a year here, I’ve seen the design team continuously come up with ideas to change our processes, and some of these changes have resulted in great improvements in how we work. It’s impressive to see how everyone contributes ideas, and once applied, they scale across the community. This is something I think could be more challenging to achieve in government.</p><p><strong>Veron: </strong>Thank you for sharing that perspective. From a scale-up standpoint, we’re always keen on adapting and iterating, especially as the team has grown from five to fifteen in just a couple of years. The idea of continuous improvement is ingrained in our ways of working.</p><p><strong>Veron:</strong> For those reading this article, they might be interested in designing for or working within the government as a designer. I’m curious to hear from you, as navigating the public sector can be daunting for new designers. I often come across young designers keen on transitioning into the public sector, either within government or for companies serving the government. What advice would you offer to designers who are new to this environment?</p><p><strong>Simon:</strong> It’s understandable to feel overwhelmed by the complexity of the public sector. Many of the issues you’ll be working on might be unfamiliar, so there’s definitely a learning curve. From my experience, you’ll gain a lot by working closely with researchers and attending research sessions to gain insights. On top of that, you’re likely to be working with subject matter experts who can always provide valuable knowledge about the context.</p><p><strong>Veron:</strong> Did you find you had enough time to learn? I ask because I recently had a session with some graduate students who expressed concerns about not knowing enough about the subject matter or feeling like it would take a long time to learn.</p><p><strong>Simon:</strong> When you’re starting out as a designer in the public sector, especially at the entry level, that’s okay as no one expects you to know everything. Take your time to learn as much as possible. Personally, when I started at the Home Office, I didn’t know much about their operations, so I was highly motivated to learn everything I could about the organisation and how it works. Over time, things naturally became easier as I immersed myself in the work and learned more each day.</p><p><strong>Veron:</strong> I want to highlight something you mentioned about being motivated to learn and being interested. I think that’s a crucial aspect of being a designer — having the curiosity to learn from those around you and the work you’re involved in.</p><p><strong>Simon:</strong> Definitely. Whether it’s in the government or now here at Accurx, one thing I’ve always appreciated is being surrounded by people who are passionate about their work and willing to guide and share insights with you.</p><p><strong>Veron:</strong> Totally. It’s been a pleasure talking to you today. Your reflections have been incredibly insightful, especially considering the relatively short time you’ve been here. I’m sure our readers who are interested in working for the public sector and designing for it will gain a lot from your experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdzqK2ACpCIUygiQ5Y3-sg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46d0e5176a65" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>