<?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 Alec Johnson on Medium]]></title>
        <description><![CDATA[Stories by Alec Johnson on Medium]]></description>
        <link>https://medium.com/@Alec_Johnson?source=rss-b37f35c9d6e2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZT-LT7eJp5JKlTofDu1PcQ.jpeg</url>
            <title>Stories by Alec Johnson on Medium</title>
            <link>https://medium.com/@Alec_Johnson?source=rss-b37f35c9d6e2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:44:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Alec_Johnson/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[One year in]]></title>
            <link>https://medium.com/@Alec_Johnson/one-year-in-3276ec59478a?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3276ec59478a</guid>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Sat, 29 Jun 2019 13:47:36 GMT</pubDate>
            <atom:updated>2019-06-29T13:47:36.290Z</atom:updated>
            <content:encoded><![CDATA[<h4>That’s my first set of data science exams done – now to work out what’s next…</h4><p>Back when I started my Birkbeck data science MSc, I had grand plans to regularly blog about it. That didn’t happen. Turns out they weren’t kidding about it being hard to do an evening degree while working full time.</p><p>But the first year is done, and I’m now in the luxurious summer between years, while I wait for exam results and starting preparing for next year. So here’s a rambly, self-indulgent blog about where I am, and about the course so far.</p><h3>Head full of thoughts</h3><p>I now know tonnes of new stuff. Algorithm design, data structures, architecture and plenty more that I would never have got round to if I’d just carried on learning in my own time. That feels pretty fab. I feel genuinely employable now, rather than just being someone who’s done a bunch of programming puzzles on the internet. (Though I do love doing puzzles on the internet. Coding is just the adult version of the puzzle books I did for fun as a child.)</p><p>I’ve also found that my favoured direction might not be what I initially thought. I still get more excited about NLP than anything else (my wordy background meeting my techy foreground), but I’ve also realised I’m more interested in coding usable tools than I am in esoteric maths.</p><p>In particular, I’m never going to be amazing at the full-bore stats involved in some data science disciplines. But I do seem to be fairly strong at development (though I’ll see if my exam results agree…), and I already have a user-centred background, so I’m now leaning as much towards Python developer jobs as I am towards pure data science roles. My basic mindset is that making things is fun.</p><h4>Reviewing the first year</h4><p>So, the Birkbeck data science Msc. In short, I like it. Some folks have been a little disappointed by how much computer science there is alongside the data work, but for me the balance is spot on. You get a mix of data skills (algorithmic complexity and selection, statistical analysis, some R) and programming skills (fundamental logic, data structures and storage, object-oriented programming, bits of OS and assembly stuff) rather than just one thing. And while I’m no expert, I feel confident in saying you can’t do serious data science without strong computing fundamentals.</p><p>If that sounds fun, it’s a good course, mostly very well taught. But if you just want to do modelling and visualisation you might be disappointed.</p><p>I like that it’s quite varied, and it feels like this will be useful in the long-term. After all, we’ve got years of work ahead to develop specialities, so it’s good to get a sense of all the different directions early on.</p><h3>Planning year two</h3><p>Next year (by which I mean October, because academic calendars stay weird even when you’re an adult) I get to choose options and do a big project. Hurrah!</p><p>I’m definitely doing NLP, but I’ve got one other choice to make. I’m torn in 3 directions at the moment:</p><ul><li>semantic technologies (ontologies! Computer interpretation of human language!)</li><li>Java/programming approaches (because it’s everywhere, seems to turns up in search engines a lot, and I feel like a low-level language would be useful)</li><li>applied machine learning (it would be weird to do a data science MSc without any machine learning, right?)</li></ul><p>Honestly not sure at the moment, but it’s quite a fun problem to have. I might go and do some more puzzles on the internet while I think about it…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3276ec59478a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we built a tool to check our style guide]]></title>
            <link>https://wearecitizensadvice.org.uk/how-we-built-a-tool-to-check-our-style-guide-74ab6df1ab1?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/74ab6df1ab1</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[how-we-work]]></category>
            <category><![CDATA[brand-strategy]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Mon, 19 Nov 2018 14:35:23 GMT</pubDate>
            <atom:updated>2018-11-19T14:35:23.308Z</atom:updated>
            <content:encoded><![CDATA[<h4>In just a few days</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnoTfHewWoCG__VTJUJzqQ.jpeg" /></figure><p>Most big organisations have a style guide – a set of rules about how you should write when you’re at work. It will cover things like spelling choices (organise or organize?), style choices (how long should a sentence be?) and tone of voice (do you use contractions like ‘you’re’?).</p><p>Part of a style guide will be about branding. For example, at Citizens Advice we don’t call our local services ‘bureaux’ or refer to ourselves as ‘CAB’.</p><p>Another, bigger part will be about how your writing affects your readers. In our case that means keeping our writing clear and easy to act on. So in our style guide there’s lots of advice on using simple words, dodging jargon and keeping sentences short.</p><h3>The downside</h3><p>Style guides can sometimes be a bit of a hassle. And I say that as someone who loves them dearly.</p><p>If you’re a new writer, you have a huge document to absorb all in one go. Someone looking at your first pieces of work will have lots of little bits of feedback for you. This uses up your time and theirs.</p><p>It’s even worse if you don’t write regularly – perhaps you’re just publishing a one-off blog or some internal guidance. You’re suddenly expected to adopt a whole new way of writing, when you have plenty of other things to be getting on with.</p><h3>Fixing the problem</h3><p>We wanted to reduce some of this hassle – while also making our internal and external content more consistent. Plenty of plugins already exist for checking spelling and grammar, but none were easy (or cheap) to customise for our own organisational style.</p><p>So we decided to see what we could do ourselves. We set up a small team including content designers, a user experience designer and our data scientist, Ian. Ian’s made us many other brilliant tools, like the one that helps us <a href="https://wearecitizensadvice.org.uk/how-to-prioritise-3-000-pages-start-with-data-db107ac53e74">prioritise our content backlog</a>.</p><p>Together we spent several days working on a prototype that would automatically check your writing against the Citizens Advice style guide.</p><h3>Getting started</h3><p>We began by identifying our user needs, summed up by:</p><ul><li>as a new writer, I need to quickly check if my writing is in the right style</li><li>as someone who doesn’t write often, I need to avoid having to read and understand the whole style guide</li><li>as someone checking other people’s writing, I need to spend less time looking at minor style points</li><li>as any kind of writer, I need to keep working in my existing software</li></ul><p>It was also important to think about our limitations. We couldn’t make bad writing good – all we could do was hunt for specific problems. As anyone who’s ever used a spelling or grammar checker knows, it’s easy for theoretically useful software to become annoying when it tries to do too much. Mentioning no names…</p><h3>Identifying the rules</h3><p>Our content designers started exploring the style guide and working out what rules we could include. Step 1 was scribbling on sticky notes to put together an initial collection of ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xoa-HgI0k2bmk9W-" /><figcaption><em>Some examples of style guide rules we wanted to include</em></figcaption></figure><p>With only 4 days to build our prototype, we had to focus on rules we could easily codify. This meant leaving out more subtle or subjective parts of the style guide, like tone of voice. Instead we made a list of things like word choice, punctuation and sentence length.</p><h3>Building the tool</h3><p>At Citizens Advice we write in Google Docs, so when we looked at these needs we quickly settled on building a Google Docs addon. This would make it easy to fit our tool into the way people already work.</p><p>While our content designers were busy with the style guide, our data scientist and user experience designer got started on the Google Apps Script. They began by working out how we could check a piece of text and present the results to the user.</p><p>The result highlighted text to identify style problems, plus sidebar text to make suggestions. It used visual components from our design system, so the tool itself fits the design part of our style guide. After all, we couldn’t go round telling people to use the style guide if we didn’t follow it ourselves…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_HjcXIUwrqawEttF" /><figcaption>How an early version looked on-screen</figcaption></figure><h3>Bringing the 2 parts together</h3><p>Next we created a JSON-based data structure that would let content designers write style rules directly into the tool. This included regular expressions to find problems, plus explanatory text for each problem found.</p><p>This quickly got out of hand – in a good way. We initially planned to make a quick test version with perhaps 3 rules. Instead we ended up with more than 75.</p><p>Once everything was working we tested it with a few writers outside the team, and made some improvements. For example, we added a button to take the highlighting away again once you’d finished making changes.</p><p>Then, to finish off the project, we uploaded the addon to Google’s Chrome webstore so people around Citizens Advice could install it and try it out.</p><h3>Our next steps</h3><p>Even our brief testing revealed plenty more we could do with this tool.</p><p>For a start, there’s the rest of the style guide – there are still lots of rules we haven’t included. Then there are more complex features, like being able to click in the sidebar to take you to the location of the problem in the text.</p><p>We’ve paused for now, but we’re hoping to develop this further in the future. You can <a href="https://github.com/Nyzl/1i">look at the code on Github</a> if you’re interested in how it was made.</p><p>For me the biggest satisfaction was to design, build and publish a tool from scratch in just a few days. Better yet, this early version is already in use around the organisation. In fact, I’d better run it now to check over this blog…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F9f4d73%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F9f4d73%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/47d9092a0a729bc7b2367356df97dbc7/href">https://medium.com/media/47d9092a0a729bc7b2367356df97dbc7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74ab6df1ab1" width="1" height="1" alt=""><hr><p><a href="https://wearecitizensadvice.org.uk/how-we-built-a-tool-to-check-our-style-guide-74ab6df1ab1">How we built a tool to check our style guide</a> was originally published in <a href="https://wearecitizensadvice.org.uk/">We are Citizens Advice</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we designed content that puts our advisers first]]></title>
            <link>https://wearecitizensadvice.org.uk/how-we-designed-content-that-puts-our-advisers-first-f11c21f886ea?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f11c21f886ea</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[how-we-work]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 12:12:27 GMT</pubDate>
            <atom:updated>2018-08-13T13:47:35.772Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’ve been working on creating new content for our advisers – here’s where we’ve got to and what we’re doing next</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_Np5WaN6Ejbm-Ikv5lOzA.jpeg" /></figure><p>At the heart of Citizens Advice are our 20,000+ advisers, dedicated to solving people’s problems across England and Wales. Over the past year we’ve been designing new ways to create content for these advisers, so we can give them the detailed information they need and help them find what they’re looking for.</p><p>We’ve recently published the first version of this new approach. It features 44,000 words of new material on Universal Credit – one of the biggest topics for advisers.</p><p>Here’s how we got here and where we’re going next.</p><h3>Finding what matters</h3><p>We started by <a href="https://wearecitizensadvice.org.uk/how-were-making-sure-advisers-have-the-resources-they-need-f961408c2bcd">looking at what advisers need</a> from their content. This initial research showed us we needed to focus on:</p><ul><li>adding more detail</li><li>bringing content into 1 place</li><li>making it easier to find specific pieces of advice</li><li>clarifying how advisers can use external sources</li></ul><h3>Exploring our options</h3><p>The next step was <a href="https://wearecitizensadvice.org.uk/were-redesigning-our-digital-advice-to-make-it-more-useful-to-advisers-43a6aa70d675">designing and testing prototypes</a>. We tried a range of features and structures, including new topic homepages and sliding panels of adviser-only content.</p><p>For me the most important finding at this stage was the distinction between <em>recovery </em>and <em>discovery</em>. Sometimes advisers were trying to find out about a topic and how to help someone. But at other times they were trying to track down a fact they already knew – either to double-check the details or to put a reference into a case report.</p><p>This changed the way we wrote. Knowing advisers rarely read a whole page in one go, we made the headings briefer and more focused on nouns to make them easy to skim – and so easier to track down. This contrasts with our public advice, where headings focus on actions to take people through the steps of solving a problem.</p><h3>Testing and refining</h3><p>Trying out a variety of ideas at the previous stage gave us strong evidence of what was working and what wasn’t. This let us combine the best bits of our initial ideas into 1 broad design approach – ready to test more specific features.</p><p>One highlight from our feature testing was <a href="https://wearecitizensadvice.org.uk/why-we-removed-the-only-feature-everyone-liked-in-our-new-advice-tool-818c2793eb61">what advisers needed from a ‘quick links’ feature</a>. As it turns out, lots of people had opinions, but no one could agree. What sounded like an easy win on paper led to more confusion rather than more clarity.</p><p>So we took ‘quick links’ out. Sometimes what you leave out matters just as much as what you put in.</p><p>We also <a href="https://wearecitizensadvice.org.uk/people-dont-care-which-team-content-comes-from-they-care-about-whether-it-gives-them-what-they-8d94d0dc572c">abandoned some of our assumptions about structure</a> where we found we’d based content on internal teams and processes rather than genuine adviser needs.</p><p>We had 1 more crucial piece of research to do before we were ready for our initial release: <a href="https://wearecitizensadvice.org.uk/building-accessible-digital-tools-d994149ba974">accessibility testing</a>. This led to adjustments to our navigation menu design, and further tweaks to the page headings. As always, we found that better accessibility meant better design for all our users.</p><h3>Ready to go</h3><p>This took us up to June 2018, when we were ready to put our first version online. We published in 2 phases, giving advisers an opportunity to get to grips with the new approach and give us feedback before we removed the old content.</p><p>It proved popular, with good feedback giving us confidence we were on the right path. Advisers were pleased by the enhanced detail and clearer structure, saying things like ‘the new pages are a lot more comprehensive and yet very easy to use/navigate’. We’d replaced 157 pages of content with just 29, yet this meant more detail rather than less, as we’d pruned away jargon and repetition to make room for content that really mattered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*PQZUtgjuq2T7BcTz" /><figcaption>Our old Universal Credit index with its many sub-levels, compared to our new single list</figcaption></figure><p>Armed with this feedback we gathered our whole content team to analyse how we wrote for advisers. Our discussions ranged from broad points about how to identify the right level of detail, to specifics about the most helpful way to link to legislation.</p><p>We’ve also been sorting through our initial feedback for fixes and extra details to add. We’ll be contacting advisers soon to tell them what we’ve changed.</p><h3>Knowing what’s next</h3><p>We’re continuing this adviser content work with a dedicated team who’ll be looking at new content. They’ll also be exploring new features like:</p><ul><li>better case note referencing</li><li>customisable printing</li><li>content version histories</li></ul><p>We’re also looking at lots of other other priorities across the site as a whole – search, information architecture and content management system, to name just a few.</p><p>We’ll keep updating this blog as we make progress. Each step will be based on more research and feedback, so we can make sure our advisers have the information they need to give the right advice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F9f4d73%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F9f4d73%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/47d9092a0a729bc7b2367356df97dbc7/href">https://medium.com/media/47d9092a0a729bc7b2367356df97dbc7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f11c21f886ea" width="1" height="1" alt=""><hr><p><a href="https://wearecitizensadvice.org.uk/how-we-designed-content-that-puts-our-advisers-first-f11c21f886ea">How we designed content that puts our advisers first</a> was originally published in <a href="https://wearecitizensadvice.org.uk/">We are Citizens Advice</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Into the chrysalis]]></title>
            <link>https://medium.com/@Alec_Johnson/into-the-chrysalis-c278d8159be1?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c278d8159be1</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Sun, 29 Jul 2018 19:58:05 GMT</pubDate>
            <atom:updated>2018-07-29T19:58:05.787Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why and how I’m trying to move from content design to data science</h4><p>I’ve been various kinds of writer and editor since 2006, when I started my first grown-up job. But now, 12 years in, I’ve decided to switch to data science. In October I’m starting a data science MSc at Birkbeck, and I’ll be completing this part time over the next 2 years.</p><p>I’m going to try to blog this effort at a career change. Hopefully it will end up as a useful guide to anyone thinking of making a similar switch. Failing that, a horrible warning of how not to do it.</p><h3>The caterpillar</h3><p>Today I’m a senior content designer at Citizens Advice. It’s a pretty pleasing job: I make good content that helps people. Oh, and there’s a really big holiday allowance.</p><p>Content design always involves a bit of data. Google Analytics, Trends, Ngrams, user survey analysis – hat sort of thing. That’s where I started getting interested. That moment of ‘Hang on, I could do more with this than look up a few searches…’</p><p>I was also inspired by the year I spent as a copywriter on a behavioural science team. It was a good time for feeding new things into my brain: identifying measures that really matter, seeing the power of reliable quantitative evidence, and seeing how to do AB testing <em>properly.</em></p><p>Mainly, though, the thrill came from the code side of things. Again, content design got me started. A bit of html, a bit of css – and before I knew it I was tinkering with Python because a spreadsheet wasn’t doing all the things I wanted.</p><p>Then things got out of hand.</p><h3>The cocoon</h3><p>I realised I wanted to develop this combination of interests further, so I started talking to our ace data scientist at Citizens Advice (maker of snazzy things like our <a href="https://wearecitizensadvice.org.uk/how-to-prioritise-3-000-pages-start-with-data-db107ac53e74">Backlogger content prioritisation tool</a>). This escalated into some mentoring, and I got working on some little data projects – fiddling with some APIs and automating scraps of our work.</p><p>Somehow, not even delving into authentication, inconsistent date formats and the labyrinth of Jira managed to put me off. This was roughly when I realised I was enjoying the data side of my work more than the main parts of my job –which is generally a sign to look at something more seriously. So that’s exactly what I did.</p><p>Now I’m ready to enter the chrysalis – I’ve got a place on an MSc, I’m doing more coding in my spare time, and I’m trying to remember the stats part of my maths A-level. Oh, and I’m starting this blog.</p><h3>The butterfly</h3><p>Like literally every other writer I’ve ever spoken to, I spend a lot of time worrying. So I’ve been trying to think about what I’m trying to get out of data science. The MSc especially.</p><p>I have no illusions that I’ll magically become some economy-breaking AI developer. I know I’ve got 10 more years of aches and baldness than a regular graduate. I know serious tech people will groan at yet another oaf who thinks they can be a data scientist just because they read an article about trendy jobs and they quite like spreadsheets.</p><p>But in a few years I’d like to find myself in a fun job building things with data and code. Which, with any luck, will be the start of a career where I can become more specialist rather than more managerial – where I solve complex problems rather than asking other people to solve them for me.</p><p>That’s the hope. I’ll let you know how far I get in reality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c278d8159be1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The way we write at Citizens Advice]]></title>
            <link>https://wearecitizensadvice.org.uk/the-way-we-write-at-citizens-advice-19bd3a1c5cb1?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/19bd3a1c5cb1</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-creation]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Fri, 20 May 2016 19:28:52 GMT</pubDate>
            <atom:updated>2018-07-30T12:46:23.407Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a second cross-post from the <a href="http://alphablog.citizensadvice.org.uk/2016/05/the-way-we-write/">Citizens Advice digital blog</a>. We’re one year into rewriting all our advice content for the general public, plus advisers in Citizens Advice offices across the UK.</p><p>We’re working from the ground up, based on user needs and with a focus on clear English and finding new solutions to problems. We’re also creating a new case management system to be used in local offices.</p><p>As part of this, here’s some background on the writing process we use…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dghn9Zs-2IMMJ4-u614aQA.png" /></figure><p>They say writing is a solitary activity. Whoever ‘they’ are.</p><p>Sometimes it is. There are plenty of lonesome desks where people tap away in isolation.</p><p>But sometimes it isn’t, and our website is one of those times. We’re writing for a varied audience facing difficult situations. If we work alone, we can’t be sure that what we’re making is right, let alone helpful.</p><p>So we don’t just take a bit of paper and wait for the muse to come to us. We research, we test, we critique and we rewrite until we’re confident we’ve made something that works.</p><p>Here’s how we do it.</p><h4><strong>The need for needs</strong></h4><p>Whether we’re covering sick pay, post, Disability Living Allowance or one of dozens of other topics, we start in the same place: user need.</p><p>What makes people come to our website? What problems do they need to solve? What information do they need to understand? Will words be enough, or do we need something more interactive, like our <a href="http://alphablog.citizensadvice.org.uk/2016/05/benefit-checker-our-first-review/">benefit checker</a>?</p><p>We answer questions like these with research. We talk to advisers, subject experts and the public. We read the records from Citizens Advice offices. We study the data for our existing webpages to find out what parts of the site people visit and spend time reading. We look at search keywords both on our site and across Google.</p><h4><strong>The write time</strong></h4><p>Armed with the research, we write. Oddly, this can be the quickest part. That’s why we think of ourselves as ‘content designers’ rather than ‘writers’ – if all it took was writing, it would take no time.</p><h4><strong>Edit and edit again</strong></h4><p>Another thing the mysterious ‘they’ say: writing is rewriting. This one we agree with wholeheartedly.</p><p>We take every page through several rounds of refinements. First, a group discussion – we call this a ‘<a href="https://medium.com/@natalie_shaw/the-virtues-of-a-content-crit-9988b911fd96#.vximd396u">crit</a>’ . Then a more detailed study by experienced editors, making sure the structure is logical and the style matches the rest of the site.</p><p>But we don’t just talk among ourselves. We also test our work with the public and the advisers who work at Citizens Advice – the people who’ll be using the pages once they’re finished. Because if they don’t understand it, well, what’s the point?</p><p>After the public testing, a sneak preview for advisers who work for the Citizens Advice service. Two weeks where they can read the pages, use them with the public and make sure they work in practice.</p><p>Then a crucial final step: making sure it’s true. We run the content past our legal specialists, and past colleagues in Scotland and Northern Ireland, to make sure the advice is accurate across the UK. We’ll have been working with them throughout the process, but a final check is always worthwhile. Readable writing isn’t much help if it’s wrong.</p><h4><strong>Pulling back the curtain</strong></h4><p>Then, at last, we put the pages online.</p><p>But that isn’t the end. Releasing words into the wild is no different from releasing rare animals – you have to keep an eye on them to make sure they’re okay.</p><p>We watch the data. How many visitors are we getting? What searches are leading them to us? How long are they staying and what do they do next? What feedback are they sending us?</p><p>And that’s it –</p><p>– no, wait. There’s one more step. One last thing we do once we’ve raised the content, made it strong and sent it out into the world to find its fortune.</p><p>We blog about it, of course.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19bd3a1c5cb1" width="1" height="1" alt=""><hr><p><a href="https://wearecitizensadvice.org.uk/the-way-we-write-at-citizens-advice-19bd3a1c5cb1">The way we write at Citizens Advice</a> was originally published in <a href="https://wearecitizensadvice.org.uk/">We are Citizens Advice</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Citizens Advice digital: writing for two audiences]]></title>
            <link>https://medium.com/@Alec_Johnson/citizens-advice-digital-writing-for-two-audiences-f6817bda95ad?source=rss-b37f35c9d6e2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6817bda95ad</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[energy]]></category>
            <dc:creator><![CDATA[Alec Johnson]]></dc:creator>
            <pubDate>Mon, 02 May 2016 09:44:53 GMT</pubDate>
            <atom:updated>2018-07-30T12:47:17.322Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a cross-posting of something I wrote for the <a href="http://alphablog.citizensadvice.org.uk/2016/04/writing-for-2-audiences/">Citizens Advice digital blog</a>. We’re one year into a digital transformation project, rewriting all our advice content for the general public, plus advisers in Citizens Advice offices across the UK.</p><p>We’re working from the ground up, based on user needs and with a focus on clear english and finding new solutions to problems. We’re also creating a brand new case management system to be used in local offices.</p><p>As part of this, we put together some new material covering prepayment meters. Here’s how we did it…</p><p>Four million homes have prepayment meters for their gas or electricity. Four million households paying over the odds. Four million having to worry about emergency credit, debt repayments and getting to the shops before you can turn the heating on.</p><p>It’s problems like these that we wanted our new prepayment meter pages to help with – whether you <a href="https://www.citizensadvice.org.uk/consumer/energy/energy-supply/get-help-paying-your-bills/you-cant-afford-to-top-up-your-prepayment-meter/">can’t afford your prepayment meter</a>, or you just want to <a href="https://www.citizensadvice.org.uk/consumer/energy/energy-supply/your-energy-meter/get-your-prepayment-meter-replaced-with-a-normal-meter/">get rid of the thing</a>.</p><h4><strong>Behind the scenes</strong></h4><p>These pages are aimed at the public, but if you’re an adviser in a Citizens Advice office, you might need more.</p><p>Suppliers ought to respond when one of their customers says “You can’t install that meter – the cupboard is really high up and I’d never be able to reach it.”</p><p>Sadly, they don’t always. What it sometimes takes is a trained adviser telling them “You can’t install that meter – it would be in breach of condition 28.1A of the standard supply licence conditions, which state that it has to be ‘safe and reasonably practicable’.”</p><p>We wanted our new pages to help with this as well.</p><h4><strong>Detailed doesn’t have to mean complicated</strong></h4><p>We sat down with the energy regulator, Ofgem, to pick out the rules and laws that cover prepayment meters. Then we rewrote the legal jargon to say what it really means. Along the way we added summaries to help our advisers quickly find the right rules.</p><p>Next we needed to think about how to present these rules and summaries. We didn’t want to clog each page with hundreds of words of legal information. Nor did we want to interrupt the flow of the text. We settled on placing expandable boxes at the end of each page – almost like a digital version of footnotes.</p><p>The detail waits there, quiet and compact, until it’s needed.</p><h4><strong>Going public</strong></h4><p>There was one last question: why should this only be for our advisers? Well, partly because our research has told us – again and again – that complex terminology and unnecessary detail puts people off. Including too much can harm a page as much as including too little.</p><p>But we could still imagine situations where the background might come in handy. That’s why we’ve made our <a href="https://www.citizensadvice.org.uk/consumer/energy/energy-supply/complain-about-an-energy-company/check-the-prepayment-rules-your-supplier-has-to-follow/">central list of rules</a> visible to everyone. This way it’s available just in case it can help someone, but it won’t interrupt anyone’s journey to the answers they need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6817bda95ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>