<?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 Alysia-Marie Annett on Medium]]></title>
        <description><![CDATA[Stories by Alysia-Marie Annett on Medium]]></description>
        <link>https://medium.com/@alysiamarieannett?source=rss-85ae32948866------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KdDYLn4bLAsAJdCubI03fw.jpeg</url>
            <title>Stories by Alysia-Marie Annett on Medium</title>
            <link>https://medium.com/@alysiamarieannett?source=rss-85ae32948866------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:44:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alysiamarieannett/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[What I learnt from being on a panel about career progression in content design]]></title>
            <link>https://medium.com/rbg-digital/what-i-learnt-from-being-on-a-panel-about-career-progression-in-content-design-59914dd90f1b?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/59914dd90f1b</guid>
            <category><![CDATA[career-progression]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Tue, 19 May 2026 16:26:00 GMT</pubDate>
            <atom:updated>2026-05-21T08:52:31.532Z</atom:updated>
            <content:encoded><![CDATA[<p>On Tuesday 28 April 2026, I was invited to be one of the panellists for the London Content Design Meet Up. The event was about progressing in a content design career and was sponsored by <a href="https://hippodigital.co.uk/">Hippo</a>.</p><p>This was my first time on a panel and was a great experience and an opportunity to try something new.</p><p>So here’s how I was invited onto the panel and some reflections on some of the common topics people raised.</p><figure><img alt="There are 4 chairs on a stage with microphones, on the left is a screen with a Career Progression presentation on it." src="https://cdn-images-1.medium.com/max/1024/1*gcP0aTuvrl8HaLymf-2Obg.jpeg" /></figure><h3>How did I get the opportunity</h3><p>I’m Content Lead at the Royal Borough of Greenwich and am very lucky to work with Eleanor, one of the hosts of the <a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jasdeogan.com%2Fmeet-ups&amp;data=05%7C02%7CAlysia-Marie.Annett%40royalgreenwich.gov.uk%7C4bfb634b394b46b6d12f08de7dcfc8fe%7Ce632f2633f464111aa5cd54126f95105%7C1%7C0%7C639086531683854754%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C20000%7C%7C%7C&amp;sdata=oTj94whvdk3t5aHWn1MzVd7WvzrotJtahyxSE8x7MGk%3D&amp;reserved=0">London Content Design</a> meet-up/ We’ve worked together for 5 years and she’s always encouraged me to push myself and not downplay my experience. So when she asked me if I’d be up for joining the panel, I accepted despite being a bit intimidated.</p><p>It’s important in any role to push yourself out of your comfort zone and develop skills that might not come naturally. As a lead, if I don’t challenge myself and try new things, how can I expect my team to?</p><p>I’m also responsible for hiring new content designers into the team so it was a good opportunity to hear from people starting out. Hopefully we were able to encourage people to apply for content design roles even if they don’t have content design in their job title yet, or apply for more senior roles.</p><figure><img alt="3 panellists sit facing a crowd. Andy Long from Hippo, Steve Hutson from Superstars and me (Alysia) from Royal Borough of Greenwich." src="https://cdn-images-1.medium.com/max/1024/1*UfbWX97Cj-68bvcKvxE0aw.jpeg" /></figure><h3><strong>Common questions after the talk</strong></h3><h4><strong>Attitude and people skills first, tools and processes later</strong></h4><p>One of the things that stood out to me was that people are really focussed on tools and processes. This makes sense as these are things you’re using day-to-day as a content designer. However, every organisation uses different tools and has slightly different processes and should offer training to help you learn how to use them.</p><p>The more important thing is who you are, how you build relationships, approach problems and deal with challenges. You need to be good with people to communicate change and show them the value and benefits of good content. These are the hard skills. You can learn them and can improve them over time with experience but a lot of it is your own mindset. You need to be able to understand someone else’s perspective and be open to having your mind changed.</p><p>Tools and processes can be taught. Empathy, compassion and a growth mindset is what people are really looking for when hiring a content designer.</p><h4>How to know what content design role is right for you</h4><p>Content design roles can vary in different organisations and sectors. You may even be doing a content design role with a different title.</p><p>It’s worth exploring what you really enjoy and what gives you energy and fulfilment. It might be:</p><ul><li>working with other disciplines and being able to be very creative</li><li>teaching or training people in content design and best practices</li><li>contributing to wider service change</li><li>being digital focused, diving deep into analytics and iterating website content</li><li>getting into the detail of microcopy and user experience design</li></ul><p>Content design incorporates all of these things but different sectors will have slightly different requirements and projects which will allow you to dive deeper into certain areas.</p><p>If you’re not sure which type of role or sector is best for you, there are loads of content design communities you can reach out to. Speaking to other content designers informally can help you get a more honest and clearer understanding of what content design looks like in that organisation or sector. This can help you focus your search on roles and sectors that best fit you and your interests.</p><h4>How to stand out in an interview</h4><p>A lot of people asked about how to stand out in your CV, portfolio or in an interview. For me, you do not need a heavily designed CV, portfolio or cover letter. Applying your experiences, approaches and reflections and relating these to what’s being asked for in the job description is what makes you stand out.</p><p>The same applies when it comes to interviews, it’s about being able to show the interviewer that you really care about what you do and the impact you have. To do that, you need to be in a role you actually like and feel contributes to something you’re proud of.</p><p>Something I mentioned to a few people was that they can, and should, ask questions in interviews. I’m not talking your standard “when will I hear back” or “what’s the salary” but questions like:</p><ul><li>what does content design look like at this organisation</li><li>what is the team structure</li><li>what other disciplines will I get or collaborate with</li><li>where does the team sit in the wider organisational structure”</li></ul><p>These questions have helped me in the past to make sure that the roles I’m going for are actually content design. I also like to know that any jobs I apply for have the structure around them that I need to do my job whilst also making sure I can have an impact and get fulfilment in the role.</p><p>Interviews are a way to see if you’re a fit for an organisation but also if the organisation is a fit for the career you want to develop. If someone asks questions to me in an interview I know they’re interested in content design and I know that their approach to content design aligns with how we work. If a content designer can’t work in a multidisciplinary team then they’re going to struggle to have the same impact as team members who fully embrace the wider team and learn from others.</p><h3>The main takeaways of the talk</h3><p>I’m glad I got the chance to be on the panel and share my own career journey which I hope made it feel more attainable to others. We got fantastic questions and had some really lovely conversations.</p><p>To summarise the advice from the evening:</p><ul><li><strong>Show the value of content design. Don’t just talk about it</strong></li><li><strong>Find a job that allows you to focus on what you enjoy</strong></li><li><strong>Your attitude and approach is more important than tools</strong></li><li><strong>Be human</strong></li><li><strong>Be your full self</strong></li></ul><p>Also, if you’re invited to do a panel and there’s a voice in your head telling you that you don’t have the experience or people won’t care about your experience, ignore it and do it anyway!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59914dd90f1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rbg-digital/what-i-learnt-from-being-on-a-panel-about-career-progression-in-content-design-59914dd90f1b">What I learnt from being on a panel about career progression in content design</a> was originally published in <a href="https://medium.com/rbg-digital">Royal Greenwich Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2024 in reflection: Clarity in chaos]]></title>
            <link>https://medium.com/@alysiamarieannett/my-2024-in-reflection-clarity-in-chaos-a1b0477e7f7a?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b0477e7f7a</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[new-year-resolution]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Tue, 31 Dec 2024 17:15:47 GMT</pubDate>
            <atom:updated>2024-12-31T17:20:53.985Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2024, I chose ‘clarity’ as my word of the year. If I’m honest, clarity flew out of a clear and transparent window and left me chasing it into 2025. I may not have achieved clarity but here’s what I’ve learnt that I’ll be taking into the new year.</p><figure><img alt="A grey British Shorthair cat sits on the top of a sofa peering at her reflection in a large round mirror." src="https://cdn-images-1.medium.com/max/1024/1*ZpdNLJIYHsats2liq65eAQ.jpeg" /><figcaption>Willow the content cat reflecting on 2024</figcaption></figure><h3>3 steps towards clarity in 2025</h3><h4>Think first, not fast</h4><p>I know, I know, take a shot for every time I say ‘reflect’. I talk about it a lot but this year I’ve had less focus time to do it. I’ve really seen the impact of this on my work satisfaction, celebrating achievements and identifying failures and learnings.</p><p>I genuinely believe that some of my lapses in judgement this year are due to a lack of focus time, juggling too many things and focusing too hard on delivery. It left me working in a silo, not really hearing what people were saying and not questioning feedback and not adapting fast enough to feedback. And you know what that led to? Taking several step backs later and not being able to move onto the next thing after all.</p><p>This has made it really clear to me that I need to put this time aside in 2025. Having worked over the quiet Christmas period, I’ve had time to do this and realised how much I’ve missed it (hence this blog and the reviewed blogs ready to be published on the <a href="https://medium.com/rbg-digital">RBG Digital Blog</a>).</p><h4>Look before you lead</h4><p>This year I want to work out when to step in, when to step back and when to hold the step ladder for someone else. I tried lots of different things in 2024 but it didn’t always go well. Sometimes acting as a coach, sometimes working as peers and sometimes taking the lead.</p><p>It’s hard to get the balance right between making sure people:</p><ul><li>have agency over their work and have opportunities to lead whilst not taking on too much and getting overwhelmed</li><li>feel safe to try things and making mistakes whilst still catching situations before they escalate</li><li>feel safe to ask questions but not feel like they need approval</li></ul><p>This is something I’m keen to continue to practice this year so I can better support people and give them what they need from me. I won’t always get it right but hopefully I’ll strike a better balance.</p><h4>What leadership means to me</h4><p>One thing I’ve realised this year is that I was fighting to get clarity on what it means to be a ‘lead’. I’ve tried lots of different things this year and I’m glad I did as it taught me that I cannot be the leader everyone wants and it’s exhausting to try. You’ve just got to take it day by day and adjust, rather than asking people what they want/need as it changes so often.</p><p>Instead, what it really comes down to is being my authentic self and doing my best. I’ll always try to support people but I’m very aware of what I can help people with and what I can’t. This is important as I don’t want to overpromise. It’s easy to not have a solution to everything, admit that and still listen and support them with what is within my control. I also want to lead with what I think is best, this includes adapting to each person and situation individually but not just doing what other people think I should do.</p><h3>Things I’m proud of from 2024</h3><ul><li>Launching a new website and two new sections of the Greenwich Community Directory</li><li>The new Health and Adult Social Care content — this was a big project for me before I became lead and I really loved it. It’s lovely to finally see it live and seeing how we can build on it as we digitise services</li><li>Doing my first talk for Content Club — as someone who hates talking in front of others this was out of my comfort zone. I learnt a lot from doing it and know how to improve my public speaking for next time</li></ul><h3>Word for 2025</h3><p>2024 was a year of doing. This was great as we’ve achieved a lot this year with lots of product launches and content transformation. But next year I want to focus on going deeper, asking more questions, better understanding service needs and processes to help create more effective change.</p><p>I’ve always struggled with asking questions (read any of my school reports), so this will be an interesting challenge for me. I want to focus more on being attentive, listening more actively and leading with curiosity.</p><p>So that will be my word of the year: Curiosity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b0477e7f7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talk: Stop talking about content design]]></title>
            <link>https://medium.com/@alysiamarieannett/talk-stop-talking-about-content-design-e4bdf0b2cac7?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4bdf0b2cac7</guid>
            <category><![CDATA[content-designer]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Mon, 13 May 2024 08:24:21 GMT</pubDate>
            <atom:updated>2024-05-13T08:24:21.964Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I was invited to do a talk for Content Club. Content Club is a group run by design and content people run by community members. It is sponsored by Content Design London.</p><p>The talk was based on a blog post I wrote called <a href="https://medium.com/rbg-digital/adapting-your-content-design-process-for-services-5aae1771209f">Adapting your content design process to build better relationships</a>. The talk focused on how I’ve started to approach to communicating and building relationships with subject experts in a council environment. It follows one main rule which I named the talk after — Stop talking about content design.</p><p>I haven’t done many talks so it was a bit out of my comfort zone and I’m trying to bring myself to watch it back. There’s something about hearing your own voice and seeing your face on a camera that brings out all the negative self talk in your brain. But I’m pushing that aside to share the video of the talk because I like to think the content was good, even if delivery could be a bit better.</p><p>So here it is. You can watch the video, read the transcript or get Medium to read the transcript out for you.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FcXw4Js_1Q2M%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DcXw4Js_1Q2M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FcXw4Js_1Q2M%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6ad8554b32dda9b288b71457ad5bd196/href">https://medium.com/media/6ad8554b32dda9b288b71457ad5bd196/href</a></iframe><h3>Transcript</h3><p>Hi everyone, I’m Alysia and I’m Content Design Lead at the Royal Borough of Greenwich.</p><p>I’m going to talk a bit about my approach to stakeholder management today and why I’ve stopped talking about content design to non-design people.</p><p>I’m going to talk for about 20 to 25 minutes and then I want to open it up to have more of a conversation about your own approaches and see what we can learn from each other. Particularly interested in if this approach works for you or specifically doesn’t work for you in your own organisation.</p><p>But before we get into it. I’ll quickly tell you a bit about how I got into content design.</p><h4>Slide 2: How I got into content design</h4><p>I have had quite an unusual content design career path because I have only ever done content design.</p><p>I did an English degree at university and after the usual comments of “You’ll never get a job with that degree” or “are you going to be a teacher?” I started applying for any and every job that was even remotely related to my degree (you also shouldn’t need a degree to do content design). One of the many jobs I applied for, happened to be for a content designer at Medway Council and somehow despite no content design experience I got the job which I think had more to do with having the right attitude than direct experience.</p><p>I believe that being very open to learning from others goes a long way, so if you don’t have a content design background, don’t let it put you off from applying for content design roles especially if you’ve been doing similar work but without the title. Although content design is hard, as long as you care about making things simple and accessible, you’ll probably make a good content designer.</p><p>I’ve been a content designer for about 7 years, 6 of those have been in local government.</p><p>I did 1 year during covid at a tech startup where I was the first person in the team with content design experience. In that role I talked about content design a lot. Mostly because I was sat in a marketing team and they had an adjacent product team and it was very hard to collaborate with other product disciplines. So I did a lot of presentations and inviting myself to meetings and I do think we got to a better place. But it was a real struggle not having people in your direct team who really know what you need to have in place to do proper content design. It’s also hard when you can’t show them because you can’t collaborate with the people you need to. After that role, I really wanted to stop having to advocate for content design and just start doing proper content design again.</p><p>I decided that my happy place was local government, getting to work on content for all sorts of things from Christmas bin times, to getting a marriage licence to finding out if you can cut down a tree in your garden. So I started looking around and ended up at Greenwich where I’ve been for about 3 years.</p><p>Having done content design in local government for most of my career, I have tried and tested pretty much every approach to stakeholder management I can think of with varying degrees of success. But have finally got to my current approach, which is what I’ve named this talk after: Stop talking about content design.</p><p>I do want to start by saying that this is an approach that works for me and my context at a local council. I am also in a very lucky position at Greenwich in that content design is very well advocated for by senior leaders in the Digital team and they actually know what we do and the value we bring. They also promote this when talking to senior leaders in other departments which helps to remove some of those initial barriers. But like most organisations, we still work with lots of people who don’t know what we do and the value we bring.</p><p>I’d also say like every approach, it’s important to read the room and adapt if it isn’t working for you, your subject experts or your organisation. But hopefully some of what I’m going to talk about rings true for you and you’re able to try out some of these things yourself.</p><h4><strong>Slide 3: Stop talking about content design</strong></h4><p>Stop talking about content design. I know some of you will be thinking that this sounds counterintuitive. And that you have to talk about content design and help people understand what you do to get buy in and approval to do it.</p><p>I get that and it is true within your own team. It’s much harder if you don’t have that initial support from a manager, a head of service or other content designers or disciplines you work with.</p><p>But if you do have that support, then those are the only people who you really need to talk about content design to. They can help make sure you’re in the right meetings and that you have support when you’re frustrated about a lack of content design awareness from other teams.</p><p>The rest of the subject experts you work with probably don’t need to know.</p><p>I’m not saying we shouldn’t be trying to raise awareness of the value of high quality content and design, but I am saying we shouldn’t do it by talking about content design.</p><h4><strong>Slide 4: Content design challenges</strong></h4><p>I’d say one of the challenges I’ve heard most from other content designers is burn out from constantly having to advocate for content design and telling people why you should be invited in from the start.</p><h4><strong>Slide 5: The value of content design</strong></h4><p>But what if we didn’t have to explain the value of content design? What if we stopped talking about content design altogether?</p><h4><strong>Slide 6: Have you ever asked a friend to describe what you do for work?</strong></h4><h4><strong>Slide 7: That scene from Friends about guessing Chandler’s job</strong></h4><p>If you’re familiar with Friends, you’ll remember the scene where they’re trying to remember what Chandler does for a living. He’s basically a data guy but to them it’s just ‘something to do with numbers’.</p><p>The content design equivalent would be ‘it has something to do with words on websites’.</p><h4><strong>Slide 8: Who needs to know what content design is</strong></h4><p>It doesn’t really matter if our friends and family can explain what we do (although its nice when they have an idea).</p><h4><strong>Slide 9: You need to work with colleagues to create good content</strong></h4><p>But it does matter when our colleagues don’t know what skills we bring and what we can help them achieve. Because if they don’t know, they won’t give us their time and if they don’t give us their time then we risk our content being inaccurate or facing a blocker when we’re ready to publish it.</p><h4><strong>Slide 10: Things I’ve tried that didn’t work</strong></h4><p>We’re content designers, we love talking about content design. That’s why we go to so many talks and meet ups outside of our working hours. We love nerding out about words and design. But we can’t expect other people to want to do the same. Especially when they have their own jobs and their own lives to juggle.</p><p>We’ve all had times where we’ve felt frustrated explaining why things need to be accessible or why content needs to meet a valid user need. But we need to remember and treat our stakeholders as users with valid user needs too.</p><p>That doesn’t mean we shouldn’t push best practice or not design accessible content. But it does mean that we need to listen and hear them out and understand what matters to them and what they need.</p><p>I’ve tried and failed plenty of times and although I don’t think there’s one right way to do content design, I have learnt that there’s plenty of wrong ways. In the interest of transparency and accountability here are some ways I’ve done it wrong in the past</p><h4><strong>Slide 11: Doing presentations about content design to non-product or design people</strong></h4><p>Those presentations are hard enough to do with people who have user centred design knowledge but doing it to a crowd of people who have no interest in learning about how to do content design is often a waste of your time and their time.</p><p>Have you ever watched a golf YouTube video? My partner watches them all the time and nothing will make me stop listening to someone faster than hearing them talk in detail about how to do something and then hearing them congratulate themselves about how well they did it.</p><p>Self-congratulatory presentations about how great you are and why your job is really important only makes people feel you’re saying their role isn’t. Now I’m sure you’re not framing your presentation like that but there’s something about hearing someone talk about the value they bring that can really make you stop wanting to listen. Maybe this says more about me than everyone else but that’s an issue for another day.</p><p>What I am saying is that unless you make it relevant to the people you’re presenting to, they’re probably not going to take much from it.</p><p>I’ve done plenty of these presentations in the past and some have had positive responses but they just didn’t change anything.</p><h4><strong>Slide 12: </strong>Reeling off the content standards and what we do and don’t publish</h4><p>Sometimes the easiest thing to do if someone asks for something that you know isn’t best practice is to say. It breaks our rules to do that.</p><p>You’re not really helping them understand why and what the alternative is. You’re just making them feel disempowered. You may even panic and frustrate them if they think you could now be the person standing in the way of them getting the task they have to do ticked off their to do list.</p><h4>Slide 13: Just doing the work and hoping no one notices</h4><p>Sometimes having tricky conversations is hard. It can be really tempting to just do the thing and hope no one notices. But this is a pretty risky game to play.</p><p>If they do notice, you’ve broken trust and damaged an existing relationship or put another barrier in the way of building a working relationship with them. They may even tell others and no one will want to work with the team.</p><p>If they don’t notice, they won’t know what you’ve changed or why so really you’re just pushing the problem further down the line or pushing it on to the content designer who works with them next.</p><h4>Slide 14: Saying no</h4><p>Saying no is a necessary evil but saying no without context doesn’t help to manage expectations.</p><p>You need to explain why you can’t do what they’re asking, better understand what they need to do and find a better way to help them to that.</p><p>Or say ‘not yet’ and help explain when you’ll be able to work with them.</p><h4>Slide 15: Saying yes</h4><p>Nothing says ‘I’ve had a hard week’ than just saying yes to everything even when you know you should push back.</p><p>The conversations are hard but sometimes you need to have them.</p><p>That being said, you do need to compromise and sometimes you need to give in for your own wellbeing or ask a colleague for support. In our team, our content designers are able to lean on each other to have these conversations if one of them isn’t in the headspace to have them themselves.</p><p>In those cases, it’s a yes for now but we’ll review again in a few weeks when we have more time to improve the content as needed. Or a ‘yes for now and explaining what the problem is and how you plan to address it together in future.</p><h4>Slide 16: How to help them understand content design without talking about it</h4><p>Now I’ve just talked for ages about what not to do. So here are a few things that I think do work well when trying to help people understand content design without talking about it.</p><h4><strong>Slide 17: Treat subject experts like you would your users</strong></h4><p>We would always get to know our users through data or research to help inform how we write for them. So we should be doing the same with our stakeholders.</p><p>Only when we understand their needs, their priorities, outcomes and perspectives can we work out what they need and why. This will inform all our future interactions with them and help us build a good working relationship.</p><h4><strong>Slide 18: Avoid assumptions and approach conversations with an open mind</strong></h4><p>It’s easy to work ourselves up and get nervous and anxious befroe going into these conversations. Bursting in with a load of ammunition (or research) about why we’re right and why they need to do what we say isn’t going to help build that relationship. It also won’t help us understand why they want what they’ve asked for. It’s better to save all that evidence up for when know a bit more about them and the work and are ready to make a proposal of how we can meet that goal.</p><p>Knowing what they need and why, can help us find a more suitable solution. For example, if someone comes to us asking us to put their team structure on the website, we would be able to sit down with them and ask what they want to achieve and find an alternative that meets our standards.</p><h4>Slide 19: What they ask for vs what they help residents do</h4><p>They may say: ‘I want to promote my team’ and we’ll panic and get ready to go to battle because we know ‘team pages’ aren’t useful to residents who don’t know or need to know what teams our organisation is made up of or what they do.</p><p>Instead of assuming there’s not a valid user need. It’s worth pressing to see what they’re trying to achieve.</p><p>‘What do they need to know about the team?’</p><p>Instantly it’s less of a stalemate and it’s a conversation.</p><p>They may say something like “because people don’t know what we do”</p><p>You can say “well what do your team help residents do”</p><p>They may say “they help them with the process of getting an Education, Health and Care Plan’</p><p>And together you’ve realised at the same time what you actually need. A page that helps parents apply for care and support for a child.</p><p>At no point did you have to talk about best practice or content design or make them feel like they have no say over content about what they do.</p><p>We didn’t have to say</p><ul><li>We don’t publish team pages</li><li>Or we write user focussed content that meets a valid user need which doesn’t mean anything to them</li></ul><p>Instead you’ve come to a shared understanding of what is needed. You’ve built a relationship, the subject expert feels listened to and you’re both happy that the content you’ll be working on is needed.</p><p>Of course, if it’s not needed. The same sort of questions can help you identify that. You may ask who it’s for and find out its to help residents understand the process of the team and you can ask them which parts of the process they need to know about and what happens behind the scenes that only practitioners need to know. You’re not saying no to the content, you’re putting up what residents need and identifying opportunities for other content such as an intranet page that helps new colleagues understand how to make a referral and who they need to talk to.</p><h4>Slide 20: Frame your proposal based on what matters to them</h4><p>Once you have that relationship and know what they care about and what they want to achieve, you can make your conversations and proposals relevant to them. You can grab their interest and make them see instantly that you’ve heard them and can help them meet their goals.</p><h4>Slide 21: If they care about X talk about X</h4><p>You may have talked to them and they’ve mentioned that they need to save money, or meet new statutory duties, or save staff time or promote a service they run.</p><p>When you talk to them, you can explain your proposal in terms of those things.</p><p>For example, if they’re trying to save money talking about how good quality content is the cheapest way to help residents find what they need and transact with the council may help.</p><p>It can also help people find alternative options and manage their expectations if a particular service is at capacity and there is a long waiting list.</p><p>Basing it in what they’re trying to achieve can help you frame your proposal in a way that is valuable to them. It can help them understand why you’re making that suggestion and increase the chances of them embracing it. You’ve asked them for their expertise about the service and you’ve shared your expertise in accessible content design.</p><h4>Slide 22: Involve them in the work.</h4><p>Having someone come in and tell you how to write about your work or refuse to publish something you’ve asked for is pretty disempowering and it can feel quite patronising.</p><p>By involving them in the work, you can avoid them feeling that change is happening to them and instead help them see the part they’re playing in improving experiences and interactions for residents. We can’t do the work without them and it’s important to acknowledge that.</p><p>We’ve recently been working with a subject expert and we ran a workshop to understand what they do and what it helps residents achieve.</p><p>We didn’t talk about content design, even though principles of ‘good services’, user stories and user focussed design were the reasons for running the workshop.</p><p>We even stopped discussions about content outputs. We wanted to stop people thinking “I want this info on this page” and start thinking about what residents need and how they help them achieve it. This helped them rethink how they think of content and gave us a better understanding of what information the resident needs.</p><h4>Slide 23: Quote from a colleague</h4><p>That colleague later said this:</p><p>“I don’t know what a content desig ner is and I probably don’t need to. But just from working with you I’m starting to understand what a content designer does”.</p><p>I didn’t set this up, it was just very timely that she said this when I was planning for this talk. I think it really sums up the benefit of not talking about content design. It just feels a lot more inclusive and less intimidating to people who are new to working with digital disciplines.</p><p>They bring their service expertise, we bring the digital skills but we just need to understand how we can work together to get the right information out there.</p><h4>Slide 24: <strong>Show them what good content looks like</strong></h4><p>You can tell people how to create good content or what we shouldn’t do. But telling them why you don’t do those things may not help. They may need to visualise what your solution will look like or see how people interact with it.</p><p>For example, if they want FAQs or a page with lots of graphics or interactive elements, they may need to see someone interact with it to understand why a basic information page works better</p><p>It’s easy to get a false impression that everyone is happy with the work. You’ll be working together in Word docs, all agreeing on the content and then you’re about to go live and they see it and go ‘Oh I wasn’t expecting it to look like that’.</p><p>Showing them prototypes and mock ups of what you’re imagining will encourage those conversations earlier. Knowing what they want it to look like can help you work out how you can show them what you’re proposing works better. Or find a compromise that works for both of you.</p><p>It’s very hard to argue with user testing that shows that people can’t interact with certain elements on the page or see how confused or how long it takes them to find what they need.</p><p>Again, you can do this without talking about content design or in this case user research. You can just show them videos of how people are interacting with it so they can see for themselves what the issues are without needing to explain the technicalities and jargon associated with the issues. This is particularly useful with accessibility. We all know that the WCAG guidelines can be pretty daunting, if they don’t have to know the requirements, then we shouldn’t try to make them. We can just say ‘this person missed all of this information because the information is on an image they can’t see’.</p><h4>Slide 25: <strong>Talk to them in language they understand</strong></h4><p>We’re often talking to subject experts and explaining why we use simple language and why we remove internal words, team names and jargon.</p><p>Imagine saying “we can’t use the acronym SEND in our IA because people may not know what it stands for”.</p><p>So many of us are guilty of using our own internal language and jargon when talking to subject experts. It’s pretty hypocritical and it can be pretty intimidating. Just like we would simplify legal language so people aren’t put off from reading it, using our own design jargon when talking to subject experts may put them off from listening to what we’re saying. It puts up a barrier between you and the service team and that can really isolate people and prevent collaboration and shared understanding which is key in building relationships.</p><h4>Slide 26: You can stop talking about content deisgn by doing content design</h4><p>One final thought I’d like to leave you with is that the best tip for stopping yourself from talking about content design is to do content design.</p><h4>Slide 27: Apply a content design approach to stakeholder management.</h4><p>Step 1 of content design: Do research, find out what subject experts want and need and why</p><p>Step 2: Gather needs: Find out what they do and what messages or services they need people to know about and be able to access</p><p>Step 3: Journey mapping: Find out how their service works, the processes they follow and the different channels they use to talk to residents. Use that to set more realistic expectations for residents interacting with the service</p><p>Step 4: Use language they use. Avoid content design jargon so they understand what you want and need from them</p><p>Step 5: Pair writing: Work together on the content and bring them along in the decision-making process so they understand what you’re doing and why</p><p>Step 6: Share and iterate: Get feedback from them about how they found working with you, get them to talk about how you helped them. It means a lot more from one subject expert to another than from a content designer talking about their own work. And use that feedback to shape how you work with the next subject expert</p><h4>Slide 28</h4><p>That’s it from me, I’d love to hear what other people think. Do you completely disagree with this approach? Have you tried something similar? Did it work or does it not work for you? I’d love to hear a bit more.</p><h4>Questions and answers</h4><p>Question: How do you tend to know when to persevere with something, when to switch tactics or when to say okay we’re gonna have to park this for now?</p><p><strong>Answer</strong></p><p>Knowing the people first before going into these conversations helps.</p><p>The best advice I ever got was from my first manager, I was having a lot of back and forth with a team and the email chain felt very aggressive. I remember showing him and going “what do I do with this they’re not listening to me”. And he goes “have you spoken to them? Have you walked over there and spoken them?” And I was like “No”. And we went over and I met them and they were just the loveliest people and it was absolutely fine and we worked it out in about five minutes.</p><p>So having a basis of a relationship when you start those conversations helps and when you go into those conversations knowing in your head what your sticking point is. So for us it tends to be accessibility or if something is completely not usable then there tends to be a bit of a a stopping point.</p><p>We’ve had meetings in the past where we’ve gone in and reached a stalemate. They’ve explained their side, I’ve explained my side and we sort of know that we’re not going to agree and we sort of said “should we should we take a break here and bring this back to a group and we’ll talk through it, we’ll mock something up we’ll bring it back and then we’ll we’ll talk it through. That was about FAQs typically, still FAQs 10 years on.</p><p>But yeah just having a bit of a break and knowing where you need to stop. It’s not helping either of you and you’re just going to get more and more frustrated and that could damage relationships if you start getting defensive. Also knowing when to to stop for yourself like “okay I’m rising to this a bit too much” and then actually stepping back and thinking okay what is it that matters to them, why are they upset. Oh they’ve got a deadline that’s really important that they’re really worried about missing it, okay so if we talk to their manager and say is it okay for us to push this deadline back a week you know their manager says yes suddenly their stress is completely gone.</p><p>So I think it’s understanding why you’re getting heated about it and why they’re getting heated about it and then working out how you can compromise and move forward together. Just making sure that we remember that we’re both humans trying to do our best jobs</p><h4>Question 2:</h4><p>Do you think that the term content designer just isn’t descriptive enough in itself? Do you see some shift away from calling it content design?</p><p><strong>Answer</strong></p><p>I think it’s a tricky one I love being a Content designer and I love the name of it. I think it’s the design element that I like having in there because I think it opens it up.</p><p>Subject experts don’t really know what it is, even if it was Content Writer or UX Writer. I don’t really think they need to know. I think it’s the same with other people’s roles, we have so many team names, especially at a council and team name acronyms that confuse people.</p><p>I wouldn’t change the name but I wouldn’t use it that much with a service team. I wouldn’t say “Oh I’m doing content design I’m a Content designer”. I would just say “Oh I help you make information easy to find, use and understand.</p><p>I like having the content designer title because I think the designer element in it makes it easier for like product designers and other people like that to to remind themselves to invite you to the design stuff.</p><h4><strong>Question 3:</strong></h4><p>Do you work with service designers in your organisation? How do they fit in?</p><p><strong>Answer</strong></p><p>Yeah so we have service teams so those are the people who run the council services. Then we have service designers within our product team as well. So depending on what type of project it is we would have service designers involved.</p><p>I think that’s kind of where I get this approach from. I’ve learned a lot from service designers. We had a meeting in the past with someone from I think the British Heart Foundation about how they’ve started renaming services. They did these workshops where they went in and said “okay what what do you help people achieve what they want” and they basically worked through it that way to help people understand what services are.</p><p>I’ve really taken that approach in how I do relationships because I feel that was a really nice way of breaking down. It makes it clear it’s not the teams that matters and it’s not the outputs, it’s how do we communicate what is available to people.</p><p>Working with service designers is such a privilege because you can learn so much from them and I’m aware that not everyone has service designers to work with. It gives you that extra richness and context about how the service works behind the scenes. It makes it much easier for us to do good content design as well because they tend to be the bridge between you and the service and they understand the processes better and also understand user centered design so they can help bring you together.</p><h4>Question 4:</h4><p>We do training at the University of Edinburgh for staff who work on websites and we debated whether to put content design in the name of the training. Have you encountered that problem or anything similar to it?</p><p><strong>Answer:</strong></p><p>We’ve sort of said “these people will be working on your project with you” and content design is there but people don’t really know what that means. It just creates a bit of a barrier of people being like “I don’t really know what that means” but we don’t really use content designer more widely outside of job ads.</p><p>We’re trying to help people across the organisation understand how to create better quality content or user focused content. We’re not saying ‘content design’ for that, we are thinking of you know ‘How to write for residents’ training for service team so it’ll be a combination of us working with the Comms Department to say “this is how we communicate on the web, this is how you can write clearly in your letters to residents, phone calls’. So we are trying to come up with some training internally to spread the knowledge of good quality content without saying content design because they aren’t content designers but everyone can help create better content if they understand the principles of it.</p><figure><img alt="Illustration of two people standing on either side of computer screen with the word ‘Content’ on the top of a webpage" src="https://cdn-images-1.medium.com/max/1024/1*rh3UvqvwBJ8jDs4Av9P4WA.jpeg" /><figcaption><a href="https://www.freepik.com/free-vector/people-with-digital-content-creation-concept_3226111.htm#fromView=search&amp;page=5&amp;position=16&amp;uuid=51c4856d-2b63-4fb8-aef8-2dee6118e224">Image by rawpixel.com on Freepik</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4bdf0b2cac7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving our content allocation process]]></title>
            <link>https://medium.com/@alysiamarieannett/improving-our-content-allocation-process-8209435883c4?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/8209435883c4</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[local-government]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Fri, 08 Mar 2024 18:02:29 GMT</pubDate>
            <atom:updated>2024-03-08T18:06:37.470Z</atom:updated>
            <content:encoded><![CDATA[<p>In my last blog I talked about how we’re <a href="https://medium.com/@alysiamarieannett/improving-how-we-manage-website-content-requests-4ebb6063d7cc">improving our website request forms</a>.</p><p>This will help streamline some requests but we also need to improve the way we prioritise and allocate requests.</p><h3>How our content designers do website requests</h3><p>Our content designers work on a rota. Two content designers will be on each week, with a one or two week gap off the rota.</p><p>Some requests are small and fit easily into our current website request process. These are easy to pick up and action in the 1 day a week each person on the rota is allocated.</p><p>However, other pieces are more complex. They may:</p><ul><li>require content and development work</li><li>need scoping to ensure we’re fixing a real problem for users</li><li>be large content projects. For example, to design multiple new pages of content for a new section or to redesign all the content in a section</li><li>require meetings and negotiation between in-house digital colleagues and external agencies, consultants or providers for products procured by service teams</li></ul><h4><strong>Challenges</strong></h4><ul><li>Bigger content work can get lost in the request system or during the handover process (which happens in a Teams chat)</li><li>Content designers don’t know which pieces to prioritise over others</li><li>Hard to balance bigger website requests with large product work (content designers on the rota do 1 day of website requests, 3 days of digital product work, 1 day of learning and development and team time)</li></ul><h3>A content roadmap</h3><p>One way we’re looking to address this is to give content designers better oversight of those large requests.</p><p>We want to do this without duplicating tickets and conversations.</p><p>For this reason, we’re using a Trello board to:</p><ul><li>show the running order of content improvements for the new website</li><li>capture the big requests that have come through our website request process</li><li>allocate larger project work to the content designers who have capacity to work on them</li><li>capture guidance and insights we need to document to strengthen our content design community of practice and upskill others across the organisation</li></ul><p>This will allow us to:</p><ul><li>see if we can fit larger requests into work already scoped and allocated in our digital roadmap</li><li>have better oversight of large tickets that can hang around or get lost in the website request system</li><li>better celebrate the work that our content designers are doing outside of product work</li></ul><h3>Trialling the roadmap</h3><p>So far, it’s helping us more evenly split large requests amongst our content designers.</p><p>It is also helping us see how much work is coming in.</p><p>It has also helped me realise that we need to push back on some of these requests. Some are largely ideas from service teams and there may be better solutions that we should be suggesting instead.</p><p>Some ideas may be suggested but may not have the right level of sign off from senior leaders in the directorate. It’s important that we check these with senior leaders to ensure they help to meet the outcomes set out in each teams’ strategy. This will also help ensure we’re prioritising the work that has the largest impact.</p><h3>Next steps</h3><p>We’ll continue to trial using this to allocate content work and will update to share how it’s going.</p><figure><img alt="A whiteboard where someone has sketched out a product roadmap." src="https://cdn-images-1.medium.com/max/1024/1*wJAcQpCUos4a5YJP4_1snA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8209435883c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving how we manage content requests for royalgreenwich.gov.uk]]></title>
            <link>https://medium.com/rbg-digital/improving-how-we-manage-website-content-requests-4ebb6063d7cc?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ebb6063d7cc</guid>
            <category><![CDATA[website-maintenance]]></category>
            <category><![CDATA[our-work]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[local-government]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 17:10:34 GMT</pubDate>
            <atom:updated>2024-12-20T10:23:07.438Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving how we manage website content requests</h3><p>In my last weeknote I started writing about how we’re reviewing and streamlining our content ops but realised there was too much to talk about.</p><p>So here’s more about our current process of managing content requests and how we’re looking to improve it.</p><h3>Our current process</h3><p>We started doing general website requests at the start of 2023. Before then, colleagues would email a shared mailbox to ask for changes which would go to the Comms team.</p><p>Holly led on revamping this process and we’ve been using a request system that we share with the technology team for over a year now.</p><p>We have our own section for websites that our content designers and developers look after.</p><p>The requests we get are much more detailed than before due to the forms we use. But we know we can improve this further.</p><p>There are a few ways we’re looking to improve this process.</p><ol><li>Improving the forms for our colleagues and team including clear communication and expectation setting</li><li>Better oversight, prioritisation and allocation of requests</li></ol><h3>Reviewing our website request forms</h3><p>We know from our regular retros that we’re not getting requests through in the best way.</p><p>There are 4 main problems we’re looking to address.</p><h4>1. People are using the wrong forms</h4><p><strong>Challenge</strong>: People don’t use the different forms we have for their different types of requests.</p><p>We have the following forms:</p><ul><li>Get content advice (for when someone wants something but isn’t sure if it is feasible or where to get started)</li><li>Create new content</li><li>Update web content</li><li>Get a form report</li><li>Update a form</li><li>Report a website or intranet problem</li></ul><p>In an ideal world, we’d have one form with logic that would allow us to triage requests. Unfortunately, the system we have doesn’t allow us to do this. So we need to find new ways to link people across to the relevant forms where we can or merge similar forms together.</p><p>We think we’ll end up:</p><ul><li>merging the ‘Get content advice’ and ‘create new content’ together.</li><li>expanding these to include ‘new website features’ — we get lots of requests for ‘portals’ that we’d like to show we have alternative solutions for</li><li>keep the separate ‘update web content’ form but include ‘update a form’ within it as often you need to update the form and the content anyway</li></ul><h4>2. People request changes in different ways.</h4><p><strong>Challenge</strong>: It can be hard to tell what needs changing</p><p>In our forms, we ask people to tell us about a change in a specific way so we can easily tell what needs to happen.</p><blockquote><em>Change from: [Existing content]<br>Change to: [New content]<br>Reason: [Why the change is needed]</em></blockquote><p>However, we still get this information in different ways and the best way depends on how much needs changing.</p><p>At the moment some people:</p><ul><li>follow the template above (mostly for small changes) — 5/5 easy to follow</li><li>attach a word document with changes highlighted — 5/5 easy to follow</li><li>attach a word document without changes highlighted — 3/5 takes some time and has a risk of missing changes if the doc is large</li><li>attach a PDF of the changes — 1/5 we can’t copy any info from it so have to type everything from scratch. Also PDFs make our eyes water</li></ul><h4>3. Unclear prioritisation and realistic timescales</h4><p><strong>Challenge</strong>: We get requests with little to no advance notice</p><p>Although we have a brief explanation of how we prioritise requests in the form, people still send us requests that need to go live the same day.</p><p>This can force us to drop work, double check urgency with the service or push back on the service’s deadline.</p><p>We know this will always happen to some extent. But we’d like to make the prioritisation clear and set more realistic expectations.</p><p>Part of this is improving our own priorities. We’re currently working on a roadmap and Trello board to give better oversight of work and help us make better, more strategic decisions around what work to prioritise.</p><p>Another part of it is clearer communication with people when they do request something last minute. We need to get better at saying ‘not yet’ and negotiating timescales with people to identify what really does need to be met.</p><p>We don’t see something as a priority if we get a request through last minute without advance warning. But we will if there’s been an urgent policy change and the service had no advance warning.</p><h4>4. It’s not clear why the content is needed</h4><p><strong>Challenge</strong>: We can’t identify the user need from the request</p><p>We also include a field in the form to understand what is needed.</p><p>This includes:</p><ul><li>a summary of what they need</li><li>where it is needed such as the council website or intranet</li><li>what the content will help people do</li></ul><p>Sometimes even after filling this in, it is still not clear why the content is needed. This means we have lots of scoping chats which take up a lot of time.</p><p>We’ll always need these chats and they’re a valuable way to explain why we’re asking the questions we’re asking, especially for new content. It’s also a nice way for them to be able to put a human face to the people responding to their requests. But we’d like to get that information up front for smaller requests.</p><p>Our content designer, Nicole Sebestian is going to be reviewing and improving our website request forms based on these challenges and we’ll share back what we learn on the <a href="https://medium.com/rbg-digital">Royal Greenwich Digital Blog</a>.</p><figure><img alt="Our current update content request form with lots of sticky notes with ideas on how people use it and potential improvements" src="https://cdn-images-1.medium.com/max/948/1*hhH8xfd87STRyzDucsYfBA.png" /><figcaption>Reviewing one of our current request forms</figcaption></figure><h4>Tell us how you manage requests</h4><p>If you are doing anything similar, we’d love to have a chat about it.</p><p>You can reach out to me by emailing alysia-marie.annett@royalgreenwich.gov.uk</p><h3>Next steps</h3><p>We know that the request forms won’t fix everything.</p><p>We also need to look at our internal processes to improve the way we prioritise and allocate requests.</p><p>In my next blog post, I’ll write about <a href="https://medium.com/@alysiamarieannett/improving-our-content-allocation-process-8209435883c4">how we’re trialling a new way of allocating content work</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ebb6063d7cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rbg-digital/improving-how-we-manage-website-content-requests-4ebb6063d7cc">Improving how we manage content requests for royalgreenwich.gov.uk</a> was originally published in <a href="https://medium.com/rbg-digital">Royal Greenwich Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote 2 of 2024]]></title>
            <link>https://medium.com/@alysiamarieannett/weeknote-2-of-2024-9a9aa5c34829?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a9aa5c34829</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[local-government]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 09:20:52 GMT</pubDate>
            <atom:updated>2024-02-05T09:20:52.000Z</atom:updated>
            <content:encoded><![CDATA[<p>The last few weeks I’ve been in the world of:</p><ul><li>product launch prep</li><li>streamlining our content operations</li><li>recruitment</li></ul><figure><img alt="A grey british blue cat looking up seriously. She sits with one elbow on a leg perched like she’s a regular at the bar." src="https://cdn-images-1.medium.com/max/1024/1*zZXVZMLNVEkvs0bGeJG1Lw.jpeg" /><figcaption>Willow the Content Cat thinking about her to-do list</figcaption></figure><h3>Prepping for the launch of the Greenwich Community Directory</h3><p>At the end of the month we will be going live with the first release of our Greenwich Community Directory. Starting with the ‘support for adults’ section.</p><p>It’s a long time coming but we’re also super excited for it to become real and for people to start using it.</p><p>We don’t have full control over the current directory so it’s had a Beta banner on it reading ‘This is a new website’ for about 100 years. So I can’t wait for people to realise we genuinely have a new directory that is easier to use, accessible and inclusive.</p><p>This week we’ve been trying to work out what we’ve still got left to do. Thankfully, we have Alex (our product manager) and Melanie (our deliver manager) to wrangle the team to make sure we’re not missing anything and forcing us to agree a go-live date.</p><p>From the content side, I’m mostly reviewing the footer pages and making sure we’re using legally compliant privacy policies, accessibility statements and disclaimers. Somehow I’ve managed to get this far in my life without ever having written one from scratch so it’s an important one. I typed interesting but I’d by lying if I said I read cookie statements for fun.</p><h3>Streamlining our content operations</h3><p>We’re far from perfect when it comes to content ops.</p><p>We started doing general website requests at the start of 2023 and have come a long way from people emailing a shared mailbox to ask for changes.</p><p>We do have a full process in place but it’s time to review and improve it.</p><p>Holly set up our process and has been rallying us together every month to review how it’s going so we can make improvements.</p><p>We also have had really useful insights from Alice and Nicole, our two newer content designers on the process. Coming in fresh means they’re better able to spot what feels a bit sticky and what could me smoother.</p><p>So this month we’ve been focusing on reviewing:</p><ul><li>our website request forms</li><li>how we approach price changes for the new financial year</li></ul><p>I started writing about what this work looks like but it’s too much information for one blog. I’ll write a dedicated post on how we’re reviewing our content operations next week.</p><h3>Things I’m watching, reading and listening to</h3><p><strong>The Advice Trap by Michael Bungay Stanier</strong></p><p>I’m trying to get better at coaching so I’ve been reading The Advice Trap. It’s easy to digest so I read it really quickly but I’m keeping hold of it to complete the exercises at the end of each section.</p><p><a href="https://www.mbs.works/advice-trap-book/">The Advice Trap by Michael Bungay Stanier</a></p><p><strong>Global content design, hosted by Sarah Winters</strong></p><p>I love a podcast so this week I’ve started Global Content Design. It is really interesting to see where content design is and what it looks like across the world.</p><p><a href="https://contentdesign.london/blog/global-content-design-podcast-launch">Global Content Design podcast launch</a></p><p><strong>Someday, Maybe by </strong><a href="https://www.goodreads.com/author/show/21580036.Onyi_Nwabineli"><strong>Onyi Nwabineli</strong></a></p><p>Non work related, this is the book I’ve been reading on my commute to the office.</p><p><a href="https://www.goodreads.com/en/book/show/59952176">Someday, Maybe</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a9aa5c34829" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote 1 of 2024: A [Fri]day in the life]]></title>
            <link>https://medium.com/@alysiamarieannett/a-fri-day-in-the-life-bb18591e06fc?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb18591e06fc</guid>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[adayinthelife]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 17:14:17 GMT</pubDate>
            <atom:updated>2024-02-02T16:24:52.754Z</atom:updated>
            <content:encoded><![CDATA[<p>Today has been one of those days that shows a bit how my days have changed since becoming a content lead. It’s a bit of lots of little things.</p><h3>My Friday</h3><ul><li><strong>7.30am: Breakfast and morning walk</strong></li><li><strong>8:45am: Plan for the day ahead</strong></li><li><strong>9am: Recruitment</strong>. Reviewed the notes and comments from our interview panel for our content design vacancies and booked in chats with a few applicants</li><li><strong>9:30am: Standup</strong> for the new website project</li><li><strong>10am: Meeting to gather information about a new system. </strong>Mark (Lead Developer) and I met with a colleague and a provider for a system to deal with Tree enquiries that the service are using. We talked through digital and accessibility requirements we’d need before we start using it and came up with next steps to ensure the journey to the system is smooth and alternative options for people who are digitally excluded.</li><li><strong>11am: Digital and Customer Services whole team meeting</strong></li><li><strong>11:30am: Tea break and meeting prep.</strong> Checked what was on the agenda for our content crit and quickly prepped a retro for 15 minutes time</li><li><strong>11:45am: Retro</strong> on how to approach updated for the price changes for the new financial year. Wrote up actions and added them to our business as usual Trello board so we can assign ourselves to each one</li><li><strong>12:45: Lunch. </strong>Had a sad cheese roll and started reading ‘The Advice Trap’</li><li><strong>1:30pm: Website request scoping.</strong> Met with Mark, Lead Developer to scope big website requests and had my brain fried talking about an exciting proof of concept to streamline price changes to be updated across systems, forms and content pages</li><li><strong>2pm: Sat in on a content proposal session </strong>run by Laura and Nicole to share their findings from a content review for Births, Marriages, Deaths and Citizenship. Mostly to hear about the service’s priorities as I’m planning to collate a list of subject experts alongside their priorities that we can use to make our interactions with them more relevant to them</li><li><strong>2:45pm: Shared some feedback</strong> with the team about the session</li><li><strong>3pm: Asked for help</strong>. Reached out to product managers for a crit session on a content roadmap I’m working on</li><li><strong>3:30pm: Monthly blog drop in</strong>. Wrote this weeknote whilst waiting to see if people had any blogs ideas or drafts they wanted feedback on</li><li><strong>4pm: Wrote assumptions to test our new Health and Adult Social Care content with residents</strong></li><li><strong>4:30pm: Prepped for first monthly catch up with Comms. </strong>We’re setting this up<strong> </strong>to align on our strategies, find overlap in our work and opportunities to connect content across channels</li><li><strong>5pm: Finished this weeknote and logged off</strong></li><li><strong>6:30pm: Body balance class</strong> to stretch out my limbs so my body doesn’t fuse into the shape of my chair</li></ul><figure><img alt="A grey British Shorthair cat sits in front of a copy of ‘The Advice Trap’" src="https://cdn-images-1.medium.com/max/1024/1*gDU98sw6X0hohM3v8lfNaA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb18591e06fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2023 in reflection]]></title>
            <link>https://medium.com/@alysiamarieannett/my-2023-in-reflection-6f778c042f86?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f778c042f86</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[resolutions]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Fri, 05 Jan 2024 16:20:34 GMT</pubDate>
            <atom:updated>2024-01-05T16:20:34.368Z</atom:updated>
            <content:encoded><![CDATA[<p>This year has definitely been another one full of challenges.</p><p>It’s an exciting time as we spot more opportunities to extend and improve our content design practice at Greenwich and build better relationships.</p><p>Here are things I’m proud of, things I’ve learnt, what I plan to leave behind and my wishes for 2024.</p><figure><img alt="Paper with ‘New Year Resolutions’ written on it above a pen." src="https://cdn-images-1.medium.com/max/1024/1*NHL1bnpUKGfS5zzIYIkAMQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Tim Mossholder</a> on <a href="https://unsplash.com/photos/white-printer-paper-on-brown-wooden-table-3I3WVoA-Gks?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><h3>Challenges we overcame</h3><p><strong>Website requests</strong> — Got through our first year of developers and content designers doing all website content requests. We’ve got a long way to go but it’s been a great way to understand the current content landscape and gradually bring people along to understanding how we work and how to create clear content with a clear purpose.</p><p><strong>Team change</strong> — We got through lots of team changes and were honest and open about what we were doing, how we were feeling and what we all needed to do to support each other.</p><h3>Things I’m proud of</h3><ul><li>Wrote 12 personal blog posts</li><li>Got our Royal Greenwich blog up and running</li><li>Got (more) comfortable sharing my work and self promoting. My post about ‘<a href="https://medium.com/p/5aae1771209f">Adapting processes to build better relationships</a>’ got over 1.5k views which is a good reminder when you think no one cares about what you have to say</li><li>Spoke to loads of people for Health and Adult Services content and started building relationships with people across the service</li><li>Took on a new challenge of content design lead</li><li>We welcomed 2 new content designers taking the content team up to 6</li><li>We started raising awareness of the value of content. When presenting to heads of service we were told ‘We trust you, you don’t need to pitch the why, we just want to hear who you’ve spoken to and who has been involved’</li><li>We saw a few different products go live and have 2 more going live in early 2024</li></ul><h3>Things I’ve learnt this year</h3><p><strong>Be clear what you can and can’t support people with<br></strong>I can’t change people’s situations but I can help reduce pressure at work or share guidance. It’s okay not to be able to fix everything. Most people don’t want the sorrys or sympathy, they want practical guidance. It’s better to admit when you can’t help with something and point them to people or services that can.</p><p><strong>My weaknesses are my strengths<br></strong>I was always told being quiet would hold me back. But listening to others and reading the room and assessing the situation is a strength. It has helped me learn what stage people are at, what their concerns are and how I can work with them better to bring them around to change in a way that is fair, relevant and valuable to them.</p><h3>What to let go of</h3><p><strong>Out: </strong>Waiting for permission or sign off<br><strong>In: </strong>Telling people what we’re doing, why and giving them clear oversight throughout</p><p><strong>Out: </strong>Worrying about treading on other people’s toes<br><strong>In:</strong> Making connections and giving people the opportunity to get involved when they have capacity and an interest in the task</p><p><strong>Out:</strong> Only asking people what support need from me<br><strong>In:</strong> Being direct and clear about what I need from other people and how that helps me better support others</p><h3>Wishes for 2024</h3><p>Leadership (in the formal sense) is new to me. So I want to really work on leadership skills and do a better job at understanding what holds people back and what they need to overcome those challenges. Part of this is definitely leaning more into coaching and holding back from offering advice.</p><p>Make better connections across directorates. We want them to know and trust us to help meet our shared outcomes. This will also give our content designers more agency to improve content.</p><p>Give more structure and oversight of content opportunities so we can prioritise work better and be more strategic and less reactive.</p><p>Strengthen our community of practice and do a better job of recording content decisions and lessons so we can reuse them across projects and be more consistent.</p><h4>My word for 2024: Clarity</h4><h3>Top reads of 2023</h3><p>It’s so lovely to see so many people writing about their work. I read so many great posts this year but here are some that have influenced me and that I’ll go back to for future work and some that just felt super relatable.</p><ul><li><a href="https://lapope.com/2023/12/09/content-modelling-and-structured-content-the-basics/">Content modelling and structured content: the basics | Lauren Pope</a></li><li><a href="https://joulee.medium.com/the-looking-glass-chains-of-assumptions-21821b0ce5e2">The Looking Glass: Chains of Assumptions</a></li><li><a href="https://medium.com/openclassrooms-product-design-and-engineering/how-we-built-a-priority-framework-for-content-designers-7b8d73829845">How we built a priority framework for Content Designers</a></li><li><a href="https://medium.com/flo-health/empowering-users-with-knowledge-how-we-transformed-content-ux-to-better-serve-user-needs-b9e97feb7c01">Empowering users with knowledge: How we transformed content UX to better serve user needs</a></li><li><a href="https://medium.com/catbird-content/why-i-train-designers-to-write-a779f62c1ebc">Why I train designers to write</a></li><li><a href="https://medium.com/indeed-design/content-design-lessons-from-the-crib-05961bd52ef4">Content Design Lessons From the Crib</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f778c042f86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Separate your self worth from your work]]></title>
            <link>https://medium.com/rbg-digital/separate-your-self-worth-from-your-work-bf8fb1f1b907?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf8fb1f1b907</guid>
            <category><![CDATA[self-worth]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Fri, 15 Dec 2023 16:47:51 GMT</pubDate>
            <atom:updated>2023-12-18T11:40:05.226Z</atom:updated>
            <content:encoded><![CDATA[<p>This is inspired by a talk from <a href="https://medium.com/u/5d4c86d0175d">Lauren Pope</a> called Everything, Everywhere All At Once hosted by <a href="https://contentdesign.london/content-club">We Are Content Club</a>.</p><p>It also comes from conversations I’ve had with other content designers and my own reflections.</p><blockquote>You don’t need to get better at content, you need therapy</blockquote><p>One of the biggest skills of designers is attention to detail. We sweat over the small things and it helps make the work better. But it also makes us highly critical, mostly of ourselves and our work.</p><p>We care a lot about our content because we know the value it brings and how the smallest things can make a big difference to users. But this can be exhausting. It makes us want to get it right.</p><p>We want the content to be great and it can be frustrating when things stand in the way of that. Like tricky stakeholders, bad systems or processes. But sometimes we cannot do everything we’d like to do to make the content better.</p><p>Then we kick ourselves for it and question ourselves.</p><blockquote>I shouldn’t have compromised on X</blockquote><blockquote>I didn’t spend enough time on research</blockquote><blockquote>I didn’t get all my questions answered</blockquote><blockquote>I couldn’t influence that person to change X</blockquote><p>But we need to be kind to ourselves and the people we work with and work out what we can and can’t do. It’s important to prioritise things we can influence, things that add value and our team health.</p><figure><img alt="Kit and Lingjing presenting about ‘Change’, they sit in front of a slide reading ‘We are in the business of change. We expect everyone to provoke change and create condition’." src="https://cdn-images-1.medium.com/max/1024/1*PW6IbX8HVv2aCATQKty7ZA.jpeg" /><figcaption>Kit and Lingjing presenting about Change at our Product team away day</figcaption></figure><h3>Things to remember to help separate your self worth from your work</h3><h4><strong>Not having influence isn’t a reflection on how good of a content designer you are</strong></h4><p>You can be the best content designer in the world and still be told ‘no’. This has nothing to do with your ability.</p><p>Instead of beating yourself up about not being able to influence someone, focus on areas you can influence and put your energy there instead.</p><p>There are also times when we can improve content but improving content doesn’t change the demand or processes behind a service.</p><p>Of course, when we’re able to work with service designers to completely improve everything, we’re likely to feel more satisfied with our work. But this is not always possible. Sometimes we just have to make some tweaks and move onto the next thing.</p><h4><strong>Don’t let your ego get in your way</strong></h4><p>This isn’t a negative or a selfish thing. We naturally all want to make our work as good as possible. It’s hugely rewarding to look at a piece of your content and feel like you’ve done a great job.</p><p>But it also siloes us from others if we start seeing our colleagues as barriers to being pleased with our own work. Or by thinking our work and our time is more important than other people’s.</p><p>This job is hard, but all jobs are. We all have our own priorities, our own deadlines and our own projects. We’re all trying our best and it’s important not to focus on the set backs.</p><p>It’s worth reframing what you see as valuable work.</p><p>Instead of focusing on:</p><blockquote>“This content would’ve been better if X had let me rewrite that paragraph”</blockquote><p>Ask yourself:</p><blockquote>“How have I build relationships and communicated the value of what we do?”</blockquote><blockquote>“Where have I compromised for the benefit of relationships with service teams?”</blockquote><p>There is more to our work than good content outputs. Building strong relationships with teams will open doors to working with them in future.</p><p>You can compromise on things whilst still explaining how you can make further improvements in future phases.</p><p>Sometimes you just need to ease people into change one small tweak at a time.</p><h4><strong>Celebrate the small thing</strong></h4><p>We are working with lots of content that needs a lot of work. But we can’t always improve everything all in one go. This is often due to:</p><ul><li>service teams being over capacity and not being able to dedicate time to work with us</li><li>conflicting priorities</li><li>complicated systems, services and processes that need a full transformation</li></ul><p>Instead of asking:</p><blockquote>“Is this work good enough?”</blockquote><p>Ask yourself:</p><blockquote>“Is this content better than it was?”</blockquote><p>Any little changes we’re making still have a big impact. Just changing a broken link or removing some out of date information is a huge win.</p><h4>Lean into your communities to avoid cynicism</h4><p>Cynicism can damage your self worth and your work.</p><p>We’re all going to feel negative at times and that’s okay. That’s why you should lean on your communities to talk about challenges, give each other advice and have a bit of a rant when you need to.</p><p>But we need to make sure that cynicism doesn’t seep into our work and our interactions with subject experts.</p><p>We need to acknowledge what could’ve gone better and think of how to approach it differently next time. This is far more useful than blaming people, things or systems.</p><h4>You’re more than your work</h4><p>You are a whole human being. Work is just one part of your life.</p><p>The work you do in the week does not change who you are as a person. It’s important not to let any doubts you have from your work seep into your daily life.</p><p>Do the work as well as you can then shut it out at the end of your day.</p><p>It’ll benefit you, anyone you live with, your work and your colleagues.</p><h3>What I’m reading and listening to</h3><ul><li><a href="https://lapope.com/2023/11/02/prioritisation-for-content-teams-a-guide/">Prioritisation for content teams: a guide | La Pope</a></li><li><a href="https://brenebrown.com/podcast/immunity-to-change-part-1-of-2/">Brené with Lisa Lahey on Immunity to Change, Part 1 of 2</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf8fb1f1b907" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rbg-digital/separate-your-self-worth-from-your-work-bf8fb1f1b907">Separate your self worth from your work</a> was originally published in <a href="https://medium.com/rbg-digital">Royal Greenwich Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first full month as Content Lead]]></title>
            <link>https://medium.com/rbg-digital/weeknote-7-my-first-full-month-as-content-lead-e0ccc419da98?source=rss-85ae32948866------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0ccc419da98</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[leaderhip]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Alysia-Marie Annett]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 16:28:49 GMT</pubDate>
            <atom:updated>2024-05-24T10:08:10.601Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently became Content Lead at Royal Greenwich and I’ve been navigating the change in responsibility since then.</p><p>I spent my first couple of weeks chatting to people to understand how they were feeling, what they wanted from me and answering any questions. This helped me work out what I need to focus on and what the team need most. I’m still juggling my projects and the new responsibilities so I’m grateful to be in a team that is so capable and who are being patient with me.</p><p>I’m writing this with a headache and a cat that is sitting on my back and biting the back of my ponytail so hopefully this is coherent.</p><figure><img alt="Dory, a blue fish from Finding Nemo looking confused and asking ‘Who am I?’" src="https://cdn-images-1.medium.com/max/600/1*6QjAX0hGpgSQ1uscLL7cgw.jpeg" /></figure><h3>What’s been good and what’s been hard</h3><p>Here’s the good stuff:</p><ul><li>Getting invited to lots of important conversations and chances to open more doors to content design</li><li>Opportunity to think big about content, not just on projects and across projects but across the organisation</li><li>Agency to help others make decisions and ensure the voices of our content designers are heard</li><li>People supporting me and others through changing roles and project responsibilities</li></ul><p>Here’s the hard stuff:</p><ul><li>Lots of meetings and little time to do hands on content work</li><li>Lots of context switching but a need for big scale strategic thinking</li><li>Lots of big decisions that could impact more than just my own work</li><li>Lots of juggling change both for me and for the rest of the content designers and teammates on my projects</li></ul><p>Yes the good stuff and the hard stuff are the same.</p><p>Just like our biggest weaknesses are often the flip side of our biggest strengths.</p><h3>What I’ve learnt so far</h3><ol><li>I need to step back from some of the detail so I have time and clarity to see the wider picture and make connections</li><li>I need to carve out more time to focus on our community of practice</li><li>I need to start saying no or at least ‘not yet’ to more things</li><li>I need to reign in some of my big ideas to focus on what we can and need to do right now</li><li>I need to give the team more time and agency to do the work and get less involved in the day to day content work</li><li>I need to give less advice and listen more, especially to new or lesser heard voices</li></ol><h3>What I need to prioritise</h3><ol><li>Building relationships with people who can open doors and help advocate for content design. Particularly senior leadership and Comms</li><li>Our content design community of practice sessions and how we can get the most value out of them</li><li>Thinking time</li><li>Defining roles and responsibilities. With lots of change in the team, we need to revisit our capabilities and ensure people know what to expect from new roles. We need to give people a chance to do more of what they want but in a way that is fair based on their role</li></ol><h3>What I’m excited about</h3><p>We have two new starters. We’ve been the same 4 people for over 2 years so it’s nice to have fresh faces, perspectives and ideas.</p><p>There’s a new energy and it helps remind us all of what we’re doing and how great our jobs are.</p><p>We’re also going to be advertising 3 new content design roles soon. So keep your eyes peeled if you want to join our content team at the Royal Borough of Greenwich!</p><h3>A bit about my leadership</h3><p><strong>Leadership style</strong>: Calm and adaptive.</p><p><strong>Current priority</strong>: Supporting people to feel confident with things not being perfect and getting comfortable with uncertainty.</p><p><strong>Strengths</strong>: Listening to people’s concerns and adapting my approach to meet their needs and priorities.</p><p><strong>Blindspots:</strong> Knowing the right time to expand our connections. Our content designers need to have the agency to do good content design but we need to make sure the relationships are in place to communicate some of that change to them without it setting us back.</p><p><strong>What I’ll be hands on with: </strong>Engaging with service teams to share the value of content design and build relationship that allow us to do that properly.</p><p><strong>What I’ll trust others to do:</strong> Anything in areas they’re interested in or passionate about that play to their strengths.</p><p><strong>What I’ll surround myself with:</strong> Context from the rest of the organisation so I can learn what matters to them and spot opportunities for us to add value through content.</p><figure><img alt="Woman pulling a thinking face with a background of letters, question marks, target boards and a desk indicating juggling different responsibilities." src="https://cdn-images-1.medium.com/max/1024/1*86KOFqkmYJwvANeR895oxg.jpeg" /><figcaption><a href="https://www.freepik.com/free-vector/unemployment-abstract-illustration_20770033.htm#fromView=search&amp;page=1&amp;position=2&amp;uuid=fc5104cc-bdb5-456c-88c4-b9b1bac16dd0">Image by vectorjuice on Freepik</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0ccc419da98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rbg-digital/weeknote-7-my-first-full-month-as-content-lead-e0ccc419da98">My first full month as Content Lead</a> was originally published in <a href="https://medium.com/rbg-digital">Royal Greenwich Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>