<?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 Catherine Hills on Medium]]></title>
        <description><![CDATA[Stories by Catherine Hills on Medium]]></description>
        <link>https://medium.com/@daughterofbev?source=rss-4f6c71dafff9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*X6b_Oo40Pf2iY--DIJyq7g@2x.jpeg</url>
            <title>Stories by Catherine Hills on Medium</title>
            <link>https://medium.com/@daughterofbev?source=rss-4f6c71dafff9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:07:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daughterofbev/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[Will software eat itself?]]></title>
            <link>https://medium.com/@daughterofbev/will-software-eat-itself-93f9f66327b3?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/93f9f66327b3</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 22:04:15 GMT</pubDate>
            <atom:updated>2026-09-16T12:46:55.735Z</atom:updated>
            <content:encoded><![CDATA[<h3>Will Software Eat Itself? How “product” and “skills” became a prefix for work that has always existed</h3><h4>The fourth in a series about the both/and scenario of designed operations and the intelligent use of people to design AI</h4><p>Many roles are now “AI exposed” even though I, amongst other voices, see the changes differently and from a view of possibility and agency. I believe that design and other disciplines still have an important role in software and the development of artificial intelligence, and can help ‘make the world a better place’.</p><h3>The beauty of hindsight</h3><p>The title for this next article in this series is riffing off a band title, <em>Pop Will Eat Itself</em>.</p><p>Otherwise known as PWEI, PWEI were a band who I enjoyed in the 90s, giving away my age, no botox here. PWEI as they were otherwise known sounded cute, but evolved as artists in Thatcher’s Britain and mixed in political messages and witty commentaries on contemporary culture into their music and message, capturing a strong fanbase globally.</p><p>Like PWEI, SWEI, <em>Software Will Eat Itself</em>, also sounds cute, until you look under the hood.</p><p>Before I begin, I am relating opinions from my perspective and am more than happy to discuss this with you, dear reader, to add a touch of Bridgerton, should you wish to reach out.</p><p><em>I’d also like to add a disclaimer, this post isn’t anti-product. I have worked in product, strategy and design and research for most of my career. It’s a perspective on what has happened to design in the software industry.</em></p><p><strong>My lens on the introduced SWEI problem</strong></p><p>I am an experienced executive leader, consultant and adviser. I have served as a designer, educator, researcher, experience strategist, operations and change and transformation specialist. I have applied design and research in many multi-sector environments from SaaS to retail, education and financial services to the public sector, and have served as both a practitioner and capability leader in local and global product and technology teams or organisations.</p><p>Although trained as a designer and oriented in design and development since the beginning of my career in digital and software, and also, originally in fine art, I would also consider myself a product leader. I have since completed a Masters by Research in information systems and am currently on a break from a PhD investigating the design of AI and robotic systems through the lens of compassion, design and ethics.</p><p>I have served in product leadership teams and advised to executives in excess of two decades. A good portion of the research to strategy work I have directed, even in part, has informed a vision, roadmap and delivery pipeline, from opportunities and themes to initiatives to epic-level discovery or design sprints, and team-led execution.</p><p>Almost all of this work was human-centred and experience-led, using design research and mixed-methods research approaches. I have created opportunity sets, written jobs to be done, set prioritisation frameworks, sequenced and broken down initiatives, epics and user stories, sliced features, built capability and have been involved at every step of the strategy to delivery lifecycle. And although I have served in product leadership, I have never held a ‘product management’ job title.</p><p><strong>Design, product and AI</strong></p><p>In prior articles, I described how the design disciplines and sub-disciplines interact with current and new software such as forms of artificial intelligence (AI), from model decision making to making the outputs associated with machine learning, generative and agentic AI.</p><p>This article relates to the operating model I’ve designed which supports the design of safer AI software and relies on multi-disciplinary human involvement.</p><figure><img alt="The Six Phases — Design X AI 1. SENSE — Situate the challenge 2. FRAME — Set what &amp; why 3. BUILD — Structure the how 4. MAKE — Shape the surface 5. SHIP — Go live safely 6.EVOLVE — Feed back to SENSE 7. DESIGN — Design as a meta-band, running around every phase, also connecting to OUTCOMES OUTCOMES — Community, Planet &amp; Society www.cathhills.com © Catherine Hills 2026" src="https://cdn-images-1.medium.com/max/1024/1*ZQp9zIoAaq-dx_ZOb92yRQ.png" /><figcaption>Design x AI Operating Model 1.3</figcaption></figure><p><strong>How it relates to this article</strong></p><p>In this article I will discuss the workforce convergence and dilution of skillsets through the software industry’s power structures and use of automation. Part of this discussion will look honestly at how “product” or “skills” became a prefix for work that has always existed and must be human-originated. The disciplines I will focus on are design and product management, but I also consider other peer disciplines.</p><h3>Introducing the product re-labelling and re-skilling problem</h3><p>Open any software industry product job advert and you’ll find a set of terms presented as if they were invented inside the product discipline: product design, product delivery, product discovery, product strategy, product research, product marketing. Underneath these sits a second layer of frameworks and tools (e.g., product requirement documents, product evals, product roadmaps, product jobs, product taste, product sense) presented with the same tone of product-native invention.</p><p>While product management may have unique characteristics, not one of the aforementioned prefixed terms and it’s meaning is original or unique. Furthermore, not one of the frameworks or tools I mentioned are native to product management. The originating disciplines themselves <strong>still exist</strong>. Design, research, delivery, strategy, marketing, and engineering all continue to exist as independent disciplines and established, and diverse, professional fields, all with their own training, literature, and practitioners.</p><p>Why this product-prefix is happening, I believe, is not a natural evolution of discipline reinvention. “Product”, like “Technology”, is now a professionalised and centralised organisational power in software organisations. Product and technology organisations over the recent decade and a half, have become the common naming convention for two side by side organisational capability verticals in many of these companies. As with other disciplines, such as marketing, in many of these structures design has become a subordinate, often, in contemporary software, when embedded, a diluted discipline reporting into ‘Product’.</p><p>‘Product’ has since borrowed the methods of the aforesaid disciplines and reissued them under a ‘product’ label, often presenting them as though product invented them. However, the underlying practice, and often the practitioners themselves, whilst still evolving, still exist, often with deep valuable and relevant expertise. The label, however, and who now gets credited for it, has changed. And many folks outside of or new to software and artificial intelligence may not have a wiser understanding.</p><p>The implications of product prefixes are more than semantics. The impact of this seeming innocuous language and labelling shapes who gets hired, whose expertise counts as foundational rather than optional, who reports to whom, and increasingly, whose codified knowledge is available to be automated out from under them. A true rug pulling situation, and quite destablising for the many skilled professionals in software.</p><p>Furthermore, the frontier AI company and LLM marketing mandate of ‘abundance’, and ‘progress’, is in reality attempted industrial scale competitive automation of many already appropriated human roles. I believe this is a form of ‘workplace engineering’ which ultimately undermines diversity in organisations.</p><p>This is in fact a problem not only for these organisations but society as a whole. Many human workers in highly skilled professional fields, such as design, do not appear to be protected or redeployed, or furthermore, valued, in software. And a compounding factor is that when a company builds its whole structure around just two functions, “Product and Technology”, everything else (e.g., established professions including design, research, marketing, ethics, delivery, support) is pushed into a supporting, then automated or optional category by default.</p><p>It is truly ironic, that as a result, many organisations in software are now being criticised or even litigated against for poor design choices. Narrowing an organisation’s core to “product and technology” reduces diversity and who counts as core staff, which should raise alarm bells, not just about where good ideas come from, and also highlights a significant and critical risk, where investment is needed, who influences the way decisions are made and how these software solutions are designed.</p><p>Like ‘green washing’ and sustainability, I see this as the great “product and technology washing” of design and other professional disciplines in software. Software is eating itself. Not only am I wondering if this will be regulated and when this will stop, but consequentially, I am still attempting to understand why any of this is currently considered normal or ok.</p><h3>The tale of two definitions</h3><p>Design is a rich, diverse, and established field, built upon research-informed theory, philosophical debate, and the ‘shoulders of giants.’ When we look at how contemporary software professions have evolved, we see a stark contrast between established professional standards and modern practitioner definitions.</p><p>Consider the International Organisation for Standardisation (ISO) definition of Human-Centred Design:</p><blockquote>Example 1: <strong>Human-centred design (HCD)</strong></blockquote><blockquote>An approach to designing interactive systems that centres on the needs and characteristics of the people who’ll use them — applying human factors, ergonomics, and usability knowledge to make systems usable and useful, improve wellbeing and satisfaction, and reduce the risk of harm.</blockquote><blockquote><em>ISO 9241–210:2019, Ergonomics of human-system interaction — Human-centred design for interactive systems</em></blockquote><p>Contrast this with the industry’s default definition of software Product Management:</p><blockquote>Example 2: <strong>Product Management</strong></blockquote><blockquote>The job of a product manager is to discover a product that is valuable, usable, and feasible.</blockquote><blockquote><em>Martin Eriksson</em></blockquote><p>The irony here is significant. You may not be aware that the contemporary product mandate is lifted entirely from IDEO’s famous <a href="https://designthinking.ideo.com/introduction">Three Lenses of Innovation</a>. IDEO has practised human-centred design since 1978, and its co-founder, David Kelley, pioneered these concepts at <a href="https://dschool.stanford.edu/">Standford’s d.school</a>, long before “product discovery” became a software buzzword. Similarly, the <a href="https://www.designcouncil.org.uk/resources/the-double-diamond/">UK Design Council</a> conceived the Double Diamond framework in 2004, now relabelled and modernised appropriately, mapping the systemic journey of discovering and defining problems before designing and delivering solutions.</p><p>By taking these holistic design frameworks grounded in the human experience and psychology, and compressing them into the transactional language of a product backlog, the software industry did not invent a new methodology. It merely appropriated an existing one, renamed it, and handed the driving wheel to a product manager.</p><p>This is not a sustainable model of behaviour. The software industry is expecting less human involvement through the development of skills and automation, and one person or a single role is responsible for much more decision responsibility than, often, their expertise supports. For people with less expertise, this makes enterpeneurship more accessible, which is at once positive, but the flipside is less so. These generative technologies and automations do not scale well, particularly with an exclusive ‘product’ lens, which I will explain further in this article.</p><p>While I am arguing that product managers are not designers, they are important stakeholders to a design decision. Unfortunately, the product operating model attempts to make other disciplines subordinate to product, instead of retaining discipline and peer autonomy, whilst sharing a common mission and mindset.</p><p>Notedly, this was one of the strengths of the <a href="https://agilemanifesto.org/">Agile Manifesto</a>.</p><p><strong>The dilution of intent: ‘Product Jobs’ versus causal theory</strong></p><p>This pattern of professional appropriation is starkly evident in the software industry’s treatment of <strong>Jobs-to-be-Done (JTBD)</strong>. Originally developed through Clayton Christensen’s groundbreaking innovation research and published in <em>The Innovator’s Solution</em> (2003), JTBD was conceived as an application of the causal theory of human behaviour. JTBD theory sought to understand the deep emotional, social, and psychological reasons why a customer ‘hires’ a solution to make progress in a specific challenge.</p><p>Yet, within contemporary product practice, it appears that this expansive methodology has been thoroughly misunderstood. Enter “Product Jobs” or “Job Stories.” These are rigid, templated statements (<em>“When I am in a certain situation, I want to perform an action, so I can achieve an outcome”</em>), the framework has been conflated with standard Agile user stories.</p><p>What the modern product operating model labels as a “product job” is almost always a superficial task description, such as exporting a report or clicking a menu item, rather than the complex causal mechanism Christensen described. This semantic simplification strips the theory of its analytical substance, leaving behind a relatively hollow template.</p><h3>The problem of the ‘product’ operating model</h3><p>Now, product framing is landing software in hot water. The product operating model has become a dominant approach but this has resulted in a loss of discipline independence, skillset dilution, and reduction of diverse discipline autonomy. Further, I have noticed, people who work in ‘tech’, aka. software, forget that what they are designing and building are not always products.</p><p>This statement from Don Norman, expands the remit of design in the new software and frontier AI context, but is not holistic to all applications of design which I will next explain.</p><blockquote>We are no longer designing products or interfaces; we are designing the systemic feedback loops that govern human behavior, resource distribution, and digital ethics. When you design a system of that scale, every pixel is a policy, and every algorithm is an environment.</blockquote><blockquote>— Don Norman</blockquote><p>Let’s look at different kinds of applications of design in software and why the product lens is limiting.</p><p><strong>Products</strong></p><p>A product is a discrete, bounded, often narrow entity, designed to help a specific user or solve a problem in a transactional manner. Products are linked to revenue and short term optimisation. They are governed by tight feedback loops and business outcomes. Treating a whole system, platform or service like a product simply does not work.</p><p><strong>Platforms</strong></p><p>Platforms are not products, platforms are part of ecosystem building blocks. Platforms are infrastructure, that support multi-sided exchanges, and others to build, trade, create or connect. They provide the foundational architecture, protocols and standards to support diverse channel interactions, and ecosystem involvement. Platforms need to be built appropriately, with flexibility, stability and ergonomics. Platforms cannot be treated as a standalone application or optimised for feature output over structural stability.</p><p><strong>Services</strong></p><p>Services are not products that ship, rather, services evolve along a journey. Services are holistic, and end-to-end, with multiple touch points, people, actors and functions as well as interdependencies, and support complicated front stage to complex back stage orchestrations. Services are not just a digital interface, they are multi-layered, and matrixed. They cannot be built like a digital product, because they also incorporate operational workflows, however a digital product may or may not be a component of a service.</p><p><strong>Systems</strong></p><p>Systems are not products. They are interconnected and dynamic organisms. Systems are made up of a web of actors, structures, policies, and non-linear feedback loops. Systems can be complex and even chaotic. Where one lever is pulled, it may have predictable or unpredictable reverberations, results or consequences elsewhere in the system. Systems require evaluation, stewardship, continuous balancing and ethical principles, governance and forecasting, as well as monitoring. Narrow Language Models are complicated less complex systems. Frontier AI and Large Language Models are an example of a complex adaptive system.</p><p>I have not included other kinds of design here. Yes there are more, this is not an exhaustive list.</p><p>Now let’s look at the product prefix application.</p><h3>Examples of the product prefix</h3><p><strong>Delivery </strong>compared to: <strong>Product Delivery</strong></p><ul><li>Project and program management (e.g., planning, sequencing, and shipping work) has traditions going back to PMI and PRINCE2.</li><li>Product delivery reframes standard delivery management as a “product” specialty; usually it’s delivery management now sitting under a product reporting line, not a new skill.</li></ul><p><strong>Design Thinking </strong>compared to: <strong>Product Discovery</strong></p><ul><li>Design thinking is a human-centred design process popularised by the UK Design Council, IDEO and the Stanford d.school in the 2000s. It is a form of participatory design that emerged in Scandinavia in the 1970s. Design sprints were also popularised by Google Ventures and these incorporated frameworks like the Double Diamond and design thinking.</li><li>Product discovery is Marty Cagan’s SVPG framing recasts the same diverge then converge process as a distinct “product” activity, separate from design.</li></ul><p><strong>Peer Functional Strategies</strong> compared to: <strong>Product Strategy</strong></p><ul><li>Peer functional strategies (e.g., design strategy, engineering strategy, marketing strategy) belong to each function (e.g., design, engineering, marketing) and set their own strategy beneath overall business strategy. Design strategy directs craft and experience investment, engineering strategy directs technical architecture and platform investment, marketing strategy directs positioning and channel investment.</li><li>Product strategy treated as senior to, rather than a peer of, the others in product and technology businesses. It becomes a parent strategy and a dependency.</li></ul><p><strong>Research</strong> compared to: <strong>Product Research</strong></p><ul><li>Research, including market research, ethnography, human factors, commercial and academic disciplines with twentieth-century roots.</li><li>Product research and UX research splits general research practice into product-specific labels, often carried out by researchers trained in the original, broader discipline but often reduced to product manager-led customer discovery sessions or synthetic AI research.</li></ul><p><strong>Marketing</strong> compared to: <strong>Product Marketing</strong></p><ul><li>Positioning, messaging, segmentation, go-to-market have been formalised in marketing theory since Kotler and mid-century marketing practice.</li><li>Product marketing reduces general marketing craft to a single product line; segmentation, messaging frameworks, and launch sequencing are inherited directly from classical marketing, not newly developed in product teams.</li></ul><p><strong>Software Engineering </strong>compared to: <strong>Product Engineering</strong></p><ul><li>Computer science and software engineering (e.g., architecture, systems design, implementation) has a decades-old professional and academic lineage.</li><li>Product engineering reframes engineers on product teams as accountable for product outcomes rather than technical specification alone, however prior to this framing, UX and design did this as part of the system of work.</li></ul><p>The same pattern of unattributed borrowing of existing frameworks and tools applies, and it’s worth separating them out as implementation-level tools rather than discipline equivalents.</p><p><strong>Evaluation Research and Testing </strong>compared to: <strong>Product Evals</strong></p><ul><li>Evaluation research and usability testing (HCI, statistics, 1980s-90s); in AI specifically, systematic model performance testing draws on ML evaluation methodology.</li><li>Evals is product language for user testing and validation, or AI model performance testing. It is an implementation method drawn from evaluation research, not a discipline in its own right.</li></ul><p><strong>Business Analysis and Requirements Engineering</strong> compared to: <strong>Product Requirements Document (PRD)</strong></p><ul><li>Requirements engineering and business analysis – specifying functional and non-functional requirements, formalised in software engineering since the 1970s-80s.</li><li>PRDs are emerging as standard artefact for scoping a feature: goals, user stories, acceptance criteria. The same discipline business analysts and systems engineers already practised, now scoped to a single feature.</li></ul><p><strong>Opportunity Spaces</strong> compared to: <strong>Opportunity Solution Trees</strong> also named <strong>Product Opportunity Trees</strong></p><ul><li>“How Might We” ideation statements, a technique from design thinking traced back to Procter &amp; Gamble in the 1970s and popularised by IDEO.</li><li>Opportunity Solution Trees were pioneered by Teresa Torres to structure product discovery work. The tree organises discovery by placing an outcome at the top, which branches down into the opportunity space (customer pain points), followed by solutions and experiments. Torres’s framework deserves credit as a highly effective, product-specific synthesis; it bridges traditional design thinking techniques with continuous product execution. Often, however, in product circles the design thinking background is not acknowledged.</li></ul><p><strong>Visual and Brand Design</strong> compared to <strong>Product Taste</strong> or <strong>Product Sense</strong></p><ul><li>Visual and brand design craft (typography, composition, brand systems) plus qualitative research judgement – trained skills with their own teaching and critique traditions.</li><li>Framed as an individual, near-innate instinct held by strong product leaders e.g., “good taste,” “sharp product sense.” Repackages trained aesthetic and research judgement as personal intuition, detaching it from design and research expertise. Problematic, because instinct can’t be credentialled or questioned, and reduces the value of a design or research qualification that in fact builds intuition through expertise.</li></ul><p><strong>Jobs to be done (JTBD) </strong>and<strong> Agile User Stories </strong>compared <strong>Product Jobs</strong></p><ul><li>Clayton Christensen’s innovation research (developed with Anthony Ulwick, formalised in <em>The Innovator’s Solution</em>, 2003) is a causal theory of <em>why</em> customers <em>hire</em> a product to make progress in a specific situation.</li><li>Commonly reduced in product practice to “product jobs” or job stories – templated statements (“when I ___, I want to ___, so I can ___”) that are really just user tasks. This is a watered-down version of Christensen’s theory, conflated with user stories not an application of it. What’s called a “job” in most product usage is a task description, not the causal mechanism Christensen described. The simplification strips out the theory’s substance while keeping its name and borrowed authority.</li></ul><p>An anecdote:</p><blockquote>A half-day of research training doesn’t make anyone a research expert, any more than a half-day of design training makes someone a designer, marketer or a product manager. The relabelling with a product prefix doesn’t just rename research, it minimises the training and expertise required to be an expert researcher, because “product research” implies a skill any PM can pick up as a side competency. “Research” as a standalone discipline requires years of methodical academic training.</blockquote><h3>The colonisation of context</h3><p>The strategic flattening of adjacent disciplines into product-prefixed roles can be viewed as an active colonisation of organisational context. Driven by the deliberate “workforce engineering” of tech organisations, this architecture creates a semantic environment where every architectural asset, human interaction, and feedback loop is reclassified as “product-owned.”</p><p>Through this mechanism, the product operating model successfully establishes a singular hierarchy of ownership and governance, resulting in the systemic dissolution of surrounding professions. This positioning frames the product arm of a software enterprise as the ultimate arbiter of value, rendering mature disciplines outside of product — for now — as inappropriately subservient to a singular mandate.</p><p>Within the design realm, this dynamic reduces the design practitioner to isolated, pixel-production decision-making, severely diluting the strategic decision making input an experienced designer can make, even though interaction and visual design are nuanced and important sub-disciplines. It also reduces the scope of the design capability. And while product managers are not designers, the foundational models popularised by Eriksson and Cagan may have been weaponised to absorb and dilute the contributions of independent disciplines.</p><p>Furthermore, by aggressively cutting resources and absorbing external frameworks, methods, and skillsets into a single product management umbrella, organisations create a “totalisation” effect. This engineering of a single-prefixed overarching “product” discipline yields dangerous consequences, laying the groundwork for a hollowed-out “skills creation” paradigm designed to automate the very professional contributions it has just finished incorporating.</p><h3>The counter view: a natural evolution in software?</h3><p>Natural field evolution has a recognisable pattern in that new terms emerge to name genuinely new practice, credit tends to flow towards whoever did the original work, and the exchange runs in more than one direction over time.</p><p>What’s described above doesn’t consistently have that shape. The direction is one-way (e.g., design, research, delivery, marketing, engineering, and business analysis) have all in some way shape or form been renamed into product. Product terminology hasn’t, yet, over the same period, been absorbed back into those fields.</p><p>The renaming demonstrates changes in organisational power (e.g., product’s control of roadmaps, budget, and headcount) rather than where underlying innovation happened. Again, think Christensen’s Jobs to be Done research and IDEO’s Three Lenses of Innovation predate their “product” versions, sometimes by decades.</p><p>However, the practitioners doing the work are still, but often less so, the same people who did it under the original name. Sadly, in software, this has had a consistent effect: whoever controls the relabelling gets to write the canon, run the organisation, and define seniority, while the discipline being absorbed has to argue and advocate for the recognition of expertise it already had and still maintains in the rest of the world.</p><h3>Codification exposure</h3><p>This intentional hollowing of discipline autonomy reaches its logical conclusion in the current wave of algorithmic automation. I would like to call out that this playbook is cyclical and unpleasant: first, the product operating model isolates a complex, highly specialised discipline, such as design, qualitative user research, or technical delivery, and strips away its strategic, systemic dimensions. In the case of design, it forces a rich, human-centred, philosophical and technical practice into a hyper-localised, mechanical execution layer.</p><p>Many design leaders have commented on this risk: design, instead of evolving its remit and application more fully, which as a discipline design is naturally attuned to, desgin is reduced to automating its own reduced application. This might show up as less design and more selection, whcih moves design from design to taste (e.g., selecting UI components from a pre-baked Figma library). This devolves the design capability to less design and more production ‘upskilling.’ It also results in design becoming competitive with peer disciplines such as product (e.g., when a product manager or another colleague uses a generative AI design tool incorporating that very library’s codified knowledge). Research is flattened (e.g., via skills based rules, running rapid, binary user-testing scripts or prompts). The shift here is also interesting, in that in the past for design tooling, often the most sophisticated yet usable tool was the preferred one, now the bias has shifted to fast output over human design origination or involvement. This is an analogy for most professions where skills are watered down — the very skills spent years crafting and developing ‘intuition’ around.</p><p>By reducing these holistic disciplines such as design to a repetitive, assembly-line cadence, the product ecosystem successfully manufactures a false perception that these roles are merely mechanical, low-leverage execution tasks. And it limits the potential not just of individuals in professional roles, but possible outcomes they drive and potential of the outputs they create. For example, the process of ideation or design, also, often requires drawing and pen and paper thinking. Multiple studies have demonstrated this improves creativity, learning and innovation potential. Yet the common belief, while I do support the inclusion of ideas coming from many sources, is that generative AI tooling and automation will amplify creativity.</p><p>Once a discipline, such as design, has been thoroughly diluted and commoditised in this manner, it is ripe for structural elimination. Organisations are actively utilising this artificial simplicity to justify the creation of automated “skills” engines. By feeding these narrow, stripped-down tasks into generative AI pipelines and automated workflow templates, companies claim they can bypass the need for experienced practitioners entirely. A product manager, armed with an AI copilot, is told they can now generate prototypes or synthesise research independently.</p><p>This is the ultimate danger of the “totalisation” effect: it creates an echo chamber of engineered mediocrity. It replaces deep ethical forecasting, relational empathy, and structural systems design with a frictionless pipeline of automated outputs. The software organisation celebrates the immediate speed of these automated inputs, remaining entirely blind to the fact that they have systematically eradicated the very human expertise required to prevent architectural debt and societal harm.</p><blockquote>Tacit, uncodified expertise is valuable, and organisations are at risk of forgetting this.</blockquote><p>I’d like to reiterate that designers who build software and artificial intelligence systems are doing genuinely valuable work. However turning tacit expertise ( human-input, rules, ethics, values, patterns, decision-making, inclusive design) into not only usable solutions but systems design has consequences. Codifying expertise also makes it transferable in a new way. If design is however reduced to pixel selection, this is different. This is why many a design leader and influential professional figure is lamenting the reduction of design to visual design only, even though visual design is critically important!</p><p>This is given once a design system or pattern library exists as a structured, documented asset, it becomes exactly the kind of thing that can be packaged into an automation tool that runs against it without needing the person who built the judgement behind it. It is different when designers own these systems. They can evolve them. However that means evolution and decision making is difficult to manage and articulate and as I’ve said in multiple commentaries, that needs to be design and human led, and design governed, because designers have the expertise to do so. Perhaps in partnership with engineers. And of course as this kind of tool has become an enabling service to the entire product and technology organisation, then a product manager.</p><p>However, the organisation believes now they have a system, like a design system, the buck stops there. That is because the reductive mental model of design is the pixel creation. And then the automation and production through generative AI. The irony is that other disciplines, including product or technology people, face the same exposure from the artefacts they’ve been busy relabelling as their own.</p><p>Code standards, code snippets, components, product requirement document templates, product discovery playbooks, product prioritisation frameworks, product opportunity trees. Writing these down and standardising them is good practice. But automation hides the skills, makes them less teachable to a machine or learnable for a junior hire. Tacit, uncodified expertise is valuable for many reasons, and organisations are at risk of forgetting this.</p><h3>Safety, and conduct, first</h3><p>Designers, nor other established professions, should not be made redundant, or indeed “product and technology” or “AI” “washed” they should evolve. Judgement, testing assumptions, and navigating messy stakeholder situations, and wicked problems, involving tacit information sharing and relational exchanges, all central to design work, aren’t reducible to a codified artefact.</p><p>It’s worth being again reflective here, the very act of packaging expertise into frameworks and documentation, the thing both product and design, as well as engineering, disciplines in software have spent the last decade doing as part of best practices in record keeping, to be more “scalable”, is also what leaves that expertise most exposed to automation.</p><p>‘Product’ isn’t exempt from the automation. Without a promotion of diverse disciplines, it seems that the race to be the ‘last person standing’ is really shortchanging the next generation of software technologists who might be interested in design or product or indeed other evolving sub-disciplines emerging from these professions.</p><p>The prefix, absorption and appropriation behaviour, reducing designer headcount in software, disadvantages design and indeed the organisations this is occurring in. It diminishes the potential of great design to happen, and that shortchanges a duty of care in software and reduces the potential for multidisciplinary teams to develop real solutions that enable human flourishing.</p><p>As I reminded readers in my prior article, “<a href="https://medium.com/@daughterofbev/how-to-check-your-ai-system-still-matches-your-values-f31d528b412b">How to Check Your AI system Still Matches Your Values</a>”, the software industry and businesses have the opportunity to do this differently. As mentioned in the prior article, <a href="https://hai.stanford.edu/ai-definitions/what-is-human-centered-ai">HCAI or HAI</a> is:</p><p><em>An approach to AI that prioritizes human needs, values, and well-being throughout the development and deployment of AI systems. HAI prioritizes collaboration between humans and machines, ensuring that technology is developed with empathy, ethics, and user experience in mind. HAI integrates insights from fields like computer science, psychology, ethics, and design to build systems that are trustworthy, inclusive, and aligned with societal goals. — </em><a href="https://hai.stanford.edu/ai-definitions/what-is-human-centered-ai"><em>Standford University HAI</em></a></p><p>I’d also like to emphasise – this article is not about accusing product management of being ‘meanies’ or claiming ill intent towards any individual product leader. However, my intention is to speak truthfully about a single-directional, power-tracking, credit-erasing pattern. This pattern is a different thing from disciplines genuinely converging and cross-pollinating.</p><p>It’s worth paying attention to this now, rather than defaulting to “evolution,” which actually, is professional gaslighting. None of this is saying product management as a role is not relevant or valuable, or that genuine new practice can come from it, particularly around <em>prioritisation at scale</em> and <em>cross-functional alignment</em> to value. However, what value is that? That is what I’m querying here.</p><blockquote>In this world of generative tooling, the control around what is automated and what should not be automated should be controlled by the profession that invented it.</blockquote><p><strong>What we need to think about</strong></p><p>My argument is that when a term, framework, or skill gets a “product” label, or another, it’s worth asking whether something new was created, or whether an existing discipline’s practice, tools, and people were absorbed and their origins removed and the lineage of knowledge broken. This matters for hiring, for career fairness, for who’s left exposed when codified expertise gets automated, and for the profession and software industry’s professional integrity.</p><p>The solution is not by naming the design, research, strategy, delivery, and business-analysis professions with a ‘product’ prefix. Or indeed potentially automating a skill. In this world of generative tooling, I believe the control around what is automated and what should not be automated should be controlled by the profession that invented it. The solution is to be responsible and credit the practitioners who built that expertise and the frameworks, and honour their skills and experience.</p><p>There is a real dilemma when the workforce or the profession does not feel in control of their outcomes. Conduct is important and that also relates to internal systems change and workforce transformation. Many people I speak with lament the ‘world of work’ we are in. Core values such as dignity, respect and autonomy deserve attention.</p><h3>The end of the assembly line: reclaim the discipline? Or accept the changes?</h3><p>When I look beneath the veneer of the “product operating model”, I find that its ultimate consequence is an acute vulnerability to the very automation the ‘software’ and ‘AI’ tech industry now mandates, and diminishing towards the very professions and colleagues that were so great to start with. It’s worth sitting with.</p><p>By stripping design, research, and delivery of their respective professional discipline’s autonomy, reducing them to a series of prefixed tasks like “product discovery” or “product taste” in pixel production, the software industry has accidentally tripped itself up.</p><p>Ultimately, it may not matter if it design shows up as ‘product’ or not, but it will matter if expertise is undone. The software industry has diluted deeply creative, ethically matrixed human practices into rigid, predictable assembly lines. Furthermore, if a job has been engineered to look like a predictable assembly line, it becomes remarkably easy to convince an executive that an LLM can do it for a fraction of the cost.</p><p>This is the reality of the frontier AI “abundance” narrative. It is the industrial-scale human-competitive automation of roles that are becoming deliberately diluted ahead of time. When companies claim that product managers or other roles equipped with generative AI can now independently run research synthesis or generate user interfaces, they are celebrating an echo chamber of engineered mediocrity.</p><p>A narrow language model can mimic a standardised product template, but it cannot exercise ethical forecasting. A large language model cannot navigate a chaotic social ecosystem. It cannot hold space for the complex, matrixed human interdependencies that define a true service or system. However, both NLMs and LLMs have their uses. The designed intent is what drives better outcomes.</p><p>Despite the potential possibilities or degradation of design and other professional disciplines, we must stop pretending that this “product and technology” or “AI” “washing” of established professions is a normal or healthy evolution. The dilution of important, nuanced skillsets is a critical risk to innovation, a degradation of organisational diversity, and a direct threat to the safety of our shared digital environment.</p><blockquote>It is time to look beyond the bounded limits of the product operating model and remember what we actually do: we design the systemic feedback loops, the relational journeys, and the architectural foundations of our world.</blockquote><p>To the designers, researchers, and specialists who feel “AI exposed” under this unfortunate mandate, the path forward is not to become better cogs in the machine. The path forward is to assertively reclaim our discipline autonomy, even if it has been renamed ‘product’ or downplayed as an AI ‘skill’. We must stop letting our discipline be colonised by a transactional vocabulary.</p><p>It is time to look beyond the bounded limits of the product operating model and remember what we actually do: we design the systemic feedback loops, the relational journeys, and the architectural foundations of our world.</p><p>I would also like to say that designers, and anyone who conducts design, have a responsibility to evolve too. It is not enough to sit on our laurels and rely on synthetic research or the AI rendering of an interface, without the thinking first. Not all ‘design’ is suitable for software, and designers need to learn the context to apply their discipline to it.</p><p>This does not mean the tools or replicable methods and frameworks take over, this means revisiting what design is, and undertaking appropriate research and speaking with people to meet HCD ISO and HAI standards in software.</p><p>I’ve worked with many fantastic product partners who understand the value of design. However, because of said practitioner influencers, many product managers opt for the “CEO of the product” mindset, as endorsed by many product thought leaders. Product managers are not always designers, and if product management went back to its roots it may more healthily and sustainably evolve the role into something that makes sense, is sustainable and uniquely valuable in software.</p><p>Furthermore, designers, researchers and indeed other professions who interact with software must enact change, either in themselves by considering the stay or go question, or by taking control moving forward in situ or in a different direction.</p><p>It is incredibly difficult to change the status quo in existing organisations without forward-thinking boards or executive investment, however, demanding honesty is a great start.</p><p>There is the value of our established professions to lean on. Acting with agency, means looking forward to where we wish the design profession, and related professions must arrive in the future.</p><p>In conclusion, ask yourself this: What makes a great professional partnership and journey, and is that being realised with the company, and colleagues you work with, or with the AI services you use as execution partners or copilots?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93f9f66327b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why AI Projects Need a Loop, Not a Straight Line]]></title>
            <link>https://medium.com/@daughterofbev/why-ai-projects-need-a-loop-not-a-straight-line-6edf5b59f3c1?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6edf5b59f3c1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 21:44:57 GMT</pubDate>
            <atom:updated>2026-08-27T10:20:04.760Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The third in a series about the both/and scenario of designed operations and the intelligent use of people to design AI</strong></p><p>This week I’ve been running some simple tests on trust and search as a consumer, simply using the Google Search and Gemini in AI Mode. I initiated this test after speaking with a person who I respect and trust, one of the best people I’ve ever had the privilege to work with and someone who is wise and empathetic. Someone who noticed a mischaracterising pattern on search and worked out a way to solve it.</p><p>Note: if this happens to you, I am happy to refer you to my contact should you require advice, but before I retell this scenario and personal story, let’s talk about UX anti-patterns.</p><h3>UX anti-patterns as anti-social values derivative</h3><p>In the older terminology of user experience design, we used to call these instances ‘anti-patterns.’ Detectable or undetectable software user experience events, interface issues or system patterns that are undesirable and appear uncontrolled, yet exist because they haven’t been captured or prioritised as a mistake to fix.</p><p>Anti-patterns sometimes show up in the interface, so they appear to be a design mistake. If an organisation is unaware of these issues, I’d consider this an error of judgement or oversight, if it hasn’t been discovered yet, or serious neglect, if it has and the organisation hasn’t fixed the issue. I’d argue that most people who call themselves UX folks, who are designers, researchers, ethicists, change managers or someone with moral fibre or leaders with moral responsibility, would want to fix these issues.</p><p>However often, for example, designers, as is well recorded, are often not in charge of an organisation, and not always in charge of the endorsement of proposed designs. So when we say the design outcome or event is poor, it may well be. A poor decision is can potentially be a symptom of systemic interactive non-intentionally harmful decision matrixes. And poorly designed decision systems. Or it can simply be irresponsible.</p><p>Designers and systems thinkers who are ethical and human-values aligned could help with this — however this is, at times, not enabled despite best efforts, so let’s not blame the designers. Let’s blame the rigour of the organisation and the organisation’s investment in safety by design.</p><p>Right now, Anti-Patterns are happening alot more often, are often unmitigated and having societal impacts that are on a spectrum from good to bad. Our media focuses on the bad and controversial.</p><p>Quite rightly so, as social impacts and corporate responsibility issues need to come to light. However, we do have agency and choices, and decision makers must be suitably accountable, and their systems designed to fix problems of misuse.</p><p>Example 1: Social Media.</p><ul><li>Facebook helps save lives and find loved ones during disasters such as tsunamis or earthquakes, versus</li><li>Facebook harms millions of young people through endorsing harmful advertising and content through algorithm design choices.</li></ul><p>Example 2: Large language models vs small language models.</p><ul><li>SLMs assist climate scientists to model large complex bodies of data to understand new insights around climate behaviour, or by researchers to more accurately diagnose skin cancers saving lives, versus</li><li>LLMs can be used by bad actors for fraud, illegal activities, or warfare potentially harming individuals, communities and society.</li></ul><h3>A short story about search</h3><p>Essentially, search listings and ‘great search’ have always been representative of the original vision of the world wide web, equity and access to information, sharing and communication between individuals, communities, networks institutions, citizens and jurisdictions, as well as with private information networks.</p><p>When I entered new media, then digital, then tech, the promise of the web was huge. It was creative, dynamic and it was an open field.</p><p>Now there are major problems. One only needs to sample the laundry list of misdeeds, poor decision making and ill use to balance out the good uses of these systems and the intent of the inventors behind these technologies.</p><p>While the intent and principles remain, alot of things have since changed. Search was the gold standard of incredible software engineering, a pinnacle of great design, equity and access.</p><p>Search engine optimisation, another professional skillset was a highly valued craft, which *could* be used for good but always towards a race to the top of the search listings. SEO, as with any tool, can also be used poorly or to support unethical practices.</p><p>While we have the ‘well intended’ web, we also have the malicious use of internet infrastructure and the unpleasant and unethical use and commoditisation of these systems.</p><p>Now, Search is adware, misinformation and increasingly, delusional. Algorithmic bias predominates. Recently in Germany, Google was taken to court and successfully litigated against for this very reason and being non-responsive to customers.</p><h3>My search story</h3><p>After chatting with my friend and former colleague, my personal brand search indexing has been surprising, amusing and at times disturbing to explore. My own content has been misconstrued, my personal brand and even writing mischaracterised. My profile has been co-mingled with other profiles.</p><p>I have used the AI Search functionality to discuss with Gemini as to why my profile, content and articles have been misrepresented. Why it is damaging to my brand. Gemini, on the same search platform as Google Search, apologised to me for mischaracterisation, but said it could not help change Google’s service.</p><p>Gemini for all it’s intelligence did not direct me to a support pathway with Google or Alphabet. It did not help me find an avenue to fix the problem. It instead told me how to correct my LinkedIn post and profile, even though there was absolutely nothing wrong with it, if an audience member bothers to read past the search listings. Which is the risk.</p><p>This is concerning, litigious territory. It’s also professionally harmful, difficult for consumers and upsetting for those represented poorly in this manner. I know I felt crappy seeing it.</p><h3>AI systems change after launch</h3><p>Many delivery projects still treat “finished” as a real, fixed state. That is how it seemed before LLMs. But it wasn’t the case as most people in software can tell you. One of the reasons the field moved to continuous agile workflows in software delivery was for this very reason. Priorly, a team — or you, yourself — built something, launched it, and it stayed roughly the same until someone changed it on purpose.</p><p>AI systems like most software, but multiply by x, don’t work that way. They respond to real-world data that keeps shifting after launch. A tool that worked well on day one can behave differently six months later — even if nobody touched the code — because the data feeding it has changed.</p><h3>Six steps that loop back</h3><p>A better approach uses six steps, and the sixth step leads straight back to the first:</p><p>1. <strong>Understand the problem. </strong>Talk to the people affected.</p><p>2. <strong>Decide what you’re building and why. </strong>Get that signed off.</p><p>3. <strong>Build the system underneath.</strong></p><p>4. <strong>Design what people actually see and use.</strong></p><p>5. <strong>Launch it safely, and keep watching it.</strong></p><p>6. <strong>Check what’s working, retrain if needed, </strong>and feed what you learn back into step one.</p><h3>Why the loop needs different people at each step</h3><p>Each of these six steps calls on a different kind of expertise. Understanding the problem needs people who can research and listen. Deciding what and why needs people who can weigh trade-offs and get sign-off. Building the system needs engineers. Designing what people experience, interact with or see needs designers. Launching safely needs people watching for what goes wrong. Checking and retraining needs people who know what “working” actually looks like for that system.</p><p>When a team flattens — when one role, sometimes silently, absorbs several of these jobs — the loop doesn’t disappear. It just runs with fewer checks. The step most often lost first is the last one: checking what’s working and feeding it back. That’s the step with no obvious owner once the specialists who used to do it are gone. A team can keep building and shipping without it. It just stops closing the loop.</p><p>This is why the team model is a design decision, not just a cost decision. The six steps are only as strong as the weakest step, and the weakest step is usually wherever a discipline was removed to save time or money.</p><h3>Who needs to be in the room</h3><p>Deterministic or older software is traceable and stable; modern AI systems are probabilistic, contextual, and harder to pin down. Their behaviour shifts with data, prompts, and orchestration, making debugging and assurance non‑local. Until monitoring matures, safety confidence comes from layered automated checks, manual verification, and imposed signals.</p><p>That’s why any suggested fix can’t be more process for its own sake. The fix is being clear about which group of people should be involved, and when.</p><p>So who needs to be in the room?</p><p>It depends on the phase and what decisions are being made. Here is an example of how it might be sped up in a virtuous and continuous loop.</p><h3>The Six Phases</h3><p><em>The Six Phases — Design X AI</em></p><ol><li><strong>SENSE — </strong>Situate the challenge</li><li><strong>FRAME — </strong>Set what &amp; why</li><li><strong>BUILD — </strong>Structure the how</li><li><strong>MAKE — </strong>Shape the surface</li><li><strong>SHIP — </strong>Go live safely</li><li><strong>EVOLVE — </strong>Feed back to SENSE</li></ol><p><strong>DESIGN (7) — </strong>Design as a meta-band, running around every phase, also connecting to OUTCOMES</p><p><strong>OUTCOMES — </strong>Community, Planet &amp; Society</p><figure><img alt="The Six Phases — Design X AI 1. SENSE — Situate the challenge 2. FRAME — Set what &amp; why 3. BUILD — Structure the how 4. MAKE — Shape the surface 5. SHIP — Go live safely 6.EVOLVE — Feed back to SENSE 7. DESIGN — Design as a meta-band, running around every phase, also connecting to OUTCOMES OUTCOMES — Community, Planet &amp; Society www.cathhills.com © Catherine Hills 2026" src="https://cdn-images-1.medium.com/max/1024/1*ZQp9zIoAaq-dx_ZOb92yRQ.png" /></figure><p><strong>SENSE — an example</strong></p><p>Let’s look at the ‘Sense’ phase as an example. It is a term that I think is well paired with ‘Understand.’ It is better to ‘Sense’ first, ‘Understand’ next, then decide whether to ‘Respond’ or not later, which if not mitigated leads to speed over substance.</p><p>In Sense, which is the understanding phase, it might be members who represent:</p><ul><li>people who think about ethics and society;</li><li>people who set strategy and rules;</li><li>people who do user research;</li><li>the technical team who build and test the AI;</li><li>the team who shape the overall experience; and</li><li>the team who design the screens and interactions.</li></ul><p>Each of these groups or people matter. As do the phases of decision making. Leave a group or phase out, and you haven’t removed a risk. You’ve just left it unmanaged.</p><p>You can see here, as I’ve said before, I haven’t said designers make all of the decisions, but designers design and contribute to this model, the decisions and the outcomes. I’ve demonstrated that there needs to be discipline in the way the operating model is designed to support better designed work systems and outcomes. It is the culture of <em>designed</em> <em>decision-making</em> and <em>design</em> that needs to be improved in AI systems design.</p><h3>Why the loop matters</h3><p>This loop lets you react quickly. A new AI model comes out. A law changes. Something goes wrong. Any of these can send you straight back to the “decide what and why” step, for the specific part of the system affected, without starting the whole project over.</p><p>A straight-line process only checks once — at exactly the point when the system is least like what it will become. A team that has kept its specialists can use the loop as intended: revisit one step, fix one thing, keep moving. A team that has flattened its way past those roles has a loop with a gap in it, and won’t find out where the gap is until something breaks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6edf5b59f3c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Check Your AI System Still Matches Your Values]]></title>
            <link>https://medium.com/@daughterofbev/how-to-check-your-ai-system-still-matches-your-values-f31d528b412b?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f31d528b412b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 11:47:58 GMT</pubDate>
            <atom:updated>2026-08-14T03:26:03.370Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The second of a series about the both/and scenario of designed operations and the intelligent use of people to design AI</strong></p><p>Last week I published an article titled <a href="https://catherinehills.substack.com/p/why-most-ai-problems-arent-about?r=2b9qm&amp;utm_campaign=post-expanded-share&amp;utm_medium=post%20viewer">Most AI Problems Are Not About the Technology</a>, both on <a href="https://medium.com/@daughterofbev/why-most-ai-problems-arent-about-the-technology-f8b74fb9e46d">Medium</a> and on <a href="https://catherinehills.substack.com/publish/post/209742275">Substack</a>.</p><p>Before designers advocated for users and insights, ‘great UX’. Now designers and multidisciplinary teams have an increased remit – to design responsible human-values-led experiences, and in the case of AI, to deliver on the promises AI Systems teams make to society.</p><p>This article will reflect on the connective tissue of a Human-Centered Artificial Intelligence (HCAI or HAI) and Values-Sensitive Design (VSD) informed six phase Design x AI operating model, the input of multidisciplinary professions, and the importance of this work now with the onset of artificial intelligence.</p><figure><img alt="Claude’s approval preferences — Manually approved is checked" src="https://cdn-images-1.medium.com/max/498/0*zcRaJlOFI7apkSOT.png" /><figcaption>Claude Approvals Preferences — August 2026</figcaption></figure><h3>It happened before, but now it’s faster</h3><p>I spent over a decade advocating for the importance of user experience (UX) design in modern software, arguing for consistency across platforms and the integration of agile and lean UX methodologies. <a href="https://www.amazon.com.au/Lean-UX-Applying-Principles-Experience/dp/1449311652">Lean UX</a> came in to support better cross functional interactions and decision making, before a pixel was created.</p><p>This was around the transition to mobile-first design, noticing the significance of collaboration between design and engineering, and the need for reusability and efficient processes in creating software experiences that met the needs of users. I advocated for a user-centered approach, ensuring that design aligns with user expectations and behaviour to enhance engagement and reduce friction.</p><p>However as is often the case, timeframes got squashed in favour of ‘efficiency’, designers had to still produce high quality research, artefacts, and testing. The n-x runway discussions got compressed to continuous discovery, lovely in principle but exhausting in reality, and at times weaponised agile theatre gave way to a whole generation of resentful unhappy people in delivery, including designers, and UX folks, who just didn’t want to work with SCRUM, SAFe or “wAgile” anymore.</p><p>The truth is designers have always been the minority discipline in delivery teams. There was a trend towards UX and UI pairs, then this was flattened to ‘Product Designers’ and ‘Product Managers’. Product Managers, many former digital project managers, and digital producers, absorbed UX-literacy into their roles. Some UI designers loved ‘Unicorn-ing’ their craft, did front-end and became design systems folks. Some more senior folks gravitated to human-centric experience strategy and service design, also the domain of analysts and consultants. UX designers also became exhausted advocating for their work and best practices, disgruntled and considered leaving design for product management. Or leaving the design profession all together.</p><p>Some actually did that. The issue is though, now, more than ever we really need designers. We continue to need skilled UX folk who can evolve their strengths and make discerning decisions about artificial intelligence usage and adoption. We still need research, ethics and usability wunderkinds. We also need creatives and the input of diverse team members. For magic ✨.</p><p>This is because design, ethics and human-centricity and indeed planet-centricity is at a critical juncture. Now the gauntlet has been lowered and the kraken has arrived — artificial intelligence. Enter classical science gone wrong, deterministic thinking in a probabilistic complex systems world. We are in the midst of change and the threshold of transformation.</p><h3>Issues of accountability and collaboration</h3><p>Additionally, have advocated for better partnerships between disciplines, acknowledgement of the end-to-end craft of design required to deliver successful software products and services. So did many other folks. I also pin-pointed the issue for designers after at the time almost two decades of delivery hands-on experience. Things were getting faster. Engineering teams needed to be ‘fed.’ Designers couldn’t be everything to everyone, however great UX still needed to happen. Personally I was also on the mouse wheel. Like many design leaders with one foot in delivery I was struggling with operational pressures, getting things done and advocacy. I wanted to liberate myself from the cycle. These slides were published just prior to my first executive leadership role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBbVqgsNge-Ujf5Mgra9IQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RtV0Dw59C7P-D3H267Vtpg.png" /><figcaption>Slides form Convergent Experiences (2017) at UX Gatherings © Catherine Hills</figcaption></figure><p>There was such a thing as the <a href="https://chiefexecutive.net/ideo-ceo-tim-brown-t-shaped-stars-the-backbone-of-ideoaes-collaborative-culture__trashed/">T-Shape</a>, a concept championed by IDEO. The T-shape examined the phenomenon of difference in the design field. See below the part of my talk on plugging the gaps. IDEO’s <a href="https://chiefexecutive.net/ideo-ceo-tim-brown-t-shaped-stars-the-backbone-of-ideoaes-collaborative-culture__trashed/">Tim Brown said</a>, “The right person for us will talk about how other people have helped them do what they have done. There is some evidence there of empathy, collaboration and interest in working with other people.”</p><p>IDEO also championed <a href="https://www.ted.com/talks/tim_brown_designers_think_big">Design Thinking</a>, a collaborative design framework that is used by virtually everyone from management consulting to delivery teams. Mind you, now apparently design thinking and the double diamond, now relabelled by the UK Design Council as <a href="https://www.designcouncil.org.uk/resources/framework-for-innovation/">The Framework for Innovation</a> is in death throes with AI, although <a href="https://www.nngroup.com/articles/design-process-isnt-dead/">NNGroup</a> say no, it is compressed,</p><p><em>“The real skill in modern design is not the ability to abandon process — it’s process literacy: picking the right approach and tool for the problem.”</em></p><p>It has become somewhat fascinating and ridiculous. At this point I’d like to reference a movement here to more humanistic thinking about roles and relational values in design and technology. During the pandemic I contemplated this problem. Read on.</p><h3>The redistribution of UX tasks</h3><p>I looked at an effective partnership between designers and product managers or for that matter any other role collaborations and overlaps in software. I found that partnership is relational and requires mutuality, or cooperation between parties. I explored how understanding each other’s roles, setting shared goals, and communicating effectively can lead to meaningful and effective relational partnerships characterised by trust and joint risk management.</p><p>The framework I designed suggested kinship is an aspect of relational roles in software that can foster mutuality between partners. With kinship and mutuality, partnerships may become more meaningful and productive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2Bn6_QJveirakRLfzUEyA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UrbS7nfjJS-Cjv2VO97PGA.png" /><figcaption>Slides from Designers and Product Managers (2021) at LAST Conference © Catherine Hills 2026</figcaption></figure><p>This requires reciprocity and it takes a few willing partners, not withstanding a village.</p><h3>Now we have generative and agentic AI</h3><p>Now we have AI, to quote <a href="https://www.amazon.com.au/Full-Stack-Human-Mindset-Technology/dp/1394346255">Dara Simkin</a>, how might we go more full stack human? The answer isn’t necessarily to take everything and make it a skill. Although agentic ‘skills’ might be helpful!</p><p>There are many useful questions to ask before creating a ‘skill.’ How long they will be helpful for is a really valuable question. As is querying the durability. This is the human values question: how many skills do we give away? What will keep us busy when we do? Do we honestly trust artificial intelligence to do our jobs well? Who reviews the skills? Is ‘automatic approval’ really ok? Do you spend more time training the machine than people? That ratio really matters.</p><p>I believe it’s a combination of these questions and understanding that artificial intelligence simply isn’t reliable yet. A human’s ability to review high volumes of AI output rapidly diminishes our ability to be credible in our review. Can we trust AI to review exclusively?</p><p>Currently — no. It’s a slippery slope.</p><h3>Where good values get lost</h3><p>Good intentions have the potential to disappear quietly.</p><p>Imagine you promise your users that your AI system will be honest but truthfully you cannot guarantee that outcome. The value that is set for the delivery is that “We will be truthful.” That promise to be truthful has to become a real, specific rule about your data and your model. Then it has to be built into how the system actually responds. Skip a step, and the promise won’t survive, even if everyone involved meant it sincerely and care about the values.</p><p>This might assist: enter Value Sensitive Design (VSD) and Human-Centered Artificial Intelligence (HCAI or HAI). <a href="https://www.tandfonline.com/doi/epdf/10.1080/0960085X.2025.2595915?needAccess=true">VSD</a> is a user-focused approach to creating technology that puts human values first. <a href="https://hai.stanford.edu/ai-definitions/what-is-human-centered-ai">HCAI or HAI</a> is:</p><p><em>An approach to AI that prioritizes human needs, values, and well-being throughout the development and deployment of AI systems. HAI prioritizes collaboration between humans and machines, ensuring that technology is developed with empathy, ethics, and user experience in mind. HAI integrates insights from fields like computer science, psychology, ethics, and design to build systems that are trustworthy, inclusive, and aligned with societal goals. — </em><a href="https://hai.stanford.edu/ai-definitions/what-is-human-centered-ai"><em>Standford University HAI</em></a></p><h3>The six phases, underpinned by design</h3><p>I presented last week the Six Phase Model, a virtuous and continuous loop that must be human-led and human-orchestrated with AI in the loop.</p><p><em>The Six Phases — Design X AI</em></p><ol><li><strong>SENSE — </strong>Situate the challenge</li><li><strong>FRAME — </strong>Set what &amp; why</li><li><strong>BUILD — </strong>Structure the how</li><li><strong>MAKE — </strong>Shape the surface</li><li><strong>SHIP — </strong>Go live safely</li><li><strong>EVOLVE — </strong>Feed back to SENSE</li></ol><p><strong>DESIGN (7) — </strong>Design as a meta-band, running around every phase, also connecting to OUTCOMES</p><p><strong>OUTCOMES — </strong>Community, Planet &amp; Society</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ltv9vy_uJ2nEYWxb.png" /></figure><p><strong>FRAME — an example</strong></p><p>Let’s look at the ‘Frame’ phase as an example. It is better to ‘Sense’ first, ‘Understand’ next, then decide whether to ‘Respond’ or not later, which if not mitigated leads to speed over substance. If it passes ‘Sense’, then we go to ‘Frame’.</p><p>Frame is a critical phase. Software and AI Systems are a bottom-up build, from big-picture to detailed information incorporating what people actually experience. For an AI system, Frame:</p><ul><li>Sets what the system is for and what’s off-limits.</li><li>Decides which AI model and data you use.</li><li>Decides how the system works behind the scenes.</li><li>Experience modalities and how the synthetic properties interact with people.</li><li>The scope of prompts and system safety rules.</li><li>Higher order decisions on the experience descending from the promise in ‘Sense’.</li></ul><p>A promise made in ‘Sense’, such as “we value privacy”, has to become a specific rule about your data, then be built into how the system actually runs. “We value privacy” can’t be skipped in later stages. The promise needs to survive to reach the person using the system, values must persist. This can be traced through the layers of the system, and if it isn’t recognised by users and AI system beneficiaries, that’s not a technical issue, it’s a values issue.</p><p>As I hope has been very clear through out the phases and decisions and what I shared on VSD and HAI, the inputs are the domain of many disciplines but the golden thread is design, supported by ethics, research and so on. There is room in AI Systems development for people with diverse strengths, suitable for strategy and software delivery, who are critical at every point, from values to experience design to interaction design and service design. I will continue to explain this in forthcoming articles.</p><h3>A simple test</h3><p>Not only before an AI system goes live, but at every phase, ask: does the system still deliver on promised values? Which values have been missed? Look at this carefully, review the social contracts and documentation. It is important to deliver on promises that are human-values aligned and responsibly designed. It not only builds trust and credibility, it means you are improving the chances of delivering safely, as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f31d528b412b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Most AI Problems Aren’t About the Technology]]></title>
            <link>https://medium.com/@daughterofbev/why-most-ai-problems-arent-about-the-technology-f8b74fb9e46d?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8b74fb9e46d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 22:01:01 GMT</pubDate>
            <atom:updated>2026-08-12T01:38:45.059Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The both/and scenario of designed operations and the intelligent use of people to design AI</strong></p><p>Most AI problems don’t look like disasters. They look like small things that build up over time: unclear rules, confusing screens, missing safety checks, knowledge or expertise gaps, and no one in charge of a decision.</p><p>An AI tool that sounds confident but gives wrong answers, misleading or inappropriate advice. A recommendation system that quietly limits what people see. An internal tool that works well in testing but breaks once it meets real data. A coded prototype that doesn’t scale or meet technical standards, requiring rebuilding and creating digital waste.</p><p>None of this looks like “the AI is broken.” It looks like no one was watching that part of the system.</p><h3><strong>The real cause</strong></h3><p>The real cause usually isn’t technical.</p><p>Earlier this week I posted <a href="https://www.linkedin.com/in/catherine-hills-96a1b515/">on LinkedIn</a> with a statement “Design is a discipline, not a screen.”</p><p>The reality is that in many product and technology organisations, design has required a steel grip to be viewed as something more strategic than interfaces added at the end of a project, after the real decisions are already made. The confounding part is that ‘screen design’ for any visual interface is actually very important.</p><p>This is not a new problem. If you are curious, read Alan Cooper’s fabulous book advocating for interaction design as a discipline in software in “<a href="https://www.amazon.com.au/Inmates-Are-Running-Asylum-Products/dp/0672326140">The Inmates are Running the Asylum</a>.” It was written in 1999, which might make you cry or laugh, particularly the bullying of ‘creatives.’</p><p>Creatives are often, in my experience, a key ingredient to adding any magic✨ to designed software and I’ll include AI there, to reference <a href="https://www.youtube.com/watch?v=eh8bcBIAAFo">Jenny Wen</a> and her joy in interaction design that made her successful at Figma, now Claude.</p><p>Designers do not need to let go, but adapt. Let’s look at this new chapter with AI. My suggestion is that design is more important than ever.</p><h3><strong>Design is multidisciplinary</strong></h3><p>To my prior point, relegating design to the interface misses the moments that decide whether an AI system is safe: how it makes decisions, what values are built into it, what happens when something goes wrong, and whether it treats people with respect.</p><p>All of this is part of a designed approach.</p><p>Design is a multidisciplinary practice that integrates:</p><ul><li>Systems thinking: understanding relationships, flows, constraints, and emergent behaviour</li><li>Research: studying people, contexts, cultures, and environments</li><li>Ethics: anticipating harm, shaping values, and protecting human outcomes</li><li>Interaction behaviour: defining how systems respond, adapt, and communicate</li><li>Orchestration: coordinating models, data, logic, and human control</li><li>Lifecycle stewardship</li></ul><p>However this is impacted if, by a choice or organisational decision, the system is flattened, cycle times up speed and people need to produce work more quickly.</p><h3><strong>Who needs to be in the room</strong></h3><p>Deterministic or older software is traceable and stable; modern AI systems are probabilistic, contextual, and harder to pin down. Their behaviour shifts with data, prompts, and orchestration, making debugging and assurance non‑local. Until monitoring matures, safety confidence comes from layered automated checks, manual verification, and imposed signals.</p><p>That’s why any suggested fix can’t be more process for its own sake. The fix is being clear about which group of people should be involved, and when.</p><p>So who needs to be in the room?</p><p>It depends on the phase and what decisions are being made. Here is an example of how it might be sped up in a virtuous and continuous loop.</p><p><em>The Six Phases — Design X AI</em></p><ol><li><strong>SENSE — </strong>Situate the challenge</li><li><strong>FRAME — </strong>Set what &amp; why</li><li><strong>BUILD — </strong>Structure the how</li><li><strong>MAKE — </strong>Shape the surface</li><li><strong>SHIP — </strong>Go live safely</li><li><strong>EVOLVE — </strong>Feed back to SENSE</li></ol><p><strong>DESIGN (7) — </strong>Design as a meta-band, running around every phase, also connecting to OUTCOMES</p><p><strong>OUTCOMES — </strong>Community, Planet &amp; Society</p><figure><img alt="The Six Phases — Design X AI 1. SENSE — Situate the challenge 2. FRAME — Set what &amp; why 3. BUILD — Structure the how 4. MAKE — Shape the surface 5. SHIP — Go live safely 6.EVOLVE — Feed back to SENSE 7. DESIGN — Design as a meta-band, running around every phase, also connecting to OUTCOMES OUTCOMES — Community, Planet &amp; Society www.cathhills.com © Catherine Hills 2026" src="https://cdn-images-1.medium.com/max/1024/1*ZQp9zIoAaq-dx_ZOb92yRQ.png" /></figure><p><strong>SENSE — an example</strong></p><p>Let’s look at the ‘Sense’ phase as an example. It is a term that I think is well paired with ‘Understand.’ It is better to ‘Sense’ first, ‘Understand’ next, then decide whether to ‘Respond’ or not later, which if not mitigated leads to speed over substance.</p><p>In Sense, which is the understanding phase, it might be members who represent:</p><ul><li>people who think about ethics and society;</li><li>people who set strategy and rules;</li><li>people who do user research;</li><li>the technical team who build and test the AI;</li><li>the team who shape the overall experience; and</li><li>the team who design the screens and interactions.</li></ul><p>Each of these groups or people matter. As do the phases of decision making. Leave a group or phase out, and you haven’t removed a risk. You’ve just left it unmanaged.</p><p>You can see here, I haven’t said designers make all of the decisions. I’ve demonstrated that there needs to be discipline in the way the operating model is designed to support better designed work systems and outcomes. It is the culture of <em>designed</em> <em>decision-making</em> and <em>design</em> that needs to be improved in AI systems design.</p><h3><strong>A simple test</strong></h3><p>Before an AI system goes live, ask: who had a say? Which decisions were made without someone essential? Most AI problems, looked at closely, come back to the same answer: a person or group that should have been in the room, wasn’t. And that might be the people you are designing it for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8b74fb9e46d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who really is the smartest (or fastest) in the room, anyway?]]></title>
            <link>https://medium.com/@daughterofbev/who-really-is-the-smartest-or-fastest-in-the-room-anyway-fadb64e87fba?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/fadb64e87fba</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 06:17:54 GMT</pubDate>
            <atom:updated>2026-04-25T06:37:17.167Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A short opinion piece how we might respond to the latest wave of technologies including Generative Artificial Intelligence (GAI), written by a human (not with ChatGPT). Written June 3, 2023, published Saturday 25 April, 2026.</em></p><figure><img alt="Prompt: help me create an image of smart people listening to nature while AI bots run in parallel, helping create clean water and renewable resources" src="https://cdn-images-1.medium.com/max/1024/1*joSX3l96uvTC1D_LP_BACQ.png" /><figcaption>“AI and nature working together for sustainability” — Image produced for published article April 2026 with Claude 1.3883.0 (93ff6c) 2026–04–21T17:24:01.000Z</figcaption></figure><p>I’d imagine you might have been living under a rock if you noticed what a flurry everyone is in about Artificial Intelligence (AI), particularly the generative kind, including services similar to ChatGPT.</p><p>There are many different reasons for why people might be curious about or indeed afraid of AI and the impact these technologies might have on society. The promise is that AI is going to make things faster, better, quicker, light speed. AI is going to make life for us all easier, if you believe Elon, more abundant, help humans reach new heights by enhancing our lives and reducing human involvement in certain roles or tasks that might hinder us from great progress. It will improve response and processing times, lightening our load and save businesses and organisations tonnes of money. We will reach the next stage of human and technology evolution. And so on.</p><p>The fourth industrial revolution is at hand. We, as humans, are already competing with the speed of change, particularly if we deal with technology as part of our existing lifestyles or simply responding to the changing environment and world around us.</p><p>We are therefore rushing to get in front, catch up, be part of and influence this next wave of technologies. Additionally, while many of us might be anticipating positive change, or sitting in neutrality, the remainder of the population may be feeling petrified of what these new technologies could do to our general livelihoods and careers, which is quite understandable.</p><p>We stand at the edge of a new societal paradigm, but we haven’t quite defined what that looks like yet, and that can be unsettling, even thwarting the supposed positive intentions of this change. For myself this is because it is less driven by the human and more driven by the progress of the technology itself. Much like the way we work in software engineering, we often demand that we understand the ‘why’ behind the vision of what we are building, rather than building a thing without strategy.</p><p>Many of us are, if not already knowledgeable, striving get ahead and learn everything. In our current situation, I see the behaviour of many enthusiastic new adopters of AI as the equivalent of going to the AI waterpark, grabbing an inflatable doughnut called ChatGPT or something similar, and jumping on it, moving on a current of fast flowing water which might take us through a series unknown tunnels until reaching the water at the bottom of the slide. Potentially thrilling and fun, great for the curious, fun for experimentation, but dangerous if supervisors with the right intent (eg. health and safety of the riders) aren’t watching the ride.</p><p>To further the metaphor there are multiple key issues here, for example the flow and quality of the water (the data quality, accuracy and propagation of it via services), the scaffolding of the systems (the algorithmic logic of the services themselves) and if the experiences and interactions have a short term or long term positive effect when we complete the ride, beyond a thrill (does it enhance our wellbeing, are we able to improve lives or conditions for living, is it safe and trustworthy).</p><p>Likewise the wide-eyed learners are assisted with many great learning opportunities available right now so we can feel more ‘in control’, engage with, enhance or commercialise these services. One aspect of this with generative AI is the quite accessible skill of prompt engineering, which once learnt is the skill of good questions for the robot to be able to create reliable answers. The problem is though, that the data contains identified and unidentified biases. It requires many rinses and repeats of sets of data to understand how reliable it might be and much of this relies on standards and governance of data sets. This is not exclusive to prior models of AI and machine learning, but also an issue for generative AI.</p><p>In terms of possible futures, AI might feel somewhat threatening, given the anthropomorphising of AI and robots is creating the anticipation of an uncertain future around humans as the perceived superior intelligence and beings on our planet Earth. Of course given the state of the planet, you could say we deserve this. Tongue in cheek. Let’s hope we can save our planet, other beings and ourselves. As humans we are perfectly designed for Earth and I can only anticipate that AI and robotic technologies purposed well might help us save our planet, not destroy it.</p><p>Certainly news services are not helping with the wave of issues getting in the way of identifying the inherent possibilities and positive outcomes of AI and robotic technologies. Certain news services that cater to fear mongering and misinformation may be ‘othering’ these new technologies, in so much dealing with humanistic robots much like they would with minorities threatening the existing power over status quo.</p><p>For consumers there is a very serious aspect to the consumption of these AI products and services. Given these chat interactions as the machines learn and improve appear, semantically, more human and possibly, given the information they share and process via these interactions, possibly smarter than us, the vulnerable and less educated may not regard AI and robot interactions with a critical mandate. We have seen this recently in Europe where, tragically, a chat bot suggested a man should take his life to save the planet. Another additional serious note is that as many experts have raised, society could become more corruptible and more dangerous as a result of the misuse of AI.</p><p>Of course we have a choice. As a society, the majority of us could go down the route of ignorance is bliss. Forget this AI stuff and just enjoy life. Buy and build lots of AI powered products and services, continue to consume and blindly permit services and products that might allow machines to learn from us until we potentially become non-competent or competitive in comparison to AI and well designed robots, and are simply ranked as more vulnerable bodies of organic matter. Or allow these products and services to perpetuate and intensify global and society inequities, because we are too ‘on the ride’ to stop. This is what humans are good at right? I say this with some irony. I do not think we should continue this way.</p><p>Likewise, in technology the parallel behaviour to the consumer is pick up the tech in order to be market competitive. As in many organisations, workers move at pace, want to be first and lead the field or competitive marketplace. In tech, these growth drivers are compounded by a need to keep running, to do a great deal of things, however, that many of us are unaware that we need to slow down, if not pause. It’s been this way for quite some time and we are seeing now, more than ever, that tech workers are burning out.</p><p>I used to think it was simply growth agendas and FOMO (fear of missing out — aka greed). However it is more than this. I believe these workers are simply unsupported without secure pathways when AI or other roles and actors take over. Like many other people, tech workers are also seeking to stay career relevant, in order to maintain their jobs and livelihoods. Thus, the response to these conditions is to fulfil the expectation of working smarter, faster and light speed, like these machines might. This is pressing us both as tech workers and societally into corners and compounding the issue of cognitive overload. The conditions are not permitting us to slow down. Nor does the human brain thrive in these conditions.</p><p>This is where the AI buddy model may be helpful in reducing the load and helping us make decisions. However when training data is simply public domain generated, aggregate, inaccurate and unreliable, supporting threads of misinformation and diminished trust, making organisations vulnerable to litigation and individuals vulnerable to being misled, we are in a difficult spot. Not withstanding the restructuring or reduction of ethics teams in the organisations which create these technologies, or indeed punishing whistleblowers.</p><p>Now people are saying the train has left the station. We may not be able to reverse prior decisions. Leading figures in AI development are quitting and saying sorry folks, it may be too late. The whole situation has become rather deterministic. Remember the singularity. Terminator anyone? That’s a dystopian view.</p><p>It seems as though right now, in society, we are simply accepting and playing out the teenage science fiction fantasy of a cis gendered white male of privileged upbringing with centrist-right parents. This is not diverse, inclusive or ethical. Let’s stop. AI is political. The things that people will do with AI will be political.</p><p>I’m not personally anti-machine or AI. However, I believe in dignity, access, equity and inclusion. My feeling is that if machines start looking, thinking and talking like us and we think they are sentient then let’s treat them with respect and work out how to co-exist. If there are risks to people or planet then we have an issue. We must prevent and also solve that problem.</p><p>So let’s get off the theme park ride. You know the one that looks really fast, sparkly and amazing. But you get on it, it’s fun for a minute, but there is a risk of regretting it and possibly vomiting during the ride or straight after, because it wasn’t really good for you or others. Perhaps, if the fairground is responsible, we can more easily choose an equally fun and inclusive option. Especially make sure that the ride has been thought through by wise decision makers, initiated designed and engineered properly, tested first and is safe for humans. Because we know that when trust is broken and people or the planet are hurt, we won’t think the ride is fun anymore.</p><p>When I was at school I decided I wanted to do study design at university and to do so, in order to prepare myself and have a portfolio, in my final year of the VCE I dropped maths. I was in the top stream for mathematics at my year level and my school principal was horrified. “You cannot drop maths,” she said. I did though. My timetable would not permit me to do both maths and design. Not one option worked.</p><p>Instead of maths, in my final year I picked up legal studies. Legal studies seemed like the best of a limited selection of things that I could chose from. I didn’t hold legal studies in high esteem like I would maths or science, as I did not intend to become a member of the legal profession, but it seemed better than most other things I could choose from.</p><p>Typically, being a dedicated student, I worked late and hard during my final years at school to complete assignments, study for exams and get the best marks I could to enter university. However, when I showed up to legal studies classes, I didn’t expect to be particularly interested and expecting to be bored, often tuned out, sometimes falling asleep in class.</p><p>Understandably, at first my legal studies teacher clearly thought I was a bit of a dropkick. That was, until I started handing in my assignments. I found legal and ethics projects interesting and resulted in my best marks for the entire year. The irony was astounding. I’d found an easy path with something I learned to enjoy and did well at it.</p><p>I got into design at university, goal achieved and studied other things too, including fine arts and information systems. I am still working as a designer, researcher and strategist. I have taught design and wrote a major thesis about it. Psychology, philosophical arguments, debates and ethics have continued to sustain my interest and led me to another phase of study and research.</p><p>I might add, there’s nothing wrong with living under a rock by the way. You might be wiser than many of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fadb64e87fba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ThisisDoing — celebrating being ‘better together’]]></title>
            <link>https://medium.com/@daughterofbev/thisisdoing-celebrating-being-better-together-bfa8865a0931?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfa8865a0931</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[human-centred-design]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sun, 10 Apr 2022 09:15:33 GMT</pubDate>
            <atom:updated>2022-04-11T06:55:08.555Z</atom:updated>
            <content:encoded><![CDATA[<h3>ThisisDoing — celebrating being ‘better together’</h3><h4>A reflection on ThisisDoing V3 with the Experience and Service Design team at The University of Melbourne</h4><p>In my role over the past few years as one of the Australian chapter leads for The Human Centered Design network, aka <a href="https://www.thisishcd.com/">ThisisHCD</a>, I have been exposed to incredible content and people in our field here in Australia and globally. In this article I wish to celebrate the team I have most recently led, the Experience and Service Design team at the University of Melbourne, and our learning experience at the <a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing Festival V3 — APAC 2022</a>.</p><h3>ThisisDoing V3 — February 2022</h3><p><a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing</a> was a learning festival dedicated to the cross-disciplinary knowledge share of methods and topics in the field of human-centered design. The event was held for the community in the Asia Pacific region in February 2022.</p><p>The objective of this year’s <a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing</a> was to provide <em>“practical tools and fresh perspectives exploring how compassion, dignity and play can help us be ‘Better Together’</em>.”</p><blockquote><em>“I gained a lot of value out of the first few sessions, a major message in the sessions was check yourself before you wreck yourself, as people who are leading design” — Amy Huynh</em></blockquote><p>I personally found this year’s <a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing</a> event timely, in that it brought together some topics with currency around our responsibility as designers and researchers in the field of human-centred design. Additionally, the sessions highlighted the opportunity to learn about how to participate in design ‘doing’ with self-compassion for ourselves as designers and encouraging an active awareness of the impacts of our behaviours on the people we design with.</p><p>In a series of team meetings I led afterwards, my team provided personal ‘reviews’ of the event, along with some brilliant discussion, personal reflections and sketch notes. Our team considered the topics in light of our next iteration of an HCD Playbook we have been developing and how to integrate concepts of self-compassion, safety and dignity into the content.</p><p>Beyond design, we had a range of people invited from our broader team, including service improvement, change and culture team members. This article is a review and reflection on <a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing</a>, incorporating the contributions of members of my team.</p><blockquote><em>“I liked the immersion in design culture and the intersection of the personal and professional ” — Catherine Harris</em></blockquote><h3>Designing with Humility — KA McKercher</h3><p><a href="https://www.linkedin.com/in/kelly-ann-mckercher/">KA Mckercher</a>’s powerful delivery of this topic was grounded in their recent engagement and reflections on their own experiences in contemporary commercial participatory and co-design practices.</p><p>KA emphasised the importance of humility for designers and the traps of humility, highlighting saviourism, privilege, prioritising the wrong things, failing to build on what exists and assuming people “think the way you do.”</p><blockquote><em>“I really enjoyed KA. As designers we are not fixers, we are coaches, facilitators and obstacle removers” — Amy Huynh</em></blockquote><p>KA recommended the importance of ‘power with’ as a principle, rather than ‘power over.’ They emphasised the simple principles of listening and speaking with people before commencing design or design thinking.</p><p>The additional importance of trauma awareness neatly tied in to the next topic by Rachael Dietkus around Trauma Informed Design. KA emphasised designers’ accountability and recognised the value of being mindful in situations where we may not have the background, knowledge or skills to have immediate compassion for those we design for.</p><blockquote><em>“There were a lot of good reminders or cautions in the Designing with Humility — I considered this a stand out session” — Catherine Harris</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*laM00kx2my1vmZK-IGxXsg.png" /><figcaption><em>Sketchnote “Designing with Humility — KA McKercher” by Natalia Alessi (2022)</em></figcaption></figure><h3>Trauma Informed Design — Rachael Dietkus</h3><blockquote><em>“I am now really conscious around the power dynamic — between designers and the people we are designing for” — Nancy Samayoa</em></blockquote><p><a href="https://www.linkedin.com/in/rachaeldietkuslcsw/">Rachael Deitkus</a> provided incredible references and a knowledge introduction to the topic of Trauma Informed Design. In Rachael’s presentation she spoke of the intersection of the social work and design domains and the history of socially responsible design. Rachael pointed out the importance of collaboration and mutuality in how we design with and for others as designers. She mentioned the importance of not only reflection but reflexivity — an inquiry method that is assistive in not only reflecting on externalised events but the internal motivations of the inquirer in this context, designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/0*wqZnE1gB9CKkLgd3" /><figcaption><em>Sketchnote “Trauma Informed Design — Rachael Dietkus” by Natalia Alessi (2022)</em></figcaption></figure><h3>Bringing Compassion into Play &amp; Work — Belina Raffy</h3><blockquote><em>“Belina’s improv session was fantastic, some of the pointers there were important to techniques. There was a lot of positivity building on people’s ideas” — Nancy Samayoa</em></blockquote><p><a href="https://www.linkedin.com/in/belina-raffy/">Belina Raffy</a> used collaborative building techniques akin to Improv to provide ways in which ideas could be ‘built upon’ in groups. Her practical and indeed joyful delivery of this Play and Work session brought light into the prior discussions around listening to the value of others’ ideas and what others say. Belina’s activities focused the cohort, who were moved into breakout sessions, on active listening techniques. In my observations of the response from the attendees, very active on our Zoom chat and loving the methods Belina introduced during the day around play and the importance of play and compassion at work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/0*hj9VtyZXS3A28bIb" /><figcaption><em>Sketchnote “Bringing Compassion into Play &amp; Work — Belinda Raffy” by Natalia Alessi (2022)</em></figcaption></figure><h3>Journey Map Ops — Marc Stickdorn</h3><blockquote><em>“Marc simplified a variety of approaches to journey map creation, engagement, influencing and operationalisation from what appear to be complex concepts down to the clearest advice” — Cath Hills</em></blockquote><p><a href="https://www.linkedin.com/in/stickdorn/">Marc Stickdorn</a> presented simple explanations around the pros and cons of various choices in the implementation and operationalisation of journey maps. Marc covered a variety of topics, including; map reliability, the state represented in a map, what kinds of people or experiences the map might be representative of, the scope and scale of a map, the focus of the map communication and the depth and visualisation of the map information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/0*fx9T2cUDDsAqYsKN" /><figcaption><em>Sketchnote “Journey Map Ops — Mark Stickdorn” by Natalia Alessi (2022)</em></figcaption></figure><h3>Facilitating a Safe Space — Adam Lawrence and Renatus Hoogenraad</h3><blockquote><em>“Renatus and Adam helped us understand, via an intimate scenario, how important it is to have core tenets of respect and safety incorporated into any design or design-led research activity eg. consent” — Cath Hills</em></blockquote><p><a href="https://www.linkedin.com/in/adamstjohnlawrence/">Adam Lawrence</a> and <a href="https://www.linkedin.com/in/renatus-hoogenraad/">Renatus Hoogenraad</a> come from theatre backgrounds which inform the way they interact with organisations as trainers, as well as applying this knowledge into an enactment of a quasi intimate space and how this might feel for designers and researchers. Acknowledging sometimes the scenarios we engage with as designers can be messy, they talked about the props and tools we can use as designers to create a space within which we can enact on our spaces of design inquiry, safely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/0*YRIc4iO6nPp0qK08" /><figcaption><em>Sketchnote “Facilitating a Safe Space — Renatus Hoodengrad and Adam Lawrence” by Natalia Alessi (2022)</em></figcaption></figure><h3>In conclusion</h3><p><strong>Attending </strong><a href="https://www.thisisdoing.com/the-doing-design-festival">ThisisDoing</a><strong> nurtured a deep passion for learning, building of capability and creation of spaces for knowledge sharing. The team and I had a great time learning and reflecting on the sessions we attended.</strong></p><p><a href="https://www.linkedin.com/in/ahhuyn/"><strong>Amy Huynh</strong></a>’s natural affinity for social research and systems thinking means she is one to watch. Outside of our shared interest in literature and Murukami, I have enjoyed Amy’s insightful thinking and self reflection. Amy’s background with an economics and finance specialisation in her undergrad provide a unique lens on what is a strategic discipline traditionally occupied by ‘creatives,’ her innate skills in insights gathering, listening and observation as well as her awesome icebreaker ideas make her an awesome team member and valued contributor.</p><p>An avid lover of all things green and a Buffy the Vampire Slayer fan, <a href="https://www.linkedin.com/in/catherine-h-64819911/"><strong>Catherine Harris</strong></a> is a deep expert in qualitative market research and customer experience in the education sector. Catherine is a passionate learner in all things design and design thinking, building on her experience in the marketing domain. Catherine credits her solid delivery of presentations and influencing skills to a period of teaching English in Japan after graduating from her Bachelor of Arts in History as well as her background in education consultancy.</p><p><a href="https://www.linkedin.com/in/nancy-s-70a6a349/"><strong>Nancy Samayoa</strong></a>’s deep passion for social impact and innovation combined with her background in teaching and architecture provides potent thinking and an avid interest in all things living in designed physical spaces. Nancy has taught digital design modules in three dimensional virtual reality spaces. Nancy is also co-running a design podcast on sustainable design that is earth centred, with <a href="https://msd.unimelb.edu.au/">Melbourne School of Design</a>. I have loved collaborating with Nancy in our roles as sponsor and mentor with the University of Melbourne’s<a href="https://ipp.eng.unimelb.edu.au/"> Innovation Practice Program</a>.</p><p>Hailing from Argentina, <a href="https://www.linkedin.com/in/natalia-alessi-b59b3a52/?originalSubdomain=au"><strong>Natalia Alessi</strong></a> is a visual communication expert, who is completing her PhD in Design at RMIT School of Design here in Melbourne. A talented designer, researcher and illustrator, Natalia has also co-chaired Service Design Now, one of Australia’s distinguished conferences in this domain. Prior to this role, Natalia has taught visual comms at <a href="https://www.rmit.edu.au/about/schools-colleges/design">RMIT School of Design</a> and prior to her current role was with the enterprise design team at RMIT University.</p><p>Finally, my name is <a href="https://www.linkedin.com/in/catherine-hills-96a1b515/"><strong>Catherine Hills</strong></a>, many people call me Cath or Chills. I’m a design, research and product leader, and also an educator, thought-partner, writer and editor here in Melbourne, Australia. I lead and build capability in design strategy, UX and product delivery teams and also co-deliver the UX Expertise module at <a href="https://www.rmit.edu.au/about/schools-colleges/design">RMIT School of Design</a>. I have also presented at multiple local conferences and community events. I like to be curious and find great personal satisfaction in helping people reach their potential, one step at a time, or in leaps and bounds.</p><p><em>Thank you to Amy, Catherine, Nancy and Natalia who all contributed their thoughts and reflections to this article, and to </em><a href="https://www.linkedin.com/in/gerryscullion/"><em>Gerry</em></a><em> and the </em><a href="https://www.thisisdoing.com/the-doing-design-festival"><em>ThisisDoing</em></a><em> team for a wonderful learning event.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfa8865a0931" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems and Agility (Part 2 of 2)]]></title>
            <link>https://medium.com/interactive-mind/design-systems-and-agility-part-2-of-2-42418819f65a?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/42418819f65a</guid>
            <category><![CDATA[hcd]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sun, 14 Oct 2018 07:46:07 GMT</pubDate>
            <atom:updated>2018-10-14T07:46:07.306Z</atom:updated>
            <content:encoded><![CDATA[<h4>Extended from my recent talk at UX Australia Conference #UX2018, part two of<a href="https://medium.com/interactive-mind/design-systems-and-agility-part-1-of-2-b96c188acfca"> Design Systems and Agility</a></h4><p>This is the second of a two part series of articles created to support my thinking on <a href="http://www.uxaustralia.com.au/conferences/uxaustralia-2018/presentation/design-systems-and-agility/">Design Systems and Agility</a>, as presented in my talk at UX Australia this year. The purpose of this Part Two is to discuss and show the results of a survey live the weekend prior to #UX2018. This is a long article so I’ve added in an ‘Abstract’ in the next section to summarise key findings.</p><blockquote>There is a great deal of excitement around design systems in the design community. Everyone is saying we need a design system, but why do we? What is the value for designers, teams and organisations?</blockquote><p>I felt it would be valuable to create a preliminary survey to industry to help establish a light-touch benchmark on the current state of design systems. People who contributed to the survey included members of the design community, as well as other adjacent functions who help designers build systems as well as endorse and collaborate with us, including as product and engineering team members.</p><p>The survey, titled “<em>How do you interact with design systems?</em>”, was set up to establish some evidence around the use of design systems in industry, to share stories of other people sharing the same challenges, as many designers are now, and to help focus us as a community on next steps for discussion.</p><p>Even though I have had my own experience with creating, maintaining and interacting with design systems in various scenarios and contexts, as a design practitioner, researcher and humanist, I couldn’t resist asking others about their thinking, too. As most of us would agree, one participant isn’t enough to create deductions and most organisations are organised and operate differently on a case by case basis.</p><p>The focus of the survey questions is across design systems development in design, product and technology teams. Or things happening around the design system itself. I sought to understand how these design systems relate to individuals, teams and organisations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aDfauhTbUWeHCTupJ7avw.jpeg" /><figcaption>Design System Epic: How might we understand the value of design systems?</figcaption></figure><h4>Abstract: Key Takeaways from the Design Systems Survey</h4><p>In case you don’t have time to read this entire article, here’s a wrap up of key takeaways. Design systems:</p><ul><li>Increase team productivity significantly, aiding speed to value and first in market approaches;</li><li>Provide designers and their teams time to problem solve;</li><li>Benchmark usable, accessible interfaces and interactions with reusable components if supported with best-practice front-end engineering and design practices;</li><li>Should be incepted by running an experiment or service design approach first (research, discovery and testing) to understand use-cases, risks and opportunities in their development;</li><li>Are aided by an associated style guide and playbook for users of the system within teams in the organisation;</li><li>Ensure consistency, which is perceived as king and is considered essential for teams and improving the user experience of products and services;</li><li>Originated with a service design approach, aids in originating, maintaining and increasing user adoption of the system itself;</li><li>Decrease rework and waste, as well as mitigating unnecessary design system effort and legacy;</li><li>Need support as inception, maintenance and adoption is a pain point;</li><li>Have the power to be user and human-centered;</li><li>Require teams to be flexible and allow co-ownership of the system across functions and teams in a way that makes sense for your organisation;</li><li>Are valuable to teams both in Agile and Waterfall delivery contexts; and</li><li>Aid collaboration and reduce friction in team decision making.</li></ul><h3>The Survey, Recruitment and Participation</h3><p>The <a href="https://goo.gl/forms/VEYINllOyIZOMuYr1">survey</a> consisted of twenty questions about design systems, the people who use them and their teams. The objective of the survey was to gather a sample of data to understand the current state of use, expectations and perceptions of design systems in industry today. The survey statement inferred my intention to understand how design systems are currently interacting with people in companies with both established and emergent design systems. The supporting explainer of the survey was:</p><p><em>“A short survey to help us understand your experience of design systems in your working life.”</em></p><p>Survey recruitment was conveniently sampled via the my social networks, via Slack communities, LinkedIn and Twitter. The data collection was live for two weeks, for one week before and one week after #UX2018 but promoted over twenty-four hours. Thank you to any connections who retweeted the survey link, truly appreciated.</p><p>At the #UX2018 conference, a sample of the data was presented and had been through a first round of synthesis. The presented information was based on a population of twenty six participants. When finished, the survey data consisted of a total of thirty four responses, from a range of people in the design and technology industry with a range of role titles.</p><h4>Organisations Represented and Geographic Regions</h4><p>I received a range of responses from different regions including Australia and possibly New Zealand, as well as the United States and Europe. Some really amazing and well known businesses were represented, some with publicly applauded with established design systems as well as younger emergent ones. Data has been de-identified and will not be disclosed though due to an agreement provided to those who submitted their information.</p><p>Thank you to any friends who helped with this survey, and those who I don’t know super well, I’m truly grateful for your participation.</p><h4>Role Titles</h4><p>Titles of people who participated in the survey included; Visual Designer; UX Designer; UI Designer; UX Engineer; Front End Engineer; User Researcher; Product Designer; Product Manager; UX Manager; Design Systems Lead; Interaction Designer; Director, UX; Engineering Lead; UX Specialist (UX researcher, designer); and UX Strategist.</p><p>52.9% of participants who contributed to the survey said their role title was ‘UX Designer’ (18 participants). The second largest group, at 14.7% of participants, said their role was ‘Product Designer’ (5 participants).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*amqCj-5q5H2LdB93PX0mNA.png" /><figcaption>Q1 What is your role? Answers showed UX Designers (52.9%) and Product Designers (14.7%) were the largest groups in the survey population</figcaption></figure><p>Although UX and Product Design were the roles most represented in the survey at approximately 68% of the 34 participants, functions were represented across many facets of design, as well as engineering, product management and design leadership roles.</p><h4>Responsibility Sets</h4><p>Participants were then asked, “<em>Are you responsible for design, user research and/or user testing in your role? Choose the options that apply.</em>”</p><p>The answers to the survey showed that of most of the participants, in their roles they had multiple responsibilities. Individually their responsibilities were distributed across the main UX and Product Design discipline ‘verticals.’</p><p>These verticals were consistent with the dominant ‘trifecta’ of <a href="https://clearleft.com/posts/is-the-t-shape-evolving">UX deeper T</a> skill categories, including:</p><ul><li>Design (execution): 91.2% (31 responses)</li><li>User Testing: 88.2% (30 responses)</li><li>User Research: 85.3% (29 responses)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LRlBzFTpQC-4zYbYG0k96w.png" /><figcaption>Q2: Are you responsible for design, user research and/or user testing in your role? Choose the options that apply</figcaption></figure><p>Remaining single participant feedback came in at the following individual sets of responsibilities, as specified by the participants themselves under the alternate ‘Other’ category:</p><ul><li><em>I do participate in them but am not responsible</em>: 2.9% (1 response)</li><li><em>Development</em>: 2.9% (1 response)</li><li><em>Design team documentation</em>: 2.9% (1 response)</li></ul><p>This information showed, overall, that the many individual participants who contributed information in this survey undertake at least two specialist areas of responsibility within their roles, if not three, as part of their day job.</p><p>The dominant case is that for at least 31 of 34 participants their primary responsibility is design (execution), combined with user testing and/or user research. For most of the 31 participants who undertake design execution in their day jobs, 29 are responsible for all three types of tasks, including user testing and user research.</p><p>Let’s not jump the gun, but it looks like our designer participants are potentially quite busy with more than one focus. Not only this but they need to juggle these focuses across a day, a sprint or initiative.</p><blockquote>How might design systems make it better for all of us, to give us the space do all the things necessary to create better experiences for both ourselves as team collaborators and the users of our products, systems and services?</blockquote><h3>What is the Purpose of a Design System?</h3><p>In the next section of the survey, participants were asked, “<em>What do you believe a design system should do?</em>”</p><p>Key themes that emerged were as follows:</p><ul><li>Collaboration, Efficiency and Alignment</li><li>Focus Time for Bigger Problems</li><li>Interaction Design over Visual Design</li><li>Consistency, Scale and a Source of Truth</li><li>Ease of Use, for All</li></ul><h4>Collaboration, Efficiency and Alignment</h4><p>Collaboration between team members was mentioned as a focus for many of the designers who participated in the survey. Many felt this was a positive or aspirational effect of what a design system should do.</p><blockquote><em>Design Systems should:</em> “Enable our teams to move faster through the design &amp; development process. With a design system in place, our designers can spend energy solving bigger problems than creating new design patterns. Additionally, Product Managers should be able to graph wireframes, knowing that we have patterns already for how certain features or interactions work. This allows them to move faster.”</blockquote><p>In the above scenario, wireframes are no longer the exclusive domain of UX Designers but anyone in the team. Other use cases for collaboration and alignment being important via design systems being established included; <em>“Consistent design patterns and informing appropriate usage,” “Provide a framework for collaboration and consistency”</em> and <em>“Establish quality and create a unified voice and point of view.”</em> Quality was considered by some participants as part of the creation of standards and best practices in not only the system itself and interaction design but also accessibility and usability.</p><blockquote><em>Design Systems should:</em><strong> “</strong>Align best practices incorporating accessibility factors, usability and align teams to produce high quality, cohesive products.”</blockquote><p>Participants also talked about scaling the system based on collaborative decision making; <em>“Set global styles and patterns on shelf for your product to grab when designing anything new. It should also be extendable so when new or nuanced scenarios arrive, your team can add to the guide.”</em></p><h4>Focus Time for Bigger Problems</h4><p>For designers, managing their tasks and efficiency, economy and ease of use in relation to a design system being implemented was raised as an important factor: <em>“With a design system in place, our designers can spend energy solving bigger problems than creating new design patterns,”</em> and, “<em>They should aid a designer’s creativity, as the focus of their work shifts to Design Thinking instead of pixel-pushing.”</em></p><blockquote><em>Design Systems should:</em><strong><em> </em>“</strong>Provide designers with a set of validated &amp; well thought out components and guidelines they can use to solve diverse problems across product(s), in a consistent way.”</blockquote><p>Additionally, design systems, many participants concur, can only be defined as ‘good’ if they have been user tested.</p><p>In my experience, design system ownership, once productionised into code, is only powerful if the ownership of the design of the system itself makes a case for human or user-centered design approaches and continuous improvement methods. For something new or for a change to be inducted into system requiring additions and/or innovation an experimentation cycle must occur. For example, a new pattern should be usability tested in situ to all affected contexts, or a a new flow or user journey should be fully prototyped and tested for down stream system effects and dependencies before being inducted into the system.</p><h4>Interaction Design over Visual Design</h4><p>Interaction design in software is set in the context of complex adaptive systems (CAS) eg. considering states, conditions and variables. Design systems are perhaps the answer designers in technology have to deal with the complexities of multiple CAS, their actors and their environments. Responses to what design systems should do indicated that interaction design has a bigger part to play than visual design alone.</p><p>A priority of focus on Interaction Design over Visual Design makes absolute sense in the context of moving parts and complexity. Participant comments included; <em>“Less focus on cosmetics, more focus on interactions,”</em> and, <em>“A grouping of elements together to create a greater whole. Gestalt, the whole before the parts.”</em></p><h4>Consistency, Scale and A Source of Truth</h4><p>For some participants, the perception of a design system was as an enabler to teams and efficiency. Additionally design systems are perceived as an enabler of consistency in the interface and user experience. With reference to patterns, scale and team conversations, the design system is an enabler and aa source of truth for the following reasons, because it:</p><ul><li><em>“Establishes consistency in design patterns, both design and front-end wise”</em></li><li><em>“Creates a scalable system that is maintainable”</em></li><li><em>“Guides better conversations between design and development”</em></li></ul><p>The latter point was fascinating, given traditional tensions in engineering around design decisions in the interface and feasibility versus perceived desirability. Additionally, in relation to the prior commentary on best practices and validation this forces the point. Nothing can be admitted into the design system without the due protocols. However there is a risk here around ownership, and who owns the design system. Is it design, product, engineering or all actors in the team that interacts with the system?</p><blockquote><em>Design Systems should:</em> “Give structure to ambiguity.”</blockquote><h4>Ease of Use, for All</h4><p>Making interfaces more learnable for users and easier for the designer, and their teams, to execute design efficiently and easily sounds like win, win, no?</p><p>Participant responses on this occasion covered both sides of the system image; from process, <em>“Make things easier — speed up the process of development,” to the job of the designer, “Make my job easier,”</em> to the perceived benefit for users additionally, <em>“Easier for the user to learn and use.”</em></p><p>The above comments do not infer that the designers or participants in the survey regardless of role wish to loosen their grip on great interface design. Let’s be sure about that. Their responses are about improving the process of delivering great products and services via standardisation.</p><p>Read <a href="https://medium.com/interactive-mind/design-systems-and-agility-part-1-of-2-b96c188acfca">Part 1</a> of <a href="https://medium.com/interactive-mind/design-systems-and-agility-part-1-of-2-b96c188acfca">Design Systems and Agility</a> for more information around the setting for design systems, CAS and why design systems appear to be so important in our current state of work, particularly in design operations, technology delivery and team collaboration.</p><p>The first questions in the survey relate to perceptions of design systems in industry.</p><p>The subsequent questions relate to experience and evidence based responses regarding how design systems interact with teams in participant environments.</p><h3>Does your Team Need a Design System?</h3><p>In the next section of the survey, participants were asked, <em>“Do you believe your team needs a design system?”</em></p><p>Overwhelmingly, the answer was, “Yes.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvThCUrBdFXjZNzonPiX5A.png" /><figcaption>Q4 Do you believe your team needs a design system?</figcaption></figure><p>In a similar vein to the prior question around what design systems should do, key themes that emerged were as follows, to support why participants felt their teams needed a design system:</p><ul><li>Consistency and Coherence</li><li>Better Communication Between Functions</li><li>Adaptability</li><li>Maturity as a Dependency (of the Design System Itself)</li><li>Increased Efficiency and Speed to Market</li></ul><p>Details of each of the above, in relation to why participants felt their teams needed a design system, are listed below:</p><h4>Consistency and Coherence</h4><p>The value of a design system, for a team, is the system as an enabler for clear, thoughtful decision making in the interface and experience.</p><blockquote><em>Why my team needs a design system: “</em>Not only for consistency of experience across the product, but to help ensure product teams are thoughtful about what new components they introduce and the scalable value they bring.”</blockquote><h4>Better Communication Between Functions</h4><p>Functional ‘bumps,’ as some might put it, happen often in teams with cross-functional members. As users of systems we are designing with, it makes sense to improve the communication around as many decisions as possible. After all, many rituals via Agile and Lean approaches are instated in teams to help minimise duplication, improve communication and collaboration. Therefore design systems are considered by some participants as a communication tool:</p><blockquote><em>Why my team needs a design system:</em>“There is a bit of friction between design and dev, and a design system would help guide conversations “</blockquote><p>Additionally, the system itself presents a benchmark to the team around how to articulate information in the interface more efficiently, eg. How might we display this information, with an existing pattern, view or flow, or is a new interface/interaction required to be tested in order to validate user responses prior to funding work in production/in the code base/in the service/in the real life experience?</p><blockquote><em>Why my team needs a design system: “</em>It will help inform every design iteration we work on”</blockquote><h4>Adaptability</h4><p>Not every team or team member enters an organisation with context and for many designers and/or teams this can create pain points.</p><p>For external agency teams, for example, or freelancers, the non-existence of a style guide can hold up productivity and prevent the team from running from day one. This is not a dissimilar problem for designers in in-house teams either, who I often have observed peddling double speed to create a design system in parallel to the initiatives that they are running.</p><blockquote>A design system can be a great way to onboard new team members into the eco-system they are serving and set them up, as users, to run fast, rather than to move slowly.</blockquote><p>On the bright side for agencies, but perhaps not so much for the organisations or in-house teams they are serving, a business opportunity might present itself in the creation of a style guide in addition to the design system it supports.</p><blockquote><em>Why my team needs a design system:</em>“We are consultants that must adapt to different client needs/ style guides”</blockquote><p>A pain point here for the organisation is that creating a new style guide to support a design system a) costs more money and b)may happen in isolation away from in-house teams or create duplication across the business. Sometimes however , if you are an in-house design entity, this may be the best way to spin up a design system quickly with a third party vendor, rather than your own team that may be struggling to get the support and time to do it in-house. The point being you need a dedicated way of creating a design system if you are considering working on this in-house eg. create a team or custodians of the system. This can be done via dedicated resources or a guild.</p><h4>Maturity as a Dependency (of the Design System Itself)</h4><p>A point made by some participants regarding design system maturity as an indicator of teams and design maturity in the organisations the systems themselves serve was particularly interesting! The nature of software delivery and many teams means that if there is a universal system, naturally things will be in and out of sync. Teams will be faster and slower, adoption will be higher or lower depending on who’s in the mix and how the design system has been rolled out.</p><p>Part of this might be to do with the nature of the system and how the organisation ‘gets it’ which is why I mentioned, very hurriedly in my ‘tiny talk’ at #UX2018 that if you have a design system, it’s highly likely you may also need a playbook. Additionally you will need a community around the design system and eventually, it may be that you will need to scale work systems processes around the system <em>to get it to work</em>.</p><blockquote><em>Why my team needs a design system: </em>“Because we have different levels of maturity and a flexible design system can provide some clues. As long as it doesn’t become design by numbers”</blockquote><h4>Increased Efficiency and Speed to Market</h4><p>Consistency was repeated frequently by participants in the survey. However, the causation of the mention is not just about the interface. Commentary form participants related to the impact of researched, benchmarked and tested interface decisions within the design system on the decision making for the teams themselves. For many participants, it’s about the system as translator and the universality of the system. Let’s not forget consistency around interfaces though too and the impact of system ubiquity eg. omni-channel experiences and the problem of parity across multi-device contexts.</p><blockquote><em>Why my team needs a design system:</em>“We are terrible in delivering consistent experiences. Our products doesn’t feel like the same company built them” “Consistency is key to ensure the user doesn’t see the internal silos of your company :)”</blockquote><p>One can understand why ‘bootstrapping’ with Lean Startup approaches and off the shelf open sourced frameworks such as <a href="http://getbootstrap.com/">Twitter Bootstrap</a> has been so popular for startups. Not only is there a way to do ‘design’ quickly but the out of the box framework provides a means for a small entity to maintain consistency, increase efficiency and speed to market once value is established in market. And this works for enterprises too.</p><blockquote><em>Why my team needs a design system: “</em>I worked in an enterprise software company for 6 years. A design system completely revolutionised my team’s ability to focus more time on innovation and less on reinventing the wheel every project.”</blockquote><h3>Design Systems as an Enabler to Better Working Approaches for Designers and Their Teams</h3><p>Participants were asked, <em>“How do you believe a design system might help you in your work?”</em></p><p>The participant responses were affirmative that design systems are perceived to be helpful. Participants explained various value that could be derived for teams from a design system:</p><ul><li>Improved Team Interactions</li><li>Work Efficiency, Lessened Cognitive Load</li><li>Benchmarked Standards and Visibility</li><li>Onboarding of New Team Members</li></ul><h4>Improved Team Interactions</h4><p>Participants mentioned that a design systems could lower friction in their team’s communication and working practices. An orderly design system might help engineers understand the logic of the front-end relating to interface and interaction design decisions. Team members could have the freedom to effect change in the system in a way that collaborative decision making is necessary creating consistent guidance to the team on patterns and interactions. Additionally other functions such as marketing or sales can interpret the design system into their own conversion and purchase funnels if peripheral to areas such as the core product engineering technology stack, service engagement verticals in the broader system.</p><blockquote><em>Why are design systems helpful? </em>“It has made us faster, more consistent and shifted the focus of conversations to be more objective”</blockquote><h4>Work Efficiency, Lessened Cognitive Load</h4><p>Survey participants frequently return to time as a benefit as well as attention to problem solving, as a helpful effect of establishing a design system with consistently used patterns. They also considered the users’ cognitive load with comments relating to the consistency of the experience and less unnecessary differentiation in the design across the front end.</p><p>The benefits also extend to process efficiency, in that high fidelity prototypes and experiments might be created in code with system components already created in front-end service architecture. The barrier to communication is lowered for team members such as engineers inheriting design specifications in that the design system may also have a representative style guide that can be used to communicate decisions around what to use and in which context to use it to afford quicker design decisions within the team, then enabling faster execution by engineering team members.</p><blockquote><em>Why are design systems helpful? “</em>I can spend less time designing smaller parts of the experiences and reuse existing design decisions, which allows me to focus on the bigger problems our customers are facing.”</blockquote><h4>Benchmarked Standards and Visibility</h4><p>Visibility is important in many contexts, from Agile walls to Design Systems. How might a design system be visible? Visibility of a design system, if productionised in front-end architecture, may not be enabled to all team members without a style guide. An alternative might be to create the component visibility in the design software library using ‘symbols’ in Sketch or other devices based on the ‘source of truth’ for a design system. An early stage design system could simply be an audit in the form of a paste up, where all design system components are grouped on print-outs on screens on a wall.</p><blockquote><em>Why are design systems helpful? </em>“Design systems help reconcile our interfaces, make design frameworks visible, components visible”</blockquote><p>So there is a dependency on design system fidelity, in how a system can be made visible. Therefore, for many participants in the survey, a design system is standards made visible and benchmarked across system interactions and visual components presented in a single artefact group that can be consumed by users, the team, to make better design decisions.</p><blockquote><em>Why are design systems helpful? </em>“Collaboration tool, consistency, provide structure and a tool to scale with”</blockquote><h4>Onboarding of New Team Members</h4><p>Participants mentioned it was helpful to have a design system to get started more quickly and provide a catalyst for design decisions in teams. Onboarding team members or new people into the design environment was a significant benefit. Automation of process around how team members access the system, contribute, push to and pull from the system presents additional opportunity, to enable better get up and go for anyone using the system for the first time.</p><blockquote><em>Why are design systems helpful? </em>“So we are not always starting from scratch but following a previously laid out path”</blockquote><blockquote>Overall, Design Systems are about enablement, communication and scale. Not reinventing the wheel over and over again.</blockquote><p>Another interesting outcome was around design community alignment. Participants touched on the ability to utilise a design system within the community of designers to create a benchmark and align other design team members to a process of agreement. Potentially, additionally, design systems can be used to layer constraints and identify opportunities across practice for design system development.</p><blockquote><em>Why are design systems helpful? “</em>To align practices”</blockquote><p>We know that as design systems mature, there is a chance that artificial intelligence might help us evolve them or even suggest suitable interactions and design patterns for new use cases as well as relatable ones, providing us with more opportunity to query the way we define problems and the solutions we deliver.</p><h3>Teams and Design Systems</h3><p>In the next section of the survey, participants were asked, <em>“Does your team have a design system?”</em></p><p>While almost half of participants said they do, a quarter said they didn’t have a design system. The answers in the ‘other’ category, that also consisted of one quarter of participants, were quite revealing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sduRGn3cL9G8PmSayybZjw.png" /><figcaption>Q7 Does your team have a design system?</figcaption></figure><p>Answers to ‘Other’ included the following themes.</p><h4>It’s in progress</h4><ul><li><em>“It’s in progress. Parts are usable as is others aren’t and can hold up development if used”</em></li><li><em>“It’s in the making”</em></li><li><em>“Working on it”</em></li></ul><h4>Needs funding or support</h4><ul><li><em>“Nearly there a half created one that needs more buy in and resources to work together on”</em></li><li><em>“Sort of. It’s rudimentary at this point, but we’re working on it”</em></li></ul><h4>Not exactly a ‘design system’</h4><ul><li><em>“We use a modified version of an existing design system that came with our platform”</em></li><li><em>“Yes but it’s a living style guide — more developer focused”</em></li><li><em>“Kind of. I won’t call it design system because the process of creating it was based on one product”</em></li></ul><p>Many ‘other’ answers related to information in the next section, talking about the challenges of design system persistence. As you can see from above, the comments relate to an emergent design maturity. Many organisations either have a design system or are starting to build them. However what a design system should be, why is best for their practices, organisations and teams, and how the the design system should co-exist and be utilised is still being matured. No doubt participants who said ‘yes’ to having a design system share a similar status. Maturity and knowledge is still being established in the design system space to articulate these ideas more clearly.</p><h3>Design Systems Present Challenges</h3><p>After being asked if their teams have design systems, they were then asked, <em>“What has your experience been in starting/maintaining the design system?”</em></p><p>The general consensus is design system inception and management is challenging, difficult and requires wrangling to get it right. The themes here from participants are:</p><ul><li>Getting a Design System Started, Adopted and Maintained is Hard</li><li>Design Systems Need Service Design</li><li>Ownership Needs to be Defined</li><li>Every Organisation is Different</li><li>The Threat or Opportunity of Automation</li><li>Documentation and Support is Needed</li></ul><p>These themes are explained below, in the next few sections. I’ve included many verbatim quotes here as the information on learning will be useful to many in industry who are reflecting on how to solve for the ‘Design System Adoption Problem’ now.</p><h4>Getting a Design System Started, Adopted and Maintained is Hard</h4><p>Some participants said getting a design system up and running wasn’t difficult which demonstrates some maturation in design system adoption across businesses. Positive news for all advocates of design systems out there and great for anyone who is struggling to find time, funding or support for the inception of a design system in their organisation.</p><blockquote><em>Starting/maintaining a design system: “</em>It took considerable effort to establish, but has got its own momentum now and buy in across the team”</blockquote><p>However the data of the survey shows serious pain points for many participants. These pain points are oriented in the culture and maturity of the organisation, the use of the design system and the culture around the design system itself.</p><blockquote><em>Starting/maintaining a design system:</em> “Easy to start when the team is immature. Difficult to maintain flexibility in it as the team advances — can become a bit of a cult”</blockquote><p>The reference to cult-ism is reasonable. Aforesaid friction around ownership and the ‘source of truth’ was raised in the survey data. The emergence of design ops is a new movement and is now providing designers with the leverage to operate not as a creative peripheral function but a business unit that does things of value. However cult-ism in ownership is something different else, and we may need to resolve it to enable design systems to succeed and benefit our teams.</p><p>Return on investment is difficult to establish in a business case without retrospective findings as mentioned by some participants as well, which also supports the rise of design ops and business orientation in design functions; <em>“Trying to get it started has been hard amongst the business they can’t see immediate return.”</em></p><p>The solution to this ROI problem might be via surveying/interviewing the users of the system eg. the teams and organisation. In order to work out the way productivity might be enhanced, a suggestion would be to treat the design system like any other initiative. Perhaps run a lean experiment with a system for one initiative etc to establish value rather than move forward with no data or learnings to support.</p><blockquote><em>Starting/maintaining a design system: “</em>Starting and maintaining systems is life, it is hard”</blockquote><p>The next verbatim participant feedback demonstrates again that while the decision to start a design system may not present huge difficulty, the reality of building and owning a design system product and service requires much more attention. Much like a product or service initiative, with design systems there are trade-offs too:</p><blockquote><em>Starting/maintaining a design system:</em> “Pain. We tried to incorporate the design system in our project but as it wasn’t mature enough and didn’t have all the elements we required, we were having to go through the process of getting them signed off which slowed us down massively. As we were time poor we ended up moving away from depending on the design system and will be looking to integrate some of the additional components post-launch.”</blockquote><p>Process is needed but slow processes, logically, cause dependent systems and teams to slow down as well. And if other teams rely on a design system, being slow can be a critical interdependency risk to adoption of the system across products and services.</p><p>Which brings me to the next section, about design systems and service design.</p><h4>Design Systems Need Service Design</h4><p>Another participant mentioned the ‘service design around’ the design system which brought a twinkle to my eye, because this is, I feel, a key to getting design systems solved for designers, teams and organisations.</p><blockquote><em>Starting/maintaining a design system: “</em>I worked at a client beforehand that had a huge design system across brands and it was a maintenance nightmare — mainly because the service design around HOW teams use it wasn’t thought out. For a design system to succeed, it must be driven by the organisation structure and culture. If the business isn’t set up to support the system as a product, it will 100% fail.”</blockquote><p>This comment mirrors my experiences to date. Having resuscitated one design system, pitched another, incepted two and observed an amazing design system that’s ready to go and not adopted… as well as other cases of change and issues with definition around launch and rollout to users, isn’t it terrible that as design teams now we might have ‘permission’ to build these systems, we can’t get the systems to work for us, or our teams.</p><p>Not only for us, as individuals but other users too. Think of the beneficiaries of these systems if the service is considered eg. the users on the other side of the system we design. In order to not fail everyone, we must understand the needs of the organisation, the needs of the users in teams as well as the outcomes for the people who experience the effects of the design system in our products, systems and services. Then, we must design for them both in the product, the design system, and the service it is delivering to it’s users.</p><h4>Ownership Needs to be Defined</h4><p>Part of the service design of design systems is defining owners. At the Melbourne Web Meetup last year I talked about design systems in relation to experiences we are designing for and the source of truth. I hadn’t fully synthesised my ideas at the time and was thinking about consistency and system ubiquity (all systems we design for in an ecosystem) in relation to design systems and letting go of execution.</p><blockquote>How might we still design if we don’t execute the design at pixel level? We problem solve, improve and innovate around and with the design system</blockquote><p>This letting go was in relation to our self-identification of designers in what we do as practitioners. The audience at the Melbourne Web Meetup consisted of designers and engineers.</p><blockquote><em>Starting/maintaining a design system: </em>“Difficult! Our UI team has grown and then diminished so maintaining a process has been difficult. Gaining consensus on which ‘system’ is the right one within engineering is also been a struggle”</blockquote><p>At the time, my opinion was that the best place for designers, embedded in engineering teams, who had an interest in creating better space for problem solving and UX, would be to take a position of advocacy for design systems. This advocacy would be to empower engineering to hold the source of truth, the design system artefact, which is in many cases (unless the service is different) a technology artefact.</p><p>Tools are an additional pain point for some participants as our product and service eco-systems become more complex. As designers, we need to behave like engineers or product/creative technologists. While these challenges create learning opportunities, they also embody frustration for many designers who are not equally equipped for the task. Space for learning also needs to be afforded to designers if faced with additional challenges outside of their knowledge set. Likewise, designers need to collaborate with people skilled in the areas they are interacting with, such as engineering, to succeed.</p><blockquote><em>Starting/maintaining a design system: </em>“Frustrating, there are no mature tools for this task, only hacks with react or sketch, abstract. This isn’t the first design system I create though, so it’s easier this time around but the company is a lot more complex than before where I had just three apps on three separate platforms”</blockquote><p>The challenges of new terrain, in my mind, creates the case for passing ownership of the artefact to the team rather than the individual. The high fidelity artefact being the production code or the end-state prototype, rather than the working Sketch files or lower fidelity designs, means that the design system exists independently and requires many hands to ‘ship it’.</p><p>In a team I worked with on native apps we sought to reflect the production code in Sketch via regular version control and merge rituals. However this was highly manual and time intensive. We didn’t have the Sketch and React integrations web teams benefit from, technically we couldn’t make our system universal to the web system or present it in the same setting. We hacked responsive design principles into our approach with device widths and landscape versus portrait orientation for various devices (iOS and Android) in our design system views. Due to system constraints and integration restrictions, we could only react back into the work stack manually rather than automate easily with two different kinds of production code (Swift and Android/Java) like we can now with React and Sketch. The ability to reverse this manual flow to high fidelity is an opportunity in the native app environment, however in the web environment we are still improving on this across all technologies and system stacks, so we still have a way to go.</p><blockquote><em>Starting/maintaining a design system: “</em>Difficult to have a source of truth and keep track of divergence. Difficult to maintain once design system between designers, and between design / FED”</blockquote><p>The desire to push production code as the source of truth has been the often unarticulated agenda for many human-centered designers, including UX-ers, I have worked with to date. This is not to say that system ownership should not exist with design, but that UX-ers wish to be relinquished of the execution load, the pixel pushing, to help them have time to problem solve, particularly if participating in Agile cross-functional teams.</p><blockquote><em>Starting/maintaining a design system: “</em>HARD. We are on to our second version of the system. It’s hard to get the components structured well, named well, and designed well. We learnt a lot in the first go of it, and believe our second pass is better suited for the company. It takes way longer than you expect, and must be done well by detail- and abstracted-orientated people”</blockquote><p>Saying this, interaction and visual design is intrinsic to the user experience of products and services and we cannot ignore it. The UI and product design focus, of part of our community, is equally important and informs the way we design for usability and accessibility. Challenges around consensus also exist.</p><blockquote><em>Starting/maintaining a design system: “</em>Hard to get consensus.. and it is constantly evolving/ living set of guidelines”</blockquote><p>As a profession we have fractures between UX, service design, UI and product design. Our agendas are similar and different. Design systems can serve an objective to solve this design culture alignment issue with something visible to refer to, in order to help us all do our best work and prevent factional disparity in the way we deliver value to our customers and users.</p><blockquote>Perhaps working out the best service provision and work system approach to a design system is the way to go, in order to align design community team members as well as other functions</blockquote><p>For me, working with engineering or other functions is non-negotiable in the approach to design system creation. While it may be faster and useful to spin up the first phase or slice of a system independently, over time the community ownership of the system with rituals built around it in a cross-functional guild oriented approach has been the best way to execute and manage the design system, to keep it living, that I’ve seen to date.</p><h4>Every Organisation is Different</h4><p>Processes are different in every organisation as are how we are organised. While we might establish standards in design systems, the strategies we use to approach how we might organise around the design system and provide a service strategy to support one/many in our design operations might vary.</p><p>I’ve talked quite briefly about using playbooks to support a design system at #UX2018, however a playbook can only be supported by understanding your users and system constraints/dependencies first. Running a discovery and vision approach for a design system could be hugely useful to take it beyond an experiment that has a likelihood of failure if strategies to system adoption aren’t understood early and reviewed often.</p><p>Stories from participants in this survey were quite telling of different approaches to design system organisation. This detailed story from one participant describes a participant’s approach to the complexities of an organisation with mixed adoption of a design system and a team that owns the system itself:</p><p><em>“I typically pull from the existing design system to craft mockups.</em></p><p><em>Since all our design and front-end development teams are at different stages of fully embracing the system, I am also responsible for lobbying for updates to be made in order to be compliant with the system. These arguments typically don’t end at “Because we need to be consistent”, as my stakeholders are wary of doing things simply for the sake of falling in line.</em></p><p><em>So oftentimes I craft arguments based on UX principles (which sometimes includes running studies of people using a mockup with our “old system”, which really is a hodge-podge, versus the new system).</em></p><p><em>I also have conversations with the team heading up the design system creation, so that I can ask questions or point out aspects of the experience that have yet to be addressed.”</em></p><p>This story retells an approach of a user, a UX Designer, interacting with the system, using user-centered arguments to provide the right approach to her team. There is a load on the designer to justify similarity and change in execution it seems. Everyone wants to make an impact, don’t they, but perhaps not at the users’ expense ie. the customer.</p><h4>The Threat or Opportunity of Automation</h4><p>Design systems present a threat or opportunity depending on one’s position and approach to design. The dominant attitude from participants is that design systems help us design better and problem solve more. However we, as a community may still maintain a social conscience and awareness of the effects of opportunities for our colleagues who are user interface focused.</p><blockquote><em>Starting/maintaining a design system: </em>“I wasn’t responsible for creating or maintaining it, but having recently started to use it I can see its benefits in terms of efficiencies, although I wonder if it would make some of our in-house UI designer roles redundant.”</blockquote><p>Often what I also see is a defence of creativity in relation to the use and maintenance of the design system, and the perception of the design system as creativity’s rival. However, once the usability and user experience is established as ‘good’, there is great opportunity for optimisation and emotional design to delight end-users. However, even then the design system establishes visual design as a theming and optimisation function. Although not much was said about this by survey participants, it’s definitely a frustration I’ve heard vocalised by creatives, visual or UI designers despite their support and belief in consistency.</p><p>My thinking is optimistic, because a design system might only accelerate our approach to better interaction design and more beautiful visual interactions. If some design decision making is benchmarked, in flexible architecture, we may have better ways to optimise these interfaces for our users. Don’t forget we might mimic these paradigms of systematisation in other design execution areas such as service, voice, touch, mixed reality contexts too.</p><blockquote>Design systems present a threat or opportunity depending on one’s position and approach to design. What is your design mindset?</blockquote><p>As long as design systems do not infiltrate in to the dark side, rather with the right service and user interaction around them, and correct automation, they will help us use the force for good. The disclaimer to this is as long as we use them ethically and responsibly, with the right community ownership, attention and problem identification, before solutions in the design system are realised.</p><h4>Documentation and Support is Needed</h4><p>The repeated friction between system and use is clear from participant feedback, in that maturity is not established around design system behaviour with teams and organisations, yet. We have many opportunities to improve this, however these opportunities warrant a deep breath and view of the vision for the system and how people and teams should use it.</p><blockquote><em>Starting/maintaining a design system: “</em>It is a living, breathing organism that must evolve as we grow/change/need it to. Also, documentation — a central documentation area — is crucial.”</blockquote><p>The next sections will discuss Agile approaches, team focuses and user centered design in relation to design systems.</p><h3>Is your team ‘Agile’?</h3><p>Participants were asked about starting and maintaining design systems in the previous question, then they were asked, <em>“Do you work in an agile team?”</em></p><p>Answers overwhelmingly “Yes” to working in an agile team, with three quarters of participants answering this option. Almost ten percent of participants said “No,” and fifteen percent said “Other.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w80w4E7MrVeoLgINgskuGg.png" /><figcaption>Q9 Do you work in an Agile Team?</figcaption></figure><p>Answers to ‘Other’ included the following themes. Participants with a consultancy focus talked to the variety of methods and approaches taken in market with customers who are organisations. Others talked about projects, quasi-Agile approaches, waterfall and then some natural cynicism about whether Agile is ever done well crept in too.</p><h4>It’s Mixed</h4><ul><li><em>“Multiple clients with multiple methodologies”</em></li><li><em>“In namesake, yes, but in my perspective we often roll out in waves”</em></li><li><em>“Projects some of which are agile”</em></li><li><em>“Not true Agile, it’s leaning toward waterfall”</em></li><li><em>“Hahahahahaha no one does Agile,…”</em></li></ul><p>So while teams might be cross-functional and multi-disciplinary, Agile mindsets and approaches appear to be disputed or non-existent for approximately a quarter of the participants who responded to the survey.</p><h3>Design Systems and Agile Teams</h3><p>Participants were asked about starting and maintaining design systems in the previous question, then they were asked, <em>“If yes, how important do you believe a design system is for a designer working in an agile team?”</em></p><p>The question presented a five point likert scale to participants with a range from <em>Not at all Important</em> (1) to <em>Highly Important</em> (5):</p><ul><li><em>#5</em>: 58.1% (18 responses)</li><li><em>#4</em>: 29% (9 responses)</li><li><em>#3</em>: 12.9% (4 responses)</li><li><em>#2</em>: 0% (0 responses)</li><li><em>#1</em>: 0% (0 responses)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bd8PtbJvxsYbYy-Q32dIgw.png" /><figcaption>Q9 Are you responsible for design, user research and/or user testing in your role? Rate from where 1 is not at all Important to where 5 is Highly Important</figcaption></figure><p>The answers from the ‘Yes’ group, including some who didn’t answer ‘Yes’ specifically, given there were thirty-one responses in total, not thirty-four, indicating that the perception of importance of a design system for designers in an agile team was considered to be of moderate to high importance by most survey participants.</p><h3>In agile teams, design systems are important</h3><p>In light of their answer to whether design systems are important for designers in agile teams, participants were then asked, <em>“Why do you feel this way?”</em></p><p>Themes that came through were around quality, iterative process, speed to market, ability and also the idea that agile doesn’t matter, that design systems also operate well in waterfall project delivery settings:</p><ul><li>Benchmark Consistency and Increase Speed</li><li>Designing the Experience, not Just the Interface</li><li>Design Ops Enable Iterative Design Processes to Happen</li><li>Shared Design Context with Delivery Teams and Functions</li><li>Also, The Team Doesn’t Need to be Agile</li></ul><p>These themes are further elaborated on below:</p><h4>Benchmark Consistency and Increase Speed</h4><p>Many participants mention speed to market as a key benefit of a design system, in aiding them to be more efficient and consistent in their practice.</p><blockquote><em>The importance of design systems for designers in agile teams: </em>“It enables the designers to prototype at speed using existing components”</blockquote><p>Interestingly when speed is a focus, and team capability isn’t perceived to be as important, a design system may help to maintain design quality, which might otherwise be undermined without one.</p><blockquote><em>The importance of design systems for designers in agile teams: </em>“Speed of delivery, team capability isn’t under scrutiny”</blockquote><p>Interestingly participants seem to have misread the goal of “Agile” which is speed to value for the customer, not speed to market. It seems the teams or organisations they serve may have this ‘first in market’ mandate at the expense of value.</p><blockquote>Perhaps the value of a design system for an agile team is better expressed as a ‘speed to value’ enabler, in that designers and their teams have more time to problem solve than to re-invent the interface wheel repeatedly</blockquote><blockquote><em>The importance of design systems for designers in agile teams: </em>“Speed is crucial in agile, and easily reference-able design systems help you move quickly”</blockquote><p>While speed is important, what is also important is the experience. The design system may create risk in enabling quick ‘solutions’ which, if not treated as experiments, may cause inherent risk in the speed to market race many of us seem to be participating in. I‘d advocate that it’s ok to slow down or have space to think with your team.</p><p>Let’s not follow a predictable road, avoid fatalities, and have the agency to correct course with our design systems as an enabler. Good suggestion, if we can afford the time and space to do so. While design systems answer and efficiency and time constraint on our work approaches they could also enable poor behaviours in the execution of invaluable solutions for users. Hence the designer is still needed, even if some actions are automated over time.</p><h4>Designing the Experience, not Just the Interface</h4><p>In this light, survey participants again returned to the value of problem solving enablement in light of the use of design systems:</p><p><em>“Teams want to be able to work quickly, validate their experiences as soon as possible. Having a system that enables agile teams to focus on the customer problem, and not deciding what shade of green to use on a button”</em></p><p>The benefit of a design system is focus. While the process and execution are important, having something that is reliable to help create conventions in the use of patterns and interactions as well as information design can have tangible benefits for the product and service end-user. For the user of the design system, the designers and their teams, including for many engineering and product team members, all of a sudden there may be less discussions on the visual presentation of a call to action and more conversation around the why users should interact with it in the first place.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>Less spec work makes it easier to talk about the whys rather than hows”</blockquote><h4>Design Ops Enable Iterative Design Processes to Happen</h4><p>Just like the systems we create, whether they be product or service oriented, we need to provision around use and allow the systems to be living and evolvable. Many of us are working in continuous delivery and continuous improvement environments and it makes sense to systematise parts of the architecture that touch other parts in order to make that part of the system relatable and flexible to work with.</p><p>Designers naturally iterate on ideas and solutions, hence it makes sense to enable a tool that creates systemic efficiency for many people interacting with it as users in an eco-system not unlike engineers do already.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>Design is by a nature inherently agile as it should be optimal for a specific experience and should be flexible to extend always”</blockquote><p>System architecture is a term that is often applied to the engineering code and technology services, and not necessarily to the design decision layer that applies to a user experience. However the execution of design decisions have the potential to affect the system technology architecture just like any other change to a service, API, warehouse or repository.</p><p>Designers are working in engineering environments frequently, creating a state where design and engineering interact, together with other functions, to change, improve, innovate or depreciate a system are frequently interchangeable in intent with different kinds of execution methodologies. Therefore, in a technology context, design, though inherently considered ‘creative’ is very much technical and vice versa.</p><p>The task of design is now to make the best decisions we can for the people who are our end-users of design systems, by improving our own team efficiencies as users of these systems also, so enters the age of Design Ops.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>library maintenance enables continuity and extensibility of evolving design decisions”</blockquote><p>Given the shared context with engineering, in delivery we are all actors, working together to deliver something to an audience of our products and services. We just need time, as the participants in the survey are telling us, to spend more time on the why and less on the how.</p><h4>Shared Design Context with Delivery Teams and Functions</h4><p>By sharing design execution in a systemic way that anyone can use it, we create focus for efficient design process when things need to be built with production code. The ability to sketch something, reuse patterns, whiteboard with our colleagues and prototype quickly are all benefits of establishing a design system with core components that are reusable.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>In my company we are months ahead of the engineering team in terms of work so it is difficult for us to be part of that sprint, however we have to work with the engineers and help with the work they are doing continuously”</blockquote><p>Having the ability to create a shared understanding via a system has multiple benefits, especially if it is well adopted and scaled appropriately, adapting to changes. No person is an island, and certainly this is the case in organisations delivering products and services to customers.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>Helps designers keep their work consistent across the product, across time, instead of falling into the trap of myopically designing one screen in isolation”</blockquote><p>The gathering of the interface into a fidelity that helps more than one function or specialisation in a team or organisation create a mutual understanding is a win. Having the ability to create rituals around system maintenance, in order to enable the ability to sync users of the system with decisions being made in a vast organism that is an organisation, can only help progress, a shared understanding for design system users and efficiency in decision making.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>Helps to sync our design and engineering efforts all the while keeping other teams informed”</blockquote><p>Having a single source of truth for design and engineering diminishes tensions and helps alignment in teams in order to progress team collaboration and focus.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>So we can focus on delivering things. Not slide decks, but real outcomes. Working in the same methodology as devs helps bring alignment of focus and maintain view of the deliverable”</blockquote><h4>Also, The Team Doesn’t Need to be Agile</h4><p>While agility is important to many participants in this survey, possibly given many are working in agile teams already, it is also important to acknowledge that design systems have value for waterfall and project delivery teams too.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>I think it’s important for all teams, so I don’t feel the “agile” nature impacts my viewpoint. I’ve worked on very agile teams previously and think a design system there would be just as beneficial as it is to a more waterfall style”</blockquote><p>While the benefits of design systems clearly exist for teams working with an agile approach to delivery, waterfall oriented project teams might still benefit from the ability to create, maintain and evolve a design system too.</p><blockquote><em>The importance of design systems for designers in agile teams: “</em>I don’t see how an Agile work environment changes anything about the design system, or vice versa”</blockquote><p>All in all design systems clearly have value for many reasons in agile and waterfall delivery settings.</p><h3>Who is responsible for the Design System?</h3><p>Participants were then asked, <em>“Who in your team is responsible for the design system, if you have one?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFYC_nro5I7ZdEfknkk5hA.png" /><figcaption>Q11 <em>Who in your team is responsible for the design system, if you have one?</em></figcaption></figure><p>Participants were able to answer multiple times. Most people answered across three functions including; design, engineering and product.</p><p>The most roles nominated as responsible for design systems were, in order of frequency of mention:</p><ul><li>UX Design (13 votes)</li><li>Front-end Engineering (12 votes)</li><li>UI Design (10 votes)</li><li>Product Design and Visual Design (7 votes each)</li><li>Product Manager (4 votes)</li><li>UX Engineering and User Research (2 votes each)</li><li>UX Manager, Product Owner, Service Designer, Whole Team (1 vote each)</li></ul><p>While more regular delivery roles dominate the mentions and UX and Design have majority ownership in this survey’s findings, we now have what appear to be perceived business oriented and strategic roles (product managers, UX managers and service designers) entering the area of design system ownership. Delightfully, ‘whole team’ was mentioned as well.</p><h3>Are Design Systems and User Centered Design a Thing?</h3><p>After this the survey was flipped to thinking about end-beneficiaries, the users of the systems and products we design for, <em>“In general, how important do you believe a design system is to user-centered design?”</em></p><p>The question presented a five point likert scale to participants with a range from <em>Not at all Important</em> (1) to <em>Highly Important</em> (5):</p><ul><li><em>#5</em>: 47.1% (16 responses)</li><li><em>#4</em>: 23.5% (8 responses)</li><li><em>#3</em>: 23.5% (8 responses)</li><li><em>#2</em>: 5.9% (2 responses)</li><li><em>#1</em>: 0% (0 responses)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bdaej_l1xoZDmTe4tUzRmQ.png" /><figcaption>Q12 <em>In general, how important do you believe a design system is to user-centered design?</em></figcaption></figure><p>Almost half of participants voted for option five, ‘highly important,’ in response to the question, <em>“In general, how important do you believe a design system is to user-centered design?”</em></p><p>Slightly less than this number voted for neutral to moderately important and a low percentage of participants, less than six percent, voted for slightly important on the scale.</p><blockquote>All in all, allowing for the number of votes in moderate to high on the scale, almost seventy-one percent of participants consider design systems moderately to highly important to user-centered design.</blockquote><h3>Why should design systems be user-centered?</h3><p>In light of their answers to whether design systems are important to user-centered design, participants were then asked, <em>“Why do you feel this way?”</em></p><p>Themes that came through were around interdependencies of approach versus systems, learning and cognitive load, user needs and stakeholder feedback or interactions:</p><ul><li>User-centered Design (UCD) Can Happen With or Without a Design System</li><li>Design Systems May Not Cover All User Needs</li><li>Learning is Improved, Cognitive Load is Lessened</li><li>Helps with Mitigating Effects Highest Paid Person’s Opinion (HiPPO) Syndrome</li><li>Ultimately the Team is Enabled to Become More User Centred, Too</li></ul><p>These themes are further elaborated on below:</p><h4>UCD Can Happen With or Without a Design System</h4><p>Some participants commented that user-centered design can happen independent of design systems, which is absolutely true, it can. UCD is not interdependent on design systems, however design systems can enable UCD, enhance and improve it via the volition of the teams who make system changes or create system components.</p><blockquote><em>Why should design systems be user-centered? </em>“Helps guide the process, but you can be user-centered (whatever that means lately) without a design system”</blockquote><p>Just like UCD it depends on the team and the approach. And remember, approached and built correctly, a design system can afford better accessibility enablement too.</p><p>Supporting this conjecture around the need of design systems, a related question came up regarding the need for a design system, particularly with finite, non-continuous projects:</p><blockquote><em>Why should design systems be user-centered? “</em>I think it depends on the work. Some projects don’t require ongoing maintenance in the same way that enterprise products do, for example, so a design system might be too much”</blockquote><p>Decisions regarding effort and value of design system investment must be made to warrant a systemic approach to implementation. However a user-centered approach to the design of anything can never be awful and is always better for the user.</p><h4>Design Systems May Not Cover All User Needs</h4><p>Despite the sense that many survey participants felt, “<em>You can be user focused with anything,” </em>there was still conjecture that a design system may not always be user-centred due to the constraints of consistency.</p><p>It seems that the following comment, below, relates to frustrations around the maintenance of consistency as a trade off for user value, in favour towards the value of continuity. It may be an edge-case but it is a useful point to consider.</p><blockquote><em>Why should design systems be user-centered? “</em>Design systems are an important ingredient in creating continuous experiences. Continuity builds trust and confidence, which are fundamental aspects of user-centric design. That said, I don’t rate it 5/5 because I believe there are other elements of user-centered design that are also highly important. For instance, I wouldn’t sacrifice a niche user need for a certain type of interaction simply because it isn’t embraced by a design system”</blockquote><p>This commentary signals a frustration with systems and generic ubiquity. It could be that as design team owners, while we should act as gatekeepers to ensure the quality and adoption of the design system is maintained, we should be open to new scenarios, needs cases and improvements for users.</p><h4>Learning is Improved, Cognitive Load is Lessened</h4><p>Interestingly, overall the use of ‘user’ is interchangeable in some of the participant feedback. Users are both the individuals and teams who collaborate and use the design system internal to the organisation. But, also, users are the people who use products, systems and services.</p><blockquote><em>Why should design systems be user-centered? </em>“Continuity of components makes for a more learnable experience; efficiency of code makes for a faster experience”</blockquote><p>It is fair to conclude, after understanding previous commentary and themes, that design systems have benefits for multiple user roles.</p><blockquote><em>Why should design systems be user-centered? </em>“For larger sites and organisations, a design system helps to create cohesive interfaces, which are easier for the user to learn and use. Eases cognitive load”</blockquote><h4>Helps with Mitigating Effects of HiPPO Syndrome</h4><p>We all understand the frustration, as designers, that we experience in this scenario; we’ve done the due diligence on problem solving, ideation, prototyping and testing and an influential stakeholder comes along and wants to change the interface design or user experience. Design systems present the opportunity for user-centred validation (or invalidation) to occur in a way that is absolutely scientific and unarguable, if we as teams enable feedback loops into our design system services.</p><blockquote><em>Why should design systems be user-centered? </em>“Cuts down on ambiguity when using proven (patterns) influential stakeholders can’t argue with it”</blockquote><h4>Ultimately the Team is Enabled to Become More User Centred, Too</h4><p>Overall, many participants felt positive about user-centred approaches to design systems given it is their job to advocate for the customer/users. So not only is the design system user-centred by enabling better team practices and capability, the team inherits the benefits of user-centred design as well:</p><ul><li><em>“User centered design feeds back into the system, so it is always relevant for our customers”</em></li><li><em>“It just helps use tried and tested patterns but if the patterns aren’t good it’s not user-centred”</em></li><li><em>“A design system is only valuable to a user if it helps her reach her goals”</em></li><li><em>“I think it’s context specific”</em></li><li>“<em>Everything should be user, value centered to ensure success and sustainability”</em></li><li><em>“it aligns with best practices and validated principles of creating easy to use products for all user segments”</em></li></ul><blockquote><em>Why should design systems be user-centered? </em>“I’m a uxer…”</blockquote><p>Some participants felt a this was a complex question to answer, though, due to the constraints of the way their own teams were organised. For example, in this participant’s case:</p><ul><li><em>“This is a confusing question. For digital products: Design is a bucket that encompasses interaction and visual design. The Interaction practice has the user as king, the visual practice only needs To be in good graces with the user”</em></li></ul><p>However, consistency wins from a user-centred design and value approach. For many participants this is the explicit value of a design system, to create consistency and modularity from which better, user-centred design experiences might be created:</p><ul><li><em>I think if the design team feels less cluttered we can spend more time on the user and that is what really matters</em></li><li><em>A framework for consistency of approach</em></li><li><em>Consistency cross-products</em></li><li><em>Consistency! And forces you to consider different states &amp; scenarios for each component, which can’t be done when working with full screen mockups.</em></li><li><em>because consistency really matter for user, it will really help them to understand our product</em></li></ul><p>Overall, without a user-centred, consistent approach, participants feel not only teams might be misaligned, but the user experience of other systems, products and services may be less user-friendly too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*efgrmliExBB5ftkY0J7yaw.jpeg" /><figcaption>“I need space to do all the things” (Edward Scissorhands meme via imgflip.com)</figcaption></figure><h4>A Brief Note about Unicorns</h4><p>In conclusion, it is valid to hypothesise that design systems may be the solution to provide designers and their teams more space, and time, to do the work that’s needed for the best outcome for our users, as well as their teams and themselves.</p><p>I often hear revulsion in the voices of designers who vocalise around having to do the ‘full stack’ of UX in agile cross-functional product and service delivery teams. It seems that revulsion stems from the fact that our responsibilities cater for three jobs in one eg. interface design, user research, user testing. And this is just the second or third diamond, not the first. Nor might this approach actually be human-centered, as teams may progress down a path that has predefined parameters that may be within and outside of our control as designers additionally.</p><p>In a cross-functional team of one designer, how might the designer get ahead with research, undertake design experimentation and execution as well as test and learn, rinse and repeat? Let’s not forget the problem of vision and design ops responsibilities. Just like Engineers and Product we need to do our housekeeping too.</p><p>We all know that Agile and UX has presented the ‘unicornisation’ of the designer. Lean UX has presented an antidote to the unicorn, however with Lean we need a systemic approach, as with Lean, we are moving towards process efficiency on the factory floor. Enter, The Design System.</p><p>Any discipline practitioner presents a T-shape to their team and cross-functionally, making us all a bit dissimilar. What this means in multi-disciplinary teams, is that the team collaboration we are establishing as we get to know each other, as we share competencies, skills and knowledge, will always have a different ‘flavour.’ This isn’t any different in design, as many designers are different, yet may present with a similar job title.</p><p>This doesn’t account for the introduction of Lean in Agile UX and product design, which suggests helpfully, that we should draw first. However the constraints of a draw first, and draw to execute, approach favoured in agile relies on a system that allows our colleagues to execute design solutions on our behalf, especially if, as designers, we are moving to the next set of problems to solve.</p><h3>A Note: Thank You to Participants</h3><p>I’d like to thank everyone who participated in the survey. Your time and participation was hugely appreciated and I hope you find the information in this article valuable for your team. For anyone creating, establishing or maintaining a design system, I hope this is useful in your day to day work. There is more information to share and synthesise, but perhaps I’ll publish that next time in a separate article.</p><p>Ciao for now, folks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42418819f65a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interactive-mind/design-systems-and-agility-part-2-of-2-42418819f65a">Design Systems and Agility (Part 2 of 2)</a> was originally published in <a href="https://medium.com/interactive-mind">Interactive Mind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems and Agility (Part 1 of 2)]]></title>
            <link>https://medium.com/interactive-mind/design-systems-and-agility-part-1-of-2-b96c188acfca?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b96c188acfca</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[complex-adaptive-systems]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Sat, 15 Sep 2018 14:19:34 GMT</pubDate>
            <atom:updated>2020-02-07T14:04:24.766Z</atom:updated>
            <content:encoded><![CDATA[<h4>Extended from my recent talk at UX Australia Conference #UX2018</h4><p>In August this year, I gave a <a href="https://www.beautiful.ai/deck/-LKofvYFW1yi0TbmMcKh/2018-August-UXAus2018-Design-Systems-and-Agility">20 minute talk on design systems</a> and their importance to, not only designers, but teams and organisations. This talk sat in many camps, from design ops to human-centered design, front-end engineering to UX and interaction design.</p><p>The talk this article is based on has been iterated on from a previous talk presented last year at <a href="https://www.meetup.com/en-AU/the-web/events/244943794/">The Web Meetup</a> in Melbourne, which was more technically oriented.</p><h3>Why Design Systems?</h3><p>The value of a design system is more than just the system itself.</p><p>It’s also the potential benefits for designers, teams, build efficiency and de-risking, continuous improvement enablement and the reduction of system legacy. Design systems aren’t just a notch on the visual/UI designer and front-end engineer’s belt.</p><p>I started thinking about the subject matter in 2013, when I was creating responsive web components from the ground up with a lean methodology. We were trying to create a single source of truth in the front-end architecture of our system. At the time I was working as a senior UX designer in a cross-functional delivery team within a product engineering setting. At the time, I worked closely with approximately seven engineers and a product manager.</p><p>In a workplace previous to that we’d been looking at living style guide implementations like <a href="https://github.com/kneath/kss">KSS</a>. It was a central design and engineering team in a university environment where faculties were like rogue fighter planes not thinking of the mothership. We wanted to enable them to move fast, but they forgot about the fact that they’d need to refuel. We were trying to help them retain speed, autonomy and efficiency yet also keep our online presence consistent and responsive. At the time design systems weren’t called design systems, yet.</p><p>As I’ve matured as a designer, I’ve realised that it’s not only the system itself that is interesting but the environment within which the system exists. I’m interested in how the system serves the designer, the teams and the organisation it functions within as well as the system’s users in different roles.</p><h4>Who do design systems serve?</h4><p>Design systems are built to serve our teams, as users. If a design system is done right, as designers, we might think more about our product, system and service end-users more often, collaborate with others more easily and become more efficient.</p><p>It is also my belief that via enabling design systems to exist and be adopted, designers and their teams will be gifted with the capacity to give those users and/or customers <em>the attention they deserve</em>.</p><p>Not only this, but design systems that are systemically consistent, utilised widely and easy to adopt or improve, allow designers and their teams to divert their focus on design to problem solving.</p><h4>Time to do the good stuff</h4><p>We might even have time to draw out our own and other’s thinking. Much of the time it’s rushing to screen, without a compass. <a href="https://medium.com/u/b5236ab10f89">Eva-Lotta Lamm</a> talked about the amazing ability of designers to be visually literate, problem solve and communicate powerfully via sketching at #UX2018.</p><p>In our practices I don’t see this occur this nearly enough. A ‘draw, first’ approach is mainly championed in tech via approaches such as <a href="https://www.interaction-design.org/literature/article/a-simple-introduction-to-lean-ux">Lean</a> and <a href="https://vimeo.com/204254753">Design Thinking</a>.</p><p><a href="https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond">First diamond design</a> is something I spoke of at in a talk at <a href="https://uxgatherings.com/events/catherine-hills-blended-design-roles">UX Gatherings in January</a>. It’d be great to see designers, their teams and organisations helping each other more, as the externalities of design execution within organisations cannot be ignored.</p><p>Design systems can provide a support to designers in Agile teams, so broader teams are able to look at first diamond design more often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1q4sDjmRSz8JILCoGNe-Gg.jpeg" /><figcaption><a href="https://www.flickr.com/photos/phploveme/13163823343/">‘Design beyond design’</a> (public commons licensed, credit Jinho Jung UX Camp Seoul 2014)</figcaption></figure><p>Design <em>without</em> humans, especially requiring their interaction or participation, should never be considered ‘good’ design. It’s simply a lick of paint or an unvalidated assumption. It may not make sense. It’s design in isolation.</p><p>Design systems might give us more time to do the good stuff, with others. This comes with a disclaimer however, as design systems, including planning, build and maintenance, require commitment, investment and people time.</p><h4>Design System Hypothesis 1</h4><p>My primary hypothesis is that the value of creating great design systems, is that via the creation of these design systems, with adequate support and documentation, we might generate consistent, useable, accessible, intuitive and user friendly interactions that can be built by anyone in our teams and improved easily with user research and usability testing.</p><h4>Design System Hypothesis 2</h4><p>Not only this, but my secondary hypothesis is that design systems might help designers and teams spend more time speaking with the people who interact with these systems, products and services, therefore having our time freed up to undertake user research, problem solving, prototyping, experimentation and usability testing in order to provide the best solution or outcome.</p><p>I have a bunch of other thoughts, but let’s get to it. The design system survey results from a small network of industry participants will be presented shortly, in Part 2 [to be published].</p><h3>Getting Design Systems Buy in is Hard</h3><p>Which is why I was thinking about this talk. Designers often say, “we need a design system or style guide” knowingly, as if it’s a requirement or everyone should get it. However, often our colleagues don’t.</p><p>Sometimes you’re just lucky. You might work with some people who have created a design system before, colleagues who are excited by new stuff, stakeholders who get the value or you are working with some clever engineers or other designers who like a challenge and nerd out on consistency.</p><p>The latter has happened to me more than once and I had a great time creating and resuscitating some GUI (web and app) design systems. This, starting with an audit, which also takes time, resulted in a much more consistent experience for the teams and for users.</p><h4>Planning and advocacy</h4><p>However, unless you get the cycle time right with your design and engineering team, having a consistent experience may not mean it’s more usable, learnable or accessible. Teams need to undertake due diligence on user research and usability testing too, to make sure the user scenarios that are inherited in the GUI design system execution make sense in the correct context for the user.</p><p>While building design systems in different capacities has been massively rewarding, I’ve also worked with many teams where getting the value of design systems defined, communicated, supported and funded is often challenging.</p><h4>Collaboration and productivity</h4><p>Additionally, for designers and their teams, due to competing priorities, they often are challenged in their time, capacity or ability to support, build and maintain a design system. They may also need to get business teams and engineering on board to share the load.</p><blockquote>Creating a design system sometimes becomes a job times two, rather than part of daily deliverables.</blockquote><p>Design system effort is often relegated to a business as usual work type by organisations we serve. The challenge is that design systems are considered peripheral, lower priority and not as important as the revenue generating initiatives we desperately ‘need’ to ship or release to market. Slowly this is changing. <a href="https://medium.com/u/b772ab9982da">Andy Budd</a> talked about the “productivity boom” with design systems at #UX2018.</p><p>Regardless of whether the team have the sponsorship to get the planning started, consistent design system <em>adoption</em> across teams and across organisational silos is also a challenge once the system is instituted.</p><p>So there are many problems to solve. Thinking about the logistical implications of design systems is complex, just like any other system.</p><p>Next, let’s think about the our daily complexities and factors influencing human-centered design and technology.</p><h3>Our working context in UX design and tech</h3><p>Melvin Conway spoke of the approach of organisations to system design in software in this way:</p><blockquote>“Organisations which design systems… are constrained to produce designs which are copies of the structure of these organisations”<br>- Conways Law (1968)</blockquote><p>Sixty years ago, Melvin Conway was not speaking of the human-centered design approach to systems thinking which we recognise today. This statement might be the legacy of an organisational perspective that may not have understood the interactions of the users. The systems were designed to suit the organisational mental model(s).</p><p>In contemporary organisations, to this day, we are often dealing with the same problem as Conway’s in the re-design of legacy systems, products and services. Amazing, given it’s now 2018 and not 1968. However we are dealing with complex adaptive systems and this current situation is not surprising.</p><p>Thankfully we have seen a shift away from Conway’s Law in the last few decades with a growing recognised importance of human-centered design; Agile transformations in many businesses; changes to engineering methods and architectural approaches; exponential increase of technology advancement; and an increasing automation of repeatable jobs.</p><p>Technology, design and business teams have been navigating this complexity in various strategic ways, including:</p><ul><li>Microservices technology architecture;</li><li>Agile ways of working; and</li><li>HCD, Service and Organisational Design (including Systems Thinking).</li></ul><p>Still, I see issues with our advancement in these ways of working. Human-centered design still requires advocacy and support, Agile is not always adopted well. We are getting better at it, but it’s taking time.</p><h4>Our working environments</h4><p>In modern working contexts, our awareness of change still can freeze teams and can cause delays in decision making. This is because we are working within Complex Adaptive Systems environments, which makes things difficult to predict and chaotic. <a href="https://medium.com/u/6622cc0505ed">Lauren Currie</a> spoke of complex adaptive systems in her amazing opening keynote at #UX2018, where she showed a flock of birds hovering in wind currents.</p><p>Perhaps as a legacy of Murphy’s Law, people are worried about chaos or things that seem messy. Generally, unless used to design thinking process, organisations may lean towards assumptions and quantitative ‘certainties’ for comfort, perhaps until it’s too late.</p><blockquote>“If anything can go wrong, it will”<br>- Murphy’s Law (1952)</blockquote><p>Human-centered design approaches help us all navigate ambiguity and chaos. However, unless we work with human-centred advocates or those who understand and trust in ‘the process’, as designers we may experience challenges in the perception of our roles. Organisations might be more comfortable to see us as visual designers than designers of experiences.</p><p>Designers often attempt to negotiate in these environments and, sometimes successfully, to speak business and technical language in order to help others understand the value of our approaches. Designers need to onboard others into our worlds, so we can enable them to understand the value of what we do, which adds complexity to our roles in the form of additional advocacy and leadership skills.</p><p>What doesn’t help the situation is that organisations are trying to speed up to keep with the times, sometimes at the expense of their own understanding of the problems we need to solve, together.</p><h4>Things are getting faster</h4><p>We are moving in an exponentially faster working world than ever before. As people we are struggling to conceptualise change. <em>The Law of Accelerating Returns</em> ( Kurzweil, 1999) is actually happening — right now.</p><blockquote>“Most long-range forecasts of what is technically feasible in future time periods dramatically underestimate the power of future developments because they are based on what I call the “intuitive linear” view of history rather than the “historical exponential” view.”<br>- Ray Kurzweil, The Singularity is Near (2005)</blockquote><p>As designers, we need to challenge what “Singularity” means to us. Should a future defined by science fiction really be a reality we should follow as a community or in society? I believe we need to be “good ancestors” and create a legacy for generations after ourselves. <a href="https://medium.com/u/b1fa02015e7f">Alan Cooper</a> spoke of this in his impressive closing keynote at #UX2018.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S5m1KT_IyMbtx6wJhlqEQQ.jpeg" /><figcaption>Law of Accelerating Returns — Ray Kurzweil (1999)</figcaption></figure><h4>Science fiction as a vision of the future</h4><p>Tesla, the car company, I’m assuming was named after Nikola Tesla, the inventor of the Alternating Current. Tesla has made impressive innovations in technology.</p><p>Nikola Tesla is quoted at the beginning of Kurzweil’s book <em>The Singularity is Near</em>, with the statement:</p><blockquote>“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some of the creation of the brain unfolding to success”<br>- Nikola Tesla (1896)</blockquote><p>Of course you can understand Tesla’s excitement. How might we feel though, if we create ‘a <a href="https://en.wikipedia.org/wiki/Frankenstein%27s_monster">Frankenstein</a>’ unwittingly?</p><p>In <a href="https://www.goodreads.com/book/show/83518.The_Singularity_is_Near?from_search=true"><em>The Singularity is Near</em></a>, Kurzweil talks about the “magic of technology” and favourite science fiction books. Many of those stories were great, but some are troubling too. As a society we often forget the lessons of history. As a community in technology we don’t seem to be paying attention to science fiction questions enough.</p><p>I see this playing out in contemporary media, such as <a href="http://bladerunnermovie.com/"><em>Bladerunner 2049</em></a> last year. Personally, I thought the film was pants and felt disappointed. Forgive me if you disagree. Perhaps I was the wrong generation in the audience… even though the film was marketed as a blockbuster <em>to everyone on the planet </em>who was over eighteen years of age and could attend a cinema.</p><p>For me, the 1985 original had more substance, paid attention to the ethical themes of <a href="https://www.goodreads.com/book/show/36402034-do-androids-dream-of-electric-sheep"><em>Do Androids Dream of Electric Sheep</em></a><em> </em>and was faithful to Philip K Dick’s discussion of the implications of synthetic memories in androids who think they are human. Was it inhumane to allow robots to think they were human? You decide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*8JMbKpORhA5sSFHGPOfieg.jpeg" /><figcaption>Blade Runner 1982</figcaption></figure><p>My point is that designers have the capacity to change the world, influence people around us and be humanitarian in what we do professionally either by ourselves, with our teams or in partnership with the organisations we serve. And bring that humanity to technology. The capacity to be humanitarian and ethical can be unlocked by allowing ourselves to be human-centred.</p><h4>You don’t need to build ‘things’ to be a good designer</h4><p>As ‘designers’ we are often perceived as people, in organisations that do not understand human-centered design, who make things pretty. We might also self identify the value of our process with making or executing things. I did a talk about this at <a href="https://uxgatherings.com/events/catherine-hills-blended-design-roles">UX Gatherings</a> in January 2018.</p><blockquote>“Anything that can go wrong will go wrong while Murphy is out of town”<br>- Mrs. Murphy’s Law</blockquote><p>As designers we, ourselves, are challenged at separating our value from owning our execution work. In this light, think about Mrs. Murphy’s Law as a bit of a spin on Murphy’s Law (1953). We could easily apply this to designers. Let’s admit it, it’s difficult to hand over the driving wheel if there’s no system in place to help someone else make the best decision with the right support. Also we may not trust them to do it well.</p><p>As designers, we can’t just be about the look and feel exclusively. In technology this is naive and doesn’t serve the user. If you don’t care about the user experience, please don’t design… anything.</p><blockquote>Designers need to put the air masks on occasionally and let others execute, or risk becoming a blocker in an Agile team.</blockquote><p>Sometimes we need to rely on our teams and even people who work in other functions to ‘do’ the design. If we, as designers, don’t trust our Agile cross-functional team member’s capacity to understand how to make the right decision based on a experience and professional knowledge, we need to give them the ability to do it. We can’t blame them for not having a shared understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PaJ7cLkaGavOD-Z9KLizg.png" /><figcaption>iMac (1998) by Apple</figcaption></figure><p>Sometimes this is even a problem within design teams, never mind with other functions. This is not to suggest you shouldn’t care about design or owning work, but the genius of Jonathan Ive was supported by user experience greats in his team, then at Apple, such as <a href="https://medium.com/u/1808934e1fd3">Don Norman</a> and dare I say it, Steve Jobs *insert joy emoji here*. We just need to create the scaffolding so people don’t fall down. Enter the value of design systems.</p><p>UX designers are often the intersection between business, other disciplines and our users. We have a responsibility to the users and organisation we are serving. However, our need for control needs to be smarter. We may need to hand over the reigns occasionally, but let’s get the horse ready first.</p><h4>Keeping the cowboys at bay</h4><p>Our perceived preciousness about design execution is because of a lack of trust due to things like the Cowboy (below). Perhaps our concerns are warranted, especially if we don’t have build standards, play books or design systems, yet. The Cowboy can create poor decisions without support, ignore recommendations and cause chaos where there shouldn’t be any.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*e8vs3d466s_QcwNwj1bQbg.jpeg" /><figcaption>When you turn away, I’ll change your design and release it (designers all know that person, right?)</figcaption></figure><p>We’re in new technology frontiers, there’s a lot of cowboys and it’s easy to freak on the details. Relinquishing a level of control is ok though if we have a system to support us.</p><p>Remember, we’re working in fast moving times now and in technology we have to be prepared to be ‘less precious’ whilst still maintaining quality of interactions and the way we design information.</p><p>We need systems to help us, not only to defend our users from cowboys, but, more positively, to enable teams to cross-functionally support designers with well thought out decisions.</p><p>And also let you have a holiday occasionally, right?</p><h4>The beginning of design systems in web GUI</h4><p>For me, web GUI systems started when <a href="https://medium.com/u/52f676b44c62">Brad Frost</a> created his <a href="http://bradfrost.com/blog/post/atomic-web-design/">responsive design</a> framework. He called it Atomic Design and it was based on the periodic table of elements. For many, it sought to answer the multi-device context and content parity issue designers and front-end engineers were experiencing in the web, as well as increasing system and device ubiquity. User adoption of mobile phones was rising. Around the same period <a href="https://medium.com/u/1608f116ad21">Luke Wroblewski</a> was also leading discussions on mobile first design.</p><p>Agile at this time, for many engineering teams was being adopted more ubiquitously as a way of working. Designers and front-end engineers were moving fast. It just wasn’t efficient to design one thing for a single use-case anymore, we had omni-channel experiences and small teams to build large quantities of things. This point in around 2013–14 was where I saw front-end interfaces becoming like micro-services or a component relating to a ‘moment’ in a service design blueprint. For UX designers, this was important, so we could get on with other stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uhcVPeGql8ejpHjYIbpdJQ.png" /><figcaption>Atomic Design — Brad Frost (2014)</figcaption></figure><h4>Economy of scale</h4><p>Brad Frost introduced into GUI web design an <a href="https://en.wikipedia.org/wiki/Economies_of_scale"><em>economy of scale</em></a>. Use this term as part of a benefits statement next time you need to sell your design system to your product and service delivery teams. The term came from a person called Adam Smith, a Scottish economist and moral philosopher wrote a book called <a href="https://en.wikipedia.org/wiki/The_Wealth_of_Nations"><em>Wealth of Nations</em></a> (1776). His work influenced many generations of modern economists. It might help your agenda.</p><h4>Our attention should be on new frontiers</h4><p>I am not going to suggest that as designers we shouldn’t care about visual interactions, information or visual design, we absolutely should, however designing experiences isn’t only about the screen, the presentation layer or indeed about graphical user interfaces (GUI).</p><p><a href="https://medium.com/u/58c11dfcdf0a">Bill DeRouchey</a> talked about the science fiction future (in a good way) extensively at #UX2018 in relation to design professions. Remember the interface/interactions we design can and will be any of these things and more:</p><ul><li>Screen user interfaces;</li><li>Human to human;</li><li>Multi-sensory (including Touch and Voice);</li><li>Machine/AI;</li><li>Virtual/mixed reality; and/or</li><li>Ethical.</li></ul><p>We all have these things to look forward to, as well as designing systems and standards for these new interfaces to eg. how might we design a voice interface design system? Given the changes that are coming with the future of work, it’s time we all, as a community become more human-centred.</p><p>As a design community getting usable and accessible front-end GUI design systems feeling good and well adopted in engineering for graphic interactions could mean that we have so many opportunities:</p><p>a) GUI interactions have a better chance of feeling good for users;</p><p>b) we can spend more time learning about humans we are designing for and problem solving;</p><p>c) we’d have an industry benchmark on interface systems thinking that we could replicate and extend for other types of interaction contexts; and</p><p>d) a population of really amazing people can start looking at the next frontier, and possibly stop a robot war or dystopian future too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*o9vPcKcegzgPDtErEU3ydA.jpeg" /><figcaption>Say “No” to Robot Wars and Guns — Meme with image from <a href="https://en.wikipedia.org/wiki/The_Terminator">The Terminator</a> (1984)</figcaption></figure><p>Are design systems helping us make our design response to systems that are complex and adaptive more consistent? Next, I’ll define Complex Adaptive Systems (CAS) for you and how it relates to Agile.</p><p>Then, I’ll tell you a story about the weather as a metaphor for Complex Adaptive Systems to help you understand the theory.</p><h3>Complex Adaptive Systems (CAS) and Agility</h3><p>As designers of experiences, we seek to make sense of complex relationships between things. These things include:</p><ul><li>People and/or teams who design, build or deliver products, systems or services;</li><li>The product, system or service and components of each;</li><li>Users/customers who interact with products, systems or services we design and also interact with and their networks; and</li><li>ourselves.</li></ul><p>The systems we design are complex and adaptive, not unlike the weather, or teams! Complex Adaptive Systems are defined as:</p><ul><li>Made up of many individual parts or agents;</li><li>Individual parts or agents, or agents, in a CAS follow simple rules;</li><li>There is no leader or individual co-ordinating the action of others;</li><li>Via the interactions of the agents new patterns are generated; and</li><li>If elements in the system are altered, the system adapts or reacts.</li></ul><h4>How CAS relates to the Agile Manifesto</h4><p>The first part of each statement in the Agile Manifesto speaks to dealing with change; short iterative cycles, incremental learning, being close to users and the empowerment of self-organised teams to make decisions.</p><p>The Agile Manifesto states:</p><ul><li>Individuals and interactions <em>over processes and tools</em></li><li>Working software <em>over comprehensive documentation</em></li><li>Customer collaboration <em>over contract negotiation</em></li><li>Responding to change <em>over following a plan</em></li></ul><p>GUI designers might freak out over Agile not favouring processes and tools. However, have faith friends, as GUI design systems, ideally, should manifest as a working software artefact. And it might help you be better friends with your engineering colleagues. Own it together, don’t get factional, ok?</p><h4>And before you hate Agile forever</h4><p>Agile principles support great human-centered design process and interaction. Check these awesome principles that will make your fears about design quality fade away:</p><ul><li>Principle #1 <br>Our highest priority is to satisfy the customer through early and continuous delivery of software</li><li>Principle #9<br>Continuous attention to technical excellence and good design enhances agility</li><li>Principle #11<br>The best architectures, requirements and designs emerge from self-organising teams</li><li>Principle #12<br>At regular intervals the team reflects on how to become more effective, then tunes and adjusts it’s behaviour accordingly.</li></ul><p>So many opportunities for great work, great collaboration and great user experience design, if done well.</p><p>You might ask, “how are Complex Adaptive Systems like people, teams or design systems?”</p><p>Ok, so let’s move to the weather… and explaining Complex Adaptive Systems metaphorically. Then you’ll see how GUI Design Systems in technology and the weather have much in common, they might almost be kindred spirits.</p><h3>A Story about the Weather: Explaining Complex Adaptive Systems</h3><p>Weather is an example of a complex adaptive system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2sgtuEvgErG5GxNf7_sTQ.jpeg" /><figcaption>USA flooding 2018 (public commons licensed)</figcaption></figure><p>As a designer of complex adaptive systems, we may sometimes act like satellites, observing patterns and the changing system’s effects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eaFRBmZ0KlSHFr79C_KBPA.jpeg" /><figcaption>Image courtesy of NASA (public commons licensed)</figcaption></figure><p>We may also interact with, influence or change the effects of complex adaptive systems periodically, eg. daily or per sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*i0v4T4m0905nBRMSkt9ZyA.gif" /><figcaption>Example of a weather radar (public commons licensed)</figcaption></figure><p>We might also have different ways to help us monitor change and methods to help us increase predictability eg. with analytics, data or via observation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*cuLw6y3o3yzJRN0W6aadiw.png" /><figcaption>Weather observation types (public commons licensed)</figcaption></figure><p>However, nothing is as reliable as the ability to understand change retrospectively eg. via trends and behaviour over weeks or months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMeW5WQJgl0AhqgsdJjdMQ.jpeg" /><figcaption>Elnino over time (public commons licensed)</figcaption></figure><p>There are barriers to predictability and we must consider how to make system adjustments responsibly, perhaps incrementally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Bw8hTQtgD5H_cq_mTq_Ng.jpeg" /><figcaption>Greenhouse Gases in January 2006. Image courtesy of NASA (public commons licensed)</figcaption></figure><p>The people who interact with these changes might say, “Is this wierd?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3iwFJoIN2DMJaafkjVZFgg.png" /><figcaption>Is this wierd? Yes or No — From iSEE Change</figcaption></figure><p>The effects of weather can be chaotic given the nature of the system and limited predictability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*So0Vbp3jX4eQmfUZe0A5RA.jpeg" /><figcaption>Hurricane Irma Survivors (public commons licensed)</figcaption></figure><p>“Oh no, it’s snow” (below) versus “Oh, yay it’s snow” (below next).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JpTDkmtogFBrh2askuPs6Q.jpeg" /><figcaption>Snow #1 Oh no, it’s snow (public commons licensed)</figcaption></figure><p>Not only is the user prepared for the weather but she is enjoying it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kfg3it0LaDHBV_nPPOLgAw.jpeg" /><figcaption>Snow #2 Yay, it’s snow (public commons licensed)</figcaption></figure><p>As designers of an experience that interacts with users we may wish to understand initial conditions, in order to make incremental adjustments to limit the potential of chaos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3TiE2y2W4aausaqVEmlaw.jpeg" /><figcaption>Edward Lorenz ‘The Butterfly Effect’ or sensitivity to initial conditions</figcaption></figure><p>In the design of complex adaptive systems, we may favour incremental change, as the effects could be chaotic eg. double pendulum swing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*32ScPcwileB9wSaXzaMhLw.gif" /><figcaption>Example of a double pendulum swing, it becomes unpredictable</figcaption></figure><p>When sailing, it might be difficult to predict weather more than a few days in advance. Which is why we might rely on north stars or beacons, rather than the wind or the tides, as the latter systems change repeatedly, with different effects. What a beautiful world, if we choose to navigate it carefully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*P6DzgPzgd979HwzKeVtqNw.jpeg" /><figcaption>Sailing with the stars (credit <a href="https://www.flickr.com/photos/dalmaszalontay_or_szallonntai/18058043164">Dalma Szalontay</a> on Flickr)</figcaption></figure><p>THE END.</p><p>Hopefully you get the gist. There’s a bit of an environmentalist agenda in there too. Did you pick it?</p><h4>In Conclusion</h4><p>Humans interact with Complex Adaptive Systems every day. If it’s not what is outside our bodies and minds, the complex adaptive system is ourselves. Perhaps that’s why meditation has had a revival!</p><p>Seriously though, that is why becoming more human-centred as a designer and is really important. I’m thinking in particular of lone UX and product designers in Agile teams. Design systems create a way for designers and other people of all shapes and sizes to work together in order to make better decisions in the things we create for people. Well considered design systems will help us get there, certainly in the short term.</p><p>Thanks for reading. Part 2 of <strong>Design Systems and Agility </strong>is coming. See you there soon! In the meantime find me at @daughterofbev</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b96c188acfca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interactive-mind/design-systems-and-agility-part-1-of-2-b96c188acfca">Design Systems and Agility (Part 1 of 2)</a> was originally published in <a href="https://medium.com/interactive-mind">Interactive Mind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Undertaking Design Work within a Dual or Multi-Track Development Process]]></title>
            <link>https://code.likeagirl.io/undertaking-design-work-within-a-dual-or-multi-track-delivery-process-96787b00da95?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/96787b00da95</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[codelikeagirl]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Wed, 02 May 2018 05:45:43 GMT</pubDate>
            <atom:updated>2018-05-06T23:10:07.666Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating a shared understanding and ownership around what you are trying to learn, test and build is hugely motivating and empowering for both teams and individuals. If you are a collaborative designer who enjoys working with Agile principles and Lean UX methodologies in both discovery and delivery, Dual Track processes may work for you.</p><p>In principle, I love the concept of Dual Track. Done well, a <a href="https://jpattonassociates.com/tag/dual-track-development/">Dual Track Development Process</a> enables quick and efficient test and learn cycles, helping designers and their teams create better experiences in the product, systems and services they engineer together.</p><p>Additionally, Dual Track, as an enabler, has team and cultural benefits. These benefits may be optimised in the way opportunities are discovered, how problems are defined and which solutions are delivered to the user. Including the members or representatives of self-organising cross-functional delivery teams in the discovery process enables team engagement.</p><p>Also, a throughput of knowledge within the team, from understanding the business or customer problem through to how a solution is is tested and optimised in market, creates team superpowers and a better shared understanding.</p><blockquote>Dual Track, done well, has team and cultural benefits in how well opportunities are discovered, problems defined and solutions are delivered to the user of a system, product or service</blockquote><p>Note: This is the long form version of this article. Short form articles will be coming soon!</p><h3>Before we go too far, what is Dual Track?</h3><p>Desiree Sy came up with the term Dual Track in her <a href="https://uxpa.org/sites/default/files/agile-ucd_0.pdf">research paper</a> on Agile user-centered design for Autodesk (2007). <a href="https://jpattonassociates.com/dual-track-development/">Jeff Patton</a> picked up on this and subsequently explained it as a <em>development</em> approach. In my mind, it is a process method that, if followed with discipline such as adherence to an Agile mindset and Lean approach, can be very successful in delivering value to customers and exciting to participate in for teams.</p><p>The great thing about Dual Track is that it essentially ‘kills’ the idea of innovation happening in isolation and gives the ability to innovate back to the delivery team populations too, rather than having a top-down, waterfall to delivery effect.</p><blockquote>The great thing about Dual Track is that it essentially ‘kills’ the idea of innovation happening in isolation.</blockquote><p>Dual Track development, with an Agile mindset, enables teams to run discovery to analyse and de-risk opportunities. This should happen first, before “feeding” delivery with ideas that have proven value for both the business and the customer, reducing waste as well ensuring technical feasibility. Opportunities that have successfully passed through the discovery process are either adopted into the release backlog or ‘killed’ before they reach development.</p><p>If passed through discovery successfully, this means that the opportunities that reach delivery, and therefore potentially accepted into to core products, systems or services, meet the minimum accepted value (MAV*)incorporating desirability, viability and feasibility, to de-risk delivery time and effort and optimise innovation.</p><blockquote>The minimum accepted value (MAV*) considers the desirability, viability and feasibility of opportunities or ideas.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Vij-_uOlvzjEAfBD.png" /><figcaption><a href="https://designthinking.ideo.com/?page_id=1542">Three Innovation Drivers</a> (Tim Brown, IDEO, 2006)</figcaption></figure><p>This approach is complementary to Agile approaches and associated methods such as <a href="https://www.thoughtworks.com/continuous-delivery">Continuous Delivery</a>, <a href="https://leankit.com/learn/kanban/continuous-improvement/">Continuous Improvement (Kaizen)</a>, <a href="https://www.oreilly.com/ideas/what-is-lean-ux">Lean UX</a> and <a href="http://www.designkit.org/human-centered-design">Human</a> or <a href="https://www.interaction-design.org/literature/topics/user-centered-design">User-centred Design</a>. The reason for this complementarity is that Dual Track processes enable teams to be set up to identify building the right thing, for the right context, at the right time, with the right people.</p><p>Jeff Patton’s illustration (below) describes ‘Learning Velocity’ and ‘Development Velocity’. As you can see from Jeff’s diagram, some things go in to the release backlog and some things don’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oY4Dv5x5GYpoXJ2EE-t9SA.png" /><figcaption>Illustration from Jeff Patton’s article “<a href="https://jpattonassociates.com/dual-track-development/">Dual Track Development is not Duel Track</a>” (2017)</figcaption></figure><p>Dual Track development is a product, design and engineering process. Within software development, design, product and technology work together to engineer a product, system or service. Therefore Dual Track is a process methodology that we can apply to anything we design, build and test with customers.</p><blockquote>Dual Track development is a product, design and engineering process.</blockquote><p>Test and learn cycles can be applied in both discovery and delivery. Rapid feedback loops are incredibly important in enabling opportunity creation, speed to market, value assessment, use-case assessment and understanding customer expectations quickly. The value of learning for a team can be applied to any cohort of people that are affected by the opportunity you are discovering or delivering to market.</p><p>Given the learning benefits for teams, Dual Track sounds very human-centred doesn’t it? And this benefit doesn’t only apply to users and customers, but our teams too. Designers are curious, as are our colleagues, therefore it is difficult to resist the attraction of a Dual Track delivery process done well, with an Agile and Kaizen approach.</p><h3>Why did we choose Dual Track development?</h3><p>To provide context, we were a new team and spinning up adjacent to the core delivery teams around known entities within a large organisation with millions of users. Established delivery teams were focusing on defined and known customer groups, while we were considering a new customer and problem domain. Given my team had some freedom around how we could choose to deliver, we considered what we needed to do and that naturally pointed to something like Dual Track development.</p><p>Our decision was an outcome of a huddle between the team leads, describing what we needed to accomplish when <em>someone</em> said, “that sounds like Dual Track.” So Dual Track, in our context, resonated with us. We were thinking about how to enable speed to market and learning. We identified possible growing opportunities emerging as a result of a single Vision track and multiple stakeholder engagement exercises as well as a preliminary learning phase including lean research and customer interviews.</p><p>The Vision track then kicked off a secondary track, Experiments, fed by the Vision track. These functioned synchronously. Once the Vision track has a defined ‘customer journey’ and opportunity or ideas backlog associated with it, it will then naturally evolve into the Discovery track or potentially persist as the customer journey is iterated on. Streams of initiatives might flow out of this evolved Discovery track, triggered by the customer journey target state and the opportunity and ideas backlog.</p><p>It’s important to remember, based on your learning stage in research and discovery as well as data confidence, that whether Single, Dual or Multi-Track, you can spin tracks up and down as needed, just like discovery and delivery streams. These tracks may be dedicated to different approaches such as vision creation, experiments, discovery or delivery teams. These tracks and streams can be activated and de-activated based on your program maturity stage too. To picture this in your mind, see tracks as vertical and streams as horizontal, like the picture (above).</p><p><strong>Our team scenario with Dual Track, in a little more depth</strong></p><p>We chose to run a Dual Track process model with an Agile approach because we needed to run discovery and delivery quickly, on a critical business strategic path, with what was initially a single, small team. We were right at the beginning of the learning journey and wanted to test and continuously learn in a <a href="https://www.gotosage.com/blog/the-5-minute-lean-manufacturing-refresher-course-and-how-to-get-maximum-benefit-from-lean">Lean</a> and efficient way, with what really became a <a href="https://in.kaizen.com/about-us/definition-of-kaizen.html">Kaizen</a> mindset.</p><p>We wished to mitigate risk and both architectural and experience legacy by avoiding building changes into our core systems, <em>before</em> we understood the customer and business value of what we were seeking to change or innovate around, to the best of our ability and if, in fact, we could build and test the ‘thing’ at all. As a team, it was our desire to learn from a small cohort of engaged customers <em>before</em> we scaled any solution to a significant percentage of market exposure. Therefore because of our need for efficiency, we required near-state, attainable outcomes to kick the team off and incept experiments. We proceeded to production code quickly in order to evaluate concepts that were considered <em>within reach</em> and we had <em>reasonable high confidence</em> about, to test with the target market.</p><p>Finally, <em>if</em> we could understand the parameters of the value we sought to deliver, with what might potentially create a new product adjacency to our core market offering as a business, <em>potentially</em> a new roadmap of prioritised opportunities and learnings could be pushed to market in the short term while we learned about longer term opportunities for our business with this hard-to-crack customer segment.</p><blockquote>The Dual Track process model isn’t really the solution, rather the impetus to move forward as an enabler. It’s how the team and individuals interact with the way they are organised and what protocols they have in place to understand why they make decisions that matters.</blockquote><p>So as you can see, the Dual Track process model isn’t really the solution, rather the impetus to move forward as an enabler. It’s how the team and individuals interact with the way they are organised and what protocols they have in place to make decisions. You could easily argue this isn’t Dual Track at all, however it helped us get to where we are now.</p><h3>How does Dual Track impact on the way a team interacts with each other?</h3><p>Dual Track development, underpinned by the twelve <a href="https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/">Agile Principles</a>, can impact on team behaviour in a range of ways. When done right, these are positive.</p><p>For designers, relationships are crucial, particularly in a UX and Product roles. Communication within the team and without are business requirements of our respective functions, albeit with a user experience or business focus.</p><p>Here is a top level list that just touches the surface of benefits of Dual Track development, if it’s done right:</p><p>a) Dual Track development forces collaboration and co-creation with your team and allows for customer and user-centred activities;</p><p>b) Dual Track enables the team to be involved in both discovery and delivery, which is motivating and empowering for the team;</p><p>c) Things move quickly! Designers and their team-mates must be learn to be nimble, which is a good thing (I’m biased) and instils a learning mind;</p><p>d) Dual Track works best with Agile, human-centred rituals that maintain strong communication behaviours, encouraging honesty and alignment. Being in sync with your team is important as is trust, anchoring to your goals and aligning with each other; and</p><p>e) Most of all Dual Track development is exciting and fun, once the team is comfortable with change and making decisions at a pace. For us it was running experiments, but later it could be adding features into the core system, products and services.</p><blockquote>Dual Track is complementary to Continuous Delivery in that they keep the wheels of the team moving with new initiatives that may be retained or discarded</blockquote><p>It is worth noting that the benefits of Dual Track might also apply to other Agile development processes such as Continuous Delivery. Dual Track is complementary to Continuous Delivery in that helps both spin up opportunities for delivery to test and learn, as well as keeping the wheels in discovery moving with new initiatives that may be accepted into delivery or discarded as low value.</p><p><strong>Issues for designers re: speed and ‘loss of craft’</strong></p><p>Designers may sometimes seem resist the ability to work quickly in lower fidelity because they may rear the risk ‘loss of craft’ in the interface. However, this is not a team but systemic design issue.</p><p>For example, if design pattern systems are not in place, increased fidelity designs might be required to maintain a standard consistency across the delivery of user-facing system improvements, or the identification of new opportunities for pattern and style guide creation.</p><blockquote>Designers may sometimes seem resist the ability to work quickly in lower fidelity because they may rear the risk ‘loss of craft’ in the interface. However, this is not a team but systemic design issue.</blockquote><p>There are many ways to identify ‘loss of craft’ and designers simply need to be flexible and communicate this to their team members. Not unlike the impacts on technology architecture, designers must consider this conversation an extension of the ‘system architecture’ legacy.</p><h3>The importance of psychological safety in fast moving teams</h3><p><a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">Psychological safety</a> is hugely important to create an anchor for alignment and resolving in-team differences and moving the team on to progress to the next task or objective. To be successful in Dual Track Agile, or indeed in any other fast-paced delivery approach, teams must create a ‘safe’ environment for collaboration and autonomous decision making, guided by shared team goals and success criteria for sprints or epics.</p><p>Trust and honesty in communication, when safe and respectful, can help mitigate everyone’s concerns around decision making and how to eliminate workflow issues. The importance of regular retros and actions coming from these rituals help support a <a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">psychological safety</a> agenda.</p><p>Common issues for designers in fast moving teams might include:</p><p>a) Designers might feel ‘out of sync’ with their counterparts, especially if there is one designer doing ‘all the things’ (see: unicorn). This issue can be counteracted via simple communication and adjusting the team engine’s gears to accomodate the right workflow in product, design and engineering to assist the designer;</p><p>b) Designers might have different perceptions of the value of fast-paced discovery and delivery cadences and need help adapting to the team, similar to a) but around the ability to learn and adapt;</p><p>c) Designers may have distinct and varied expectations around what their role is responsible for, or their ownership of key deliverables such as interface design vs an engineer making in making interface decisions. Designers and their colleagues must learn to respectfully ‘share hats’ in order to keep progressing quickly and retain a positive team culture;</p><p>d) Team-colleagues of designers may also have different ideas on what they expect from the designer and again, simple communication around “what I expect to do” vs “what you expect I do,” helps between both parties; and</p><p>e) If inexperienced in Agile or early career, designers may find it difficult to adapt initially to Agile mindsets and Kaizen workflows and need support around losing a perfection mindset to shift towards test and learn. This may also be a team expectation reset so all are aligned and can move forward.</p><p><strong>Shared objectives and key results or success criteria</strong></p><p>In our case, the team used the <a href="https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/">Google OKR Framework</a> and created OKRs to align against. We designed the OKRs together and, resultingly, the objectives and key results gave us an anchor. There are many advantages to having a shared goal or objective and this is a key alignment factor for both the team and the organisation and/or users you are serving.</p><p>For example, there is an in-team or stakeholder dispute about an idea, design, or approach, OKRs might help to re-orientate the conversation and align the team to make effective decisions without hamstringing discussions with opinions that may derail team goals and objectives. You might also apply this technique to acceptance criteria on a card or success criteria for a sprint.</p><blockquote>OKRs can help align the team to make effective decisions without hamstringing discussions with opinions that may derail team goals and objectives.</blockquote><blockquote>Pro-tip: You might also apply this technique to acceptance criteria on a card or success criteria for a sprint.</blockquote><p>Dual Track, given its time contingent nature, may pose issues if a person is down or out of the office eg. you are sick or on leave. Often, if there is only one designer per team, or one anyone, the absence of a key function can be hair raising! For example, if the team don’t have an understanding on how to operate when a key team member is out.</p><p>In a healthy, well functioning team, aligned to their objectives and key results, it <em>should</em> be ok and <em>safe</em> for the team to make a decision around whether or not to move forward without a key team member representing their function, knowing that there is a shared understanding underpinning anything the team decides to do. The team can always circle back later if needed, but a key thing with Kaizen is waste reduction, so keep that in mind.</p><p>If a team member is out of sync with your team, in fast moving situations like Dual Track or rapid delivery timeframes, one may need to accept that design decisions <em>might</em> be made without them if they are not there. This might also apply to designers. Therefore, keep the oil in your team mechanics; make sure you lubricate your communication skills by attempting to be as available as possible for your team, attending team rituals in person, or remotely, and most of all killing your darlings through cross-functional and customer-centred collaboration.</p><blockquote>Kill your darlings through cross-functional and customer-centred collaboration.</blockquote><p>Obviously, there are cases where decisions without designers aren’t optimal. If a designer is really needed to make a call, it is up to the team to be able to shift gears in a different direction, speed up/slow down, without holding up progress or moving cards across a wall. This may also apply to spinning up a new team in the discovery track, for example, if a key team member representing product, technology or design is not available, wheels should pause until the functions are represented.</p><blockquote>As a designer, if you establish a shared understanding with your team on objectives, this will underpin trust, confidence and alignment.</blockquote><p>Agile team rituals such as regular retros will help your team identify bottlenecks and problems then activate actions from your learnings and team decisions that result in actionable results and improvements in the way you work together.</p><p>If done wrong, the effects of Dual Track are potentially damaging to teams, creating the ‘Duel Track’ effect;</p><p>a) Discovery teams working in isolation;</p><p>b) Opportunities being handed over in a waterfall handover process;</p><p>c) Team engagement in delivery affected by a lack of a shared understanding around the problem being solved and lowered efficiency as a result;</p><p>d) Discovery being misunderstood as a solution creation process… it isn’t, discovery is a problem definition and opportunity assessment approach; and</p><p>e) Worst of all, team members might resent each other and throw tomatoes emoji over the walls (joke) and culture is affected.</p><p>Our team, so far has had huge success with an awesome Agile coach who has been managing the retention of team rituals and communication. If you’d like to read more about psychological safety, this is <a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">a great article from HBR</a>. It’s hugely important to a learning mindset.</p><p>Sometimes all that is needed is a “hey, we are doing this thing right now and this is why” kind of conversation. This is where trust is the team’s bedrock, especially if teams can’t afford the time to include everyone in delivery in discovery conversations and vice versa. <a href="https://medium.com/seek-blog/build-a-ux-wall-and-make-them-pay-attention-8243b9a80fe7">Walls are great too</a>, so team members and stakeholders can read things, as is having shared stand-ups and time together in show-cases so everyone feels included in the ideation and execution process. For designers, this is hugely important.</p><p>So, it’s really important to think about what smoke signals to look for, in order to avoid the negative effects of exclusion and isolated behaviour and build the fires of passion in your team.</p><h3>In conclusion, what’s in it for designers?</h3><p>The learning mindset is so valuable in team motivation and understanding stakeholders as well as the needs of users of products, systems and services. Given Agile experience design is very similar to and can be adapted towards a <em>kaizen </em>process, it’s really important to embrace enablers that might help your team work more efficiently and collaboratively. Within reason, any framework or process that supports engage with the people your system interacts with is worth an experiment and if working well adopting into your day to day processes as a team.</p><p>It’s absolutely worth experimenting with Dual Track development and researching best practices around <a href="https://www.agileconnection.com/article/what-does-it-mean-have-agile-mindset">Agile</a> and <a href="https://hbr.org/2016/01/what-having-a-growth-mindset-actually-means">Growth Mindsets</a>, so you and your team can explore the value of collaboration and see if it improves your ability to receive timely information on how to design and build the best experiences for the users of your product, system or service.</p><p>* If you’d like to know more about the idea of Minimum Accepted Value (MAV) <a href="http://linkedin.com/in/catherine-hills-96a1b515">please contact me direct</a>. I created the acronym and concept after a long time of thinking about the connect between human-centred design and IDEO’s value drivers with continuous delivery. I put two and two together when I was thinking about this article. It’s an ever evolving conversation 😀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96787b00da95" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/undertaking-design-work-within-a-dual-or-multi-track-delivery-process-96787b00da95">Undertaking Design Work within a Dual or Multi-Track Development Process</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Impact of Rushing on UX Teams: Dealing with the Need for Speed]]></title>
            <link>https://medium.com/interactive-mind/the-impact-of-rushing-on-ux-teams-dealing-with-the-need-for-speed-c603d510c4a9?source=rss-4f6c71dafff9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c603d510c4a9</guid>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Catherine Hills]]></dc:creator>
            <pubDate>Fri, 03 Mar 2017 09:13:45 GMT</pubDate>
            <atom:updated>2026-04-25T05:45:49.920Z</atom:updated>
            <content:encoded><![CDATA[<h4>Create and use time efficiently, in order to inject the ‘why’ into pre-planning and delivery</h4><p>As UX practitioners, how do we innovate and pivot to the best of our ability, in order to increase the likelihood of the right time, right context solutions to our customers and consumers, within an “<em>agile</em>” workflow?</p><p><strong><em>Slack</em></strong> (verb) <em>decrease or reduce in intensity, quantity, or speed.</em></p><p>More often than not, User Experience Designers perceive a friction between the business perception of UX in the creation of product strategy and effective research and design implementation. The causation of this is simply that many businesses, including software and technology houses, are confused about how to deliver consumer value to the market effectively and support this in their delivery processes.</p><p>A symptom of this problem is the conflation of design with UI asset delivery within UX in agile software development, or a finite, sprint-based timeframe omitting core user-centred methods such as research or user testing. A similar pain point for user experience designers might be the omission of discovery, validation and behavioural feedback prioritisation within pseudo-agile or lean work systems, but less so if applied to <a href="http://martinfowler.com/bliki/ContinuousDelivery.html">Continuous Delivery</a> in its purest form, incorporating validation cycles.</p><p>Other work system solutions might include processes such as <a href="http://svpg.com/dual-track-agile/">dual track agile</a>, advocated for by industry greats such as Marty Cagan and other models of process based on team and product maturity suggested by <a href="http://jpattonassociates.com/common-agile-isnt-for-startups/">Jeff Patton</a>. However without cross-functional and organisational alignment, UX delivery teams cannot achieve change easily, on their own.</p><p>Additionally, due to the nature of the <em>way</em> a value proposition and the <em>way</em> an MVP is defined, there may be limited <em>time</em> to execute synthesis that might help the team best define horizons of execution and slice features which can also impact on the effectiveness of UX delivery teams. This imposed restricted bandwidth can cause UX teams, even if gunning for continuous improvement ideals, to be forced into mini-waterfall cycles, throwing assets as needed ‘over the wall’ to engineering teams, without due diligence in testing or risk mitigation in research. Hardly ideal for the end-user or the teams/individuals involved.</p><p>A very real scenario is this. Imagine teams like this shifting gears rapidly from one feature MVP deploy to another pre-planning kickoff, on to something completely new, without the understanding of how well the prior release performed or could be improved. This organisational need for speed can impact even on the most seasoned agile UX delivery teams, without the right bandwidth to understand what is better or worse, particularly if prioritisation <em>isn’t</em> user-centred.</p><p>The mind shift and stretch for UX delivery teams in this case is to still identify the feedback for a future feature backlog with the product team in parallel, whilst working ahead for the next epic or initiative in order to obtain the user needs to justify the shift to backlog grooming, as dictated by the product roadmap. The risk, however is that feedback will be lost and ignored, in the urgency to seek the next piece of ‘gold’.</p><blockquote>The question is, in these cases, how do we, as UX delivery teams and risk mitigators, slow down speed and accelerate effective research and design in limited time frames to improve user experiences?</blockquote><p>In order to successfully combine agile methodologies with creativity and innovation, user experience designers and technology teams require room for more divergent thinking in the appropriate rhythm <em>before</em>, <em>during</em>, <em>after</em> and<em> in parallel </em>to software development workflows.</p><p>The risk in rushing or a brim-full roadmap, is that, despite best intentions, workshops or activities such as sketch sessions might become the avenue for agenda-ed synthesis, and execution opportunities could be lost without clear and considered thinking. Additionally, without time and preparation, we may lose the benefit of including the right team members and users in truly valuable sessions created to induct thought or validate our ideas and interpretations.</p><blockquote>We need to enforce the need for appropriate space for thinking and slack in our working sprints to allow for the flex into the spaces of synthesis, to avoid forced interpretation of ideas, even if meaningfully gathered, into execution that may increase dissonance between our users, our products and ourselves.</blockquote><p>Evidence preceeds itself. The use and re-use of <a href="https://www.ideo.com/work/human-centered-design-toolkit/">Design Thinking</a> methods and the <a href="http://www.designcouncil.org.uk/sites/default/files/asset/document/ElevenLessons_Design_Council%20(2).pdf">Double Diamond</a> model (2006), and, increasingly, experimentally combining this approach with <a href="http://www.jeffgothelf.com/blog/lean-ux-book/">Lean UX</a> and <a href="http://theleanstartup.com/principles">Lean Startup</a> methods, I’ve found to be fruitful for rapid discovery, problem definition and collaborative problem solving. These methods are now considered by many to be important catalysts for any innovation and/or agile workflow.</p><p>Saying this, when we are rushing, or uncertain, perhaps our best next guess is small and basic needs driven.</p><h4>What are the current, low hanging fruit?</h4><p>Firstly, let’s step back to the <a href="https://en.wikipedia.org/wiki/Kano_model">KANO model</a>, a product strategy priorisation model created by Noriaki Kano (1984). Kano’s model addresses satisfaction drivers and has been used successfully by myself and colleagues in industry to pre-prioritise issues in the product backlog.</p><p>Perhaps this is where the origin, in product-speak, of ‘Delighters’ comes from, as Kano’s measurement criteria measures the following attributes against issues in the product backlog:</p><ul><li>Basic Needs</li><li>Performance Indicators</li><li>Delighters</li></ul><p>One of the interesting aspects that Noriaki Kano considered in his model is that the cadence of ‘Delighters’ changes over time. What might be considered and validated as a ‘Delighter’ with users can become hygiene, or ‘Basic’ needs, eventually.</p><p><strong>What was shiny is the new normal</strong></p><p>Consider the example of the ‘typeahead’ or ‘autocomplete’ feature in search. The autocomplete feature was created by ex-Googler Kevin Gibbs and originally named <a href="http://allthingsd.com/20130823/nearly-a-decade-later-the-autocomplete-origin-story-kevin-gibbs-and-google-suggest/">Google Suggest</a>. This feature was developed over a decade ago by Kevin, then a Junior Software developer. This, at the time, would have been considered an innovation and ‘Delighter’, at feature level.</p><p>Now, however, it is an expected paradigm in a search experience that most users are used to interacting with. This pattern is mimicked in patterns on other sites from <a href="http://www.amazon.com/">Amazon</a> to <a href="https://www.airbnb.com.au/">AirBnb</a> and the UX of these product search experiences might be considered lacking these days if this interaction prompt was excluded from the product’s usable features. Therefore, now, according to Kano, this would be a ‘Performance’ or even ‘Basic’ consideration in a robust and reliable search experience.</p><p>For similar examples check out the <a href="http://microinteractions.com/">Microinteractions</a> website.</p><h4>The impact of change and other loop models on iterative design</h4><p>The impact of the Kano model is paralleled by the simulation of ‘loop cycles’ in many human centred and iterative models that have been created to show technology design and delivery workflows. In <a href="http://martinfowler.com/bliki/ContinuousDelivery.html">Continuous Delivery</a>, <a href="http://agilemanifesto.org/">agile</a> designers must be able to adjust to change. <a href="http://theleanstartup.com/principles">Lean Startup</a> methodologies assist with this with the Build, Measure, Learn Cycle. User Centred Design processes are also cyclical and support this approach.</p><blockquote>As designers in agile workflows, we, our colleagues and the businesses we work for, are required to be nimble, in order to serve and assist our users.</blockquote><h4>Pre-planning Discovery when engineering teams are waiting</h4><p>In order to even touch the surface of understanding human needs in product development, UX delivery teams need <em>relative</em> time to the scale of the problems we are trying to solve.</p><blockquote>The estimation of this time is usually reliant on an idea of what might be needed based on the validity of existing data and, <em>ideally</em>, before our engineering team’s hands are empty.</blockquote><p>If the well of ideas or initiatives is dry, this can create natural slack and become an <em>opportunity</em> to look at urgent or neglected persistent consumer feedback. An opportunity backlog that truly reflects very real, current and pressing problems that users would appreciate a solution for in the nearer rather than far future. This might be the low hanging fruit or it could simply be a persistent problem that is emergent.</p><p>Based on a cross-functional team’s confidence in what it knows, with reliable and valid data and sizing cards down to utilise engineering quickly, UX designers can start building real value into released experiences rather than large but somewhat desperate and invalidated improvements. Bolstering this behaviour with a robust discovery session over the course of an hour, a day (eg. <a href="http://www.jeffgothelf.com/lean-ux-book/">Lean UX</a>) or week (eg. <a href="http://www.gv.com/sprint/">Google Ventures Design Sprint</a>) can only benefit ourselves and our colleagues who are invested in what we design.</p><p>We can help each other in our agile, cross-functional teams to enable and champion authentic findings and insights that <em>might</em> become valuable attempts at solving the very real problems of our consumers and customers. If our hypotheses are wrong and consequently disproven, the ultimate value is learning and improvement, something that <em>all of us</em> can benefit from with the luxury of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c603d510c4a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interactive-mind/the-impact-of-rushing-on-ux-teams-dealing-with-the-need-for-speed-c603d510c4a9">The Impact of Rushing on UX Teams: Dealing with the Need for Speed</a> was originally published in <a href="https://medium.com/interactive-mind">Interactive Mind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>