<?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 Stu Church on Medium]]></title>
        <description><![CDATA[Stories by Stu Church on Medium]]></description>
        <link>https://medium.com/@stuchurch?source=rss-3c7eb7288686------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*T7G8BIFw0FJP6c779AISfw.jpeg</url>
            <title>Stories by Stu Church on Medium</title>
            <link>https://medium.com/@stuchurch?source=rss-3c7eb7288686------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:36:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stuchurch/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 Shape of Design]]></title>
            <link>https://medium.com/@stuchurch/the-shape-of-design-1af9a93e6be1?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/1af9a93e6be1</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Fri, 15 May 2026 11:33:31 GMT</pubDate>
            <atom:updated>2026-05-15T11:37:27.867Z</atom:updated>
            <content:encoded><![CDATA[<p>The world of strategic design — spanning products, services, and systems — has undergone a profound transformation during the last decade. This has accelerated even further over the past few years as AI has permeated our lives and professions.</p><p>The neat, linear processes that once defined design have been swallowed by an increasingly complex ecosystem. Today’s practitioners are caught in something of a paradox. On one hand, the scope of ‘design’ for many has expanded massively; we are now expected to design faster using AI tools, while simultaneously being expected to map and understand huge and complex systems. On the other hand, the day-to-day reality of some established disciplines has severely narrowed; UX, for instance, was once seen as a strategic design ‘north star’ for a business, but is now frequently relegated to just tactical, screen-focused execution (don’t get me started!).</p><p>One upshot of this is that design feels bigger and more fragmented while also evolving very rapidly. Rigid, one-size-fits-all design approaches can now feel inadequate (in hindsight, they probably always were); or even actively detrimental to positive outcomes. To thrive in this environment, practitioners can no longer operate in silos. We must become systems thinkers who treat design in a more holistic way. In their ‘<a href="https://www.nngroup.com/articles/state-of-ux-2026/">State of UX in 2026</a>’ the Nielsen Norman Group consider that <em>“The practitioners who thrive will be adaptable generalists who treat UX as strategic problem solving, rather than focusing on producing deliverables.”</em></p><p>The <em>Shape of Design</em> is a simple framework I’ve developed that attempts to provide a holistic and strategic way to think about design problems that is resilient to changes in practice and processes. My intent is for it to be a means for us to zoom out and navigate the critical components of a design project without losing our way.</p><h3>Classic frameworks (building on the shoulders of giants!)</h3><p>In thinking about this problem I’ve been influenced by several different frameworks that have hugely influenced me over the past couple of decades. These include: :</p><ul><li>Jess James Garrett’s classic ‘<a href="http://www.jjg.net/elements/pdf/elements.pdf">Elements of User Experience</a>’.</li><li>Peter Morville’s ‘<a href="https://semanticstudios.com/user_experience_design/">UX Honeycomb</a>’.</li><li>Don Norman’s ‘<a href="https://www.interaction-design.org/literature/article/norman-s-three-levels-of-design">Levels of Design</a>’ (as outlined in <a href="https://www.nngroup.com/books/emotional-design/">Emotional Design: Why We Love (Or Hate) Everyday Things</a>).</li><li>IDEO’s <a href="https://www.ideou.com/en-gb/blogs/inspiration/how-to-prototype-a-new-business">‘DVF’ (Desirability, Viability and Feasibility)</a> model of Design Thinking (with Marty Cagan later adding a <a href="https://www.svpg.com/four-big-risks/">fourth dimension of Usability</a>, and IDEO themselves later adding a <a href="https://www.ideou.com/en-gb/blogs/inspiration/what-is-design-thinking">fourth dimension of Responsibility</a>!).</li></ul><p>Perhaps less well-known in design circles is <a href="https://en.wikipedia.org/wiki/W._Edwards_Deming">W. Edward Deming</a>’s modestly titled ‘<a href="https://deming.org/explore/sopk/">System of Profound Knowledge</a>’ (SoPK). This framework is widely used in process management and consists of 4 main elements:</p><ul><li><em>Appreciation for a System</em><strong>:</strong> Recognising that success depends on the intricate interconnections between people and processes.</li><li><em>Knowledge of Variation: </em>Understanding the statistical basis for interpreting outcomes.</li><li><em>Theory of Knowledge:</em> Understanding the methods, biases and problem-solving approaches needed to solve a particular problem.</li><li><em>Psychology: </em>Understanding human psychology within a system and its effects on outcomes.</li></ul><p>What’s notable is how much more expansive the SoPK is than many traditional design frameworks; it includes both systems thinking and an explicit acknowledgement of the importance of thinking about <em>how</em> we solve problems (the so-called ‘Theory of Knowledge’).</p><p>I have attempted to synthesise the core elements of these frameworks into the Shape of Design framework, while also adding new, critical components.</p><h3>So, what actually is the ‘Shape of Design’?</h3><p>In the framework, every design project has a unique ‘shape’. This shape is not predetermined but is defined by the relative importance and effort required across nine distinct components. Each component is framed by a key design question, prompting exploration and understanding. Some projects may require consideration of all nine areas to various degrees, while others might have a much more narrow focus.</p><p>The nine core components/questions are:</p><ol><li><strong>Business<br></strong><em>What’s the opportunity?</em><br>This component involves defining the core commercial or organisational value driving the project. Activities could include conducting market research, analysing the competitor landscape, or exploring partnerships. Practitioners might focus on defining a business model, value proposition (USP), or commercialisation strategy, or they may assess organisational readiness, internal culture, and the surrounding regulatory environment.</li><li><strong>Problem-Solving Approach<br></strong><em>How do we define and solve the problem?</em><br>This area covers the potential research methods and approaches used to tackle the design challenge. At the highest level it requires the application of critical thinking skills to understand what is known, what needs to be known in order to design with confidence, and to plan the most effective path to achieve this. This could involve the application of particular design processes (like Double Diamond or Lean UX), or methods (like co-creation or participatory design), or a consideration of the nature of the problem itself (e.g. simple v complicated v complex).</li><li><strong>People &amp; Psychology</strong><br><em>Who are we designing for, and in what context? </em><br>This is the heart of user/human-centered design, involving deep user research, understanding cognitive biases, mapping user journeys, and applying principles of behavioral science to understand user motivations, pain points, unmet needs and their context of use. This can apply to <em>anyone </em>who has the ability to have an impact on final design (such as senior stakeholders, frontline staff and people involved in backstage processes, as well as ‘traditional’ end users).</li><li><strong>Ethics &amp; Legal<br></strong><em>What’s the right thing to do? </em><br>This focuses on compliance, governance, and moral obligations. Considerations may cover legal requirements like data privacy (e.g. GDPR) and accessibility (e.g. WCAG). Beyond strict compliance, teams should choose to ‘do the right thing’ and embrace corporate social responsibility, sustainability, ethical principles, bias mitigation, and inclusivity.</li><li><strong>Systems Thinking<br></strong><em>What are the wider connections &amp; implications? <br></em>This entails zooming out to understand broader ecosystems. Practitioners could map current workflows, analyse frontstage versus backstage interactions, or examine entire systems. Systemic work might also involve examining hierarchy, scale, resilience, network effects, and feedback loops to help anticipate unintended consequences across economic, environmental, and societal spheres.</li><li><strong>Performance<br></strong><em>How do we measure success?</em> <br>The very definition of a design is that it is something that is created to achieve an objective. As such, we need to be able to say whether that objective has been achieved, and that usually involves some sort of measurement or evaluation. This might involve the establishment of specific metrics or KPIs to measure tangible impacts or monitor outcomes (eg. using Google’s HEART framework).</li><li><strong>Data &amp; AI<br></strong><em>What data and information do we have, and how can we use it?</em> <br>This explores how available data and information might be used effectively to support the aims of the design. Work here can take into account various data sources (such as datasets or document repositories), metadata and taxonomies, and the need for interoperability. Depending on the solution, it could also incorporate data science methods, predictive and generative AI, or data visualisation.</li><li><strong>Design &amp; Creative<br></strong><em>How do we bring the solution to life? </em><br>This represents the execution of the experience. The activities chosen here could range from branding, UI/interaction design, and rapid prototyping to information architecture and narrative storytelling. Depending on the medium, it might span sensory and physical outputs like spatial design, visual design, animation, sound/voice, conversational design, or physical artifacts.</li><li><strong>Technology<br></strong><em>What are the technical constraints and enablers?</em><br>This component considers the technical architecture, development constraints, platform capabilities, and the feasibility of implementation. Technology is both a powerful enabler and a practical constraint.</li></ol><p>We can visualise the Shape of Design components as follows:</p><figure><img alt="A visualisation of the Shape of Design framework 1: Business 2: Problem-solving approach 3: People &amp; psychology 4: Ethics &amp; legal 5: Systems Thinking 6: Performance 7: Data &amp; AI 8: Design &amp; creative 9: Tech" src="https://cdn-images-1.medium.com/max/1024/1*ORx1RVtvRB7AUKXFmuE7Dg.png" /></figure><p>(You can also <a href="https://drive.google.com/file/d/1t0fv3HgEs73kJOfmRhkNxKtOurN8A2-k/view?usp=sharing">download high resolution version of this as a PDF</a>)</p><p>A few key considerations about the framework:</p><ul><li><strong>It’s deliberately ‘big’.</strong> Most of us spend our daily lives working within just a few of these components. The framework serves as a reminder of the broader context within which we do design. Even if your passion is a specific, deep area like building design systems, it can be very valuable to see how that fits into the whole.</li><li><strong>It’s cross-functional.</strong> Design doesn’t get done in a silo, and all nine components can have a profound impact on the way that something is designed. While separate, the nine elements are not independent of each other — there will be a variety of relationships and dependencies between them.</li><li><strong>It’s process agnostic</strong>. There are lots of published articles where authors make a claim as to why their favourite design process is obviously the best design process of all! My take is that the best process is the one that’s needed for the specific problem and context of your project. This is a foundational element of the framework,</li><li><strong>It’s a work in progress.</strong> The Shape of Design is a model and, as the old adage goes, “all models are wrong, but some are useful”. There are undoubtedly gaps and alternative ways to categorise these elements. Please let me know if you think it can be improved!</li></ul><h3>How to use the Shape of Design framework</h3><p>The framework is intended to be flexible in its use. You can adapt it to your needs, but here are four possible ways you can put it into practice:</p><p><strong>1. As a sense check / mental model<br></strong>At its most basic, the framework can be used as a mental checklist at the start of a project. During planning or in a kick-off meeting, you can mentally (or physically) run through the nine components, making a quick assessment: “Have we talked about performance metrics? What are the ethical risks here? Who understands the tech stack?” It helps frame your thinking and ensures key areas aren’t overlooked in the initial fog of a new project.</p><p><strong>2. As a collaborative thinking canvas<br></strong>The framework can also be used as a collaborative canvas. Draw the nine segments on a whiteboard or use a digital tool like Miro. As a team (including product, engineering, and business stakeholders), populate each segment with what you know, what you assume, and what you need to find out. This simple act builds a powerful, shared understanding of the project’s landscape. It becomes a living document that can be revisited at key milestones, especially for retrospectives, where you can compare the project’s initial expected shape with its final, actual shape, yielding valuable insights for the future.</p><p><strong>3. As a visual project estimator<br></strong>It’s important to understand that although the nine components are constant, different projects can have wildly different weightings of these components. This is what gives a project its ‘shape’. The initial stages of an innovation project, for instance, might start with a shape heavily weighted towards <em>Systems Thinking, People &amp; Psychology</em> and <em>Problem-Solving Approach</em> as the team explores a new, undefined problem space. In contrast, an iterative redesign of an existing e-commerce website might have a shape that weights towards <em>Performance</em>, <em>Business</em>, and<em> Design &amp; Creative</em>, focusing on optimising existing flows and conversion funnels. A healthcare or finance project would inevitably have a very large <em>Ethics &amp; Legal</em> component.</p><p>By assigning a relative weight to each component we can also create a visual representation of where the team anticipates spending the most effort. A simple way to do this might be with something akin to ‘T-shirt sizing’ (a common agile estimation technique). Assign each component a score from 1 (minimal effort/complexity) to 5 (maximum effort/complexity). This ‘size’ is a quick, intuitive judgment based on a combination of factors:</p><ul><li><strong>Complexity:</strong> How difficult or thorny is the problem in this area? (e.g. navigating a web of legacy systems would be high complexity).</li><li><strong>Effort:</strong> How much work or time will be involved? (e.g. conducting foundational ethnographic research across multiple countries would be high effort).</li><li><strong>Uncertainty/risk:</strong> How much is unknown? (e.g., using a brand new, unproven AI model would be high uncertainty).</li></ul><p>Once weights are assigned, you can generate a simple radial visualisation of the ‘shape’ of your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AvkGQ22h2j2RzHilvDMrIQ.png" /></figure><p>This process isn’t about creating a precise, scientific project estimate. Its value lies in facilitating a conversation and creating a shared understanding of the work ahead. It helps the team see the project in the same way and highlights areas of high risk or effort that need early attention.</p><p><strong>4. As an indicator of skillsets and team capabilities<br></strong>As the framework demonstrates, the range of possible skills required for a detailed understanding of a design problem is enormous and no individual can have all possible skills required. Most design professionals have a set of skills that are some variation on <a href="https://rossdawson.com/building-future-success-t-shaped-pi-shaped-and-comb-shaped-skills/">‘T-shaped’, ‘Pi-shaped’ or ‘Comb-shaped’</a> in that they have a broad understanding of different aspects of design with one or more specialisms. More recently there have even been discussions about the importance of <a href="https://nurxmedov.medium.com/companies-want-three-types-of-designers-in-2026-the-traditional-senior-isnt-one-9c5f7921249f">block-shaped</a>, or <a href="https://medium.com/design-bootcamp/the-missing-bar-why-we-need-x-shaped-people-in-a-digital-world-e57845983934?postPublishedType=repub">V-shaped</a> people! While these models are conceptually useful, it is less clear what the foundational digital design activities are that they relate to. The Shape of Design framework can be used to map the skills and strengths of an individual or a team. This can be invaluable for identifying skill gaps, planning professional development, and composing a well-rounded project team that has the right ‘shape’ to tackle the challenge at hand.</p><h3>Try it Yourself</h3><p>To make this tangible, I’ve built a simple app that allows you to quickly assign weights to the nine components and download a visualisation of your unique ‘Shape of Design’ profile. Why not give it a test drive on your own skillset, or a project that you’re working on?</p><p><a href="https://shape-of-design-562304650163.europe-west2.run.app/">https://shape-of-design-562304650163.europe-west2.run.app</a></p><figure><img alt="A screenshot of the web app for the Shape of Design framework" src="https://cdn-images-1.medium.com/max/1024/1*wwrkUH24Iyh2evp-csqT0w.png" /></figure><p>Here is my own Shape of Design (I am very much a generalist!):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GWx5H0SikLnqYSbIfvH_4w.png" /></figure><h3>Moving Forward</h3><p>Ultimately, the purpose of the Shape of Design framework is to provide a flexible, holistic lens through which to view the complex world of product, system and service design. It’s a tool for thinking, for communicating, and for navigating the challenges we face with a clearer, more comprehensive perspective.</p><p>This is the very first iteration of the framework, and I’m curious to see whether it resonates with people and how its potential value is perceived. Please feel free to take it, use it, adapt it. I’d love to hear how it works for you.</p><p>If you’d like to find out more, have a chat, or hire me please get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch<br></a><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1af9a93e6be1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking About Digital Design: Why It Matters for Your Academic Research Project]]></title>
            <link>https://medium.com/@stuchurch/thinking-about-digital-design-why-it-matters-for-your-academic-research-project-4b51d934533c?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b51d934533c</guid>
            <category><![CDATA[academic-research]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[digital-design]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Sat, 07 Jun 2025 12:10:07 GMT</pubDate>
            <atom:updated>2025-06-07T12:10:07.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A DNA double helix" src="https://cdn-images-1.medium.com/max/1024/1*o11WkdrfkF1a3fxEfEoqtA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ashraful25?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Ashraful Islam</a> on <a href="https://unsplash.com/photos/a-double-strand-of-blue-and-white-spirals-pRt3JVYlJho?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p><em>This article was first published on the University of Bristol’s </em><a href="https://researchit.blogs.bristol.ac.uk/2025/06/03/thinking-about-digital-design-why-it-matters-for-your-academic-research-project/"><em>Research IT blog</em></a><em> on June 3rd 2025.</em></p><p>Academic research projects, regardless of discipline, increasingly involve creating bespoke digital products or tools. These tools can range from specific data collection apps, to digital archives of artefacts, or even interactive tools for querying and visualising complex data.</p><p>With fixed grant funding, the big question is always: how do we make the most of the money we have to ensure that our digital tools are a success? We want the digital outputs of our research to be genuinely useful and easy for people to use, and we need to develop them efficiently. This is where design thinking, particularly User-Centred Design (UCD), comes in. It’s a way of thinking and working that can help produce focused, well-designed digital tools and make the best use of your budget.</p><h3>What’s the Problem with ‘Just Build It’?</h3><p>It’s tempting to think of creating a digital tool as merely a construction task (<em>“Let’s build a website!”</em>). However, the actual coding and development is usually the most expensive and time-consuming part of creating digital products. So, before starting to write code it’s important to be confident that what you’re planning to build is <em>really</em> what’s needed — both for the project’s academic goals and for the people who will eventually use it.</p><p>Rushing into development without this understanding risks:</p><ul><li><strong>Building the wrong thing.</strong> We might create something that doesn’t actually solve the intended problem or meet a real user need. This can lessen the impact of your research, or even hinder it if the tool is essential for data collection.</li><li><strong>Costly changes later.</strong> Making significant changes once coding has started can rapidly consume time and money. It’s far more cost-effective to invest time upfront understanding the problem and exploring solutions through prototypes.</li><li><strong>Wasting the budget.</strong> Building something that isn’t right or isn’t used wastes precious grant money.</li><li><strong>Poor usability.</strong> If a tool isn’t intuitive or appealing, people won’t engage with it. This limits its impact and could even jeopardise your academic objectives.</li><li><strong>Trying to do too much.</strong> Packing in too many features (‘featuritis’) can lead to complexity, dilute focus, and stretch resources.</li><li><strong>Project frustration:</strong> Discovering fundamental issues late in the development cycle can cause delays and frustration, potentially meaning less gets delivered than planned.</li></ul><p>Fortunately, ‘Design Thinking’ offers ways to approach digital development that minimise these risks.</p><h3>Design Thinking &amp; User-Centred Design (UCD)</h3><p>At its core, Design Thinking is about deeply understanding the people who will use the thing you create and the context in which they use it. It’s also important to involve them in the design process (that’s the ‘User-Centred’ part).</p><p>It’s not just about how something looks; it’s fundamentally about making something <em>work well</em> for its intended users in their context. Your digital tool might be for the general public, other academics, specialist practitioners, policymakers, or research participants. These groups have vastly different needs, technical skills, knowledge, and expectations. Without understanding these, designing something truly effective is a shot in the dark.</p><p>One popular process that encapsulates design thinking is the ‘Double Diamond’ from the Design Council (<a href="https://www.designcouncil.org.uk/our-resources/framework-for-innovation/">https://www.designcouncil.org.uk/our-resources/framework-for-innovation/</a>). The Double Diamond visually separates the design process into understanding the ‘problem space’ and then exploring the ‘solution space’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*voyWk2Bym-xTM_BY.png" /><figcaption>The Double Diamond by the Design Council is licensed under a CC BY 4.0 license (<a href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</a>).</figcaption></figure><p>The main aim of the first diamond (Discover + Define; aka ‘Build the right thing’) is to explore the problem space and define the problem. Discovery usually involves stakeholder and user research (such as interviews or surveys) followed by synthesis of the results to produce clearly articulated and prioritised problems/opportunities.</p><p>The second diamond (Develop + Deliver; aka ‘Build the thing right’) illustrates the need to explore the range of possible solutions and then iteratively test and refine them. Initial design ideas are usually mocked up and tested as prototypes that can be easily discarded or modified at minimal cost, eventually converging on the one that hits the sweet spot of meeting the needs of both the project and the users, while also being technically feasible.</p><p>Even if you think you already know what’s needed, making time for (at least) a rapid discovery to clarify your thinking and validate your assumptions from different perspectives is incredibly valuable. It ensures you’re tackling a genuine user need and building on solid foundations.</p><h3>Design Research: Pragmatic, Not Perfect</h3><p>Design research is a different beast from traditional academic research. While it can be just as rigorous, it’s usually more pragmatic and action-oriented. The goal is typically to do <em>just enough research</em> to gain the confidence needed to move forward with a particular design or approach.</p><p>It’s also important to recognise that there are different, sometimes competing, goals at play:</p><ul><li><strong>Academic goals.</strong> What new knowledge or understanding does the project (and the tool) contribute?</li><li><strong>Project goals.</strong> What specific function does the tool <em>need</em> to perform for the research (e.g. reliably collect specific data)?</li><li><strong>Administrative goals.</strong> Meeting funder requirements and milestones.</li><li><strong>User goals.</strong> Is the tool or product easy and perhaps even enjoyable to use? Does it help users achieve <em>their</em> objectives?</li></ul><p>Design thinking provides a framework for navigating and balancing these different needs as it encourages us to explore these issues, then narrow them down to be quite specific about the nature of the tool we are designing, and who it is for.</p><h3>Practical Design Thinking Takeaways for Your Project</h3><p>Here are some practical takeaways to help you incorporate design thinking in your project:</p><ol><li><strong>Start Early.</strong> Consider design and development needs <em>before</em> submitting the grant. Talk to support teams (like Research IT or similar digital specialists at your institution) about your ideas early on. Budgeting around <strong>10–25% of the digital development cost</strong> for design thinking activities (discovery, prototyping, testing) is a reasonable starting point, though this depends on the project’s complexity.</li><li><strong>Embrace the uncertainty.</strong> Be open during the design process. It’s an iterative journey of exploration and discovery, not always a linear path.</li><li><strong>Don’t be distracted from the real problem.</strong> It can be tempting to jump straight to a particular solution. However, deeply understanding the real problem you’re solving and focussing on it can save significant time later; there are many potential solutions to a given problem, and you may discover that features you initially thought were essential aren’t actually needed.</li><li><strong>Don’t assume your users are like you. </strong>This is a classic design mantra for a reason. Avoid assuming users share your level of expertise, motivation, or context. They almost certainly do not.</li><li><strong>Prototype early &amp; often. </strong>Use tools (from simple hand drawn sketches, to prototyping tools like Figma (<a href="https://www.figma.com/">https://www.figma.com</a>) or PenPot (<a href="https://penpot.app/">https://penpot.app</a>), or even AI tools like Bolt (<a href="https://bolt.new/">https://bolt.new</a>) or Lovable (<a href="https://lovable.dev/">https://lovable.dev</a>)) to create tangible representations of your ideas quickly.</li><li><strong>Test your prototypes.</strong> Get feedback on your prototypes from real users, but be clear what you’re testing — Is it the content? A specific workflow? The visual design? Also, don’t just ask people what they think. Instead, try to get them to interact with prototype content in the context of a specific, real-world scenario. You’ll get better feedback this way.</li><li><strong>Iterate.</strong> Your first design idea is rarely the final or best one. Use feedback to refine and improve.</li><li><strong>Keep it simple.</strong> Less is often more. Avoid unnecessary complexity and focus on doing the core things well.</li><li><strong>Get support if you need it.</strong> It’s very helpful if you can familiarise yourself with basic design processes and methods. However, digital projects are inevitably more complicated and ‘messy’ than they often appear at first sight. Research IT can help you to navigate these complexities.</li></ol><p>In summary, by embracing design thinking and UCD principles, you can significantly increase the probability that your research project’s digital outputs will be useful, usable, and impactful, while making the best use of your valuable grant funding.</p><p>If you’d like to find out more, or get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch/</a><br><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b51d934533c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Trouble]]></title>
            <link>https://medium.com/@stuchurch/deep-trouble-d8c79c618d6c?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8c79c618d6c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Fri, 06 Jun 2025 15:17:45 GMT</pubDate>
            <atom:updated>2025-06-06T15:17:45.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A sea kayker on a tranquil sea at sunset" src="https://cdn-images-1.medium.com/max/1024/1*f9a-nSmlaEA-M0xGqRv8_A.jpeg" /><figcaption>Photo by<a href="https://unsplash.com/@patrickian4?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash"> Patrick Fore</a> on<a href="https://unsplash.com/photos/man-riding-kayak-on-water-taken-at-sunset-UFqV-RqPm8w?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash"> Unsplash</a></figcaption></figure><blockquote><strong>‘Obeying rules without an understanding of the reasons behind them creates an approximation of competence which leaves one vulnerable to the exceptions.’</strong></blockquote><p>I first stumbled upon this quote more than 20 years ago and it’s one of those little nuggets of wisdom that has somehow been stuck in my ever brain since. It comes from a surprising source, too — the 1997 book ‘<a href="https://www.amazon.co.uk/Sea-Kayakers-Deep-Trouble-Magazine/dp/0070084998/ref=sr_1_1?crid=1PBQYCO8B5JB2&amp;dib=eyJ2IjoiMSJ9.VNJeGg99Eo2HkJwpO2Ivx29Ra2p_HAMAarZwYvtOFSI.gmU8ncsxTIxB2BZ1vRfszn1du_pukwHsguWIpTvuHYo&amp;dib_tag=se&amp;keywords=sea+kayakers+deep+trouble&amp;qid=1749219948&amp;sprefix=sea+kayakers+%2Caps%2C88&amp;sr=8-1"><strong>Deep Trouble</strong></a><strong>’</strong>. It’s a book that recounts perilous kayaking tales from the readers of ‘Sea Kayaker’ magazine, and the lessons subsequently learned from them.</p><p>As a once-in-a-blue-moon-when-the-weather-is-nice kind of kayaker, I can’t claim to have identified it at source. Rather, I first saw the quote in a talk given by Jeff Veen, one of the founding partners of Adaptive Path, at SxSW in the early noughties. If you’re not familiar with Adaptive Path, they were one of the early pioneers of UX and were hugely influential in shaping many of the tools and techniques that we still use today. Other alumni include UX luminaries such as Indi Young, Jesse James Garrett, Peter Merholz and Mike Kuniavsky.</p><p>Unlike the other things that filled my brain in the noughties (like Netscape, MySpace, Ajax and WAP sites for mobiles!) I think the quote has stood the test of time, particularly with respect to UX and product design. In fact, I’d go as far as to say that it’s probably even more important now than it was then.</p><p>The field of UX has seen massive growth in the past decade, only slowing down in the last year or so. As a result there’s a lot of variation in the quality and experience of UX practitioners, many having moved sideways from other disciplines, or entered the profession via UX Bootcamps. In addition Product Managers, often with no background in user research or design, are increasingly ‘doing’ UX and being responsible for design approaches and decisions. Everyone has to start somewhere, of course, but it seems to me that a consequence of this rapid UX expansion is that we have become somewhat beholden to UX processes, rather than focussing on effective problem solving and thinking about how different UX processes can be best applied or adapted to the situation at hand.</p><p>One of the signs of this lack of maturity within UX and product is that there are lots of online discussions (or, more accurately, declarations) about why Process X is better than Process Y, or why Process Z is now, apparently, dead. I understand that people have found approaches that work for their context or their company, and that’s great (whether than be the Double Diamond, Design Thinking, Lean UX, ISO-9241, Continuous discovery etc.). The wider reality, though, is that there is no single design process that <em>should always </em>be followed. Each project has different starting points with different constraints and different objectives. There is no one-size-fits-all solution. The only real constant is that there is a problem space and a solution space and you want to understand the problem space as thoroughly and quickly as you can so that you can crack on with designing and building a solution. In terms of our sea kayaker, if you don’t understand <em>why</em> you are approaching a problem in a particular way, then you are vulnerable to any exceptions that don’t fit nicely into your off-the-shelf design process.</p><p>This thinking applies to activities within a project too. Ultimately, design projects require a clear understanding <em>why</em> each step is taken — whether it’s strategy, a piece of generative user research, prototyping, or testing — and how it contributes value to the project. Without this deeper understanding, designers risk investing time and effort into activities that are of little or no value. A few real-world examples of ‘deep trouble’ design activities that I’ve observed over the years are:</p><ul><li>Spending days refining a design to meet the needs of an extreme edge case in a new product because someone had created a ticket for it.</li><li>Putting together a team to reconcile multiple personas across different projects despite the fact that no-one trusted the personas or ever used them to support design decisions in the first place.</li><li>Launching straight into ‘doing interviews’ on a discovery project with minimal domain knowledge and little understanding of the problem to be addressed because there was an arbitrary deadline to complete the interviews.</li><li>Using synthetic users or GenAI and considering it to be actual user research rather than hypothesis generation or modelling.</li></ul><p>All of these mistakes are made because there is no attempt to explore the ‘why’ i.e. ‘Why are we doing this, and what value does this add to the ultimate success of the project?’. Design isn’t a pre-defined process with pre-defined activities. It’s a messy, fluid problem to be solved that requires thought, adaptability and careful choice of tools from a practitioner’s toolkit.</p><p>Does anyone else have any tales of ‘deep trouble’? Feel free to get them off your chest in the comments (in a polite way, of course!)</p><p>Thanks for reading.</p><p>If you’d like to find out more, or get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch/</a><br><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8c79c618d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to install DeepSeek R1 locally on a Mac (for the relatively non-techie)]]></title>
            <link>https://medium.com/@stuchurch/how-to-install-deepseek-r1-locally-on-a-mac-for-the-relatively-non-techie-50bedc19476b?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/50bedc19476b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[deepseek-r1]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 16:54:17 GMT</pubDate>
            <atom:updated>2025-01-28T17:33:10.777Z</atom:updated>
            <content:encoded><![CDATA[<p>Using DeepSeek online poses potential data security risks. However, it’s quite straightforward to run your own safe, local version, even if you’re relatively non-techie.</p><p>If you’re working with sensitive data, then running Large Language Models (LLMs) locally (i.e. directly on your computer, rather than in the cloud) is crucial since it ensures that no data is shared with third parties such as OpenAI (ChatGPT), Google (Gemini) or DeepSeek.</p><p>This is especially important for DeepSeek. DeepSeek has recently released its R1 model, which has comparable performance to ChatGPT Pro (which costs an eye-watering $200/mo, and still runs at a loss!). Obviously, the fact that Chinese companies tend to have extremely close ties with the Chinese government (see: TikTok) means that you should be extremely cautious about providing any personal or sensitive information that could be (mis) used.</p><p>Fortunately, and unlike OpenAI, DeepSeek have made their models open source, which means that you can also download them and run them locally for free. This means that you can take advantage of the power of DeepSeek R1 without any of the associated costs or security concerns. You can even use DeepSeek without being connected to the internet.</p><p>This is a quick guide for non-techies to be able to run DeepSeek R1 locally. It might look a bit confusing in places (there is code!), but treat it as a recipe and follow the steps and it should hopefully just work.</p><h3>1. Install Ollama and run deepseek-r1</h3><p>Ollama is an app that allows LLMs to be run locally on your Mac. Download the <a href="https://ollama.com/download">Ollama</a> app for Mac, and install it. Once it’s installed open Ollama and click the Install button to “install the command line”.</p><p>Ollama then gives you code to paste into Terminal.app:</p><figure><img alt="Ollama dialog box with code to run LLM" src="https://cdn-images-1.medium.com/max/1024/1*hzjnP0pJNdbS916Hrzi7Mg.jpeg" /></figure><p>You can do this if you wish (it’s just a different, less powerful LLM from Meta), but we want to install DeepSeek, so <strong>do this instead</strong>:</p><pre>ollama run deepseek-r1</pre><p>There are actually three different DeepSeek models that you can install but deepseek-r1 is the only one that will realistically run on most Macs. (I have a 48GB Mac mini M4 Pro and it can barely cope with the next most powerful model).</p><p>When you attempt run deepseek-r1 for the first time it will have to be downloaded first. It’s over 4GB, so be prepared for a little wait.</p><figure><img alt="Terminal with ‘ollama run deepseek-r1’ on it" src="https://cdn-images-1.medium.com/max/1024/1*x3xatbC92kSMgrS-QVmjbQ.jpeg" /></figure><p>Once deepseek-r1 is downloaded and running in your terminal, you’re ready for the next step. (Note that you’ll need to have deepseek-r1 running in the terminal like this whenever you want to use your local version).</p><h3>2. Install Docker</h3><p>Docker is an app that allows you create ‘containers’ to run your own apps locally. Download and install <a href="https://www.docker.com/products/docker-desktop/">Docker Desktop</a>. You’ll need to create an account to do this (but it’s usually easy as you can use a Google account).</p><figure><img alt="The Docker Desktop website" src="https://cdn-images-1.medium.com/max/1024/1*y9YrXVvt5mLxAfToteddWw.jpeg" /></figure><p>Once you’ve got the Docker app installed and running (and you’re logged in), it should look like this:</p><figure><img alt="The default, empty Docker dashboard" src="https://cdn-images-1.medium.com/max/1024/1*0EET47z1l9KxzPG_r1002g.jpeg" /></figure><h3>3. Install Open WebUI</h3><p>Open another Terminal window and paste in the following code:</p><pre>docker run -d -p 3000:8080 \<br>  --add-host=host.docker.internal:host-gateway \<br>  -v open-webui:/app/backend/data \<br>  --name open-webui \<br>  --restart always \<br>  ghcr.io/open-webui/open-webui:main</pre><p>This creates a Docker container (app) that runs <a href="https://openwebui.com/">Open WebUI</a>, which will provide the user interface to your DeepSeek R1 model.</p><p>Once you have created your Open WebUI container, your Docker dashboard should look like this:</p><figure><img alt="Docker dashboard showing that an Open WebUI container has been created" src="https://cdn-images-1.medium.com/max/1024/1*7KuEw13ZnCp3MR9HmfQLiA.jpeg" /></figure><h3>4. Fire up your local version of DeepSeek R1!</h3><p>Launch WebUI using the following URL in your browser</p><pre>localhost:3000</pre><p>(You’ll be prompted to generate a local admin account first, but that only takes a couple of seconds; don’t forget your password, though!).</p><p>Then — viola! — you should have DeepSeek R1 running locally, with a nice slick looking interface:</p><figure><img alt="DeepSeek R1 running locally in Safari" src="https://cdn-images-1.medium.com/max/1024/1*XyFr3HLp_5jDKYVApyQ62A.jpeg" /></figure><figure><img alt="Sample prompt for DeepSeek R1" src="https://cdn-images-1.medium.com/max/1024/1*ozIyKKByjFqlCUxwrA1ijQ.jpeg" /></figure><p>As a bonus, you can also analyse uploaded files and interact with it via audio (just like ChatGPT).</p><p>If you’d like to find out more, or get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch/</a><br><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50bedc19476b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How can service designers influence organisational culture?]]></title>
            <link>https://medium.com/@stuchurch/how-can-service-designers-influence-organisational-culture-dbc0e2b1043c?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbc0e2b1043c</guid>
            <category><![CDATA[culture-change]]></category>
            <category><![CDATA[public-sector-innovation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Tue, 31 Dec 2024 12:30:01 GMT</pubDate>
            <atom:updated>2024-12-31T12:30:01.179Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>The quality of a service experience is underpinned by the culture of the organisation that delivers it. But as designers it can be hard to tackle cultural factors.</h4><p><em>This article was originally published on the </em><a href="https://panda.associates/how-can-service-designers-influence-organisational-culture/"><em>Panda.associates</em></a><em> website in September 2023.</em></p><h3>The culture challenge</h3><p>As service designers, our main focus is on creating better experiences for service users. And given that the user experience is underpinned by the way that the service operates, we often find that a shift in organisational culture is required to significantly improve the user experience.</p><p>Culture change is hard though, and can present a challenge for service designers. On one hand we are in a unique position to facilitate change. We can remain objective, operating at arms length to conduct research, analyse data and identify opportunities for improvement. We can also engage with service staff, taking them with us on our journey of discovery, convening important conversations and driving consensus on what needs to be done.</p><p>On the other hand we can’t possibly understand the complex web of personalities, relationships and history that influence organisational culture. And we often lack the authority to make change happen.</p><p>So how do we enable culture shifts without overstretching? From my experience of working on public sector service design, I’ve have identified the following tactics, which I see as key to both service improvement and facilitating the cultural shifts required for service transformation to occur.</p><h3>Define a shared vision</h3><p>If you can’t clearly articulate the problem that you’re solving, it’s very hard to get buy-in from service staff and effect change. It also makes it difficult to gauge progress and demonstrate success, which is vital for taking people with you. So, at the start of a project we run workshops with stakeholders and service staff and work hard to agree a shared vision. This serves as a ‘north star’ for the project team, ensuring that everyone understands what we’re aiming for and why.</p><h3>Listen to wider concerns</h3><p>In stakeholder interviews, there are always a small number of service staff who will have specific (and entirely valid) bugbears that they’ve been dwelling on, and they may launch into detailed explanations of these bugbears at the first possible opportunity!</p><p>Whilst these topics don’t always fit neatly into any discussion guides that we might have spent hours crafting, we always allow space to listen. If you don’t hear people out, they will not want to engage on the topics you need them to talk about. And if you don’t manage to get through every topic in your discussion guide, there are usually opportunities later in the process to fill in some gaps.</p><h3>Be transparent</h3><p>If service staff feel that there’s a hidden agenda or that, as a service designer, you’re ‘on the side of management’ then you won’t easily get to the core of how the service is run, or be particularly effective in catalysing change.</p><p>We need to be open and transparent in our approach. If we approach stakeholder research with genuine curiosity and a lack of ego, and if we paint an honest picture of what we’re trying to achieve (the vision), we’ve found that staff will be more likely to engage and reveal critical process details and pain points.</p><p>It’s worth nothing that while a culture of openness is ideal, this won’t always be possible, especially when internal politics are at play. Therefore we always offer the option of anonymity when interviewing internal staff. We can still be transparent with our process and insights, even when staff identities are protected.</p><h3>Provide progress updates and solicit feedback</h3><p>We usually chunk project activities into 2-week sprints. This provides an opportunity to share progress with all service staff via a ‘show and tell’ at the end of each sprint.</p><p>Although it’s tempting to use the whole session to detail the amazing work that we’ve (hopefully) done, this shouldn’t be the sole focus. Show and tells provide a vital opportunity to engage with service staff, and to encourage discussion and feedback.</p><p>Of course, some service staff may not feel qualified or confident enough to participate during these sessions. So we always provide (and encourage the use of!) alternative ways for staff to express their views.</p><h3>Tailor your communications</h3><p>Different staff within the service need different types of information about what’s happening.</p><p>Senior leaders tend to think more strategically. They need to understand how current progress will lead to success. And they need to know their objectives and concerns are being considered and communicated during discovery, and that any future service blueprint maps directly onto the outcomes that matter to them.</p><p>Frontline service staff, on the other hand, have detailed knowledge of the day to day processes and ways of working. Their focus is more likely to be on the way that any service changes will affect them operationally. The sooner they can understand or anticipate the likely direction of changes, the better.</p><h3>Involve staff in solution design</h3><p>At the end of a service design discovery phase for a local authority, we ran two ideation sessions with a combination of senior and frontline service staff. The staff were struggling to keep on top of things at that time, so there was some reluctance to give up even more time. However, with management buy-in we coaxed a range of people to attend the workshop.</p><p>We teed them up with a short presentation and collated the key evidence from our discovery research. Primed with that information, they fully engaged with the process and sketched out lots of ideas, some of which aligned with our own thinking, and some of which embellished it. But the most important outcome was that the staff were now energised by the opportunity to change. They felt heard. They felt hopeful. And they felt some sense of ownership of that change; it wasn’t just something that would be imposed on them.</p><h3>In summary</h3><p>Service design isn’t only about the quality of the research, opportunities, ideas and solutions it generates. It’s about enabling organisations to deliver change, and sometimes that requires a shift in organisational culture. As service designers we need to do what we can to enable that change, whilst recognising the limitations of our position.</p><p>If you’d like to find out more, or get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch/</a><br><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbc0e2b1043c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The need for human-centred AI]]></title>
            <link>https://medium.com/design-bootcamp/the-need-for-human-centred-ai-13b1b3cbeccd?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/13b1b3cbeccd</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Fri, 24 Nov 2023 10:21:23 GMT</pubDate>
            <atom:updated>2023-11-27T22:30:09.839Z</atom:updated>
            <content:encoded><![CDATA[<p>Like a lot of people I know, I’ve been trying to get to grips with the implications of AI for UX, Service and Product Design.</p><p>As I was stepping through some materials on AI strategy on a very popular data science learning platform, I came across the following Venn diagram (which I’ve taken the liberty of redrawing):</p><figure><img alt="A Venn diagram of AI Strategy, showing it as the intersection of data, AI and business" src="https://cdn-images-1.medium.com/max/1000/1*zuw6nYzYHhWwmX26K9hXrw.png" /></figure><p>The instructor suggested that good AI Strategy positions itself at the intersection of data, AI, and business. On the face of it, and from a business perspective, this might seem quite sensible. However, it reminded me of another Venn diagram that I’m much more used to seeing, and sharing with clients:</p><figure><img alt="A Venn diagram of Product Strategy, showing it as the intersection of UX, Tech and business" src="https://cdn-images-1.medium.com/max/1000/1*yB0HfI3XtKGc8WPdNnymIQ.png" /></figure><p>This is Martin Eriksson’s ubiquitous Venn diagram that demonstrates how Product Strategy/Management lies at the intersection of users, technology &amp; business.</p><p>Can you spot the difference? We’ve lost the users from the AI strategy and ‘Tech’ has effectively split into ‘Data’ and ‘AI’.</p><p>This set alarm bells ringing for me. If, <a href="https://en.wikipedia.org/wiki/Existential_risk_from_artificial_general_intelligence#">as has been suggested</a>, AI has the potential to pose an existential risk to humanity, then the very least we should do as part of an AI Strategy is consider how each AI project impacts people. And not just at the interface (UI) level. It’s much broader, and much more complicated than that. For example:</p><ul><li>What are the effects of AI-driven outcomes on the people who are directly affected by them? (e.g. medical diagnoses, mortgage applications, personal assistants that know everything about you, etc). Does an AI confer reassurance and trust, or does it drive detachment and disconnection?</li><li>How are people working within the companies and organisations where AI is deployed affected? Does AI help them do their job better, or faster? How do they deal with exceptions and outliers? Do they resent the AI, or does it empower them? I wrote a <a href="https://panda.associates/how-can-service-designers-influence-organisational-culture/">blog post</a> for Panda recently about how service designers have an important role in both researching and influencing organisational culture, and this is likely to be especially true for AI products and deployments.</li><li>What are the societal and cultural implications of the AI? Could there be unintended consequences (e.g. using AI voice cloning for identity theft and scams)? Can these be mitigated against?</li></ul><p>So, I suggest that a more responsible model to adopt is:</p><figure><img alt="Proposed Venn diagram of AI Strategy, showing it as the intersection of People, Data, AI and business" src="https://cdn-images-1.medium.com/max/1000/1*vVLvrbFCKewXfwb4tk2_0A.png" /></figure><p>In short, if AI is going to fulfil its promise to somehow make the world a better place, then AI projects need to focus beyond just ‘data, AI and business’ and always place human outcomes and impacts at their core.</p><p>If you’d like to find out more, or get in touch:</p><p><a href="https://www.linkedin.com/in/stuartchurch/">https://www.linkedin.com/in/stuartchurch/</a><br><a href="https://www.pureusability.co.uk/">https://www.pureusability.co.uk/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13b1b3cbeccd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-need-for-human-centred-ai-13b1b3cbeccd">The need for human-centred AI</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating objective personas with multiple correspondence analysis]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxdesign.cc/creating-objective-personas-with-multiple-correspondence-analysis-12ddf4623f05?source=rss-3c7eb7288686------2"><img src="https://cdn-images-1.medium.com/max/1000/1*c4oSN-DUyzYKnXgHIDPKHw.jpeg" width="1000"></a></p><p class="medium-feed-snippet">Personas are widespread in digital, product and service design, and persona creation is a core technique in the toolbox of UX&#x2026;</p><p class="medium-feed-link"><a href="https://uxdesign.cc/creating-objective-personas-with-multiple-correspondence-analysis-12ddf4623f05?source=rss-3c7eb7288686------2">Continue reading on UX Collective »</a></p></div>]]></description>
            <link>https://uxdesign.cc/creating-objective-personas-with-multiple-correspondence-analysis-12ddf4623f05?source=rss-3c7eb7288686------2</link>
            <guid isPermaLink="false">https://medium.com/p/12ddf4623f05</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[segmentation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Stu Church]]></dc:creator>
            <pubDate>Fri, 14 Aug 2020 14:38:36 GMT</pubDate>
            <atom:updated>2023-11-27T10:57:08.864Z</atom:updated>
        </item>
    </channel>
</rss>