<?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 Rebecca Hales on Medium]]></title>
        <description><![CDATA[Stories by Rebecca Hales on Medium]]></description>
        <link>https://medium.com/@becky.e.hales?source=rss-3f56462e4959------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wMjmabtJFdty6Ua-</url>
            <title>Stories by Rebecca Hales on Medium</title>
            <link>https://medium.com/@becky.e.hales?source=rss-3f56462e4959------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:42:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@becky.e.hales/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[SEO in focus interview: we used to be scared of change, now we run towards it]]></title>
            <link>https://medium.com/bts-design-team/seo-in-focus-interview-we-used-to-be-scared-of-change-now-we-run-towards-it-2fd63c1c693?source=rss-3f56462e4959------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fd63c1c693</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-needs]]></category>
            <category><![CDATA[search-engine-optimizati]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Rebecca Hales]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 09:27:07 GMT</pubDate>
            <atom:updated>2021-03-11T09:27:07.415Z</atom:updated>
            <content:encoded><![CDATA[<p>In January 2021 SEO Manager Jack Sperry was interviewed over on the ContentKing blog.</p><figure><img alt="A screenshot of the SEO in focus interview with BT’s SEO Manager Jack Sperry" src="https://cdn-images-1.medium.com/max/1024/1*0N3CdR_2ghEuivAVg9jfmg.png" /></figure><p>You can <a href="https://www.contentkingapp.com/blog/enterprise-seo-agile-approach/">read the full interview</a> and find out how our SEO team has grown to take on the challenges of huge migrations, product launches and new SEO initiatives.</p><p>All of this whilst creating a new operational framework that aligns expert SEO consultancy with the areas where they are most needed, allowing us to support the wider business to take more ownership of SEO.</p><p><em>Fancy joining the team? We’re currently hiring into our SEO team and more jobs will be coming up soon. Search ‘SEO’ on the BT careers site to find new roles: </em><a href="https://www.bt.com/careers"><em>https://www.bt.com/careers</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fd63c1c693" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bts-design-team/seo-in-focus-interview-we-used-to-be-scared-of-change-now-we-run-towards-it-2fd63c1c693">SEO in focus interview: we used to be scared of change, now we run towards it</a> was originally published in <a href="https://medium.com/bts-design-team">EE Design Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Here’s a frequently asked question for you — are FAQs all bad?]]></title>
            <link>https://medium.com/bts-design-team/heres-a-frequently-asked-question-for-you-are-faqs-all-bad-ebc37a746f12?source=rss-3f56462e4959------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebc37a746f12</guid>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[content]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Rebecca Hales]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 12:03:13 GMT</pubDate>
            <atom:updated>2021-01-20T12:03:13.919Z</atom:updated>
            <content:encoded><![CDATA[<h3>Here’s a frequently asked question for you — are FAQs all bad?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vseJBmwEASifPFJjIz4oaA.jpeg" /><figcaption>Image courtesy of <a href="https://twitter.com/ContentDesignLN/status/1082583032924721153">Content Design London</a></figcaption></figure><p>In this blog post, Head of Content Design and SEO Rebecca Hales writes about content design for humans and content design for machines. Can you reconcile the two when creating commercially competitive content?</p><p>When I started working for BT I was not a fan of frequently asked questions (or FAQs). They duplicate information that — if it really matters to your users — should form part of a wider well-structured, user-centric journey on your site. They also create content overhead: an FAQ needs to be monitored and maintained and risks confusing users if you don’t keep it up to date.</p><blockquote><em>“The problem of FAQs really shows in search, where you will end up with duplicate results competing for attention. You are fighting with your own content. That can’t be efficient for you or for users.” — Sarah Winters, writing on the </em><a href="https://gds.blog.gov.uk/2013/07/25/faqs-why-we-dont-have-them/"><em>Government Digital Service (GDS) blog</em></a><em> back in 2013.</em></blockquote><p>In my view, Sarah talks a lot of <a href="https://contentdesign.london/content-design/frequently-asked-questions-faqs/">sense on the subject</a>. So much so that I regret not buying a <a href="https://twitter.com/ContentDesignLN/status/1082583032924721153/photo/1">‘No FAQs’ mug when they were available</a>, to be honest.</p><p><strong>Yay, let’s delete all the FAQs</strong></p><p>When I joined last year to head up the content design and SEO team, one of the first content improvement projects I got excited about was a huge exercise to cull FAQs in the BT ‘help’ area. Part of me was jealous of the content designers who were going through more than 3000 FAQs and deleting more than two-thirds of them. So therapeutic!</p><p>I naively floated the idea that perhaps the remaining 900 FAQs would not be needed if we examined what our audience was searching for and thought about solving those problems in other, simpler, more integrated ways.</p><p>Chris Cummins, one of our brilliant content design managers, pointed out to me that our colleagues in the propositions and marketing teams provide the FAQs about products and services. Those stakeholders expect FAQs to be published to help customers: find the products when searching online, understand the benefits of those products, and self-serve should an issue arise.</p><p>And that, for me, was an example of one of the most difficult issues our content designers deal with on a daily basis: balancing user needs with business needs.</p><p>It highlighted a conflict within my own role: while wearing my head of content design hat I wanted to argue for front-loaded content written in plain English as an alternative to FAQs. But with my head of SEO hat on, I had to acknowledge the valuable role FAQs play in driving traffic via organic search in a competitive commercial world.</p><p><strong>Fine, don’t delete all the FAQs</strong></p><p>FAQs are, in theory, an easy way to address the distance that exists between user needs and business needs. Because you need to know what users’ FAQs are in order to tune your search results (and surface the things the business wants to promote) you may as well show the current FAQs in order to provide a better service.</p><p>But this eliminates deep thinking about the search term your user has entered to arrive at that FAQ, and why. Deep thinking that can help content designers improve and simplify the wider experience and present better content as part of an end-to-end journey.</p><p>And FAQs take up valuable space, too. We don’t want to confuse customers with repetitive information or put obstacles in the way of them completing an action by putting an FAQ on a page where it’s not needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*moYLQPnBNtPmAIOWcju3JA.jpeg" /></figure><p><strong>Alright then, let’s make FAQs work harder</strong></p><p>Competing business needs and user needs mean we’ve had to find a compromise on FAQs that works for the team here at BT, EE and Plusnet. We can’t remove FAQs entirely in a commercially competitive world but we can make those FAQs more user-centred.</p><p>Our SEO team, led by <a href="https://medium.com/bts-design-team/implementing-an-seo-strategy-for-bt-ee-and-plusnet-be98cc04d4e6">Jack Sperry</a>, drives tens of millions of pounds worth of traffic to our sites each year and FAQs are an important part of our organic SEO strategy.</p><p>We treat search engines as a user that helps other users find content. Search engines have specific user needs we need to meet so that they can get a good understanding of our websites. When people have questions about a product or service a search engine is often the first step in the user journey. From an SEO perspective, our aim is to optimise content so that it’s available to users via voice or text result ‘featured snippets’ before they reach our website.</p><p>From a content design point of view, we want to make sure that when customers enter our site, the information they need to know appears at the point they need it and forms a cohesive part of their wider experience.</p><p>So we’ve developed some rules to help our content designers make the right choice when it comes to FAQs:</p><ol><li><strong>All FAQs are data-led and unique on our sites</strong>. If our user research and SEO analysis shows that people are genuinely asking a question frequently and BT, EE, and Plusnet are best-placed to answer it, an FAQ might be appropriate. If there’s no data to support the need for the FAQ, don’t publish it.</li><li><strong>Put the human user first</strong>. FAQs should not get in the way of a user completing a goal on a page. Quickly providing human users with relevant, easy-to-understand information in plain English on the page also benefits the robot user.</li><li><strong>Give the robot user both questions and answers</strong>. If you want Google to know what question your content is answering, include the question early in the body text (it does not need to be in a standalone FAQ or Q&amp;A format).</li><li><strong>All FAQs meet accessibility guidelines</strong>. If you do include an FAQ or multiple FAQs on a page, make your headings and subheadings clear and consistent. FAQs should not appear in images, which exclude both people who browse using a screen-reader and search engines.</li><li><strong>Care for your FAQs.</strong> If you decide to use an FAQ or Q&amp;A format, content designers should work with content editors and the SEO squad to understand how it’s continuing to perform and be ready to improve or remove it as necessary.</li></ol><figure><img alt="The top portion of the EE Black Friday Sale page with sales promotions." src="https://cdn-images-1.medium.com/max/1024/1*dlkcQ0I4O9fWudMVv2H1uQ.png" /><figcaption>Our EE Black Friday Sale page showing deals in the top half of the page and data-led, unique FAQs at the foot of the page.</figcaption></figure><figure><img alt="The bottom portion of the EE Black Friday Sale page with FAQs in place." src="https://cdn-images-1.medium.com/max/1024/1*szj_Jqp5QZOU-LVVyUq5NQ.png" /></figure><p>I’m still not a fan of the FAQ format, but at least if we follow these rules I can take some comfort in the fact any FAQs we do have on our sites have fought for their existence and are working that little bit harder to meet an established user need.</p><p><em>Do you have a strict ‘no FAQs given’ approach? Let us know in the comments below.</em></p><p>“faq” by aronbaker2 is licensed with CC BY 2.0. To view a copy of this license, visit <a href="https://creativecommons.org/licenses/by/2.0/">https://creativecommons.org/licenses/by/2.0/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebc37a746f12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bts-design-team/heres-a-frequently-asked-question-for-you-are-faqs-all-bad-ebc37a746f12">Here’s a frequently asked question for you — are FAQs all bad?</a> was originally published in <a href="https://medium.com/bts-design-team">EE Design Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing our digital Experience Principles]]></title>
            <link>https://medium.com/bts-design-team/introducing-our-digital-experience-principles-cf7230aaf47?source=rss-3f56462e4959------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf7230aaf47</guid>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Rebecca Hales]]></dc:creator>
            <pubDate>Thu, 25 Jun 2020 09:16:01 GMT</pubDate>
            <atom:updated>2020-06-25T09:16:01.308Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Rebecca Hales and Rich Chong introduce the five digital Experience Principles we’ve created to show what customers can expect when they encounter any of the BT Consumer brands online.</em></p><p><strong>Rich Chong, Head of Product Design:</strong> In BT Consumer we have five digital Experience Principles that help us create joined-up products and services that meet user needs. The principles are pretty new to everyone, so in June 2020 we released a series of videos to introduce them properly. Those videos and accompanying guidance — shared on our internal Slack channels and on Workplace — include some examples from our squads who’ve been working to put the principles into practice. We’re really proud of our Experience Principles and we wanted to share them here on the blog, too.</p><h3>Workshopping ideas</h3><p><strong>Rebecca Hales, Head of Content Design &amp; SEO:</strong> It takes time to get these things right. In 2019 we ran workshops with individuals from all Consumer Digital disciplines to ensure that any principles we came up with could be understood and applied by anyone, regardless of their role in delivering user experiences. There was some great work done at that time, with a comprehensive set of principles created. But we soon realised there were too many principles for everyone to remember, they were too detailed, and they were focused on our own behaviours instead of user needs and their experience.</p><p>We knew we had to simplify things.</p><p>So, in January 2020 we workshopped ideas around what it means to be a customer of one of our three brilliant brands. We invited people from across the BT Consumer and brand teams to put their heads together to answer the questions ‘What do we want our users to experience?’ and ‘How do we want them to feel?’.</p><p>We decided that customers want an experience that genuinely puts them first, is daringly simple, knows them, reassures them, and — if we’re lucky — amazes them, too.</p><p>For Rich and myself, the initial objective was to put down on paper the kinds of reactions we wanted to get from the team’s content design and product design work. From that original workshop, we brought those early ideas back to the BT design team. We asked content editors, product designers, content designers, and user researchers for their view on the draft principles. We did this via a drop-in session held on our design mezzanine at BT Centre. In the end, almost 20 BT design team folk popped along and shared their critique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WnKHnrj8xc8XtfbF80PxlA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4UvAYCNPtAgY9Ltyl2Mng.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmxmbsHodZc2-tMju7Yr2A.jpeg" /><figcaption>Workshopping early ideas for a set of principles to define people’s experience of BT products and services</figcaption></figure><h3>Our five digital Experience Principles</h3><p><strong>Rich:</strong> So, thanks to that feedback, those five shared ideas about what makes a brilliant digital experience quickly became our five digital Experience Principles.</p><ul><li>Puts me first (we know that if we meet user needs, business value will follow)</li><li>Daringly simple (everything is streamlined to leave only the essential)</li><li>Knows me (we connect the dots so our users don’t have to)</li><li>Reassures me (we communicate clearly and set the benchmark for accessibility and inclusivity)</li><li>Amazes me (we go beyond best practice: we aim to be a reference point for digital experiences)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6x7cAkJCmDcVwH7kzg2Fyg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eliWUZWMAAFRby3zOs0j4g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vE6aeTFA4AhMFmegzGwxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8b-RN_tW6MIyFoEkHeneCQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnx59PBDx4wIu4ZR_Hf7WA.jpeg" /><figcaption>We have these posters promoting the five Experience Principles on display around our office</figcaption></figure><p>Having a set of principles in place helps us to share some guiding beliefs when new people join BT Consumer and help anyone — inside BT and beyond — who wants to understand how we work and what we’re striving for on behalf of tens of millions of people.</p><p>The first principle places the user at the centre. We know we have to be clear about the user need and business goals we’re trying to meet before we start. But we also know we’re not just here to make things look good. We’re designing information that will amaze our users in any medium, on any device, however they choose to consume it. So our principles also respect our users’ time by keeping things simple, personal, accessible and inclusive. They encompass how we want users to experience all of our products and services.</p><p><strong>Rebecca:</strong> As well as being evocative of what it’s like to engage with us as a customer, the Experience Principles are grounded in a balance of common sense and ambition. They’re supported by guidelines on how to put them into practice when creating digital experiences. In fact, they’re the foundation of our <a href="https://medium.com/bts-design-team/introducing-the-bt-design-team-f3ba323ce2d9">build, measure, and learn design process</a>.</p><p>We believe that guidelines are more likely to be followed if they are simple, clear, helpful, and easy to share. So, we’ve organised ourselves around those five straightforward principles, which exist in poster format (pictured above) and in our <a href="https://medium.com/bts-design-team/creating-our-design-playbook-a-story-in-two-parts-21d712c55e1e">design playbook,</a> alongside some detailed criteria.</p><p><strong>Rich: </strong>The Experience Principles are intended for anyone building digital experiences for bt.com, ee.co.uk, and plus.net. We think they’ll get better the more work we do and the more we test them out in action.</p><p>There’s a lot of practical, common sense stuff covered in the criteria for each principle. For example, the ‘Puts me first’ criteria reminds you to build quick prototypes to test hypotheses; ‘Daringly simple’ says you must remove unnecessary steps in a journey and code for speed and quality; ‘Knows me’ encourages you to present customers with options based on insight through research or powerful personalisation technologies; and ‘Reassures me’ puts the onus on you to clearly communicate how data is collected, processed and used and how securely we build our experiences.</p><p>But there’s a lot of ambition in the Experience Principles, too. ‘Amazes me’ challenges our designers to experiment and be bold. We all want to create world-class experiences and the Experience Principles and accompanying criteria are one way we’re helping everyone in BT Consumer do that, consistently and brilliantly.</p><h3>Putting the principles into practice</h3><p><strong>Rebecca: </strong>We want everything we do to contribute to our goal of creating the best experiences that enhance our customers’ lives. Now that we’ve rolled out the Experience Principles and provided our people with concrete examples of what good looks like, we’re going to start using the criteria to assess whether a user journey is meeting them effectively.</p><p>We still need to work out exactly what that assessment could look like. It may be informal, such as some form of a self-assessment for squads to do on iterations of established products and services, or it may need to be more formal, for example when we’re launching a brand new experience (perhaps akin to the <a href="https://www.gov.uk/service-manual/service-assessments/how-service-assessments-work">Government Digital Service’s service standard assessments</a>). We’ll keep you updated as work continues.</p><p><em>If you’re working in a large design team and have experience of setting standards like this, we’d love to hear from you and compare notes. Let us know in the comments below or </em><a href="https://twitter.com/RebeccaEHales"><em>chat to me on Twitter</em></a><em> or </em><a href="https://www.linkedin.com/in/richchong/?originalSubdomain=uk"><em>contact Rich via LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf7230aaf47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bts-design-team/introducing-our-digital-experience-principles-cf7230aaf47">Introducing our digital Experience Principles</a> was originally published in <a href="https://medium.com/bts-design-team">EE Design Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who we are]]></title>
            <link>https://medium.com/bts-design-team/who-we-are-24e01f5a402c?source=rss-3f56462e4959------2</link>
            <guid isPermaLink="false">https://medium.com/p/24e01f5a402c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Rebecca Hales]]></dc:creator>
            <pubDate>Thu, 24 Oct 2019 13:54:58 GMT</pubDate>
            <atom:updated>2021-05-07T15:02:18.880Z</atom:updated>
            <content:encoded><![CDATA[<p>BT is going <a href="https://www.bt.com/beyond-limits">beyond limits</a> and we’re building a design team that takes that spirit into digital.</p><p>We’re a creative and collaborative team of user researchers, product designers, content designers and SEO experts.</p><p>We design new digital products, services and platforms that are personal, simple and brilliant. We always start with user needs, we’re agile, and we treat everything like it’s a prototype.</p><p>We want to work as openly as possible, which is we why we’re sharing our progress on this blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24e01f5a402c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bts-design-team/who-we-are-24e01f5a402c">Who we are</a> was originally published in <a href="https://medium.com/bts-design-team">EE Design Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>