<?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 Anna Shipman on Medium]]></title>
        <description><![CDATA[Stories by Anna Shipman on Medium]]></description>
        <link>https://medium.com/@anna.shipman?source=rss-5cab33fd3cf2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WuqB9zmG6CemiGzU3nnnhw.jpeg</url>
            <title>Stories by Anna Shipman on Medium</title>
            <link>https://medium.com/@anna.shipman?source=rss-5cab33fd3cf2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:52:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anna.shipman/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[CTO reflections on my first year at Kooth]]></title>
            <link>https://medium.com/building-kooth/cto-reflections-on-my-first-year-at-kooth-8e004165e6af?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e004165e6af</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[healthtech]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Fri, 13 Dec 2024 11:58:24 GMT</pubDate>
            <atom:updated>2024-12-13T15:06:45.402Z</atom:updated>
            <content:encoded><![CDATA[<p>I joined Kooth as Chief Technology Officer just over a year ago. Kooth has spent the last two decades building digital mental health services for young people to help provide early and responsive mental health support. I recently shared my reflections on my first year with the team, and wanted to also share them here.</p><p><strong>It’s incredible to work on such a meaningful purpose</strong></p><p>One of the things that drew me to Kooth was the opportunity to work on such an important mission. Mental health, particularly for children and young people, is one of the most important issues of our time. We see some terrible statistics, for example over one million UK children and young people were referred to NHS mental health services in 2023/24, and 22% of high school kids in the US have contemplated suicide in the past year.</p><p>At Kooth, we know we are working on a product and service that is directly improving on that, and I feel really motivated, knowing that I am part of the solution. I know that most people who work at Kooth feel the same way.</p><p><strong>We also have a lot of exciting technical challenges</strong></p><p>Another thing that really drew me to Kooth were the technical challenges. When I joined in 2023, we had won a contract to deliver a new, improved version of our service to California. This was Soluna, and it was app-first (in the UK, <a href="https://www.kooth.com/">https://www.kooth.com/</a> is a web-based service). It also involved developments to our underlying service model.</p><p>We rolled out Soluna at the beginning of 2024, and have spent this year adding features and improving on it. If you are in the US <a href="https://solunaapp.com/">you can download it here</a>. And if you are in the UK, hold tight, because one of the next big exciting technical challenges we have is bringing Soluna back to the UK.</p><figure><img alt="Screenshots of the Soluna app. Main image is of an exercise: “choose up to six values to guide your self-discovery journey”" src="https://cdn-images-1.medium.com/max/1024/0*LqJuEwLORke-R3mJ" /></figure><p><strong>Kooth is a very inclusive and friendly place</strong></p><p>Before Kooth, I worked at the Financial Times, which is a really nice place to work. One of the things that drew me to Kooth was the opportunity to be part of a smaller and fast-paced organisation, but I was apprehensive — I didn’t think anywhere could be as nice and friendly as the FT. But I was completely blown away; it is a very fast-paced environment, things can change quickly, and we are having a big impact; and also everyone is very kind. I am really enjoying working here and am so glad I joined.</p><p>I’ve particularly loved the inclusiveness of the engineering team. When I first joined <a href="https://www.annashipman.co.uk/jfdi/meeting-everyone.html">I met everyone on the team to ask what was going well</a> and what we should look to improve, and one thing that many people mentioned was that it was a place where they could really rely on their peers to be supportive. People mentioned they’d never worked anywhere else where people were so willing to hop on a call to help you solve a problem.</p><p><strong>Over the past year we’ve launched Soluna, new pilots and grown our team</strong></p><p>So much has happened since I joined, but I’d like to call out some particular highlights.</p><p>As I mentioned, launching Soluna was a huge thing this year, and we have had a great response from users, including near total positive feedback from users who’ve completed coaching sessions: 97% “felt heard, understood and respected” and 98% would recommend Soluna to a friend. And one incredible highlight that stood out for me was <a href="https://www.youtube.com/watch?v=0xN-kDXdnno&amp;t=665s">Governor Newsom mentioning Soluna by name</a> in his state of the state address.</p><p>We also made some changes and improvements to our UK products, Kooth and Qwell, and started planning for our migration to Soluna in the UK.</p><p>We have had a lot of great new starters, including our first US engineering and data science hires. And we’ve also done a lot of work on improving our development processes, how we run out of hours support and improve the reliability of our systems, and how we share knowledge within our teams and across the company.</p><p><strong>What I’m looking forward to over the next year</strong></p><p>There is lots more to do and I’m really excited about what we’ll be doing over the next year. We are improving Soluna. We are also launching new pilots and making rolling them out much more straightforward: we are aiming for a “cookie-cutter” approach, so we can get to improving outcomes for our users as quickly as possible.</p><p>I’m also really excited about improvements we are planning to how we use data at Kooth. All our data teams (data analysts, data scientists and data engineers) are working together to optimise how data flows through the organisation and make sure we are putting it to best use for our users, our customers and for the business. <a href="https://www.linkedin.com/pulse/ethical-ai-brighter-future-mental-health-from-kooth-global-jmhjc/?trackingId=EARQyY8bSJC6buO3cWqdWQ%3D%3D">We’ve already talked a bit about our AI and data strategy</a>, and watch this space for more!</p><p>I’m also looking forward to bringing the team even closer together across the UK and US next year. We are fully remote in engineering and so we are well placed to make sure that we really feel like one team even though we are distributed as far apart as San Diego, CA and Newcastle upon Tyne, UK.</p><p><strong>We are hiring!</strong></p><p>Please watch this space for more, and if any of this sounds exciting to you too, <a href="https://www.koothplc.com/about-us/join-us">we are hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e004165e6af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-kooth/cto-reflections-on-my-first-year-at-kooth-8e004165e6af">CTO reflections on my first year at Kooth</a> was originally published in <a href="https://medium.com/building-kooth">Building Kooth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What next for No next Next?]]></title>
            <link>https://medium.com/ft-product-technology/what-next-for-no-next-next-adbb02406171?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/adbb02406171</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Mon, 12 Dec 2022 08:49:25 GMT</pubDate>
            <atom:updated>2022-12-12T10:58:29.044Z</atom:updated>
            <content:encoded><![CDATA[<p>Just over three years ago, I wrote about the tech strategy for Customer Products, <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">No next Next</a>. In this post I talk about how we’ve implemented our strategy, what the outcomes are, and what we are going to do next.</p><h3>Next brought a faster, coherent user experience</h3><p>“Next” replaced our previous FT.com site, which was powered by a monolith, called “Falcon”. Falcon could only be deployed monthly, out of hours, and Next, powered by a microservices architecture, brought huge performance and productivity gains.</p><p>Falcon also didn’t have one team in charge of the whole; different parts of the business owned different parts of the site. Next brought all of the website estate under one leadership team, meaning that product, UX and design work together to form a coherent user experience, and the tech is governed in one place making it easier to improve it, maintain it and keep it secure.</p><h3>Fighting entropy: No next Next</h3><p>It cost £10mn and took us two years to build Next. We wanted to make sure we kept that drive and focus on continuous improvement, rather than letting the tech drift so far off track that we had to throw it away and spend another £10mn and two years building another Next: our tech strategy is No next Next.</p><p>In any case, there would be no point in throwing it away and building another stack, because entropy is inevitable. The second law of thermodynamics states that everything tends towards entropy. Unless you actively work towards order, over time your system will become messy, more complex, and ultimately unmanageable.</p><p>What No next Next means is a focus on sustainability, on supportability and on simplicity. Maintaining a focus on order, continuous improvement, and active replacement of parts of the codebase that have become too complex. And accepting that entropy is inevitable and finding ways to handle it.</p><figure><img alt="Dots in neat rows on the left leading to dots all over the place on the right, showing things tending towards disorder" src="https://cdn-images-1.medium.com/max/1024/0*Ztb_8PP1K5HNan64" /><figcaption><em>Over time, everything tends towards disorder</em></figcaption></figure><h4>Giving teams the support to be great</h4><p>The Customer Products team are an incredibly smart, talented and kind group of people, and all of the ideas and execution for how we move forward on our tech strategy came from the team. Together, we realised we needed to make the space for those ideas and execution to flourish.</p><p>One of the early changes we made was moving to a <a href="https://medium.com/ft-product-technology/unlocking-value-with-durable-teams-a70efb435a19">stable team structure</a>, rather than forming teams around initiatives. When teams are long-lasting, it is easier to have a clear strategic vision and work towards it, and it also means teams have a chance to learn how to work together to perform really well and become more than a sum of their parts.</p><p>As part of that, we addressed the problem that over 80% of our repos didn’t have a clear technical owner. That didn’t mean that there wasn’t someone who owned each system, but we had no way of knowing which ones were owned and which were not. Unowned tech is an operational risk you don’t know about yet: you don’t want to find out in a production incident that actually, the only people who knew about that system have left the company.</p><p>With the move to durable teams, we also moved to full technical ownership. This did have challenges, as some teams found they owned a lot of systems, some of which they knew nothing about, and over time we are working on managing this, including sunsetting some tech, and working out where ownership may actually be in another group.</p><p>We also worked on improving our recruitment process, for example <a href="https://medium.com/ft-product-technology/making-recruitment-fair-for-people-of-colour-66a3ad907a7d">making it fairer for people of colour</a> so that we can continue to build great teams.</p><h3>Replacing parts of the codebase that have become too complex</h3><p>We <a href="https://medium.com/ft-product-technology/achievement-unlocked-6edbc0b44ddd">rebuilt a critical part of our website</a>, called n-ui, on which all of our user-facing apps depended. N-ui did a lot of work, including building and loading client-side code, configuring and loading templates, as well as tracking, ads configuration and a lot more. It was difficult to maintain, not well understood by the current team, and tightly coupled to technical decisions made at the beginning of building the new FT.com. <a href="https://medium.com/ft-product-technology/designing-a-sustainable-front-end-toolset-for-ft-com-f37c59d27eeb">We replaced it with a set of loosely coupled packages called Page Kit</a> that have been much easier to maintain, and as an additional benefit, replacing n-ui with Page Kit made FT.com faster, halving our Time To Interactive (TTI) metric.</p><p>We are now working on <a href="https://medium.com/ft-product-technology/unspaghettiing-ft-coms-content-pipeline-be1421a434cb">rationalising some of our content APIs</a> which, over time, have grown organically to be a bit like spaghetti.</p><figure><img alt="Various systems connected by lines denoting APIs that overlap each other and look complex" src="https://cdn-images-1.medium.com/max/1024/0*W5tlDwknr-j5IhUF" /><figcaption>Our APIs have grown organically to look a bit like spaghetti</figcaption></figure><p>We’ve also developed <a href="https://github.com/Financial-Times/dotcom-tool-kit">FT.com Tool Kit</a> to make it easier for teams across FT.com to install the tooling they need, and helps us keep our codebase consistent and maintainable.</p><p>As well as working on the less visible parts of the tech estate that slow down performance and developer productivity, we have also worked on simplifying and improving how we deliver features to make it easier for our colleagues elsewhere in the business to work with us. For example, we have recently <a href="https://medium.com/ft-product-technology/read-all-about-it-rebuilding-the-ft-com-newsletters-page-4a63cb16bf43">rebuilt the newsletter page</a>, and we are about to start work on improving the cancellation journey.</p><h3>Improving our supportability</h3><p>When I joined, we only had 5 people on the out of hours rota, and all of those people were people who’d worked on the original build of Next; new people didn’t join the rota. As I mentioned in <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">my previous post</a>, part of the solution to this involves doing the hard work to make the tech simpler, such as swapping out the complex parts of the codebase.</p><p>However, we also did a lot of great work to make it easier to be on the out of hours rota:</p><ul><li>We had a <a href="https://medium.com/ft-product-technology/documentation-day-how-the-ft-com-team-improved-our-documentation-to-95-usefulness-in-7-hours-b73d1a7e6f30">documentation day</a> to make sure the documentation people look at for support with systems in an incident were up to date.</li><li>We ran <a href="https://medium.com/ft-product-technology/supporting-our-systems-through-incident-workshops-c0d22a4290b9">incident workshops</a> so people new to incidents could understand what was involved. Before you’ve been involved in support incidents sometimes you feel that you need to know everything about the stack you are supporting in order to sign up, and one of the really great benefits of the incident workshops is that less experienced staff saw more senior staff saying they didn’t know what was happening, and then see what things they’d investigate to figure it out.</li><li>We introduced a shadow rota, where people could sign up to the out of hours rota but as a shadow, meaning they would get called when there was an incident, but they would not be on the hook for solving it; they would observe and learn. We found that people on the shadow rota often make really valuable contributions to handling incidents.</li><li>We’ve also just introduced a slack group called `@incident-watchers` so that people who want to learn about live incidents can be tagged when we’re having one in-hours and watch along.</li></ul><p>These changes meant that we went from 5 to 22 people on the out of hours rota, which is much more sustainable.</p><figure><img alt="A group of people sat round a table with laptops and metrics displayed" src="https://cdn-images-1.medium.com/max/1024/0*JG6pVKekY6mYt6GP" /><figcaption>An incident workshop</figcaption></figure><h3>Achieving operational excellence</h3><p>Improving the out of hours support process is great, but what is even better is improving the reliability of the site so that there are fewer failures and it is quicker to recover when there are.</p><p>When I joined, we had a rotating responsibility for improving reliability called Ops Cops, which teams would take on for a week at a time, We’ve made a few incremental changes to how we do this, each improving our reliability.</p><p>Firstly, we <a href="https://medium.com/ft-product-technology/why-and-how-we-changed-the-way-we-support-ft-com-7572371f3f36">created a dedicated team with a tech lead and delivery manager, that engineers rotated into</a> so there was consistency from week to week.</p><p>While this improved things, we found that the rotation meant that the team was not able to focus on larger, more strategic reliability work. The team also didn’t have clear metrics or service level agreements, so we then <a href="https://medium.com/ft-product-technology/next-chapter-on-our-journey-to-achieve-and-maintain-operational-excellence-of-ft-com-7dd9c7871347">created a stable team of three engineers</a> and a delivery manager, and we added a product manager.</p><p>One year on from these changes <a href="https://medium.com/ft-product-technology/operational-excellence-one-year-on-f1dccaf2f034">the team are doing great things</a>; improving observability and reliability, working more proactively rather than reactively, and making recommendations and providing tools that help us achieve operational excellence.</p><h3>Improving technical alignment</h3><p>We have multiple teams working on microservices who are empowered to make technical decisions. However, teams were getting out of alignment with each other. Different teams were making technical decisions that ultimately lead to conflicting or unclear architectural changes.</p><p>To address this, we introduced a <a href="https://medium.com/ft-product-technology/thinking-through-our-changes-with-design-documents-35c93bf0938b">technical design document</a> process. When tech leads are making architectural decisions, they share these documents with the other tech leads for discussion. This allows people with relevant experience in a different team to add useful information to a plan, whereas otherwise they might not know it is happening.</p><p>As a side benefit it also forms a documentation trail of architectural decisions. We also now use these when other teams would like to make changes to our stack.</p><h3>We are part of a larger team</h3><p>In 2022, we’ve also been able to expand our tech strategy to be much more closely supporting the goals of the business. When we <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">first started working on the Customer Products tech strategy</a> in 2018, the vision for FT.com was still around the recent launch of the new site, and our tech strategy was focused on making sure that it remained sustainable. It was about building good tech and not costing the business more money, but it wasn’t about delivering specific products that move us forward.</p><p>The best tech strategy could be summarised as “deliver what the business needs”, and now, we have <a href="https://medium.com/ft-product-technology/financial-times-subs-and-product-strategy-2021-1bc48a2a337e">a subscriptions business strategy</a>, and a clear and compelling <a href="https://medium.com/ft-product-technology/filling-the-product-strategy-gap-22fb6f792139">product strategy for FT.com &amp; apps</a> which helps us really focus our tech strategy on moving towards the most important goals for the business.</p><p>In addition, we are now working much more closely with other tech groups across the FT to pull together a tech strategy for all of FT Technology, rather than each group having their own, separate tech strategy.</p><h3>What’s next for no next Next</h3><p>We’ve seen that our tech strategy has really bedded in and allowed people to make decisions based on what helps make our codebase more sustainable, and enabled and supported the great ideas the team have.</p><p>Over time, we’ve changed how we work on tech strategy, from setting <a href="https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424">quarterly priorities</a>, to this year, following a <a href="https://www.annashipman.co.uk/jfdi/tech-strategy-process.html">deeper, more forward-looking process that helped us set priorities for the whole of 2022</a>. Our process in 2022 allowed us to really invest more in our tech strategy priorities. For example, building a team to work on API rationalisation for six months, rather than trying to do this work alongside other, competing priorities, and we’ve really seen the benefit of that approach over this year.</p><p>I mentioned that Next brought all of the website estate under one leadership team, meaning that product, UX and design work together to form a coherent user experience, and the tech is governed in one place.</p><p>As we move towards a multi-product organisation the exciting challenge for Customer Products is how to enable other tech groups to deliver features, some of which will be on FT.com and the apps, without losing the coherent user experience and the strong tech governance.</p><p>All this means that the 2023 Customer Products tech strategy will be part of a larger business strategy. So there may be no next for No next Next, but I’m incredibly excited about what we are going to do next!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adbb02406171" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/what-next-for-no-next-next-adbb02406171">What next for No next Next?</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being a Principal Engineer in Customer Products at the FT]]></title>
            <link>https://medium.com/ft-product-technology/being-a-principal-engineer-in-customer-products-at-the-ft-97ac3ecc1c9d?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/97ac3ecc1c9d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Mon, 27 Jun 2022 13:27:06 GMT</pubDate>
            <atom:updated>2022-06-27T13:27:06.790Z</atom:updated>
            <content:encoded><![CDATA[<p>At the FT we have a role called Principal Engineer. Many companies do; however, the shape of the role at the FT is different than it is at many other companies, so in this post I explain what the role is like on my team, Customer Products.</p><p>And if you are interested, we are hiring a <a href="https://boards.eu.greenhouse.io/financialtimes33/jobs/4053976101">people-focused Principal Engineer</a> right now!</p><h3>We have durable, multi-disciplinary teams</h3><p>The Customer Products group is responsible for the FT.com website and our iOS and Android apps. We have 11 <a href="https://medium.com/ft-product-technology/unlocking-value-with-durable-teams-a70efb435a19">teams formed around product areas</a>. Each of our teams has a <a href="https://medium.com/ft-product-technology/technical-leadership-in-customer-products-cec00bf983bd">tech lead</a>, a product manager and a delivery manager, who together are responsible for setting the direction for the team, working out what opportunities to focus on, and weighing up priorities within the team. Each team also has a number of engineers, and if relevant to that team’s work, design, user research and data roles.</p><p>There are currently five principal engineers on Customer Products. They report to me, the Tech Director, and they each oversee two or three product teams.</p><h3>A Principal Engineer does technical and people-focused work</h3><p>Each Principal Engineer is like a Tech Director of their own area. That means they oversee the technical direction of their teams and support the tech leads where necessary; they each line manage around three senior engineers; and they work with me on the <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">tech strategy</a>.</p><p>Principal Engineers also work on strategic initiatives that reach out of Customer Products, with other tech groups, or the rest of the business. These might be technical, for example working with other groups to improve how we do AWS key rotation, or they might be people focused, for example building a career competency framework.</p><p>The diagram below shows some of the kinds of work that a Customer Products principal engineer might work on.</p><figure><img alt="A diagram listing some of the things principal engineers might work on, ranging from technical on the left (e.g. “strategic tech projects”) to managerial on the right (e.g. “leading recruitment”)" src="https://cdn-images-1.medium.com/max/1024/0*wFNZrMz45hoyra8c" /></figure><h3>I want the Principal Engineers to be ready for my job</h3><p>My goal is for the Customer Products Principal Engineers to be running Customer Products engineering without me, and for any one of them to be a good candidate to take my job, as Tech Director for Customer Products.</p><p>Some of the things we’ve done towards that include <a href="https://www.annashipman.co.uk/jfdi/delegating-to-a-team.html">clarifying the different types of work we do</a> and making sure that we share as much context as possible, both from me to the team and the team with each other and me. We also follow an agile planning process and try to <a href="https://www.annashipman.co.uk/jfdi/prioritising-in-tech-leadership.html">focus on the ‘rocks’ rather than the ‘pebbles’ and ‘sand’</a>.</p><p>However, we are currently in the position that although the Customer Products Principals excel in both technical and people areas, the current preferences of the team are more skewed towards the technical end of the spectrum in the diagram above.</p><h3>We are hiring a people-focused Principal Engineer</h3><p>With any team you want a complementary mix of skills, so to create a more balanced senior team we’re hiring a people-focused Principal Engineer.</p><p>The kind of things that a people-focused Principal Engineer might lead on include:</p><ul><li><a href="https://medium.com/ft-product-technology/unlocking-value-with-durable-teams-a70efb435a19">Leading the move to durable teams</a></li><li><a href="https://medium.com/ft-product-technology/improving-our-career-map-for-engineers-4210185c6246">Building a career competency framework</a></li><li><a href="https://medium.com/ft-product-technology/making-recruitment-fair-for-people-of-colour-66a3ad907a7d">Improving our recruitment process to make it fairer for people of colour</a></li></ul><p>It is also an opportunity for someone to lead on the more people-focused aspects of leadership within Customer Products, to gain experience to be ready for that part of the Tech Director role; for example ensuring our retention and reward processes are fair, effective and work within our budget, or looking at ways to improve the experience of working at the FT and in Customer Products; whether that is to do with productivity, diversity and inclusion, technical competence or other areas.</p><p>However, this is not a purely people and process role. This person will still have oversight of the technical direction of two to three teams, support the tech leads in making well-informed decisions, and work with other principal engineers and other tech groups.</p><p>The difference between this role and a more technical-focused principal engineer role will be in the types of strategic project they initiate and lead.</p><h3>We do not currently have Engineering Managers at the FT</h3><p>The people-focused Principal Engineer role I’ve described above is very similar to what many organisations call Engineering Managers. However, we do not have this role at the FT at the moment.</p><p>Before I joined the FT, there were Engineering Managers. At that time, the organisation was very siloed by discipline, and as part of a move towards multidisciplinary teams, it was decided that this role was no longer needed. Much of the work that Engineering Managers did then is done by Delivery Managers now, and the role then was quite different to the role we would describe as an Engineering Manager now.</p><p>At the FT, each tech group is set up in a slightly different way. We want ultimately to align our structures; so we might create an Engineering Manager role in the future, but that is a much bigger piece of work across the whole of technology.</p><h3>Join us!</h3><p>The FT is a great place to work. My colleagues are smart, motivated and kind, and our purpose is extremely important: it is hard to overstate the value of balanced and unbiased journalism in today’s world.</p><p>We use modern engineering practices and are always looking for ways to improve, and the organisation is one that cares about its staff. If this sounds like a place you’d like to work then please <a href="https://boards.eu.greenhouse.io/financialtimes33/jobs/4053976101">apply for this role</a>, or check out our <a href="https://boards.eu.greenhouse.io/financialtimes33/">many other open vacancies</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97ac3ecc1c9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/being-a-principal-engineer-in-customer-products-at-the-ft-97ac3ecc1c9d">Being a Principal Engineer in Customer Products at the FT</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking value with durable teams]]></title>
            <link>https://medium.com/ft-product-technology/unlocking-value-with-durable-teams-a70efb435a19?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a70efb435a19</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 11:10:19 GMT</pubDate>
            <atom:updated>2022-10-13T19:17:06.853Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past six months, my group at the Financial Times has moved from project-based teams to durable teams. In this post I’ll explain why we made that move and how this is helping us deliver bigger and better things for our customers.</p><h3>We want to be able to deliver as much value as possible</h3><p>Our goal on Customer Products is to make FT.com and the iOS and Android apps be as good as they can be for our customers, and increase the lifetime value of each customer or corporate licence. As with any tech organisation, we have a tech estate that we need to keep <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">sustainable, supportable and operationally reliable</a>, while also freeing up as much time as possible to deliver value to our customers and the business.</p><p>We use everything we already know about good software development to allow us to focus on where we can really add value. We already do continuous integration, automated testing, effective code review, and many more standard development practices that eliminate wasted time and low value work, and we also experiment, release early and iterate so we don’t spend too much time on work before we know it’s valuable.</p><p>However, we realised there was something we could do around the actual organisation of the group itself to help us become a really high-performing team.</p><h3>We used to have initiative-based teams</h3><p>When I first started working at the Financial Times, my group — which builds the ft.com website and the iOS and Android apps — was made up of around 11 teams. Teams were formed around projects, usually with a product focus. For example, we had a Conversion team, whose focus was on converting casual readers into subscribers. When we had new initiatives, for example launching FT podcasts, we formed a new team.</p><p>Over the past year, we’ve changed to a new team structure: durable teams. This means our group is made up of nine teams, that each own a product area and the associated tech estate, plus our <a href="https://medium.com/ft-product-technology/why-and-how-we-changed-the-way-we-support-ft-com-7572371f3f36">ops cops team</a>, who handle in-hours support.</p><figure><img alt="A diagram showing the nine durable teams and how they overlap, along with our small ops cops team" src="https://cdn-images-1.medium.com/max/1024/0*rtDKWs9mWzjNtn6Y" /></figure><h3>Initiative-based teams have some advantages</h3><p>The main advantage of our previous structure is that each team is focused on one product goal, which is good from the perspective of working together to deliver value.</p><p>It also allows the group to quickly swarm on problems, and by not having to care about legacy code or bugs, the team are free to work as fast as they can on new features. It was a good approach for the early stages of building the new FT.com, where there was no legacy code to worry about.</p><p>It also makes budgeting easy — if we get investment to do an initiative, then we put a team together to do that initiative.</p><p>However, there are downsides to this approach, and over time they get worse.</p><h3>Forming, storming, norming, perf-</h3><p>One big disadvantage of changing teams quite frequently, is that it often does not give the team a chance to form into a really high performing unit.</p><p>All teams go through a process of team building. One way to represent the stages a team goes through is <a href="https://hr.mit.edu/learning-topics/teams/articles/stages-development">forming, storming, norming, performing</a>, as they figure out how to work together in order to achieve the best outcomes.</p><p>If you build teams around projects, this means that there is a ramp-up period while the team go through the early stages, and if the team is not together for long enough, it’s possible they won’t spend very long (if any time at all) in the performing stage. This happens if new initiatives come in and the team is disbanded to form other, new teams.</p><p>This is frustrating for the people on the team, and also means the business does not get the best value out of the highly skilled people working for it.</p><h3>Orphaned technology is an operational risk that you don’t know about yet</h3><p>If the team is disbanded to move onto other projects, the technology they have built often does not move with members of the team to the new project. For example when the podcasts team disbands to work on other initiatives, none of the work they’ve done may fit into the new teams.</p><p>This is a problem waiting to happen; it is a security and operational risk. Without ownership of tech, if any future development or maintenance is needed, it may be hard to find someone who has time to do it. In some cases, everyone who worked on a project may have left the company.</p><p>Even if no security risks arise, it slows things down. If an unowned piece of tech has outlived its usefulness, there won’t be anyone to take care of decommissioning it, meaning that over time your tech stack gets clogged up with code that is not adding value but is adding complexity and slowing everything down.</p><h3>Project-based teams remove agency from the team (and add administrative cost)</h3><p>It takes a lot of effort to form a team; you need to find the right balance of skills, someone to tech lead, delivery manage and be the product owner; you need to find engineers, customer researchers, product designers and possibly business analysts and you need to make sure that the work they are currently doing can be finished or stopped.</p><p>It also means the initiative ideas are coming from outside the team. The idea for the project comes about before the team is formed, so by the time the team has formed, it’s already been decided what they are working on, even though that might not represent the biggest opportunity for the business or <a href="https://svpg.com/four-big-risks/">even be a feasible idea</a>.</p><p>When you bring a team together to deliver a project that has already been decided, this can lead to the team feeling like a <a href="https://medium.com/hackernoon/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2">feature factory</a>, which is demotivating, and also doesn’t allow people to use their best skills to help solve business or customer problems.</p><h3>We decided to move to durable teams</h3><p>While we were some way from being a feature factory (for example, we have a really strong culture around <a href="https://vimeo.com/273987309">measuring the outcomes of our work</a>, and <a href="https://2018.continuouslifecycle.london/sessions/how-we-ab-test-at-the-financial-times-and-what-happened-when-we-started-testing-headlines-too/">A/B testing features</a> to see if they are useful) some of the issues highlighted in <a href="https://medium.com/hackernoon/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2">the feature factory blog post</a> were a little close to the bone, for example, “Team Tetris”.</p><p>We realised that one way to address a lot of the issues we had was to move to a durable team structure. This would allow us not just to solve some of the problems we currently had, but also it would allow us to really grow and unlock the potential of our teams.</p><ul><li>We can create teams that between them own our entire estate. Each team can take responsibility for the strategic direction of that area and kill things that no longer add value. We will no longer have unowned tech, which leads to security and operational risk.</li><li>Durable teams mean we do not waste effort stopping and starting teams every quarter.</li><li>Durable teams help people build domain knowledge, mastery and vision, help build organisational memory and fine tune effective ways of working.</li><li>When a team reaches peak productivity, ideas and execution are consistently better. From meaningful work we get motivated people and a better quality product.</li><li>Durable teams help us be clear about what our strategy is, what is in scope and what our capacity is.</li><li>Durable teams make it easier for those outside our group to know who to talk to about a particular part of the product.</li></ul><h3>A long-lived team can work on bigger opportunities</h3><p>A durable team is in a good position to think strategically about the part of the domain they own. When the team knows they are going to be around to experiment, iterate and see the outcomes from changes they make, then they can take bigger bets.</p><p>This works from both a product and a technical perspective. A long lived team can take a big bet on changing how we show you relevant news because they will be around to make the changes and keep iterating until they get it right. They can also take a big bet on moving database platform to unlock potential, because they will still be around to reap the benefits of the move.</p><p>When a team is just there for a short, or uncertain, length of time, then in order to make any impact, they have to stick to small, incremental improvements. Working on the big bets which might reap huge rewards is too risky — the team may be disbanded before they’ve had a chance to show the benefit. If they have a longer lifespan they are free to try some things that are higher risk. Some will fail, but some will lead to the big changes that lead to exponential growth.</p><h3>Stable teams can be empowered teams</h3><p>What we really want is <a href="https://svpg.com/empowered-product-teams/">empowered teams</a>, coming up with and trying out the ideas that can really deliver value to our customers and help the business grow.</p><p>Each of our durable teams has a tech lead, a product manager and a delivery manager. Together, they are responsible for setting the direction for the team, working out what opportunities to focus on, and weighing up priorities within the team. This includes when to focus on adding product features and when it’s more crucial to focus on improving the tech.</p><p>As a leadership team, we can step back from making sure we know the detail of exactly what each team will do and concentrate on setting the higher level strategy and objectives. Then we can trust the team to use their huge skills and experience in the domain to identify for themselves what is the most valuable work they could be doing.</p><h3>Technical ownership of our estate has already started to save the business money</h3><p>Our tech strategy on Customer Products is <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">No next Next</a>. We don’t want our tech to drift so far off track we have to spend £10m and another two years rebuilding it. Making sure all our tech is owned is part of that strategy. When all tech is owned by a currently active team, the team that owns that part of the estate can make longer-term decisions about it.</p><p>When we started the move to durable teams, we had 332 systems or repositories, of which 272 were not assigned to a specific team. This didn’t mean that no-one knew about any of them, but we didn’t know which ones people knew about and which were orphaned — we didn’t know the scale of the problem.</p><p>Now, all of our systems or packages are owned by a currently active team. As teams started taking ownership, they quickly identified systems that were no longer needed or no longer used. By the time we finished tech ownership, we had removed 47 systems and packages, and more consolidation is planned.</p><p>This saves the business money directly in ongoing infrastructure costs, and indirectly, both through engineers no longer needing to maintain these systems, and through making <a href="https://medium.com/ft-product-technology/why-and-how-we-changed-the-way-we-support-ft-com-7572371f3f36https://medium.com/ft-product-technology/why-and-how-we-changed-the-way-we-support-ft-com-7572371f3f36">operational support easier</a>.</p><h3>Handling work that falls across teams</h3><p>There are two main risks in having a durable team set up like this. One is that some work naturally falls across two or more teams. Previously we would have formed a team to work on that thing, but now we need to coordinate between the existing teams to get that done.</p><p>The way we address that is as well as Delivery Managers co-ordinating as they usually do, the Principal Engineers — who work across the whole of Customer Products — make sure they have technical oversight and input into those projects. In addition, as far as possible, we try to architect the work so it can be done asynchronously, perhaps released behind a feature flag, and linked together when work in all teams is complete.</p><h3>Making sure splitting the domain doesn’t limit opportunities</h3><p>The other risk is that splitting the domain up into set teams has the potential for limiting thinking. Where you might have previously looked for the biggest opportunity across the whole estate, you might now only look for the biggest opportunity in your domain.</p><p>The current situation is still better than it was, in that there is much more potential for teams to make those strategic decisions even within their own domain, as they own everything around that domain. But it is an important part of my leadership role, as Tech Director, alongside the Product Director and Delivery Director, to make sure that this opportunity for bigger picture thinking is not lost.</p><p>It’s also worth noting that the current durable teams are not set in stone. It may be that as the product strategy develops over the coming years the actual teams change. However, we will approach any future changes with the same principles: empowerment, total tech ownership and allowing teams to stay together for the long term.</p><h3>We got it done just in time</h3><p>We had the last handover durable team meeting on the 24th February and the FT started working from home on Monday 16th March.</p><p>We are so lucky that we got the durable teams work finished in time. Having a durable team is really valuable at a time like this. It would be extremely difficult to manage if we were still trying to put teams together to work on initiatives, while all working from home in difficult and stressful circumstances, and those teams had to bond, figure out how to work together and perform in these circumstances.</p><h3>It’s already adding value</h3><p>We’ve already seen how durable teams helps us go faster. We’ve eliminated some waste in our technical estate and teams are looking for ways to reduce it further. We recently had to take on a piece of work that we hadn’t planned for, and we were able to distribute it among the relevant teams and get started on it, without waiting to hire people for the extra work, and we know when it’s finished it will continue to be owned by those teams. And we’ve seen great ideas emerging from teams, including some excellent discovery work that’s leading to teams taking much bigger bets.</p><p>Like many others the FT has been <a href="https://www.ft.com/content/0069d422-da44-4d06-ae5b-766836bfda6e">hit by the coronavirus crisis</a>. Having durable teams and a strategy of a <a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">sustainable, flexible codebase</a> gives us the foundation to accelerate fast and have greater flexibility to support whatever the business needs, through this crisis and beyond.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a70efb435a19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/unlocking-value-with-durable-teams-a70efb435a19">Unlocking value with durable teams</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No next Next]]></title>
            <link>https://medium.com/ft-product-technology/no-next-next-42c71541ebcc?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/42c71541ebcc</guid>
            <category><![CDATA[financial-times]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[sugababes]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 15:41:42 GMT</pubDate>
            <atom:updated>2022-10-13T19:17:50.914Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, I wrote about <a href="https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424">how we worked out our tech strategy for FT.com</a>. In this post I talk about the strategy itself: No next Next. And also about the Sugababes.</p><h3>The launch of “Next” hugely improved the user experience</h3><p>In October 2016, we replaced the old FT.com site with a new site, which we called “Next”.</p><p>The previous site didn’t have one team in charge of the whole; parts were owned by different parts of the business, meaning it was very hard to create a consistent user experience, keep it secure, or iterate quickly. Next is owned by one team which allows us to take a coherent approach to continuously improving the tech and customer experience.</p><p>The new site is built on a microservices architecture, ships hundreds of times a week and A/B tests everything. It is much faster than the old site and we demonstrated that <a href="https://medium.com/ft-product-technology/a-faster-ft-com-10e7c077dc1c">this directly impacted revenue</a>. It is much <a href="https://www.niemanlab.org/2016/10/the-financial-times-flips-the-switch-on-its-new-website-after-months-of-beta-testing-in-the-open/">better designed</a>, and our subscribers now come back more frequently and read more articles when they do. Earlier this year, we hit one million subscribers, a year ahead of our goal to do so.</p><h3>But we don’t want to have to do it again</h3><p>Building Next to replace <a href="https://web.archive.org/web/20150226162405/http://www.ft.com/home/uk">the previous FT.com site</a> took took two years and cost in the order of magnitude of £10m. Building it also meant that we had very limited capacity to change the old site while that work was in progress, so as well as financial costs it also had opportunity costs.</p><p>So we need to make sure we make the most of that investment. In order to do that, we need to steer it so that we don’t make the same mistakes we made with the old site.</p><h3>No next Next</h3><p>In a phrase, our vision for FT.com is <em>No next ‘Next’</em>.</p><p>We must make sure that the product and the underlying technology do not drift so far off course that we have to rebuild FT.com again in a few years, spending entirely avoidable time and money.</p><p>Instead, we want our tech to be sustainable, supportable, and operationally reliable, and we want it to be simple enough for new starters to get to grips with.</p><p>We don’t want to spend time grappling with complex technology, we want to spend our efforts on adding new features, innovating, and continuously improving the subscriber experience and value that the FT brings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t4PmddhW3DoAjSqP" /></figure><h3>The Ship of Theseus and the Sugababes</h3><p>If we want to make FT.com, the mobile apps, and other FT digital products sustainable for the long term rather than having to rebuild from scratch every few years, we will need to replace parts of it while it is in flight.</p><p>While talking about this we came up with a few analogies. The <a href="https://en.wikipedia.org/wiki/Ship_of_Theseus">Ship of Theseus</a>, rebuilt piece by piece while at sea. <a href="http://foolsandhorses.weebly.com/triggers-broom.html">Trigger sees his broom</a> as the same broom, despite the handle and head each being replaced a number of times. Or if those analogies don’t work for you, we could use the one that clicked it into place for <a href="https://aboutus.ft.com/en-gb/announcements/financial-times-appoints-john-kundert-as-chief-technical-officer-1/">our CTO</a>, the <a href="https://en.wikipedia.org/wiki/Sugababes#Members">Sugababes</a>, where the final line-up contained none of the original members.</p><p>Whether or not you think the final line-up of the Sugababes is <em>really</em> the Sugababes, that’s the approach we need to take with FT.com and our customer products to make them sustainable over the long term.</p><h3>Replacing the first band member is already increasing performance</h3><p>In my <a href="https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424">previous post on building a tech strategy</a>, I mentioned one way of finding out where to focus is asking engineers what code they feel afraid to touch. Through this method, we found that the package that manages the assets for FT.com hadn’t been worked on since the beginning of the Next project.</p><p>It performs multiple frontend services for FT.com, including building and loading client-side code, configuring and loading templates, as well as tracking, ads configuration and a lot more. It was tightly coupled to technical decisions made four years ago, and complicated. The current team did not feel confident making changes.</p><p>We put together a small team to update it, and they have now built a new service that splits all of this functionality into a set of loosely coupled, individually documented, and tested packages. The changes the team has made mean that any of our engineers can now confidently make contributions to this critical part of how we deliver the website.</p><p>It has also had an impact on the performance of the site. The team are currently migrating all of the FT.com services to the new packages, and each services that has been migrated shows decreases in the <a href="https://developers.google.com/web/tools/lighthouse/audits/time-to-interactive">Time To Interactive</a> of between 30% and 70%. This benefits users and also has an<a href="https://medium.com/ft-product-technology/a-faster-ft-com-10e7c077dc1c"> impact on revenue</a>.</p><h3>Communicating to the team and the rest of the business</h3><p>One of the purposes of a strategy is to give focus, so we identified the highest priority areas to get us back on track. The first thing we worked on was communication.</p><p>It’s all about communication. You can have the best vision and strategy in the world but if no-one knows about it it is not going to get you very far.</p><p>We have three main audiences for the tech strategy:</p><ol><li>Engineers working in our team, who need to know what the strategy is and what the priorities are so they can make sure they are working on the right things and can get involved with wider strategic work.</li><li>People outside of the team, so that they know what our focus is, how it will impact on their own priorities, and how to influence it.</li><li>Senior people in the business, for example the board, who need to know that by doing a little, often, we will not need to suddenly request another huge multi-year investment to rebuild the site again.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zTFC8CGv0XZe8E7F" /></figure><h3>Communicating the tech strategy and priorities</h3><p>When we started working on the tech strategy we realised that there were communication channels missing so we had to fix that first. We also did some research into how people would like to receive the information.</p><p>We now do the following:</p><ul><li>In our monthly full team meeting, for all disciplines, we give a 3 minute update on our progress on the tech strategy.</li><li>I give a quarterly tech talk, open to anyone, about our progress against the tech strategy: what we’ve done and what we’re doing next.</li><li>We have a page about the tech strategy on our engineering wiki which we keep updated. Our wiki is in a private GitHub repo which means only people who have a GitHub license can see it, so we now run a nightly job that publishes it to a Heroku app that anyone at the FT can access.</li><li>Our team has a monthly newsletter, sent to anyone in the business who is interested, and we update that with the progress on the tech strategy.</li><li>When we have ad hoc updates about the tech strategy we email the team mailing list, and we always put [Tech Strategy] in the subject line so people can add filters (to make sure they never miss an update, of course!)</li><li>Finally, we are blogging about what we are working on, so you can expect to read more about it here!</li></ul><h3>Refreshing and communicating our technical principles</h3><p>Tech principles are a high impact area to focus on because if they are well known and adhered to, that’s a way to affect everyone’s behaviour and help people move in the same direction.</p><p>When I joined the FT I found that there were technical principles, but there were four or five slightly different versions in different places, many of them in slide decks from presentations, and none of them actively used.</p><p>We’ve now refreshed our tech principles and publicised them. We’ve even made posters! <a href="https://medium.com/ft-product-technology/the-new-tech-principles-for-ft-com-dd788a896309">Matt Hinchliffe has written a great blog post with more detail about that here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L6f88dpzjHd-RsLz" /></figure><h3>Making our out of hours process sustainable</h3><p>The number of production outages for FT.com and the apps is very low, but occasionally we do get called out of hours to handle incidents. The team on the out of hours support rota are very responsive and deal with issues quickly and well. However, because our tech has grown more complex over time, it’s hard to get people — especially new starters — to join the out of hours rota.</p><p>Part of the solution to this involves doing the hard work to make the tech simpler. But there are other ways to help with this. One important thing is to make sure things you might be called up to deal with at 3am are well documented, and to get our most crucial systems up to a good standard we ran a Documentation Day, which <a href="https://medium.com/ft-product-technology/documentation-day-how-the-ft-com-team-improved-our-documentation-to-95-usefulness-in-7-hours-b73d1a7e6f30">Jen Johnson has written a great blog post about here</a>.</p><p>We’ve also started running workshops to train people in dealing with out of hours incidents, which have really improved people’s confidence in being on the support rota. We will talk more about our progress on improving out of hours as we go.</p><h3>Simplifying our tech to help us focus on growth</h3><p>When systems get too complex, they become harder to support. It takes more time to identify and fix bugs, it is harder to spot potential security flaws, and engineers spend more time digging through code to try and understand it than they do on adding new features and improving the customer experience.</p><p>As the second law of thermodynamics states, everything tends towards entropy, so we have to actively work to fight this and keep our systems simple and high quality.</p><p>The effort we put into this pays off in reducing bugs and outages, increasing security, and making our technology easier to understand, meaning engineers can more easily work across the stack and spend their time on delivering things that add value to customers and to the business.</p><h3>Measuring the simplicity of our systems</h3><p>In order to reduce system complexity, it is very helpful to be able to measure it. Measurement will show us the most complex areas to tackle first, and when we start making improvements, we will be able to track our progress against the original complexity. Having a complexity measure is also important in communicating to people outside of engineering which areas need attention.</p><p>At the moment we are looking at visualising all our services and packages to indicate how well-maintained they are (for example, how frequently they are updated, how many open pull requests they have, etc). Later we will look at code complexity and other measures.</p><p>Our goal is to have an overview of our systems’ health that is meaningful to people outside engineering.</p><h3>Clarifying our architecture</h3><p>We have multiple teams working on microservices who are empowered to make technical decisions.</p><p>However, one of the common problems of the <a href="https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424">difficult teenage years</a> is that without a clear technical vision, the teams can get out of alignment with each other. Different teams can make small technical decisions that ultimately lead to conflicting or unclear architectural changes.</p><p>We are doing a piece of work firstly to clarify our current architecture and clearly identify pain points and conflicts, and then to work on decision-making. We want to make it possible for tech leads to make architectural decisions that are consistent with other teams’ technical decisions, without imposing too much process on the decision-making.</p><h3>Joining up FT.com and the mobile apps</h3><p>When FT.com was rewritten, the team intentionally left the apps out of the rewrite so as not to take on too much at once, so “Next FT” is only the website, not the mobile apps. However, the team have been working hard since then on improving the apps and making sure features that are on the website are also on the apps, and vice versa.</p><p>The apps are a crucial part of our product, because in a modern news organisation we need to offer users many ways to consume our content, and it’s important to offer different things for different user needs. In addition, people who use the FT app tend to be very engaged with the FT, so there is a lot of value in improving their experience.</p><p>Because the apps were not in the Next rewrite, the app technology is out of step with the FT.com tech, and some of the underlying technology is now quite dated. We have been doing foundational work to bring the website development and app development closer together, so we can make use of the FT.com stack.</p><p>Once we’ve finished that we will be able to move much faster on the apps and do more exciting and ambitious work to add features for our highly engaged users.</p><h3>More to come!</h3><p>We will continue sharing our journey towards making our product more sustainable, and we’d love to hear your thoughts and experiences.</p><p>And if you are interested in joining us on this journey, <a href="https://roles.ft.com/">we are hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42c71541ebcc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">No next Next</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The difficult teenage years: Setting tech strategy after a launch]]></title>
            <link>https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424?source=rss-5cab33fd3cf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f42eb94a424</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[financial-times]]></category>
            <dc:creator><![CDATA[Anna Shipman]]></dc:creator>
            <pubDate>Mon, 02 Sep 2019 09:36:37 GMT</pubDate>
            <atom:updated>2022-10-13T19:18:48.466Z</atom:updated>
            <content:encoded><![CDATA[<p>When you are launching a new product to replace an existing one, it’s easy to rally behind the mission and make the right technical decisions that will get you over the line. But after the launch, it’s very common for things to lose focus: the vision is no longer so clear, corners you cut to get the product live come back to bite, and the tech can start to feel like it’s drifting off track.</p><p>This is the difficult teenage years.</p><h3>Setting a strategy to get back on track</h3><p>We experienced this with the <a href="https://www.niemanlab.org/2016/10/the-financial-times-flips-the-switch-on-its-new-website-after-months-of-beta-testing-in-the-open/">launch of the new FT.com site in 2016</a>. The new site is much faster, responsive on different devices and uses modern technology. It has a microservices architecture and ships hundreds of times a week. The launch of the site led to a measurable increase in how often our subscribers visited the site and the number of articles they read while there, and it also led to a big increase in subscribers.</p><p>When I joined the FT in 2018 I found an excellent, smart and motivated team, good tech and a great culture. However, some things were drifting off track. This post is about how we created our tech strategy for getting out of the difficult teenage years, and how you could too.</p><h3>Strategy is diagnosis, vision and a plan</h3><p>It’s worth talking about <a href="https://www.annashipman.co.uk/jfdi/good-strategy-bad-strategy.html">what strategy is</a>. A strategy consists of three parts:</p><ol><li>Diagnosis: What’s the current situation?</li><li>Vision: What is your desired end state? Where are you trying to get to? What does ‘good’ look like?</li><li>The plan to get there: What are the highest impact steps you can take to get to your desired end state?</li></ol><h3>The vision for the launch of “Next”</h3><p>The <a href="https://web.archive.org/web/20151231154747/http://www.ft.com/home/uk">previous FT.com website</a> was a monolith that could only be released once a month, outside of working hours. The site itself was slow and it was also not <a href="https://en.wikipedia.org/wiki/Responsive_web_design">responsive</a>, so on mobile devices it looked like a tiny version of the desktop site. There also wasn’t one team responsible for the overall look, feel, and technical coherence of the site: different parts of the business owned different parts of the website.</p><p>Initially, a small team worked on a prototype of a new FT.com website, which they called “Next”. Next has a microservices architecture and is built in Node.js. The Next team focused on building a <a href="https://medium.com/ft-product-technology/a-faster-ft-com-10e7c077dc1c">fast</a>, responsive site, with an emphasis on shipping and measurement. Users were given the opportunity to opt in to the Beta, and 5% did, allowing the team to develop the site in the open with real users.</p><p>In October 2016 it was rolled out to all users, and “Next” became the current FT.com site.</p><h3>Diagnosis: The difficult teenage years</h3><p>When I joined the FT in 2018, the site was still good — fast, still using modern technology, still shipping hundreds of times a week, with a focus on measurement and A/B testing everything. The team were focused, smart and really friendly and inclusive.</p><p>However, there were some cracks starting to appear. Some of the types of comments I heard were:</p><ul><li>Engineers weren’t sure of the value of the work</li><li>There were areas of code people didn’t want to touch</li><li>There was duplication of code</li><li>A couple of services required deploying microservices in a certain order to make a change (which contradicts the point of microservices, as independently deployable units)</li><li>Feature changes felt too bitty</li><li>Some of the people who set technical direction had moved to other projects</li><li>Someone said, and this was echoed by different people in similar ways, “It doesn’t feel like we are owning or guiding a system, we are just jamming bits in”.</li><li>Finally, something I heard from different teams and different disciplines, a red flag that indicates a lack of focus: “We need more developers”.</li></ul><p>These kinds of comments show the main themes of the difficult teenage years:</p><ul><li>Lack of clear vision</li><li>The tech can start to feel like it’s drifting</li><li>Things aren’t communicated as well as they used to be</li></ul><p>This is very common after a launch.</p><h3>The vision after the launch needs to be different</h3><p>You need a vision so you know what you are working towards, and to help communicate with others what you are working towards. When you are launching a new site to replace an existing site the vision is easy to communicate, because the new site will be better than the old one in a number of ways. You are replacing something that everyone can see the flaws with, as with the old FT.com site.</p><p>It is also easier to have conversations about what is in scope and out of scope before launch because there is usually a date in mind or some kind of milestone, so conversations about whether we have time to get something done before the deadline are much more focused.</p><p>After the launch, you no longer have the old site for comparison. So you need to be clear about what ‘good’ looks like.</p><h3>Vision: No next Next</h3><p>The vision for our technology is that we make our tech sustainable.</p><p>Good is a healthy codebase that is simple enough for new starters to understand and for us to maintain, that is supportable and operationally reliable, delivers a good user experience and allows us to maintain and increase our ability to add value to the customer and the business.</p><p>Bad would be the tech drifting so far off track that we end up in a position where we have no choice but to do another rebuild; another “Next” project again in a few years, with all the costs associated with that.</p><p>So our vision is <em>No next ‘Next’</em>.</p><h3>The plan to get there: The highest impact steps</h3><p>Once you have the diagnosis and the vision, you need to work out what to do to get from where you are to where you want to be. What are the activities with the highest leverage? What are the things we should do now that will make other things easier later? What are the things that if we don’t do them now, other things we need to do later will be impossible?</p><h3>How we worked out what to do</h3><p>Sometimes, once you are clear on the vision, it’s obvious what the next steps are. Often, however, you need to do some work to get there. Here are some things you can do to help:</p><ul><li>Listen to the patterns in what people say. When I joined the team, I had a one-to-one conversation with each of the engineers, to ask them what was going well, what was going badly (or was about to go badly) and whether there was anything they thought I should know. Some clear patterns emerged from those incredibly useful conversations.</li><li>If you have a specific questions, surveys can help. For example, we wanted to find out what areas of code people were most afraid of, so we sent out a survey to ask that question, and why.</li><li>For general patterns, the <a href="https://labs.spotify.com/2014/09/16/squad-health-check-model/">Spotify healthcheck</a> is very useful. We send this out every three months, and can see clear patterns which help us prioritise.</li><li>Early on, I gathered the senior engineers together and we had a session where you lay out cards on the floor to identify priorities. (<a href="https://www.annashipman.co.uk/jfdi/russells-strategy-advice.html">I explain a bit more about how to run that session here</a>). This is a really useful exercise for surfacing things you haven’t thought of, understanding dependencies, and making sure that you are all on the same page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WlXKQRrTb2G5hhEo" /><figcaption>People laying out cards to identify priorities</figcaption></figure><ul><li>Look for artefacts, for example technical principles, dashboards, architecture diagrams and runbooks. These are high leverage things that help make sure everyone has a shared understanding. If they are missing, getting some of those in place is likely to be an early priority. If they are in place, how frequently are they updated and are you sure they are current?</li><li>Finally, a live site is different from a site in development. There are areas that won’t have been a priority before the launch that are for a site in production. For example, how does out of hours support work? How do you handle critical security vulnerabilities? And how do you act on — or even get — customer feedback?</li></ul><h3>It’s all about communication</h3><p>The most important part of a strategy is making sure people know what you’re doing and where you are going. You can have the best vision and best strategy but if no-one knows about it, it’s worthless.</p><p>Everyone in the team needs to understand where we are heading so they can make decisions about what they work on so we all get there.</p><p>People outside the team need to know our strategy so they can see how it helps the whole FT with our goals as a company, and so they can influence it if they have information that we need.</p><h3>Communication takes a lot of effort</h3><p>Communicating the vision and strategy involves communicating your message in lots of different ways: emails, presentations, small group discussions, posters, etc.</p><p>You have to say the same things over and over again, until you are bored of the sound of your own voice saying them, and then even more; because every time you say it, it will be new to someone. Perhaps they missed the last meeting, or weren’t listening, or are new. But if you want people to know what the strategy is, you need to keep talking about it.</p><p>Communication is harder after the launch because the vision may not be as clear, and some of the people involved in the launch will have moved on to other projects. So it’s important to put even more effort into how you communicate your vision and strategy.</p><h3>It isn’t too late to get back on track</h3><p>If some of this sounds familiar to you it’s worth letting you know that it might feel like it’s too late for you to get out of the difficult teenage years, but it isn’t. FT.com had been live for 18 months when I joined and we are doing well in getting back into a good shape. I hope that some of these techniques will help you, and I’d love to hear your stories about how you got your tech strategy back on track.</p><h3>More detail about our tech strategy is on its way!</h3><p>In my next post, I’ll talk in more detail about our <em>No next Next</em> tech strategy and how we are doing.</p><p>This is a blog post version of a talk I did at <a href="https://2019.continuouslifecycle.london/sessions/launch-difficult-teenage-years/">Continuous Lifecycle Conference London</a>. You can <a href="https://youtu.be/EkfqgQXfEv8">watch the video here</a>, or <a href="https://www.slideshare.net/annashipman/after-the-launch-the-difficult-teenage-years">see the slides here</a>.</p><p>And if you are interested in joining us on this journey, <a href="https://roles.ft.com/">we are hiring</a>!</p><p>*****************************************<br>You can find Anna on Twitter at <a href="https://twitter.com/annashipman">@annashipman</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f42eb94a424" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/the-difficult-teenage-years-setting-tech-strategy-after-a-launch-7f42eb94a424">The difficult teenage years: Setting tech strategy after a launch</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>