<?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 Fiona Warner on Medium]]></title>
        <description><![CDATA[Stories by Fiona Warner on Medium]]></description>
        <link>https://medium.com/@fiona.warner?source=rss-9504ae89f250------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*TBLNXy1ISwdg50odZDqVrg.png</url>
            <title>Stories by Fiona Warner on Medium</title>
            <link>https://medium.com/@fiona.warner?source=rss-9504ae89f250------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:16:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fiona.warner/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[Can you set OKRs if you don’t measure anything?]]></title>
            <link>https://medium.com/@fiona.warner/can-you-set-okrs-if-you-dont-measure-anything-d65cb0730cd9?source=rss-9504ae89f250------2</link>
            <guid isPermaLink="false">https://medium.com/p/d65cb0730cd9</guid>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[objectives-key-results]]></category>
            <dc:creator><![CDATA[Fiona Warner]]></dc:creator>
            <pubDate>Sun, 01 Sep 2024 13:27:00 GMT</pubDate>
            <atom:updated>2024-09-01T13:31:59.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Decorative image. Yellow tape measure rolled up messily." src="https://cdn-images-1.medium.com/max/1024/1*02bnjqIfKiPTd9QD8EafSg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@marta-longas-1449108/">Marta Longas</a> on <a href="https://www.pexels.com/">Pexels.com</a></figcaption></figure><p>In 2023 when our company announced the shift from traditional Objectives goal-setting methods to adopting OKRs (<a href="https://en.wikipedia.org/wiki/Objectives_and_key_results">Objectives and Key Results</a>), I was up for the change.</p><p>My partner, who’s got a ton of experience in leadership and operations, is all about OKRs. Me? Well, I was keen, but also feeling a bit like a fish out of water because I’d never worked with OKRs before, let alone led a team in setting them. I searched the internet for articles and guidance on how to set good OKRs, but struggled to find resources that made sense to a beginner and had practical guidance.</p><p>I came upon <a href="https://www.felipecastro.com/">Felipe Castro’s</a> “Beginner’s Guide to OKRs,” which stood out as the best ‘how to’ guide using simple language, explanations and useful do’s and don’ts. That guide, plus chatting with my partner, really helped me get a grip on the whole OKR thing.</p><p><em>Unfortunately Felipe Castro seems to have removed the downloadable PDF version of his book from his site.</em></p><blockquote><strong><em>Tip:</em></strong><em> if you are new to OKRs try googling “beginner’s guide to OKRs” rather than “OKRs”. The resources and content vary, so find one that makes sense to you and where you are in your journey of working with OKRs.</em></blockquote><h3>Challenges I feel with Business or Product objectives, goals and OKRs</h3><p>Whatever format your business is using, your Objectives or OKRs are meant to be ‘stretch goals’ that push you beyond your BAU (business as usual) work.</p><p>When I see business or squad goals and OKRs, I’ve always feel a number of challenges:</p><ul><li>User Researchers struggle to feed into them outside of our normal role of running research. Our work is <em>always</em> aimed at helping squads reach their goals. We struggle to find other non-BAU ways to directly impact those goals.</li><li>The goals and OKRs always seem to be focused on customer success metrics or success related to ‘delivery’ of something. Researchers don’t really ‘deliver’ in the same way, and delivery is often not in our control.</li></ul><p>As a User Research team we mostly focus on qualitative research, and therefore tend not to have metrics for success in the way that product teams might. And if we don’t measure anything, how can you set key success metrics?</p><h3>Choosing our OKRs</h3><p>By the start of the 2023 OKR year, our research team had recently grown from 3 researchers to 11 researchers and an Ops person. So I decided we needed to focus on building good Research Operations foundations to cope with this growth before we took on anything bolder.</p><p>However, our Research Operations function was also new and we lacked any solid measurements for it — or <em>anything</em> we did — which was another reason I thought this would be a good place to start.</p><p>The team’s fast growth and onboarding meant that we were being reactive in our approach to Research Operations (ReOps), and weren’t tracking the success of anything we changed. This lack of measurement presented an initial challenge in setting OKRs.</p><p>I do understand the importance of measuring the ‘right thing’ not just ‘anything’, so I didn’t want us to make up arbitrary measures for success without being strongly tied to a clear outcome or change we wanted to see. I hoped that OKRs would give us the push we needed to start measuring our Operations.</p><h3>Set-backs and successes</h3><p>Our first OKR year is now over, and we are preparing for the next. I’ve learnt a lot and I understand OKRs a lot more now, but I still find them hard to write and set. Especially for a team who [still] doesn’t work with success metrics.</p><p>The past year was a self-taught crash course in the ins and outs of implementing OKRs for the first time. Leading a team is hard work, but leading a team in something that you are new to yourself is a lesson in humility and vulnerability.</p><p>Looking back, I can see a mix of success and set-backs in leading the team in their first year of OKRs.</p><h3>Set-back: I set the O but not the KR</h3><p>I set the team’s Objective, and I wanted them to come up with the Key Results:</p><p><strong><em>Objective: “Strengthen our Research Ops to enable consistency, quality and speed”</em></strong></p><p>I gave them four focus areas (Processes, Templates, Standards, and Inclusive Research) and asked them to come up with a Key Result for each of those that fed into our Objective. This didn’t work.</p><p>Although I had talked them through what OKRs are and how they worked in theory, they hadn’t been on that in-depth journey with me to really grasp how they worked in practice. Likewise, my learning to this point had purely been theoretical.</p><p>The team had great ideas (tasks and initiatives) around those four areas, but they hadn’t nailed down ways to measure those things, and therefore not set any actual Key Results. I realised I hadn’t guided the team well enough in understanding how OKRs are different to goals or objectives, or my own thinking around the four focus areas.</p><p>In hindsight, my approach should have been more inclusive and step-by-step. It would have been beneficial to talk to them about what we could or should be measuring for each of those areas, and what success (outcome) would look like.</p><h3>Success: measuring our Research Operations</h3><p>To get us back on track, I took it upon myself to define the Key Results. I had an idea of what measures we could be using, but wasn’t clear on how we would go about measuring them.</p><p><strong>Key Results:</strong></p><ol><li><strong>Reduce the amount of time spent by Researchers on research admin for repeated tasks by 80%.</strong></li><li><strong>Reduce the time to recruit participants by 25%</strong></li><li><strong>Increase the confidence of the team to run inclusive research to 70%.</strong></li><li><strong>Reduce the time it takes to find and share insights from existing research from days to hours.</strong></li></ol><p>‘Time’ was a prominent key measure as I wanted the team to be able to move quickly and focus more on research and analytics, rather than the admin tasks associated with research. ‘Time on task’ is a common user experience metric so I didn’t imagine that we would struggle to find ways to measure this.</p><p>‘Confidence’ was the metric I chose for Inclusive Research (research with participants with vulnerable or accessibility needs). We didn’t have a clear approach for inclusive research, but I felt that before we could actively run inclusive research we had to really build the team’s confidence, breaking myths and misconceptions. I knew measuring confidence wouldn’t be an exact science, but I knew it’s where we had to start.</p><p>Once I’d defined the Key Results this set a clearer direction for the team. What was left for them to do was to figure out <em>how</em> to measure, and then establish benchmarks to measure against, before embarking on the work to actually meet the target key results.</p><blockquote><strong><em>Note:</em></strong><em> setting a success metric without existing benchmarks can be risky. I wasn’t sure if the targets (Key Results) that I’d set would be easy or tough to meet, but I knew we had to start somewhere to move forward.</em></blockquote><h3>Set-back: Brainstorming the focus areas, not the Key Result</h3><p>As I mentioned, I gave the team four main focus areas: Processes, Templates, Standards, and Inclusive Research. I based the Key Results around these topics, which all fed into our Objective.</p><p>However, by initially giving them these topics to focus on, rather than Key Results, it made it more difficult to move their focus from ‘tasks and initiatives’ to actually trying to improve the Key Result metrics.</p><p>The team came up with good problems to solve for each focus area, but they were still focussing on those ideas as ‘tasks to complete’ without any real reason, prioritisation, or understanding of how it would help us achieve the Key Result.</p><p>This brainstorming exercise would have worked better if we’d been focusing on the Key Results instead of just those focus areas. I’d set this up in the wrong order.</p><blockquote><strong><em>Tip:</em></strong><em> always make sure you have clear and agreed Key Results before you start to ‘solutionise’ how to achieve them.</em></blockquote><p>It took some time and a lot of conversations, but we moved from focusing on tasks to firstly setting up clear measurements and benchmarks. I turned their attention away from the four focus areas, and emphasised that the Key Result itself was the main focus which would help us decide which tasks to prioritise.</p><blockquote><strong><em>Tip: </em></strong><em>With OKRs the focus isn’t on lots of ideas or tasks to achieve the objective; the focus is on figuring out and prioritising which of those ideas or tasks is going to help you reach your Key Result. The Key Result is the main challenge (the ‘problem to solve’, if you like) which determines your success or not. This is the main difference between OKRs and Objectives and something to keep reiterating to the team as you get used to OKRs.</em></blockquote><h3>Success: team collaboration</h3><p>With a bunch of new faces on the team, and most of them working in different cross-functional squads, this meant they don’t usually work together.</p><p>Thanks to our OKRs we’ve had a chance to actually work together for a change. The team has really got to know each other, worked together, and now understand each other’s strengths and interests more.</p><h3>Success: a sense of ownership</h3><p>Research Operations (ReOps) affects everyone in the team directly, and the people we work with indirectly.</p><p>A shared focus of improving our ReOps function has given the team a sense of ‘ownership’ for everything we do, and a chance to have an impact on how we do things.</p><h3>Success: showing what we’re capable of</h3><p>Despite a bumpy start, the team really made some impressive strides and hit most of their Key Results. This is really impressive considering they’d started the year having never worked with OKRs, or each other.</p><p>On this journey, we’ve had some really good chats about what else we could be measuring, what might be coming up next, and what stuff we can let slide for now. It will be interesting to see what we choose to focus on for the coming year.</p><p>OKRs are meant to be stretch goals, and looking back, I think I might have underestimated just how much they could achieve. Next time I hope we can be more ambitious!</p><h3>This year?</h3><p>Our first OKR year is now over, and we are preparing for the next. The OKRs have started to cascade from above, and we’re trying to figure out how to feed into them.</p><p>As always, there is never enough time to do things as perfectly as I might like. With the OKR deadline looming, I may not be as collaborative in the OKR writing process as I would like this year, but I do hope I’ve found a better way of talking about OKRs and finding the right Key Results for us to focus on.</p><p>This is the format I’m going to use to have conversations with my team about our OKRs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m01OnSX6L2Lzy0P4AvwcAg.png" /><figcaption>Table showing area, Objective, outcome, measure, benchmark and Key Result fields to aid our conversation</figcaption></figure><p>I’ll let you know how it goes!</p><p>Our Research Operations has come a long way and continues to evolve thanks to our last OKRs. But we still don’t really measure anything in Research Practice. Something for us to work on!</p><ul><li>If you use OKRs in your qualitative research practice I’d love to hear how you do it and how it’s working out.</li><li>If you’re working with OKRs for the first time, don’t stress. Do your research and reading, talk it through with your team, and give it a go! You’ll soon figure out what works and what doesn’t, and you’ll learn a lot along the way.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d65cb0730cd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>