<?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 Davis Levine on Medium]]></title>
        <description><![CDATA[Stories by Davis Levine on Medium]]></description>
        <link>https://medium.com/@davislevine?source=rss-c96b311868cc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qxAIHsEIQdD50Bs_dlNeyA.png</url>
            <title>Stories by Davis Levine on Medium</title>
            <link>https://medium.com/@davislevine?source=rss-c96b311868cc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:35:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davislevine/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[AI is not disrupting Design]]></title>
            <link>https://davislevine.medium.com/ai-is-not-disrupting-design-b29c2ffef907?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b29c2ffef907</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 03:40:32 GMT</pubDate>
            <atom:updated>2026-03-06T21:45:24.780Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s disrupting the design process</h4><p>Like many designers, I’m watching the apparent disruption that generative AI tools are having on design. In some ways it feels like an existential crisis, but in other ways it feels like the next step in an ever evolving discipline that has never really found footing within public education or industry.</p><p>The design process will change with AI, but <em>design as a process</em> will not. A lot of discussions about AI disrupting design processes identify the shift of ‘creation’ earlier into the process, asserting creation as the new form of research and discovery.</p><p>My hypothesis is that when designers project anxiety in this change, they are projecting the double diamond as a core model.</p><p>But it’s important to remind designers, especially the generation educated in the last 20 years, that the double diamond is not <em>the</em> design process, it is <em>a</em> design process which has was <a href="https://www.designcouncil.org.uk/our-resources/the-double-diamond/history-of-the-double-diamond/">developed and marketed by the UK Design Council</a> in the early 2000s. While it codifies many principles of design, it is not the authoritative source on design process.</p><p>To wade through this noise of AI prophecy, I return to earlier design texts to ground myself in what design is and what it means “to be a designer”. One article I really enjoy and have taught in my seminar course is Nigel Cross’ article “Designerly ways of knowing” from 1982. In exploration of what makes design unique as a discipline, Cross and others argue that “Design has its own distinct ‘<em>things to know, ways of knowing them, and ways of finding out about them</em>’, identified as designerly ways of knowing. These five aspects are described as:</p><ol><li>Designers tackle ‘ill-defined’ problems.</li><li>Their mode of problem-solving is ‘solution-focused’.</li><li>Their mode of thinking is ‘constructive’.</li><li>They use ‘codes’ that translate abstract requirements into concrete objects.</li><li>They use these codes to both ‘read’ and ‘write’ in ‘object languages’.</li></ol><p>I’ll focus on points 2 and 3 as it relates to this question of AI in design: namely design being “solution-focused” and “constructive”.</p><p>According to Cross, design is fundamentally about making, creating, and modelling, in order to learn about and understand a problem space. It counters analysis-based disciplines, like science, that might sit with a “prolonged analysis of the problem”. Rather, it utilizes ‘“satisfactory solutions” to move through the ill-defined and complex problems design finds itself in.</p><p>What isn’t truly new in the conversations of AI pushing solutioning to the forefront is that design has always been about creation as discovery. With AI, the timing, tooling, and sequencing may change but the <em>process of Design</em> has not.</p><p>In my work experimenting with AI, the time from idea to prototype has collapsed to nothing. The cost of iteration and exploration is negligible. These functions are not new to design process, it’s new tooling that accelerates these functions.</p><p>Tools used in a design process are not design. They represent the best available technology to facilitate the output of a model; whether that is a prototype, mockup or journey map. Remember when website assets were sliced in Photoshop? My view of generative AI is that it is a powerful <em>tool</em> for constructive thinking and solution-focused exploration.</p><p>Embedding AI capabilities into design tools like Figma is less interesting to me than a total reconceptualization of processes as we know it. To do this, designers need to unshackle themselves from the core models taught in design schools, i.e. the double diamond, which were fit for purpose at a given time when code was costly and AI was just a Deloitte sales pitch.</p><p>We can all breathe and acknowledge that while the tools may change, Design will not. With that said…there’s a different discussion if the designer as we know it today even needs to exist, but let’s save that for another day.</p><p>—</p><p>Cross, Nigel (1982). Designerly ways of knowing. Design Studies, 3(4) pp. 221–227.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b29c2ffef907" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4: Design Activism]]></title>
            <link>https://davislevine.medium.com/week-4-design-activism-bf548d931315?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf548d931315</guid>
            <category><![CDATA[activism]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 00:26:49 GMT</pubDate>
            <atom:updated>2026-02-19T00:26:49.390Z</atom:updated>
            <content:encoded><![CDATA[<h4>DESN480 — Design Issues</h4><h4><strong>Required Reading</strong></h4><p>Fuad-Luke, A. (2009). Design activism : beautiful strangeness for a sustainable world (1st edition). Earthscan. <a href="https://doi.org/10.4324/9781849770941">https://doi.org/10.4324/9781849770941</a> Chapter 1: Scoping The Terriorty: Design Activism and Sustainability</p><p>WAI Architecture Think Tank, Hubert Murray, Hugh Campbell, Faiza Moatasim, Frederick Steiner, Sony Devabhaktuni, Diane Jones Allen, Hélène Frichot, Gideon Fink Shapiro, Sonja Dümpelmann, Lori Brown, Ivonne Santoyo-Orozco, Federico Garcia Lammers, “Field Notes on Design Activism: 4,” <em>Places Journal</em>, November 2022. Accessed 04 Feb 2026. <a href="https://doi.org/10.22269/221110">https://doi.org/10.22269/221110</a></p><p>—</p><p>Week 4 of the seminar looks at public design outside the institution of government. What happens when governments don’t provide the solutions the public needs or demands? We explore design activism as a reaction to this gap in delivery.</p><p>The first reading was Chapter 1 of “Design Activism: Beautiful Strangeness for a Sustainable World” by Alastair Fuad-Luke. This text was chosen to lay a foundational theory defining design + activism, and why these two terms are suited together.</p><p>Fuad-Luke proposes that “Design activism is ‘design thinking, imagination and practice applied knowingly or unknowingly to create a <strong>counter-narrative</strong> aimed at generating and balancing positive social, institutional, environmental and/or economic change’.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bqGumfpV8hL9vXfNUbytTg.png" /><figcaption>View of the ten key Capitals where activism operates</figcaption></figure><p>His definition positions the objective of design as the creation of a ‘counter-narrative’. As activism mostly operates outside the institutions of power that create these issues, design is not positioned as a solution, but rather a view of what <em>could be</em>.</p><p>While activist practices may traditionally be envisioned through visual communication, public demands, social mobilization, and perhaps policy advocacy, design could be a futures-making tool within the space of activism.</p><p>To expand on the idea of a counter-narrative, I would argue design plays a role in prefigurative work, representing or enacting a future world we hope to see. This can be manifested through prototypes, <a href="https://medium.com/digital-experience-design/design-fiction-32094e035cd7">design fiction</a> or speculative objects. We’ll explore this topic in more depth during our last class on Speculative Design.</p><h4>Field Notes</h4><p>The second reading of the class was a bit of an experiment. Rather than hold up one example of design activism for the class to examine, I had them read “<a href="https://placesjournal.org/article/field-notes-on-design-activism-4/">Field Notes on Design Activism</a>“ from <em>Places Journal</em>. This series is a narrative survey where “educators and practitioners share perspectives on the intensifying demands for meaningful change across design pedagogy and practice”. There are too many interesting responses to review for this post, so instead I will just outline some key ideas and quotes that stuck out to me:</p><ul><li>Are we at a point now where we just let everything crash and burn and hope we build something better? (García and Frankowski)</li><li>Design activism is a process of slowness, finding spaces in the ‘longer trajectories’ of campaigns. (Campbell)</li><li>Liberate design education from the “Hegemony of design solutions”, especially when engaging with complex issues. (Moatisim)</li><li>Make yourself dispensable. A designer can be a catalyst, but not the bedrock. (Steiner)</li><li>“I want to propose a reframing of design imagination that shifts our objective from the singular solution to plural contingencies: the “what ifs?” that could be.” (Devabhaktuni)</li><li>Place is a cultural construct, and solutions to a problem of place must be rooted in the history and ecology of the people who have shaped it. (Allen)</li><li>Follow the materials, each material choice travels backwards and forwards. (Frichot)</li><li>Center real world issues in the classroom. Work on projects that require students to take a position. (Brown)</li><li>Disciplinary silos are crumbling. Relearn knowledge shaped by nondisciplinary knowledge. (Santoyo-Orozco)</li></ul><h4>Next Week</h4><p>After a break with Reading Week, the class will shift into looking at public design from within the institution of government, and we’ll start by looking at service design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf548d931315" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3: Public Harm]]></title>
            <link>https://davislevine.medium.com/week-3-public-harm-53601c7e5820?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/53601c7e5820</guid>
            <category><![CDATA[urban-planning]]></category>
            <category><![CDATA[hostile-architecture]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 03:16:58 GMT</pubDate>
            <atom:updated>2026-02-10T03:16:58.296Z</atom:updated>
            <content:encoded><![CDATA[<h4>DESN480 — Design Issues</h4><h4>Required Reading/Listening</h4><p>Sora Park &amp; Justine Humphry (2019) <em>Exclusion by design: intersections of social, digital and data</em> 11–451 Society, 22:7, 934–953, DOI:10.1080/1369118X.2019.1606266</p><p>Kohlstedt, K. (2016, July 5). <em>Unpleasant Design &amp; Hostile Urban Architecture</em>. 99% Invisible. <a href="https://99percentinvisible.org/episode/unpleasant-design-hostile-urban-architecture/">https://99percentinvisible.org/episode/unpleasant-design-hostile-urban-architecture/</a></p><p>—</p><p>This week we explore the role design plays in creating exclusion and harm, both in urban environment and in digital systems. While many people view public sector design as “design for good”, I wanted to challenge this idea and highlight how design can intentionally and unintentionally be used as a ‘weapon’ of the state.</p><p>As a break from reading academic journals, I had the class listen to a 99% Invisible podcast episode on <a href="https://99percentinvisible.org/episode/unpleasant-design-hostile-urban-architecture/"><em>Unpleasant Design &amp; Hostile Urban Architecture</em></a>, featuring guest Selena Savić and host Roman Mars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*rZiVhlpHYkJqAEV_.jpg" /><figcaption>‘Homeless spikes’ by <a href="https://www.flickr.com/photos/chaircrusher/">kent williams</a>, <a href="https://creativecommons.org/licenses/by/2.0/deed.en">CC BY 2.0</a></figcaption></figure><p>The episode highlights various examples of hostile urban architecture and unpleasant designs that deter and prevent public nuisance, such as benches that prevent people from laying down and sleeping, classical music played outdoors to discourage loitering, and blue lights installed to prevent intravenous drug users from finding their veins. As Savić points out, these examples of unpleasant or hostile designs “are not <em>failed </em>designs, but rather <em>successful</em> ones in the sense that they deter certain activities <em>by design”.</em></p><blockquote>Unpleasant or hostile designs are not <em>failed </em>designs, but rather <em>successful</em> ones in the sense that they deter certain activities <em>by design”</em></blockquote><p>While these designs may be successful in producing immediate behaviour change, this measure of success is not without controversy and defines success within a narrow frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y4VjZtEEGD9hw8tR.jpg" /><figcaption><a href="http://weburbanist.com/2014/10/04/anti-object-a-public-bench-designed-to-be-everything-proof/"><strong>Camden Bench</strong></a> image by <a href="https://en.wikipedia.org/wiki/Camden_bench#/media/File:Camden_bench.jpg"><strong>The wub</strong></a> (CC BY-SA 4.0)</figcaption></figure><h4>Unethical Design or Social Signifier?</h4><p>These design interventions are controversial depending on which side of the argument one takes. On one side, they disproportionately target the most vulnerable and marginalized groups in society, i.e. individuals experiencing homelessness and those struggling with drug and alcohol addiction. They further criminalize and punish certain public behaviours without providing meaningful solutions.</p><p>Nothing is done to address the root cause of the problem, rather these designs respond to the symptoms. They are a simple, although sometimes creative, reactions to the complex problems <a href="https://medium.com/@davislevine/week-1-defining-public-design-4968b19432eb">discussed in Week 1</a>. Sleeping in public is not eliminated because you stop people from sleeping in certain spaces, it just pushes the behaviour further out of public view. To illustrate this point, the hosts discuss pigeon spikes, the spiky things placed on buildings to prevent birds from landing. These do nothing to reduce the number of birds in a city, it just pushes them to land elsewhere.</p><p>However a balanced view is possible with this analysis. One could argue that activities such as loitering and drug use <em>are</em> criminalized behaviours, and these interventions serve to deter them. They are social signifiers to what is considered ‘acceptable’ behaviour in public space. As noted by one of the guests at the start of the episode, certain behaviours can drive customers away from businesses and reduce perceptions of public safety. From this perspective, such designs are deemed necessary because governments are not adequately addressing underlying issues, and those implementing the designs are responding with the limited tools available to them.</p><h4>The Immutability of Harm</h4><p>All design influences human behaviour to some degree, which raises the question of where that influences crosses an ethical line. When does influence become coercion? Design can compel someone to buy a product, or it can prevent someone from sitting in a public space.</p><p>Savić speaks to the relational nature of design and how it creates space for ethical interpretation. Unlike a police officer <em>policing</em> behaviour, there is no space for negotiation, contextual understanding or social mediation with hostile architecture. It is perceived as <strong>permanent and immutable</strong>, influencing behaviour in a blunt manner. Therefore, one aspect of ethical design may be the preservation of space for human agency and autonomy.</p><h3>Digital Exclusion</h3><p>The second reading, <em>Exclusion by design: intersections of social, digital and data </em>by Park and Humphry, extends the notion of harm from the physical to the digital. The paper uses case studies from the Australian government to examine two examples of digital exclusion: the <a href="https://en.wikipedia.org/wiki/Robodebt_scheme">Robodebt scheme</a> and an AI-powered personal avatar for disability assistance called Nadia.</p><p>Robodebt is the colloquial name for an automated Online Compliance Intervention system designed to detect and recover overpayments to welfare recipients. In many cases, the algorithm proved inaccurate (and later deemed unlawful), automatically sending debt notices demanding repayment. When payment was not received, the system initiated collections. Sometimes without recipients’ knowledge simply because they were living at a different address.</p><p>This is an example of citizens being treated as “guilty until proven innocent”, echoing a point made by Alistair Croll in his podcast episode on on the C<a href="https://www.fxgov.com/p/why-tax-matters">anadian tax system</a>. I can attest to the emotional toll this logic creates . <em>Every time </em>I get a notification from the CRA my stomach drops…until I find out it’s a GST rebate or something else less interesting.</p><p>The irony of public design is that the most vulnerable and digitally excluded populations are often forced to use new government technologies that are often poorly designed and implemented. These services are frequently identified as prime candidates for technological innovation, yet without thoughtful design the risks of harm are magnified, especially in the age of generative AI.</p><h4>A Human-In-The-Loop</h4><p>In a digital context, full automation through algorithms and AI in government process mirrors the immutability of hostile architecture. It leaves little room for negotiation. As one student noted in class, such systems operate as black boxes that cannot be easily explained or challenged. Public managers are often compelled to trust and defer to the algorithm, because questioning a single decision can call the integrity of the entire system into doubt.</p><p>To counter the unintended consequences of algorithmic governance, the term “human-in-the-loop” is a trending statement in discussions about AI. Proponents are quick to point this out as a way to alleviate the anxiety of automation by preserving some degree of social negotiation or agency. At a minimum it provides a quality control check, at best it still enables the recognition of context and nuance in service delivery.</p><h4>The Challenge of Algorithmic Policy</h4><p>I’ve worked on government services that provide monetary benefits to citizens, similar to the welfare example above. As much as there is a desire to completely automate these systems, what was clear from back office staff is simply this: life is complex. Policy makers attempt to create rules that don’t necessarily reflect this complexity, often needing to rely on incomplete data about individuals’ lives. This reality does not lend itself to cleanly automated processes without human intervention. One concern with generative AI will be an attempt to fill in this incomplete data set in a way that appears rational and logical without an understanding on the harm that it can cause. This was an underlying flaw in the Robodebt scheme, and I can imagine this similar logic being attempted with generative AI.</p><h4>Wrap Up</h4><p>Both readings demonstrate the significant potential for harm that governments can enact, intentionally or unintentionally, through design. While design can mitigate harm, it can just as easily magnify it.</p><p>Next week, we will turn to design activism. Exploring what happens when governments fail to support the public in addressing their problems, and when people take solutions into their own hands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53601c7e5820" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2: Government Engagement]]></title>
            <link>https://davislevine.medium.com/week-2-government-engagement-dd6aac612971?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd6aac612971</guid>
            <category><![CDATA[public-policy]]></category>
            <category><![CDATA[codesign]]></category>
            <category><![CDATA[civic-engagement]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Sun, 01 Feb 2026 20:19:24 GMT</pubDate>
            <atom:updated>2026-02-01T20:19:24.989Z</atom:updated>
            <content:encoded><![CDATA[<h4>DESN480 — Design Issues</h4><h4>Required Readings</h4><p>Sherry R. Arnstein (2019) <em>A Ladder of Citizen Participation</em>, Journal of the American Planning Association, 85:1, 24–34, DOI:10.1080/01944363.2018.1559388</p><p>Trischler, J., Dietrich, T., &amp; Rundle-Thiele, S. (2019) <em>Co-design: from expert- to user-driven ideas in public service design</em>. Public Management Review, 21(11), 1595–1619. <a href="https://doi.org/10.1080/14719037.2019.1619810">https://doi.org/10.1080/14719037.2019.1619810</a></p><p>—</p><p>The second week of the seminar explores the different ways citizens can engage and participate in government policymaking.</p><p>The first reading was “<a href="https://www.tandfonline.com/doi/full/10.1080/01944363.2018.1559388">A Ladder of Citizen Participation</a>” by Sherry Arnstein. Originally published in 1969, Arnstein proposes a typology of eight levels of citizen participation, arguing that “citizenship participation is a categorical term for citizen power. It is the <strong>redistribution of power</strong> that enables the have-not citizens, presently excluded from the political and economic processes, to be deliberately included in the future.” For Arnstein, meaningful participation equals power redistribution. Who has it? How is it granted, and how is it enacted?</p><blockquote>Citizenship participation is a categorical term for citizen power. It is the <strong>redistribution of power</strong> that enables the have-not citizens, presently excluded from the political and economic processes, to be deliberately included in the future.</blockquote><p>Outside of the anti-poverty policymaking Arnstein developed her typology within, these rungs provide a framework designers can use to assess the degree of citizen power enabled through participatory design practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*GuntaAUufacoVaFqWlr61w.png" /><figcaption>Arnstein’s eight rungs on a ladder of citizen participation</figcaption></figure><p>To articulate the various levels of citizen power, Arnstein’s eight rungs move from levels of “nonparticipation”, starting at <em>Manipulation,</em> where “instead of genuine citizen participation, the bottom rung of the ladder signifies the distortion of participation into a public relations vehicle by powerholders.”</p><p>As one moves up the ladder, degrees of power shift into the hands of citizens culminating in <em>Citizen Control,</em> where power is vested in the communities impacted where they can “be in full charge of policy and managerial aspects, and be able to negotiate the conditions under which ‘outsiders’ may change them.” Governments no longer functions as the intermediary between communities and the resources they need.</p><h4>Arnstein’s Eight Rungs and Co-Design</h4><p>In <a href="https://medium.com/@davislevine/week-1-defining-public-design-4968b19432eb">last week’s readings</a> from <em>Leading Public Design</em>, the changing nature of design towards the social describes a shift to what is referred to as an “anthropological-design” approach. What might commonly be call user research. Design’s use of participatory methods moves away from the expert designer and invites citizens into the design process. As designers increasingly invite citizens into this process, we should critically assess how, why, and what this means through the lens of power.</p><p>I specifically wanted the class to discuss co-design, using Arnstein’s ladder as a model to examine power. The topic of co-design was introduced through the reading <a href="https://doi.org/10.1080/14719037.2019.1619810"><em>Co-design: from expert- to user-driven ideas in public service design</em></a><em> </em>by Trischler, Dietrich and Rundle-Thiele, in which the authors outline a seven-step co-design framework for public service design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yL_OmjTrWSJwWUy-TFLJ1A.png" /><figcaption>Seven-step co-design framework by Trischler, Dietrich and Rundle-Thiele</figcaption></figure><p>Through a case study approach, the authors identify different steps of co-design using projects primarily focused on communication and messaging strategies for public campaigns. While bringing in end users to inform communication strategies may not represent the pinnacle of community power relations, these practical examples demonstrated how co-design may produce better inputs, even though the output or final solution is mediated and filtered through decision makers and powerholders. The authors highlight this dynamic in the final step “Building for Change”, where “viable solutions” are determined with stakeholders and decision makers, not the impacted citizens.</p><h3>Co-design: Citizen Control or Tokenism?</h3><p>The case study examples gave the class a reference to discuss how and where co-design fits in Arnstein’s typology. As a practice, co-design can be situated across the rungs depending on how it is organized, implemented, and actioned. At the level of <em>Manipulation</em>, designers may bring citizens into a process where no real participation occurs, using end users as a “rubberstamp” to demonstrate a human-centred design process. At its most unethical, within the levels of “nonparticipation”, co-design is a form of intellectual resource extraction, especially pernicious when working with vulnerable or marginalized communities.</p><h4>A Focus on Power</h4><p>My personal perspective is that too many designers use terms like co-design thinking they are enabling higher degrees of citizen power when participation often sits, at best, within the “degrees of tokenism.”</p><p>Using Arnstein’s model, co-design should shift the power of design and decision making to those invited to participate. More often than not, co-design is simply a <em>Consultation</em> practice where “participation remains just a window-dressing ritual” because it “offers <strong>no assurance</strong> that citizen concerns and ideas will be taken into account”. Without a shift in power and control from input to output, ultimate authority remains with public manager and powerholders to decide what constitutes a worthy solution.</p><h4>A Focus on Partnership</h4><p>Working within government, a hierarchical organization built around accountability and decision making, creates a challenge when identifying ways of working that intentionally shift power dynamics. A feasible blueprint to what power-sharing co-design could look like in government may be Arnstein’s rung of <em>Partnership,</em> where “power is…redistributed through negotiation between citizens and powerholders. They agree to share planning and decision-making responsibilities…”</p><p>Here, I am not referring to co-design as a method for gathering user input on public messaging. Rather, this approach would re-evaluate how programs, policies and services are developed and implemented. Arnstein notes that <em>Partnership</em> is “most effective when there is an organized power-base in the community.” While this approach flies in the face of how the machinery of government is traditionally constructed, new models of citizen participation must be considered as we grapple with the increasing complexity of contemporary problems. Design, and specifically power-sharing co-design, may be one element to this new paradigm.</p><h4>Week 3</h4><p>Next week, we will challenge the idea of public sector design as “design for good” through the theme of <strong>Public Harm</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd6aac612971" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 1: Defining Public & Design]]></title>
            <link>https://davislevine.medium.com/week-1-defining-public-design-4968b19432eb?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4968b19432eb</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 20:30:50 GMT</pubDate>
            <atom:updated>2026-01-24T20:30:50.289Z</atom:updated>
            <content:encoded><![CDATA[<h4>DESN 480 — Design Issues Seminar</h4><h4>Required Readings</h4><p>Dewey, J. (2012). <em>The Public and Its Problems : An Essay in Political Inquiry</em> pp 46–49. Pennsylvania State University Press.</p><p>Bason, C. (2017). <em>Leading public design: discovering human-centred governance</em>. Policy Press. Chapter 2 and 3 pp. 21–5 2</p><p>—</p><p>As the seminar theme is on “Public Design”, the first week of readings were about exactly that — what do we mean by “Public” and what do we mean by “Design” in this context?</p><p>Part 1 of this post explores the first word: <strong>Public</strong></p><p>Part 2 will look at <strong>Design</strong></p><h3>Part 1: Public</h3><p>The class explored a definition of <em>public</em> as defined by John Dewey in his 1927 book <em>The Public and Its Problems</em>. Before defining a public, Dewey first explores the creation of the state. In searching for the origins of the state, Dewey rejects the notion that humans are inherently “political animals,” with the state being an inherent institution of human organization. Rather, Dewey argues that the beginnings of the state come into being through the need to regulate consequences that impact those who are not directly involved in a transaction between actors.</p><p>It is these indirect consequences that form a public, rather than the public being something defined by the state <em>a priori</em>. Dewey states that:</p><blockquote>The public consists of all those who are affected by the <strong>indirect consequences </strong>of transactions to such an extent that it is deemed necessary to have those <strong>consequences systematically cared for</strong>.</blockquote><p>The state, then, comes into being as the institution responsible for systematically caring for these indirect consequences that “affect the welfare of many others.”</p><p>By identifying publics, we can begin to think about the mechanisms and machinery of the state that design may be concerned with: laws, policies, services, spaces, and so on.</p><p>What I also find valuable in Dewey’s definition of a public is that it provides a framework for understanding why governments may or may not choose to intervene in certain domains of life or the extent of the intervention.</p><h4>Rediscovering the State</h4><p>What I found more interesting than the definition of a public is Dewey’s recognition that a public is not static. It is ever-evolving, driven by technological change and human behaviour. Therefore, the state, as a systemic reaction to the formation of a public, also cannot be static. It must be continuously “rediscovered.”</p><p>This raises an important question: <em>how effective is the state at understanding evolving publics, and how capable is it of being “re-made” in response?</em> I will return to this question below.</p><h4>Which Consequences?</h4><p>Dewey’s theory of the public was written in 1927. Does his theory still hold up nearly a hundred years later, in 2026? I am not sure. Globalization, climate change, and the internet paint a new backdrop for how publics can be defined and how the state must respond. This would be an interesting question to explore in future classes.</p><p>One critique or gap in his definition is the question of the state’s power in recognizing which consequences matter. There is a clear imbalance throughout political history regarding which consequences are acknowledged or deemed worthy of care. Additionally, it is sometimes the state itself that causes harmful consequences, which must be managed. This is a topic we will explore in Week 3.</p><h3>Part 2: Design</h3><p>Let’s look at the other side of “Public Design” — Design. To ground the seminar in a ‘definition’ of design within the context of the public sector, I’ve leaned on Christian Bason’s book “Leading Public Design”, specifically chapters 2 and 3.</p><h4>Chapter 2: The public sector and it’s problems</h4><p>In this chapter, Bason argues that governments have routinely failed to meet the social problems and challenges for which they are responsible. The chapter begins with a quote:</p><blockquote>Where the facts are most obscure, where precedents are lacking, where novelty and confusion pervade everything, the public in all its unfitness is compelled to make its most important decisions.The hardest problems are those, which institutions cannot handle. <strong>These are public problems.</strong> (Walter Lippmann, <em>The Phantom Public</em>, 1925, p 121)</blockquote><p>Yes, public problems are hard.</p><p>However, governments have failed to address them not because they are hard per se, but because they are complex (or wicked). And our traditional approaches to solving these problems have been fundamentally flawed from the start.</p><p>Governments rely on a “decision-making stance” according in Bason, in which a problem is identified, analyzed, options are considered, and then a solution is implemented. But in reality, by the time the feedback loop has come around, the problem has already changed.</p><p>What I have always found interesting about policy options analysis is its reliance on threes. There must always be three options. Does anyone question whether the complexity of the problem at hand can really be reduced to a single choice among three?</p><p>For a policy analyst, this decision-making process feels familiar. However, attempting to solve complex problems through familiar “best practices” is precisely why government has failed to rise to the challenge.</p><h4>Complexity; There Can Be More Than Three Options</h4><p>The topic of complexity and wicked problems was a central focus of the chapter and our class discussion.</p><p>The chapter references the work of Dave Snowden but does not explicitly introduce his Cynefin sense-making framework. I introduced this framework to the class as a way to help identify different ways of understanding a situation in order to respond appropriately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9WQ-g0xY80ORsBnKjQ9iA.png" /><figcaption>Dave Snowden’s Cynefin framework</figcaption></figure><p>The main dichotomy we explored was the contrast between complicated and complex problems. Government’s decision-making stance treats policy problems as complicated, when they should be understood as complex.</p><p>Rather than <strong>sense–analyze–respond</strong>, government should <strong>probe–sense–respond</strong>.</p><p>Probe-sense-respond is a familiar concept to designers used to iteration and testing. The principle also goes by different names and manifests in different ways. It’s well known as Agile and, more recently, has been repackaged as <a href="https://hansard.parliament.uk/commons/2025-07-16/debates/25071645000010/PublicServiceReformTestLearnAndGrowProgramme">Test, Learn, and Grow</a>.</p><p>This raises the question: what tools can public managers use to probe a situation? This is where design tools, such as prototypes, add value to government processes.</p><p>The traditional toolkit of policy development, I would argue, does not include fit-for-purpose interventions that allow for small, low-risk probing. While randomized control trials and pilots exist, these can be too large, visible, or resource-intensive to respond to the hyper-speed challenges of contemporary social problems.</p><p>Here I return to the earlier question: <em>How effective is the state at understanding evolving publics and its ability to be “re-made” in response?</em> I would argue: not very effective.</p><p>A fixation on a decision-making stance and a siloing of problems into verticals limits the state’s ability to rediscover itself in response to changing publics. We are tackling internet-era problems with a machinery of government modelled in a pre-internet era. A time when problems appeared to have clear boundaries and an option set of three promised a clear fix.</p><h4>The Problem with Problems</h4><p>Bason also argues that the problem-framing stance of government positions it in a perpetually reactive mode, and he calls for a “shift from a decision-making stance to a future-making stance.” Can government ever truly <em>solve</em> a problem if it is only reacting? Do we not simply move from one fire to the next?</p><p>This is where design can play a significant role in future-making. Design is a future-making discipline. Its primary concern is not what <em>is</em>, but what <em>could be</em>. While design often focuses on exploring near futures, there are also speculative design and <a href="https://medium.com/digital-experience-design/design-fiction-32094e035cd7">design fiction</a> methods that can help governments shift operate with a future-making stance. The class will explore speculative design in government during our final week.</p><h4><strong>Chapter 3: The changing nature of design</strong></h4><p>The next chapter the class discussed focused on defining design. Bason positions design as:</p><ul><li><strong>Plan: </strong>the objective</li><li><strong>Practice: </strong>the methods</li><li><strong>Reasoning: </strong>the mindset</li></ul><p>I focused most of our discussion on Buchanan’s Four Orders of Design as a way to show how design has shifted historically and to establish its legitimacy in government contexts, particularly in areas such as policy and services. As design moves into higher orders, we encounter greater complexity and a stronger social focus. These higher orders reveal the spaces in which public design operates, primarily in “activities and organized systems”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fd5qsdUZMs6okdbYxv1BpA.png" /><figcaption>Buchanan’s Four Orders of Design</figcaption></figure><p>As design shifts toward the social, Bason also notes that it has become increasingly “co”-focused: co-design, collaboration, and co-creation. In Week 2, we will explore co-design within a framework of citizen participation, so I will not get into the topic here.</p><p>Finally, Bason describes design as a form of reasoning, often referred to as design thinking (lowercase <em>d</em>, lowercase <em>t</em>). How does a designer show up differently in a problem space? Through “empathy, playfulness, comfort with ambiguity and complexity,…and abductive reasoning”. This mindset differs significantly from that of a traditional business or policy analyst.</p><p>This is why I am often critical of “capability building” approaches to design within organizations. Training efforts frequently reduce design to tools and processes, focusing on artefacts while ignoring the unique attitudes that trained designers bring to problem spaces. Perhaps this is a bit arrogant, but in an age of AI we need know how to defend the role of a designer, not just design.</p><h4>Defining Design</h4><p>Based on these ideas, Bason offers the following definition of design:</p><blockquote>Design is a systematic, creative process that combines different elements to achieve a particular commercial or societal purpose. The process is visual and experimental, with human experience and behaviour at its core. The results can be graphics, products, services, systems and new organisation and governance models.</blockquote><p>While not succinct, this definition captures the many dimensions of design and provides students with a broad understanding of design as it relates to the public context.</p><h4>Looking Ahead: Week 2</h4><p>Next week we’ll be exploring “Engaging with Government”, with a focus on citizen participation and co-design.</p><p>~~~</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4968b19432eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public Design]]></title>
            <link>https://davislevine.medium.com/public-design-d30ac41066aa?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d30ac41066aa</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[digital-government]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 23:01:03 GMT</pubDate>
            <atom:updated>2026-01-19T23:01:03.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>DESN480 Design Issues @ MacEwan University</h4><p>This year I am teaching the Design Issues seminar at MacEwan University, a third year course in the <a href="https://www.macewan.ca/academics/programs/bachelor-of-design/">MacEwan Design Program</a> that “challenges students to reflect on some of the major issues facing designers and the design profession…critically examined through design theory, problems and practice.”</p><p>I’ve taught this course for a couple of years, but I’ve relied on an inherited syllabus and reading list. This year I started from scratch and rebuilt the reading list and assignments to line up with a topic I’m passionate about: design in government. I’ve called the seminar: <strong>Public Design</strong>.</p><p>The central premise of the seminar argues that design in government should not be considered a neutral or objective practice, but rather it is a tool, function, and expression of government power. Students should develop a conscious understanding of design’s inherent role in upholding (or challenging) the power structures of government by examining the historical, practical, ethical, and future applications of design in this context.</p><p>With a new theme and reading list, I’m treating my course content as an ‘Alpha’, relying on feedback from the students and the public design community for suggestions on alternative sources to explore for next year.</p><p>Each week explores a different topic:</p><ul><li><strong>Week 1:</strong> Defining Public &amp; Design</li><li><strong>Week 2</strong>: Engaging with Government</li><li><strong>Week 3</strong>: Public Harm</li><li><strong>Week 4</strong>: Design Activism</li><li><strong>Week 5</strong>: Service Design</li><li><strong>Week 6:</strong> Digital Government</li><li><strong>Week 7</strong>: Public Policy</li><li><strong>Week 8</strong>: Technology</li><li><strong>Week 9</strong>: Speculative Design</li></ul><p>Every week I plan to write one or more posts on the topics, themes, and ideas that emerge from that week’s seminar discussion. This is intended as an exploration of ideas, both as a professional reflective practice and as an open forum to evaluate the course material.</p><p><strong>Feel free to subscribe and follow along!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d30ac41066aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Can Design Learn From Policy?]]></title>
            <link>https://davislevine.medium.com/what-can-design-learn-from-policy-d3d93bf4f821?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3d93bf4f821</guid>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[policy-design]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Fri, 04 Apr 2025 01:55:13 GMT</pubDate>
            <atom:updated>2025-04-04T01:55:13.120Z</atom:updated>
            <content:encoded><![CDATA[<p>Designers who work in the public sector, myself included, have been theorizing about how design can augment, influence, and transform the policy-making process. With this growing interest in design for policy, what’s missing from this developing field is an understanding of how policy development processes and the policymaker knowledge set can contribute to new knowledge creation in design. Rather than continuing to explore what policy can learn from design, I’d like to flip the question and ask:</p><p><strong>What can design learn from policy?</strong></p><p>This post is an open invitation to all policy professionals to share their thoughts and opinions on the topic. But for now, here are a few things I believe designers can take from policymaking:</p><ol><li><strong>Tradeoffs</strong><br>Policy operates at a higher level of complexity than most designers are used to. While design often focuses on individual needs, policy must consider multiple conflicting stakeholders and competing priorities. A key lesson I learned as an <a href="https://actioncanada.ca/fellowship/">Action Canada fellow</a> is that not everyone wins in policymaking. Tradeoffs are inevitable. This can feel wrong in design, where a human-centred approach aims to create a thing where each person using it is positively impacted. I don’t know if there’s a lesson to be learned here, but maybe a shift in mindset as we approach broad, complex problems?</li><li><strong>The Politics of Decisions</strong><br>Policymakers understand that the viability of any idea depends on its alignment with the political climate and the priorities of the government in power. Designers can sometimes be naive to this unseen force without understanding why some ideas move forward while others are non-starters. Understanding political realities, which policy makers can be quite adept at, can help designers frame their work in ways that resonate with decision-makers. While this applies most actively to working in government, I wouldn’t be surprised if this same design-centric ideas mindset is pervasive in private sector businesses amongst designers.</li><li><strong>Quantitative and Statistical Analysis</strong><br>Many policy analysts come from economics or other disciplines that emphasize statistical analysis. Designers can’t be everything, and asking them to be economists isn’t realistic or desired. However, while designers excel at qualitative research, we are increasingly being asked to support our work with quantitative evidence. The analytical skills of policy professionals could complement design practices and help us articulate the value of our work more effectively.</li></ol><p><strong>What else?</strong><br>These are just my initial thoughts, but I’d love to hear from you. What can designers learn from policymakers?</p><p>Leave a comment or email me at davislevine@publics.design</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3d93bf4f821" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Humans as Connective Tissue: The Hidden Costs of Government Digital Transformation]]></title>
            <link>https://davislevine.medium.com/humans-as-connective-tissue-the-hidden-costs-of-government-digital-transformation-154aca9262bf?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/154aca9262bf</guid>
            <category><![CDATA[digital-government]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Mon, 20 Jan 2025 02:27:40 GMT</pubDate>
            <atom:updated>2025-01-20T02:27:40.796Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-orEfFZn0knQ4OCkLZ8Fg.png" /><figcaption>Created using Midjourney</figcaption></figure><p>Human-centered design, by its very name, is centered around humans, but where does the dimension of labour fit into the human part of this discipline? With increasing promises of automaton through AI, in what ways are designers in the public service thinking about labour as a material of design, beyond an assessment of bureaucratic tasks? This is my contemplation on automation and the future role of labour in digital service delivery within the context of government digital transformation.</p><h3>Fear &amp; Apprehension</h3><p>When looking at a process for redesign, I often ask myself: What is the ‘work’ being done? Put another way, what is the functional value of human labour in this process? In many task-oriented roles of public service delivery, the answer may be “very little”. Reviewing, checking, double-checking, assessing information. Many of these tasks, though not all, can easily be done by computers given the right technology. If this is true, then how do the politics of labour fit into the design of future-state services?</p><p>Executives rarely outline workforce reduction as a primary goal of digital transformation, and with good reason. Programs that no longer demonstrate the need for a specific number of full-time employees (FTEs) will see their future budgets cut. From an incentives perspective, this ensures that organizations don’t ruthlessly chase job cuts in the name of digital efficiency.</p><p>In the absence of an agenda seeking to cut jobs outright, the phrase I often hear is moving staff from “low-value work” to “high-value work”. This generally means eliminating the drudgery of tasks that computers <em>could</em> complete and focusing human effort on areas best suited for humans to do.</p><p>This explanation points to what low-value work is, but there is a real lack of clarity of what new ‘high-value’ work would entail.</p><p>For employees performing ‘low-value work,’ (one can question who determines what is low-value) there is a legitimate fear of their roles being automated, even if the organizational incentives are not strong. Employees may be apprehensive about being research subjects in an initiative that might result in their replacement. When designers ask, “Why are you doing this?”, they are often seeking to understand user needs and challenges. However, this can be a threatening question for employees, representing concerns about livelihood, value, and worth.</p><p>But is this shift from low to high value work happening or is the nature of the work changing in response to new digital systems?</p><h3>Humans as Connective Tissue in Digital Transformation</h3><p>A signal of how work is changing as it relates to technology comes from Kate Crawford, in <a href="https://www.goodreads.com/book/show/50131136-atlas-of-ai"><em>Atlas of AI</em></a><em>,</em> where she states: “Instead of asking whether robots will replace humans, I’m interested in how humans are increasingly treated like robots.” In Amazon warehouses, workers “are there to complete the specific, fiddly tasks that robots cannot: picking up and visually confirming all of the oddly shaped objects that people want delivered to their homes. <em>Humans are the necessary connective tissue.</em>” (Emphasis added by me)</p><p>While Crawford’s analysis focuses on labour practices in Amazon and other large organizations, parallels can be drawn to public service delivery amid disjointed digital transformation efforts where humans often act as the connective tissue in the digitization of services. This is not the result of maximizing the use of human intelligence, but more about mending the seams that are too complex or costly to automate.</p><p>What does this look like in practice?</p><ul><li>A SharePoint site becomes the new standard for records management: Staff need to upload the files coming from multiple source.</li><li>A new public facing application form is delivered : Staff need to manually review the information and validate it against a different system from a different department.</li><li>An enterprise financial tool is mandated for issuing payments : It’s sold by a vendor and there are no APIs. Staff need to copy and paste information.</li><li>An Excel sheet keeps the proverbial lights on : Staff use this application to fill all the gaps where there is no ROI for purpose built software. And let’s be real, <a href="https://www.bbc.com/news/technology-54423988">government is run on Excel</a>.</li></ul><p>This connective role exists not because of value creation but rather the systems that should work together, don’t. It’s a socio-technical system patched together through human labour managing, tracking, and moving information. Knowledge work increasingly resembles an assembly line, aspiring to implement the principles of a Tayloristic factory floor. Exactly as Crawford describes on the Amazon warehouse floors.</p><p>Arguably, the above is simply an outcome of poor design. But I find it increasingly rare to see a holistic service design delivered across products and processes for both citizens and staff where functions are integrated within and between departments, let alone automated. A relentless focus on citizen experience can sometimes mean a de-prioritization of improving the working conditions behind the scenes, where staff are left making the system work. And modernization efforts across a service delivered by different departments let alone external organizations don’t always line up.</p><p>Human labour becomes more and more a mechanism to make things work, rather than an input for additional value creation. And the longer a department cannot identify the high-value work their staff should be doing, the more they are at risk of digital systems slowly eating away at their head count.</p><h3>Designing High-Value Work</h3><p>Automation does pose a risk to eliminating some jobs. However, in a world of limited budgets, it also presents a great opportunity to rethink and reimagine the role of labour in government. Designers working in government digital transformation should not perceive end users as the connective tissue of digital systems. They must understand the evolving role of labour in digital service delivery while designing the opportunities for high value work in the future.</p><p>— — —</p><p><strong>A note on the use of AI</strong>: This article was written by me with editing suggestions from Chat.GPT. The post’s header image was created using Midjourney.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=154aca9262bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridging the Divide]]></title>
            <link>https://davislevine.medium.com/bridging-the-divide-509584d0f5d6?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/509584d0f5d6</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Tue, 17 Dec 2024 19:37:54 GMT</pubDate>
            <atom:updated>2024-12-30T23:55:25.837Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Design Challenges the Fault Lines in the Public Service</h4><figure><img alt="Wooden bridge spanning a river connecting two buildings. Constructed using AI with Midjourney" src="https://cdn-images-1.medium.com/max/1024/1*wVgsk1-4P5ljMF6U-XvvWg.png" /><figcaption>Generated with AI using Midjourney</figcaption></figure><p>The most visible split in the structure of the public service is the divide between policy and delivery. In discussions about digital government, this divide is often left unacknowledged as the focus tends to be on improving how government builds and delivers services, not how it makes them from a policy perspective. However, digital government initiatives bring with them new ways of working, thinking, and being. More specifically we’ve seen an introduction of design methods into the public service as a tenent of digital government transformation. Without addressing the unique structural dynamics design finds itself within the public service, the promises of digital government will be slow to fruition. This post explores the dynamic between design, policy, delivery, and the public service using the concept of fault lines as articulated by Donald Savoie and Michael Wernick.</p><h4><strong>The Fault Lines of the Public Service</strong></h4><p>The separation of policy and delivery in the public service creates an organization with a clear division of responsibilities and duties. In the book <a href="https://www.goodreads.com/book/show/44179450-democracy-in-canada">Democracy in Canada: The Disintegration of Our Institutions</a> Donald Savoie calls this division between policy and delivery the “fault line”. Those above the fault line, the policy people, are responsible for thinking about, analyzing, researching, writing, monitoring, evaluating, and approving what government does and how they do it. Delivery people, those below the fault line, are the ones responsible for operationalizing the policy, working on the front line or behind the scenes processing applications, answering questions, publishing information, or building software.</p><p>While Savoie articulates a binary view to this division, Michael Wernick’s recent post on the “<a href="https://secteur-public-sector.ca/en/nine-fault-lines/">Nine Fault Lines and Seams in the Federal Public Service</a>” elaborates a more complex matrix of divisions, but nonetheless calls out the same tensions between policy and “operations”. For simplicity in this post, I’ll use the term ‘delivery’ to also mean operations.</p><p>Aside from dividing responsibilities within the public service the fault line appears to have an interesting impact on the attitudes, behaviours, and mindsets of those working on each side. Savoie claims that depending on which side of the fault line you work in, your priorities will be different noting that “Those above the fault line tend to look up to the political process and [executive council] for guidance and accountability, while those below consider that they are accountable to a variety of actors from their immediate supervisor, oversight bodies to their clients.” In other words, those above the fault line are primarily focused and attuned to what is going on above them at a political and strategic level, those on the other side are most concerned with the day to day operations of service delivery.</p><p>As mentioned above, these fault lines are not just mindsets, they are very real organizational divisions that can create an organization at odds with itself. This creates both upstream and downstream effects. Important strategic changes from central government “from the top” may be undermined if delivery programs do not believe it contributes to what they see as the true problems that citizens face. Those same challenges experienced on the front line often get ignored as they struggle up the chain of command if they don’t align to a strategic policy agenda (even if they solve a real problem). While there may be some tensions between these sides for various reasons, what I’m interested in is the role that design plays in bridging this divide as well as how these fault lines impede design.</p><h4><strong>A Public Service Resisting Design</strong></h4><p>Despite numerous government strategies being “citizen-focused” or “citizen-centred”, I’ve always been surprised why design, more specifically human-centred design, hasn’t taken root in the public service. I can point to reasons around internal capability and established working models, but Savoie points to a subtle mindset shift that exists on each side of the fault line that may provide a deeper explanation. He says that “those closest to the front lines…feel their primary accountability to citizens/clients while those farther up may feel primary accountability to citizen voters and taxpayers, as mediated by the political process.”</p><p>This difference in mindset is easy to understand. The front line deals most directly with the people accessing government services. They are a witness to the struggles of bad policy (or let’s face it, poor delivery) whereas those above the fault line — policy folks — don’t have this same visibility and thus understand the public in a more abstract sense: voters and taxpayers. Additionally, policy work often needs to balance the needs of many, which doesn’t always align to empathizing with individual lived experiences. I think this difference in perspective and visibility into the citizen experience is one part of the challenge, but it doesn’t fully explain the common points of resistance seen with design in government. I believe Savoie’s comment that those above the fault line see accountability being ‘mediated by the political process’ to be a critical concept.</p><p>Design resistance is not a rejection of empathy toward the individual, but rather a challenge to power. A key tenent of design is to utilize user research methods with people who use the designed thing, in this case a government service. A curious response I’ve hear about user research in government goes something like this: “if we learn about what they need, then we’ll have to do it.” or “The policy tells us what we need to do.” One would think that by learning what people need you’d be more motivated to do it! Senior leaders in government aren’t opposed to providing what people need or want, but they do have an understanding of how power and decision making happens. This resistance reflects a broader cultural issue, the fear that aligning with user needs might create tension with political directives, the top down direction of power, decision making and accountability.</p><p>When design enters to the public service, we are inadvertently introducing new ways of working that asks the institution and the bureaucracy in subtle ways to reverse the hierarchy of power and your sense of accountability when sitting above the fault line. Design is less inclined to look up for guidance and more inclined to look “down” and “out” to the very people who experience a policy or service. User research brings a level of visibility about the citizen experience into the public service that can potentially challenge the natural flow of decision making and accountability coming from the top. When a senior leader worries that user research will force the organization to do something, it’s not because it’s a bad idea but it may put them at odds with the direction outlined by decision makers. This begs the question: Who am I, as a public servant, accountable to at the end of the day?</p><p>Brace yourself for a somewhat controversial statement: Public servants are not accountable to, nor do they truly serve, the public. This is something that is rarely articulated yet structurally embedded within the DNA of the public service, despite public servants professing statements like “We work for the people, we serve the people”. In Canada’s parliamentary democracy, the government and more specifically the Minister is accountable to the public. The public service <em>serves</em> the democratically elected government by developing and enacting its policy agenda. And there is a long chain of hierarchy built into the bureaucracy to uphold this flow of accountability. The public service is not <em>designed</em> to meet the needs of citizens, it is <em>designed</em> to meet the needs of the government.</p><p>For many public servants this is probably an unpopular or uncomfortable position to view your work from. Many public servants wear a proud badge of serving the public. And of course they do that in many ways with great success. What I hope to highlight by pointing out this dynamic is a greater understanding of how decision making and power play out in the public service, and how design cannot thrive without acknowledging how, where, and why it best fits within the public service. While the value of design may already be successfully utilized below the fault line, those above the fault line may not fully embrace its true potential. In my opinion, design must find itself in spaces above the fault line to guide how policies are services are developed.</p><h4><strong>Bridging the Divide</strong></h4><p>The fault lines and seams of government aren’t going anywhere. But by understanding where they exist and the organizational dynamics they generate we can consciously work to bridge them. There are strategies and patterns that have proven successful to challenge the structural mindsets that come from the policy / delivery divide. To bridge the fault line, governments must create multidisciplinary teams that embed policy and delivery roles together. Design and user research must be prioritized at the outset of the policymaking cycle so that the processes and methods are not relegated to the delivery side where true change can sometimes be too little to late. And by including design up front, above the fault line, the public service can balance the needs of users with the government’s political mandate and directives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=509584d0f5d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Designer’s Guide to Working with Policy Analysts]]></title>
            <link>https://davislevine.medium.com/a-designers-guide-to-working-with-policy-analysts-41981c398dd8?source=rss-c96b311868cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/41981c398dd8</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Davis Levine]]></dc:creator>
            <pubDate>Tue, 07 Dec 2021 02:47:59 GMT</pubDate>
            <atom:updated>2021-12-07T02:47:59.601Z</atom:updated>
            <content:encoded><![CDATA[<h4>4 Tips for Successful Collaboration</h4><p>Policy has a significant role in the design of a service. It frames, guides, and dictates the interactions a user has with a service.</p><p>In a public sector context, designers overlook this ‘material’ because product teams don’t create policy. Drafting policy is outside the scope of a typical design role. However, not engaging with policy can lead to a poor user experience and outcomes. It becomes a necessity then for designers to work closely with the people who make the policy.</p><p>Ideally, you can work with a policy team when a new policy is being drafted and there is the greatest flexibility for change. But most delivery teams and designers will be working in a space of established policy. This makes change more difficult as policy hardens over time and becomes entrenched in the system.</p><p>Fighting this inertia will take effort. But this change can be the most important work you’ll do as a designer in the public service.</p><p>By following these 4 tips you’ll be better equipped to collaborate with a policy team.</p><h3>1. Establish a relationship around shared problems and outcomes</h3><p>Start your engagement with a policy team as early as possible and work on establishing a set of shared problems and outcomes. It may be a particular part of a service or an entire transformation.</p><p>The longer this dis-engagement occurs, the more difficult it will be to collaborate later in the process and the greater likelihood a turf war will pop up. These battles exist because each team views the other through a lens of encroachment rather than an opportunity for collaboration. They may think collaboration is unnecessary since they work in ‘policy’ and you work in ‘delivery’.</p><p>Rightfully so, policy teams don’t want designers showing up telling them they need to change policy, and delivery teams don’t want policy folks telling them what to build.</p><p>When you have shared problems and outcomes, your work is no longer about ‘the policy’ or ‘the design’, it’s about that common purpose. Shared problems and outcomes enable both teams to explore the relationship between policy and design. This also becomes a north star for teams to revisit later when disagreements arise.</p><h3>2. Understand the broader policy landscape</h3><p>Designers usually aren’t experts in the policy area they’re working in. When a designer comes to the table with their blue-sky vision of an ideal user experience, they usually don’t take into account the history and context of a particular domain or have an appreciation for the larger policy landscape.</p><p>Taking a broad systemic view of policy can give you insight into the types of decisions and analyses that policy teams need to make.</p><p>Policy is drafted within a broader policy landscape. This landscape includes the people or businesses seeking to access a service but can factor in a variety of forces like inter-governmental laws and regulations, compliance measures, stakeholder relations, environmental regulations, or international trade agreements (just to name a few).</p><p>You’ll find that policy analysts have many priorities they need to balance. Analysts try to work in a way that captures all possible use cases so nothing falls through the cracks.</p><p>Don’t be surprised when you bring your research findings to a policy analyst and they don’t jump at making changes. Design research may shed light on a problem within your scope, but addressing that problem may create problems for other actors. Policy analysts need to think about balancing conflicting priorities in ways that designers don’t deal with.</p><p>Taking a systems view to your problem can feel challenging as a designer (especially working at a product level), but it will help you understand the complex environment policy analysts are immersed in and better appreciate their perspectives.</p><p>By zooming out and understanding this larger landscape, you may even find new opportunities that your design can leverage. And by bringing this understanding to the table, you’ll show the policy team that you understand the constraints and considerations they face.</p><h3>3. Question the intent, not the policy</h3><p>A sure-fire way to create conflict with a policy team is to call out ‘bad policy’. You may discover a policy that seems ineffective, inefficient, or outdated. If you immediately try to change this policy, analysts will get resistant and defensive.</p><p>Every policy statement has a particular reason for its existence. If you discover something weird in policy, start with questioning and understanding the intent.</p><p>Ask questions like:</p><ul><li>Why does this policy exist?</li><li>How does it align with the problems and outcomes described earlier?</li><li>What are you hoping to achieve?</li><li>Is it attempting to mitigate a <em>known</em> problem?</li><li>Is it a <em>perceived</em> problem?</li><li>Does this problem <em>still exist</em>?</li></ul><p>If a policy team can’t answer these questions, this is a great chance to introduce the role user research can have in a policy making process.</p><p>By understanding the intention behind a policy you can work with an analyst from a common starting place. Linking intent with your shared outcomes means you are no longer focused on the policy analyst’s work.</p><h3>4. Align your work to strategic initiatives</h3><p>This tip is all about understanding what policy analysts value, and how you can use strategic priorities and initiatives of the government (or department) to your advantage.</p><p>I’ll use ‘Red Tape Reduction’ as an illustrative example.</p><p>Red tape is anything that citizens and businesses are required to do when interacting with the government and usually doesn’t provide value. Red tape increases time, costs, and frustration when interacting with the government.</p><p>You need to provide proof of payment even though we have that payment record? Red tape.</p><p>Collect a bunch of information that no one uses? Red tape.</p><p>Wait 90 days to receive a benefit? Red tape.</p><p>Governments love cutting ‘red tape’. You’ll find red tape reduction initiatives in nearly every <a href="https://www.alberta.ca/cut-red-tape.aspx">province</a>, <a href="https://www.gov.nt.ca/en/newsroom/gnwt-asks-northern-residents-and-businesses-suggestions-reducing-red-tape">territory,</a> and <a href="https://www.canada.ca/en/government/system/laws/developing-improving-federal-regulations/requirements-developing-managing-reviewing-regulations/red-tape-reduction-action-plan.html">federal government</a>.</p><p>For some governments, this cutting is a central priority and all departments are mandated to demonstrate how red tape is being reduced by an actual number count. Therefore, policy analysts and their executives really care about it.</p><p>This can become a strategic lever in your work.</p><p>For example, you may have conducted research with users and found a frustrating step in the process. You’ve figured out a way to omit that step, but it requires a change in policy.</p><p>Convincing a policy team to change this policy because it will improve the user’s experience is not always a convincing argument. Framing the change around reducing their red tape reduction count will land much better.</p><p>Different governments and departments will have various strategic initiatives. Find these and use them to your advantage.</p><h3>Conclusion</h3><p>For designers to be successful in the public service, they need to understand how their work fits within a larger context outside of the delivery team. Until policy becomes an embedded member in digital government delivery, the designer will continue to be a key bridge between these worlds. Knowing how to effectively work with these teams will increase the success of your service design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41981c398dd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>