<?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 David Burton on Medium]]></title>
        <description><![CDATA[Stories by David Burton on Medium]]></description>
        <link>https://medium.com/@idiotgrace?source=rss-17f9eac1d0ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MTWwn_SeZvAv0W-JSRdo-g.jpeg</url>
            <title>Stories by David Burton on Medium</title>
            <link>https://medium.com/@idiotgrace?source=rss-17f9eac1d0ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:50:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@idiotgrace/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[Seeing Hiroshima]]></title>
            <link>https://medium.com/@idiotgrace/seeing-hiroshima-1f97470451ca?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f97470451ca</guid>
            <category><![CDATA[hiroshima]]></category>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[history]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Thu, 06 Aug 2020 18:25:23 GMT</pubDate>
            <atom:updated>2020-08-06T18:25:23.171Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Yesterday was the 75th anniversary of the Hiroshima bomb. I was lucky enough to be able to visit the Peace Museum there in 2016. I wrote this afterwards, because it was heavy and I wanted to think it through.</em></p><p>The museum is in a park. The park is peaceful, and the rain is falling. School-children run, and tourists tour. I am uncomfortably conscious of the rubbernecking impulse that brings all of us to places like this, but the building is light and open and the prospect is beautiful. Somehow this fact does not seem inappropriate.</p><p>It’s notable, though, that the perfectly-kerned beauty of this park, while very Japanese, is far more 20th-century than the classical and lovingly-remembered intricacy of the other perfect Japanese scenes I’ve seen since being here. This is history, but it’s not romantic.</p><p>In a small lecture theatre to the side of the ticket-desk, a middle-aged woman is making a presentation. She is a successor — someone born to a survivor of the bomb. She shows pictures that her mother painted in response to a public request for survivors to recount their experiences through art. They are brightly-coloured and simplistic and horrifying. She painted them 50 years after the fact.</p><p>In one, bodies lie under grass mats along the side of a bridge. ‘My mother heard someone under there begging for water,’ she says. ‘She had no choice but to walk on.’</p><p>In another, bodies lie transformed into red blobs, their limbs truncated curlicues. Their eyes, in awful sadness, are white blobs, joined to their eye-sockets by single tapering white lines. The colours and shapes are cartoonish; the horror is that they may also be accurate.</p><p>‘My mother could not tell if they were men or women, they were so disfigured. Their eyes had burst and melted onto their cheeks’.</p><p>Her delivery is halting and heavily-accented. The presentation is powerful. It seems to reach a peroration twice, and it’s devastating: a flat, direct plea for peace, both times. The word ‘plea’ here is too close to ‘pleading’; what’s the English word for a force of moral authority you could build a new world on? Whatever it is, it’s here; not supplicant, and not accusative. Just solid. Peace must come. Peace must be.</p><p>‘We must stop nuclear development; and yes, we must end all war.’</p><p>Here and now, it is self-evident.</p><p>Here, the reminder that, for decades, we have owned bombs with the power to do thousands of times worse than this is no longer a matter of hard-nosed realpolitik covering a secret pride at still being at the top table. It is a new way of feeling shame. Not guilt; just sudden breathlessness at what we have claimed to be willing to do, whilst still imagining there’s such a thing as a good guy, and that we are it.</p><p>When I speak to her afterwards, she smiles radiantly. She asks me if I will go to the museum. I say yes.</p><p>‘You’ll learn a lot in there’.</p><p>I want to say I already have, but I’m stumbling on my words and I can only bow and offer a heartfelt thank-you with a deference I truly feel. Imagine narrating your own mother’s trauma in this way. Imagine narrating your own country’s trauma in this way.</p><p>There is a clock in the entrance hall which is counting the days since the explosion. Today it’s around 25,000. Below it is another clock, counting the days since the last nuclear test, somewhere on the planet.</p><p>Twenty.</p><p>Below it, a very Japanese take on the ‘doomsday clock’: a column of turning cogs, the top one turning 100 times a minute, the cogs below engaged or disengaged as global crisis proceeds. The top three are turning right now; the stack contains about 10. It feels a much better way of tracking the fact of consequence; the fact that crisis, and doom, start in a million small angry facts.</p><p>Nearby, a quote from Pope John Paul II: ‘To remember the past is to commit oneself to the future’. A better historian’s creed I have yet to read.</p><p>On the Shinkansen from Kyoto, I read John Hersey’s book Hiroshima. Written for the New Yorker in 1946, it tells the interlocking stories of 6 people who survived the bomb. The writing is spare and unemotional, leaving no space for any hyperbole. It describes the scattergun happenstance of untotal destruction — the flash, the fire in the aftermath, the confusion. In it, desks are blown to pieces while luggage stowed beneath them survives. Slippers are whisked from feet but feet are unscathed. German priests wander through a hellish landscape; Japanese men are nonplussed and shamed by their fortune in surviving. People spend hours in dragging the wounded to higher ground so the incoming tide won’t drown them, and then wake to see their efforts weren’t enough, and they drowned anyway.</p><p>The book describes the wounds that come from the built-in redundancy of a nuclear attack; if the heat doesn’t melt your eyes from your sockets the blast will skin you alive or drive glass through your skin. If the blast doesn’t scour you from the outside, the radiation will kill your ability to heal and strip you from the inside. Your gums will blister and your guts will expire.</p><p>In all the descriptions of physical injury in the book — far less emotional than I have the discipline to make them in the retelling — the worst moments are when it becomes clear that despite wounds that should kill, many of the melted and blistered are still alive. They’re not set-dressing in a horror film; they’re people, and they’re living this. And they are so numerous that the unwounded have no way to help them.</p><p>The museum exhibit contains leavings — fused ceiling-tiles, scorched schoolclothes, a tricycle — and remains. In one box, fingernails and skin sit, donated by the victim’s mother. She had kept them after his death on August 7th, the day after the bomb dropped and the day after his skin sloughed off.</p><p>Shadows sit on stone. In one place — and only one — a model has been made of children staggering through the ruins of the city. Their skin is shown melting from their bones.</p><p>Here, as in the book, the horror is that somehow they are still alive. The audio guide for this section is a poem, spare and short and direct. A child pleads for its mother to return. The poem barely needs to state that she won’t. It’s a devastating work.</p><p>So powerful was the blast that, at one point, Buddha statues appear, their stone skin blown away.</p><p>The museum is not bitter. In other places, such a memorial would be filled with nation-building recrimination and righteous hate; here, the Americans are only mentioned briefly, in one or two places. In an equal number of places, the fact that Americans and Korean prisoners of war died in the attack is noted. The British, who flew one of the support planes on the mission, are not mentioned at all.</p><p>At the end, a book sits, signed by all the world leaders and dignitaries who have come here. I can find no British Prime Minister. A whole display is devoted, understandably, to the visit Barack Obama made earlier this year. Next to me, an elderly Japanese gentleman with two walking-sticks painstakingly copies down the words he left.</p><p>Outside and through the peace park, the atomic dome sits. It’s an iron dome left atop its ruined walls, nonsensically still standing after being 160 metres away from the hypocentre — the centre on the ground — of the explosion; the centre of the explosion itself having been 600 metres in the air. A model in the museum showed this, and the rest of Hiroshima to a distance of 3 kilometres, with a red ball occluding the light directly overhead. The ball is the fireball; in reality a magnesium sphere 260 metres across after a single second. Over the model, it is a shadow. Over the city, it eludes sense. I stand under the atomic dome and look up.</p><p>I’m trying to imagine what a sun looks like when it is only metres away, discounting the obvious answer — brief — because it is too horrifying. I imagine that red sphere in brilliant white, a second after the explosion, as the invisible Enola Gay curves away above. I cross the Aioi Bridge — a distinctive t-shape, and therefore a cross-hairs for the bombing mission — and touch the stones on the opposite side of the river from the hypocentre. As far as I can tell, based on the picture of the dome before the bomb, these stones were here when the bomb dropped. Presumably — based on the evidence of the defaced stone Buddhas inside the museum — they were once thicker. I can’t tell.</p><p>It is the one moment today when I am unsettled, instead of horrified or ashamed or numb. I cannot say why but I only touch them briefly. It feels like touching something defiled.</p><p>But that’s the only effect. The rest of the city is calm, and prosperous; the rain has lightened and the sky is still. The park is quiet, except for the occasional sound of a large prayer-bell in a grove of trees.</p><p>I walk back across the river and towards the hypocentre itself. In preparing to come here, it seemed somehow important that there was a point — a place — a spring from which one could trace the tide of fear and forgetting that has been the age of nuclear force. I wanted precision; to know that all this pain and power has an origin; to somehow make maths of history and map the place it all began. I wanted a vector for the birthplace of the age that made me.</p><p>The point itself is a nondescript brown plinth holding a grainy photo of extreme devastation, taking up half of a narrow pavement and hard up against the boring lilac tiling of a 5-storey building. The sky above is a soft grey.</p><p>It didn’t all begin. Japan’s entry to World War Two was more like a continuation of a war it had been fighting since 1895, or 1905, or forever. Britain is the same. America too. And World War Two has never really ended; it’s just sluiced back and forth between superpowers and nations and religions and ethnicities, the endless planet-sized sea of violence and the will to power. And so here there is not a point, a place, a seed; there was no particular special human evil about the sky six hundred metres above Shima Hospital in southern Japan.</p><p>The closer I get, the more aware I become that what is here is an absence. The Little Boy device blew open an eye in a storm, a place where the air is calm enough for us to hear, below recrimination and more fundamental even than justice, the desperate imperative of peace.</p><p>The building is now, as it was then, a hospital. It was rebuilt within a year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f97470451ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain your @ — @idiotgrace]]></title>
            <link>https://medium.com/@idiotgrace/explain-your-idiotgrace-a931c59a4848?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/a931c59a4848</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[international-development]]></category>
            <category><![CDATA[justice]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Sun, 01 Mar 2020 05:54:44 GMT</pubDate>
            <atom:updated>2020-03-02T02:28:53.817Z</atom:updated>
            <content:encoded><![CDATA[<h3>Explain your @ — @idiotgrace</h3><p>@idiotgrace has been my @ for some time. I’m not sure why it seemed good to me back in 2009, but last year, as I hit the 10-year mark of working in international development, I started to think about it more, and started to wonder whether a new @ would be a good idea — something more sober, more serious, more befitting someone in the second decade of their career?</p><p>I decided not to, so this post is an attempt to work out whether that was a good idea!</p><p><strong>Idiot</strong></p><p>Starting with the way it sounds. There’s something in the tumbling slap of ‘idiot’ against the airy assurance of ‘grace’ which seems to draw a line around a place I want to live, somehow. It’s definitely not inert. That makes me quite happy.</p><p>More than that, there’s the meaning. ‘Idiot’ means someone who knows relatively little. In a complex world, everyone is an idiot. One way or another, we all have blindspots, and I have plenty.</p><p>It’s culturally normal for people like me (white, male, Anglophone, British-accented, cisgender, straight) to talk big — to pretend that we are not idiots, and that we are instead <em>terribly</em> intelligent — and I have seen that habit bear no good fruit in me. Where we could be listening to people, and learning, we are desperately fronting, underplaying what we actually have and over-stating what we don’t.</p><p>As a habit, it’s lonely; it perpetuates injustice; it teaches me to see my gifts as commodities, and not to see other people’s gifts at all. It’s both wasteful and incurious.</p><p>‘Idiot’ is a way of choosing a different approach to the things I care about. I want to listen. I want to contribute. I want to be part of work which is better because it is shared, and fairer because it is broader. Above all, I don’t want my intelligence to be used defensively, but in connection. ‘Idiot’ is a good way of disavowing the idea that brute force is the best use of my brain.</p><p><strong>Grace</strong></p><p>‘Idiot’ also recalls ‘idiom’; a private language. To a certain extent, all of us are using languages of our own invention, using our minds and bodies to translate the world we experience into something we can share. Everyone is always working to express the beautiful breadth of a world we will not ever properly explain.</p><p>And something extraordinary — meaningful, surprising, <em>graceful </em>— happens when we come together and combine our understandings of the world. Human creativity is the act of sharing our idioms, expressive and celebratory as they are of our idiocy, to further reveal the world in which we live together, to each other.</p><p>Bringing me to ‘grace’. I don’t control those new ideas, the creativity that emerges from our limitation. None of us do. We don’t control how they appear. We don’t even control the formation of the idiom which is our tiny contribution to them. But all the good things I’ve ever been a part of have been driven by this unforced abundance. Grace is a good word for that — unearned, unclaimable, reliable, present.</p><p><strong>Design and Justice</strong></p><p>This is all terribly worthy, of course. I’m not saying I’m good at these things — just that, having gone a long way and done a fair amount, these are the things I think it’s worth trying to do.</p><p>In my idiocy, I am free to receive things, and to give things, in a way which I would not be if I saw my presence in the world as being about control. I want to live and work in a way which acknowledges the fact that I am the recipient of good things, and uses those good things to do good things.</p><p>This relates to the very long journey I’ve been on, of coming to be comfortable with describing myself as a designer, though I can’t use Photoshop and I can’t code a webpage. The work I really admire seems to be driven by creativity and open-ness, and when we started to try to apply design principles in our international development work, the difference was palpable. Things got smarter, and faster, and fairer.</p><p>They also got bigger, and more complicated, harder to describe, and harder to sell, of course, but that’s not a terrible price to pay for work which is more sustainable and helpful.</p><p>I’m grateful that my professional life as a designer gives me opportunities to create spaces, and teach practices, which make creativity and freedom more likely, and broaden the span of gifts which people can practice and share. Using my privilege to bring people together and then get myself out of the way is good.</p><p>I’m grateful that my work in international development has shown me the breadth and depth of human worth, in front of which the only appropriate response is humility. It’s that humility, and gratitude, which I want to work out whenever I publish things. Even on Twitter.</p><p>We’re all idiots, speaking to each other. In that connection, we’re all given things we do not earn. And I’m grateful for, and proud of, that — idiot as I am.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a931c59a4848" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alongsiders Weeknotes: Episode 1]]></title>
            <link>https://medium.com/@idiotgrace/alongsiders-weeknotes-episode-1-682e5a55703c?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/682e5a55703c</guid>
            <category><![CDATA[social-change]]></category>
            <category><![CDATA[alongsiders]]></category>
            <category><![CDATA[ngo]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Wed, 11 Dec 2019 03:34:26 GMT</pubDate>
            <atom:updated>2019-12-11T03:34:26.717Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been thinking about weeknotes for a while, inspired by different people (but especially people working in local government in the UK). Having started a new part-time role advising on communications at Alongsiders (www.alongsiders.org), now seems a good moment to give it a try.</p><p>This is just an example, to see if I can work out how to do it! I’ve found this post about it really helpful: <a href="https://weeknot.es/what-on-earth-are-weeknotes-a81874c5cef9">https://weeknot.es/what-on-earth-are-weeknotes-a81874c5cef9</a>).</p><p><strong>Starting with Alongsiders</strong></p><p>I’ve been working with Alongsiders since the start of December, and it’s been great so far. In this job I’m trying to focus on <strong>helping</strong> people in Alongsiders movements to do communications in a way that makes sense for them.</p><p>Working at Alongsiders at the same time as being Director of Strategy at Glean is a really big learning experience — usually with Glean I’m a consultant, which means I work with organisations on short time-frames, and I’m rarely around to see plans come to reality. At Alongsiders I get to do that, which is very good, but is a new experience for me.</p><p>I’m looking forward to learning how things are paced inside an organisation like this — seeing how long things take over a long timeframe and how to keep things moving forward across 16 countries is definitely going to give me a lot of lessons to learn! I’m trying to schedule meetings with country co-ordinators to help me learn how I can help the most.</p><p><strong>Part Time Working</strong></p><p>Only working part-time has some side-effects that I’ll need to get used to. For example, so far I’ve had a lot of meetings to help me learn about what different parts of the organisation are doing, but that has meant that I still haven’t had a chance to do some things which are really important — like a complete review of Alongsiders’ content for communications.</p><p>If I’m going to make a good communications strategy, I’m going to need to understand what we already have, so I’m making time to go through the content, but it feels slower than I’d like it to be, and I’m a bit worried that I still haven’t done something which feels so basic. This week the review of content needs to move up the priority list for me.</p><p><strong>Being Part of Something Bigger</strong></p><p>My first day was our Christmas party, which was a very fun way to start in a job — a big meal (fried chicken, and chips as well as rice, I think especially for the potato-addicted Kiwis, Aussies, Americans and Brit in the office!), then a scavenger hunt (using Goose Chase, which is a great app for that), and a Korean-style BBQ meal with a secret Santa.</p><p>I ended up with a set of hairbrushes, and a medium-sized tshirt. As a big guy with a shaved head, obviously this was perfect.</p><p>It’s also been really good to get into an office rhythm of daily devotionals and reflections. It’s so helpful to connect with my new colleagues every morning, quickly in pairs, and talk about what we’re doing that day, and praying for each other. Every Friday afternoon there’s a longer reflection and music time, which is a really nice, laid-back feeling to end the week with.</p><p>It says a lot about Alongsiders that being part of this was one of the central pieces of my job description. Alongsiders don’t cut corners on building relationships and supporting each other, and it really shows so far.</p><p><strong>Suggesting Weeknotes</strong></p><p><strong>Because of that, I think weeknotes could be a really helpful tool in helping colleagues from around the world to feel connected to each other, and to support one another as we work together to help young people in poor communities.</strong></p><p>On Monday this week we had a discussion on Alongsiders’ work in 2020. There are 16 countries across Asia and Africa (and a new movement for Europe) where Alongsiders is helping young people in difficult circumstances to mentor younger people. It was a really exciting discussion, and one of the things that became clear was that it will be really valuable to share learning and encouragement across the movement, to help us all to have a sense of common purpose.</p><p>I think weeknotes are a good way of doing that, so I suggested they might be a good tool. Weeknotes are used by a lot of the people I really respect in the NGO sector in the UK, where I’m from, to talk through what has happened in their week, and reflect publicly on their work. People find them helpful because:</p><ul><li>They’re a way of practicing open-ness, which leads people to know each other better, and to share what they’re learning. Making things open makes them better.</li><li>Over time they build up into the story of your work: a new episode released every week!</li><li>They’re a way of remembering what you did in a week. We form better memories by thinking about what’s happened, and weeknotes can help us look back and see what’s good and difficult about our work, and what we can change.</li><li>They’re a way of sharing problems, and maybe getting solutions to them from people who read.</li><li>There’s no set format, you can write however you like.</li></ul><p>A lot of these things are really close to how Alongsiders works (it’s a movement where we want to be supportive to each other), so I think it makes sense.</p><p><strong>Fortnightnotes?</strong></p><p>I think in the future with weeknotes I’m going to try to keep things short, learn how to use simpler language, and write quickly. So far these week notes have taken me about 40 minutes, because I’ve never written them before and I’ve been learning as I go, and because this is a demonstration of the concept so I’ve edited it a bit more carefully so it’s clear. I definitely want to try to spend a short amount of time on them, instead of making them into long complex accounts of my work.</p><p>I’m not sure if doing notes weekly is the best way for Alongsiders — maybe notes every two weeks are better, since everyone is working hard and I want notes to be a helpful thing, not a weekly chore. I guess if we change the frequency of them I’ll need to come up with another name: Alongsidenotes, maybe? Fortnightnotes?</p><p>I’m interested to see how my colleagues feel about this — I don’t want to make their work heavier, and this is just a suggestion for something that could help. I think the most important principle of weeknotes is that they’re about work in progress, which is about trying things without knowing whether they’ll work, so I’m trying that with this. Whatever we do, I’m excited to see how we work together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=682e5a55703c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People Aren’t Browsers: Why We Have a PDF Problem in the NGO Sector]]></title>
            <link>https://medium.com/@idiotgrace/people-arent-browsers-why-we-have-a-pdf-problem-in-the-ngo-sector-d98266631f1c?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/d98266631f1c</guid>
            <category><![CDATA[international-development]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ngo]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Thu, 09 May 2019 10:05:06 GMT</pubDate>
            <atom:updated>2019-05-09T10:05:06.951Z</atom:updated>
            <content:encoded><![CDATA[<p>NGOs love PDFs. Almost every social change project I’ve worked on in the last 9 years, across every sector, has created, as one of its primary outputs, a PDF or document of some sort: a manual, a behaviour-change poster set, a strategy, a policy document.</p><p>That PDF usually reflects impact that’s been reached through other, less emailable work that we’ve performed. But there’s a consistent desire for a document to be part of what a project makes. And along with this comes a potentially dangerous problem; the idea that, when push comes to shove, what a project needs to generate is not change, but documentation.</p><p><strong>Making Change</strong></p><p>Change happens in people’s lives. This is the thing we are actually trying to achieve. And it needs to be linked to evidence that change has happened, and so the sequence after impact goes like this:</p><ol><li>Change happens.</li><li>Evidence of change is captured and recorded somehow.</li><li>Funding for further change projects comes in response to evidence that change is happening, or likely to happen; provided through the evidence recorded in step 2.</li></ol><p>The problem comes when points 2 and 3 form a closed loop of self-reinforcing activity and funding; an artificial marketplace of activity which is funded without reference to change, referring only to what we say about change. This is a long-term problem for the social change sector as a whole, too — because you improve what you measure, if what donors measure is documents, it is proficiency in documents that grows amongst NGOs, not proficiency in enabling social change.</p><p><strong>What PDFs Are Good For</strong></p><p>I actually rather like PDFs for some things. Generally speaking, when:</p><ul><li>There’s something that you need to be able to say -</li><li>For which layout is an important part of its function -</li><li>Which you need to be able to guarantee is an accurate and unedited record of its original creation -</li></ul><p>…then a PDF is great. That means that for project reports, or documents which are going to see most of their lives in print, a PDF is a useful tool, reducing ambiguity about authorship and giving you a lot of control over appearance.</p><p>PDFs allow you to present a canonical version, and make sure it looks better than a Word document, and these (especially the last one) are Very Good Things.</p><p><strong>Everything Changes, Even You</strong></p><p>However. Things you write down are only true for a period of time, and that’s the problem with PDFs. Because everything changes, especially in social change projects. Clue’s in the name. And outside major research or reporting, it’s very rare that the most important thing about your impact, whatever it is, is certainty that it hasn’t ever changed since it was written down.</p><p>This is particularly true, though, when we’re talking about making tools for social change projects — which is to say, when we’re making things that are supposed to enable people to make change in their communities (rather than enabling people outside those communities to see an image of a change that’s already happened).</p><p>When your publication — the medium through which you are saying something — is a reflection of a project that is ongoing, a PDF is usually a really terrible option. Because if the project is ongoing, then things are changing — and this is true for almost all publication types.</p><p><strong>People Aren’t Browsers.</strong></p><p>In the NGO sector we use the word ‘tool’ to refer to something that helps us to <em>do something</em>. A spreadsheet that tracks a particular metric is a tool (how many kids attended school today? How many of those kids had been part of a promotional event last week?) A user-friendly data-entry interface can be a tool, if you’re running a baseline survey.</p><p>And if you have, at some length, researched and documented a series of actions and policies which, if they were followed end to end, would result in something clear <em>being done</em>, and you can collect them in a single document, why wouldn’t you? PDFs feel like a natural place to do this. And sometimes, they are.</p><p>Only sometimes, though. Because fundamentally,<strong> people aren’t browsers.</strong> They don’t follow text like code, starting at the top of a document then working down through it, carefully and methodically noting the different contextual information and general rules before moving into specific usage cases. In more consultancies than not, I’ve been asked to create ‘tool’ documents like this as a key deliverable — ie, the thing without which the work is not considered to have happened — and it’s almost always been an infuriating experience, because I know that there was going to be a huge gap between ‘what people read’ and ‘what people do’.</p><p><strong>Change is Mixed Media</strong></p><p>More broadly than this UX problem, PDFs don’t accurately reflect how change happens. Change is big and complex and almost always surprising; and perhaps above all, change is something that is fundamentally mixed-media. The way change occurs is a mixture of words and images and movements and emotions and economies and power structures, institutions and relationships, from the personal to the national. All of which need to be relevant to, and usable by, and comprehensible to, <em>people,</em> when and where they’re trying to make change.</p><p>In the moment, faced with a need, or an opportunity to do the thing our project is aimed at, a person will not ever hold up a hand, stop everyone talking, and check which bulletpoint they’ve reached in the policy document to see what they should do next. Which means there’s no point creating a policy document which is designed on the assumption that a document is the right agent of change in every medium.</p><p>So though PDFs are a part of enabling change, so are WhatsApp messages. And so are calendars. And so are smiles. And even (real, actual, nonfictional) cups of tea.</p><p>And, quite honestly, I’m not sure where I, a rich-world outsider, would get the right to try and micromanage those things even if it <em>were</em> possible to do it through a document, which of course it very much is not.</p><p><strong>Change is Human</strong></p><p>Because <em>change is human</em>. That’s our tagline at Glean, and when we came up with it, I punched the air for happiness; because I was tired of seeing a lot of good projects work very hard to create well-designed documents that weren’t going to be used by the people they were designed with (or worse, for).</p><p>Change is human. PDFs are not. PDF addiction is the result of a desire to capture what is happening and show that it’s real. The problem comes when we imagine that the evidence of the change is the change itself.</p><p>That’s why, on projects where project managers are scared of the donor (perhaps with good reason), we are instructed to lose rounds of participatory testing and focus on creating a good poster. This happens A Lot, and it’s a rational choice in a donor-facing world. It makes projects worse.</p><p>Project managers are not stupid. they know that the donor, who pays for their salary, will never see the incremental change in worldview that happens when someone takes a self-directed step towards a better way of doing things, and that they will see a poster — because only one of those things can be attached to an email.</p><p>But it’s the small change, the honest fear shared and drained, the encouraging word from a neighbour, which will actually add up to a difference in how someone parents a child, or educates themselves, or finds food. The poster might help them get there; it will certainly help keep funding running. But change is not caused by posters. It can only be helped by them.</p><p><strong>Black Boxes and Magic Words</strong></p><p>There’s a deeper problem behind the belief that it is the poster that will make the difference (or the PDF, or even the classroom-style training session itself), which is that it is too blunt. It treats people, and the complexities of their lives and abilities and needs and brilliance and woe, as essentially black boxes.</p><p>When we make a PDF as our major output or tool, we are saying ‘I don’t really know how this can make a difference in the multi-dimensional reality of someone’s lived experience; so I’m going to assume that all that’s needed is a particular arrangement of words to unlock the problem.’</p><p><em>(Incidentally, this is also a beef I have with the phrase behaviour-change communications, because it implies that people who are acting in a way apparently damaging to themselves are sort of poorly-designed computers whose actions are simply explicable and will change in response to beaming the right message into their eyes. This, clearly, is reductive, and tempts us again towards seeing our participants, or users, as a) stupid and b) the problem — it’s a failure of vocabulary and ethics, and we need to change it. But that’s a post for another day.)</em></p><p>At the risk of repeating myself: the use of careful and particular arrangements of words in the right place is <em>great</em> and necessary. Language is humanity’s first technology (do not @ me) and we still use it for a reason. It helps us do things no other technology can.</p><p>But it does not help by itself. It helps as a very powerful means for us to engage in and move through the big complicated multidimensional spaces we occupy as people with needs and skills, within systems, under laws, and in relationships. And if our solutions aren’t addressing that complexity for itself, our solutions won’t do what we want them to do.</p><p><strong>Participation.</strong></p><p>Obviously the word that hovers behind all of this is participation. It’s a word that’s almost burned out with over-use (another favourite practice of the NGO sector), but principle behind it is what matters — who is the reason for the work? The donor, or the person in whose life and community change needs to occur?</p><p>We in the NGO sector need to be honest with ourselves and acknowledge that it is astoundingly rare for a project to truly have participants as a driving force. Because participants don’t pay anyone’s wages, or provide the structure for anyone’s career progression. In almost all cases, it is the donor’s priorities which inform what we do, and how we plan it, how we do it, how we measure it, and how we decide what to do next.</p><p>That may be perfectly natural, in our economic system. But it doesn’t change the fact that the active agents in any social change work must be the people who wish to see change in their society. That’s true ethically, because anything else is colonialism, which has done quite enough damage already; but it’s also true procedurally. Effective participatory work will always be broader than a PDF. Because a PDF may capture change. It may detail change. But it probably won’t directly <em>cause</em> change, and it definitely won’t ever <em>be</em> change.</p><p><strong>People are the Medium of Change.</strong></p><p>If people exist and make decisions and experience good and bad things in big, multidimensional contexts, then <em>people are the medium through which any change will happen in those contexts</em>. Change will happen for, through, in and because of people, and if it doesn’t, it won’t make sense. It will be more than just ineffective; it will be nonsensical. A two-dimensional shape on a four-dimensional plane.</p><p>The way to see change that makes sense, and lasts, is participation.</p><p>This is about our centre of gravity as a sector. In the absence of senior and donor-level buy-in to the idea that change can be valid even if it’s not printable, we default to making printable artifacts as evidence of change. We serve that need, rather than a user need. But that is not what we have to do.</p><p><strong>An Alternative</strong></p><p>Obviously I’m writing this to detail something I think we need to change. And as a human-centred designer I think starting with needs, rather than money, will help us to have a clear idea of how that change can happen; but at this stage, all I have is a sense that that would be a wise first step. I don’t know where we might end up.</p><p>However, I wonder whether there’s something in the fact that sequence of change I detailed at the top of the post feels a bit <em>industrial-era</em>.</p><p>Change, followed by documentation of that change, followed by further work justified by that documentation.</p><p>It feels a bit lumpen, and single-channel. What if the change was enhanced by better documentation, provided while it was going on, touching on the different aspects of change in ways that bring them out, clarify them, even amplify them? What if further work could start, not at the end of the project, but as a spin-off of it, as further needs become clear and users reflect on the change that’s already happening?</p><p>That wouldn’t always be the right thing to do. But what if the change that clarifies a technical approach was attested to, not by a single after-the-fact PDF, but by people who see and understand its impact because they have been fundamental to its design and its success?</p><p>That would involve open working (not a strength of our sector at the moment), but I wonder how many creative — even genuinely innovative — approaches would arise if donors funded work that way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d98266631f1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a chatbot for civic engagement]]></title>
            <link>https://medium.com/@idiotgrace/designing-a-chatbot-for-civic-engagement-147b38030555?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/147b38030555</guid>
            <category><![CDATA[codesign]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 09:58:15 GMT</pubDate>
            <atom:updated>2019-04-17T09:58:15.208Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a story all about how we made a (prototype) chatbot to help Cambodians engage with their local government, what we learned, and what needs to happen next, over at the Glean site:</p><p><a href="https://glean.net/portfolio/chatbot-for-civic-engagement/">https://glean.net/portfolio/chatbot-for-civic-engagement/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=147b38030555" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The writer gets over himself: finding a good tone of voice in NGO communications]]></title>
            <link>https://medium.com/@idiotgrace/the-writer-gets-over-himself-finding-a-good-tone-of-voice-in-ngo-communications-8e0bd1785066?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e0bd1785066</guid>
            <category><![CDATA[language]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[ngo]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[nonprofit]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Mon, 10 Oct 2016 09:54:15 GMT</pubDate>
            <atom:updated>2016-10-10T09:54:15.971Z</atom:updated>
            <content:encoded><![CDATA[<p>Learning to write in your organisation’s voice is hugely important if you’re an NGO communications professional. I’ve been creating a lot of content recently for <a href="http://www.glean.net/">Glean</a>’s This is a Story project — our forthcoming guide to simple NGO communications — and while I’ve been writing, I’ve been noticing a bigger and bigger difference between my voice and Glean’s voice.</p><p>This is something I could talk about forever, for I am a nerd about language and communication. But right now, I want to talk about choosing the right words <em>for your audience</em> by keeping a close eye on your tone of voice.</p><p>As always, this is about observing my own learning process, as someone who has been writing for as long as he’s been reading and who is nonetheless always discovering things he doesn’t know.</p><h4>Learning from my own writing</h4><p>That last sentence is a great example of the kind of thing I wouldn’t write in a guide I was creating for Glean. I like the sentence a lot, because of the internal rhythm of its recursive structure: by structuring it that way, I think I’m able to shed light on the internal workings of my writing, and specifically the interaction between <em>my experience</em> (which is large) and <em>my learning</em> (which is nonetheless still going on). However, in order to shed that particular light, the sentence gets <em>complicated</em>. I don’t mind that, but it means the reader needs to be willing and able to go on a little dance with me instead of walking directly from A to B.</p><p>If I was writing that sentence for a Glean guide, it would read something like this:</p><p><em>‘You never stop learning. I’ve been writing for decades, and I love doing it — but that doesn’t mean I know everything. While I’ve been creating these guides, I’ve seen many ways I can improve my writing to make it clearer for more people.</em>’</p><p>I mean, <em>hopefully</em> the version I’ve written for this blog is more characterful, and more expressive of my personal style. I certainly think it says what its saying in a more interesting way, and therefore perhaps makes the point land better <em>with people who bother to follow it</em>. But that’s the point. Its construction raises the level of attention the reader needs to pay to get anything out of it at all.</p><p>It may be more fun (for me, at least). But it is also less accessible.</p><p>That’s fine. It’s my blog. And my voice, too; I’d be a fool to try and emulate someone else. But that’s not the case when I’m writing for my organisation. Even though I am one of the major voices that shapes Glean’s content and brand, it would be inappropriate for me to bring my voice unedited into Glean’s content in all its image-laden structural back-and-forth — the result of a youth (mis)spent reading too much P.G. Wodehouse — because with Glean, I’m serving people whose needs are diverse.</p><p>(Or again, to put it in the Glean voice: <em>often when I write personally I find it fun to use complex sentences, but that can make it too difficult to follow what I’m saying. Our audience at Glean might not speak English as a first language, so I need to make sure I communicate in a way that’s as clear as possible when I’m writing for them.</em>)</p><h4>Cross-cultural communications</h4><p>I’m thinking about this today because of a conference I attended last weekend. It was a great conference — a lot of the participants are complete heroes, engaged in the thankless task of enabling rehabilitation for prisoners in often-horrifying contexts. It was great to meet them, and great to learn from them.</p><p>At this conference, almost everyone spoke English as a second language. I spent most of my time communicating in simple language, aiming for each sentence to contain a clear meaning in as few words as possible. I’ve been working cross-culturally for long enough now that this isn’t something I really think about any more, and so it wasn’t until I left that I realised the kind of language I hadn’t been using for a few days.</p><p>When I arrived home, I had a thoroughly enjoyable meal with my wife, whose conversation is always illuminating, playful and fun. That’s about a lot of things — not least the fact that she’s far smarter than I am — but it’s also about the fact that we can talk using a language that is fairly complex. When you’re having a conversation in English as a first language, humour is a huge part of things, and that humour is often linguistic, arising in ironic asides or pithy observations. Words aren’t just tools, but toys. Sentences dance. I enjoy it a lot.</p><p>But at the conference, it would have been completely inappropriate for me to communicate with that kind of complexity. If I’d have spent all of my conversations having fun with language, two things would have resulted. One is that I’d have spent the weekend being frustrated, because none of my <em>bons mots</em> (such as they were) would have made people laugh. And the second is that the conference would have been a complete waste of time. My contributions would have been worthless, because no-one would have understood them.</p><p>That’s not to say there was no humour — when you have a room containing Kiwis, Aussies, Singaporeans, Malaysians, Cambodians, Bangladeshis, Burmese, Thais, Americans, Indians, a Solomon Islander, a South African, a Dutchman and a Brit, there’s enough good-natured cultural misunderstanding to fuel a weekend of laughter, and it was so — but the fun didn’t come from the language, it came from the connection between people. The language was, of necessity, simple. And incidentally, thank God, it was English, otherwise I would have been in trouble, what with my fractured French, broken Bangla and cracked Khmer.</p><h4>Know your audience (properly)</h4><p>For the purposes of that conference, we were each other’s audience; we were each the person that the other people in the room needed to connect with and understand. So we spoke simple English, in the hope that we would maximise the extent to which we understood each other.</p><p>With Glean, I’m creating content that needs to be helpful to people around the world, but particularly to people in developing contexts. It’s vital that I recognise that if Glean is going to do good, it needs to do it in a way that’s as accessible as possible. That means Glean’s voice, and my voice, are distinct: that I have to place my desire to be understood ahead of my desire to have fun when I write.</p><p>The principle is this: I need to get over myself and serve my audience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e0bd1785066" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The good cynic: getting startup stuff done by asking awkward questions]]></title>
            <link>https://medium.com/@idiotgrace/the-good-cynic-getting-startup-stuff-done-by-asking-awkward-questions-1577315fd84e?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/1577315fd84e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[cynicism]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Sun, 07 Aug 2016 09:02:41 GMT</pubDate>
            <atom:updated>2016-08-07T09:02:41.306Z</atom:updated>
            <content:encoded><![CDATA[<p>I was recently part of a planning meeting for a hackathon. I love hackathons. The idea of getting everyone together in a room to do awesome stuff to solve big problems is inherently exciting. We put aside our barriers, embrace messiness, and <em>get stuff done.</em></p><p>The meeting went well, but there were a couple of people in the room who seemed to be pretty ready to assume the worst about the event: almost as soon as we started discussing the practicalities, heads were in hands and reasons found for each item to be very nearly a hopeless loss.</p><p>It was frustrating. I wanted to say yes — to <em>get stuff done</em> — and here were a lot of reasons to stop, to think, to wait, to delay.</p><p>Ugh. And yet. These cynics, while their style isn’t mine, didn’t kill the hackathon. Far from it.</p><h4>Cynics against meh</h4><p>There’s a distinction to be drawn here between the apathetic and the cynic; or perhaps between the <em>bad cynic</em> and the <em>good cynic</em>. One of the greatest upsides of working in the startup world is that, in my sector, there’s no space for lazy, uninspired time-markers — the people with open-ended contracts who show up to get paid and like to minimise the amount of work they do, and who spread their lack of care around like an endless flu-season.</p><p>Apathetic people are killers of projects, relationships and outcomes; they make the world a big ball of <em>meh</em> and I’m glad that in the startup world they last about as long as a snowflake in a flamethrower, because it makes running a startup that much easier.</p><p>But there are still people in this sector who get accused of being cynical; and I think they’re different. In fact I think they’re indispensable.</p><h4>Rapid Prototyping: Round 0.1</h4><p>No-one likes the voice of someone asking the difficult question; particularly if they ask them a lot. But there’s something important about people who get accused of being cynical in the startup world: they are <em>in the conversation</em>. In an age where apathy is the default, they are showing up.</p><p>In fact, these cynics aren’t as cynical as they might like to seem, and that makes them vital; because they call everyone to embrace the real promise of a project rather than hiding behind wishful thinking.</p><p>There’s no-one who defends orthodoxy as much as someone who is secretly scared it isn’t true. A cynic on your team, even if they’re irritating, is the first person who asks whether this crazy dream is going to work — and you need to embrace that person, because they’re the first of many who will ask that question.</p><p>If, on some level, they’re willing to be convinced, you need them. You might not like them, but if your project is going to be more than a series of excited phone calls and breathless concept notes — if you’re going to <em>get stuff done</em> — then you need someone around who is unimpressed. Because the first version of your product isn’t ever impressive.</p><p>Think of the cynic on your team as round 0.1 of your rapid prototyping process.</p><h4>The good cynic</h4><p>The crucial difference between the bad cynic and the good cynic is that the good cynic wants to be convinced. They’ll fight — often ferociously — for the problems they see to be recognised, because they want the solution to be real.</p><p>You need a range of emotional styles in a team. You need someone who has the idea and loves the idea and advocates for it so it becomes something people accept as desirable and true. But as well as those people, you need someone who tries to find out whether the idea will really work. And those people usually don’t look or sound like cheerleaders.</p><p>Good cynics, whether they know it or not, carry into the conversation a powerful and unspoken assumption: whatever you’re doing, it’s worth complaining about. And that’s an assumption that can’t be spoiled by someone asking an awkward question, because it’s embedded in the awkward question like a Greek soldier in a Trojan horse. As long as they’re there, it’s embedded in your work. And that makes your work better.</p><p>So the hackathon will go off well. We got stuff done, and it’s still getting done; and it’s better because some of us had our heads in our hands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1577315fd84e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Post-Dignity Design and how to avoid it in international development UX]]></title>
            <link>https://medium.com/@idiotgrace/post-dignity-design-and-how-to-avoid-it-in-international-development-ux-de483c1b3fc?source=rss-17f9eac1d0ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/de483c1b3fc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[international-development]]></category>
            <dc:creator><![CDATA[David Burton]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 04:18:06 GMT</pubDate>
            <atom:updated>2016-08-04T05:01:36.701Z</atom:updated>
            <content:encoded><![CDATA[<p>A great piece of longform writing was published at Real Life last week, coining a term I think is incredibly important to tech companies working in international development: <a href="http://reallifemag.com/the-babysitters-club/"><em>post-dignity design</em></a>.</p><p>In the context of the article, it’s used as a wry, the-way-we-live-now analysis of apps like Yelp and Pokemon Go, which talk to their users like children in order to make some very grown-up sums of money from them.</p><p>It’s a fantastic, albeit wince-inducing, point, and it made me think about the way we design user experience (UX) in our international development programming. Because while it’s certainly distasteful to treat rich-world consumers like children, it’s downright destructive to treat users in developing contexts in the same way.</p><h4>User Experience for International Development</h4><p>User experience is vital to international development programming. It’s a term that’s come out of the tech world, and a good explanation of it might be to say that <em>user experience is why your Mum finds it easier to use a Mac than to use a PC</em>; but the implications of it are felt wherever any person interacts with any system. Including (and especially) international development projects.</p><p>At my agency, Glean, we’re the ones creating the resources that end-users experience (like the <a href="http://www.sreysroskhmer.com/en/">Srey Sros Khmer website</a> or the <a href="http://glean.net/oxfam-case-study-mip">Oxfam Mekong Region Inclusion Project communications strategy</a>), so we think about this a lot.</p><p>User experience is a problem that can be found at the bottom of most, if not all, development projects where impact hasn’t been as big as people might have hoped.</p><p>Wherever someone struggles to attend their new school because it’s too far from their house, or because social norms mean they can’t leave their home without male accompaniment; and wherever a technically superb water-filter becomes unusable because it can’t stand to be left in the sun for longer than 20 minutes, that’s a UX problem. It’s a UX problem when someone creates a great resourcing strategy (<a href="http://www.whydev.org/some-bad-news-about-toms-shoes/">buy a pair, send a pair!</a>) which further breaks the impoverished economy of the place it was trying to help.</p><p>Someone has created a system, and the user isn’t benefitting from it in the way they could. Sometimes the impact is merely disappointing; sometimes it’s terrible. Sometimes it’s money that’s wasted, and sometimes it’s far, far worse than that.</p><p>In international development, we have to be aware that we are dealing with absurdly high stakes. Lives, not Pokemon, are at stake.</p><h4>Ethics and UX for international development</h4><p>International development is an ethically tricky sector to work in. On one hand, it is unarguably a good thing that money and resources are made available to meet the problems that are faced in developing countries around the world. On the other hand, there’s a long and recent history of rich nations using their money to control and define what people in poorer nations do and become. Money comes with power attached.</p><p>And most of the time, this power is practiced in an unconscious way. Even for a well-meaning international development pro like me.</p><p>When I design UX, I start with what I know, and that’s appropriate. But I need to take my users’ needs into account as quickly as possible, otherwise I’m designing products for people who are on some level <em>like me</em>.</p><h4>Assume dignity.</h4><p>But I’m not anything like most international development project participants. I’m white, male, Anglophone and have a master’s degree. None of those things are bad (necessarily) but I need to work hard to let my users’ influence my design as soon as possible in the design process.</p><p>Because we don’t create UX out of some sublime and original genius. We’re pretty smart, but we’re part of an ecosystem of human-centred design thinking, and so what Silicon Valley does with its apps gets into the air that UX designers around the world breathe. It’s part, whether we know it or not, of the ideas we have and the approaches we take.</p><p>And no-one — <em>no-one </em>— needs a project that talks to users in the developing world the same way Seamless talks to users in New York. In New York, it’s impolite. In Cambodia it becomes the very strutting, condescending, moustache-twirling image of the arrogant Westerner abroad. And there’s been more than enough of that already.</p><p>Of course (I hope) I’m very unlikely to pull the sort of directly infantilising stuff that the Real Life article identifies in such cringeworthy detail. But if its in the air, it might be in my designs. It’s another part of my unconscious assumptions, and I need to get conscious of it, quick.</p><p>Because if I’m missing that, what else am I missing?</p><h4>Human-centred design for international development</h4><p>Put that question a different way.</p><p>What does a woman in rural Cambodia know about living in rural Cambodia that I don’t?</p><p><em>Everything.</em></p><p>And that’s the point.</p><p>It’s vital not to lose sight of the fact that the people we’re helping need our help mostly because of systemic inequalities and abuses of power, not because I’m fundamentally more able or intelligent or skilled than they are. Quite the opposite, in fact: they are powerful, able individuals who deal daily with situations that would probably have prevented me from making it to my 20th birthday.</p><p>I have to recognise that I don’t know what they need; but I do know how to work out how they can get it. That’s the partnership we want to enter into.</p><p>When we help people to design projects, we do a lot of work to make our designs as human-centred as possible. We design things simply, and get them in front of users as quickly as possible, so we can work out what works and what doesn’t, and then we design again.</p><p>The process is iterative: like writing a serial story, not like building an ocean liner. Make one; launch one; test one; repeat.</p><h4>Post-dignity design and international development</h4><p>This article isn’t an angry expose. It’s just a reflection, prompted by the Real Life article, on the fact that we need to always be humble in our UX design.</p><p>We don’t know people’s needs better than they do. We probably know more about how those needs can be met — we know what is technically possible, what tools exist or can be built, how long things take, how to find out what people need. But finding out how specifically to meet those needs without creating new needs is a process that needs to be humble, open and service-oriented.</p><p>We need to listen. Because we’re useful, not right.</p><p>At the end of an article like this it’s very tempting to finish with a list of tips to avoid insensitive or damaging UX design in international development. I’m going to resist the almighty listicle, and just suggest one thing; we need to add a question to the top of the list of things we do when we design projects, and it’s this:</p><p><strong><em>What am I assuming because I’m powerful?</em></strong></p><p>For me, that means checking my massive bag of privileges and then seeking opportunities, as early as possible and as often as possible, to expose my assumptions to the people whose experience is the most important — <em>users</em>. And then to be clear with myself and everyone who works with me that <em>their views are more important than anyone else’s</em>.</p><p>My job is to hear what they need and work out how our systems can help them to meet those needs, and to do it in a way that places their needs higher than my bright ideas. Or, more accurately, to bring my bright ideas to the service of people who are far, far more capable than I am of making what they need out of the resources they get.</p><p>If I can serve the end-users of my product by making my <em>experience</em> available to them rather than just my <em>privilege</em>, I’ll make a better product, and a bigger difference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de483c1b3fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>