You’ve rolled out OKRs, but is the system actually working?
In this masterclass, OKR expert Tim Newbold explains what separates great OKR teams from the rest. He has helped organizations including Domino’s, Greenpeace, Matomo and the National Registry of Emergency Medical Technicians turn OKRs from a quarterly exercise into a real operating rhythm.
This isn’t an OKR 101. Using his OKR Accelerator Framework, Tim shows how leading teams cut down to fewer priorities, turn strategy into measurable outcomes and keep momentum with short weekly check-ins. He also explains why leaders should coach rather than control, and why hitting 100% of your OKRs may be a warning sign.
Emre Ok · 0:04
All right, we are live. Hi, everyone, and welcome to the OKR Masterclass with Tim Newbold. It's so great to see you all, and a special welcome to all of your AI note takers. We've missed them dearly. Tim, hi, how are you doing?
Tim Newbold · 0:28
Good day, good afternoon, good evening and good morning, depending on where you are in the world. How are we doing?
Emre Ok · 0:35
Exactly. We're spread across all sorts of time zones, and I'm so excited to be here with all of you, and with Tim and Tim's fresh haircut. Loving the vibes.
Tim Newbold · 0:49
Just for you guys.
Emre Ok · 0:52
While we wait for people to roll in, let's do a quick warm-up round. This is the OKR Masterclass, a conversation about how the best teams in the world do OKRs differently. But let's set a couple of things straight first, because while OKRs are a well-known, widespread term these days, there are a lot of misconceptions around them. So, Tim, let's start with this: what are OKRs not? What are they mistaken for most of the time?
Tim Newbold · 1:31
How long have we got for this question? Number one, it's not a project tool. I often see people say, "Oh, it's how we create a to-do list." That's definitely what it's not. It's not a way to control people or force them to work in a certain way. And it's certainly not a way to get an organization to focus on lots of different things and get distracted. It is none of those things. If you like, I can try and answer what it is.
Emre Ok · 2:07
All right, Tim, you have a tight three minutes to tell us what it is.
Tim Newbold · 2:14
Let me see if I can do it faster than that. OKR is simply a way of thinking about the impact you're making as a team. It's what we call outcome thinking: what are you trying to achieve, and why is it important? It helps organizations focus, and at the end of the cycle, it lets them measure whether they were successful or not. That's why the big tech firms and a lot of leading organizations use OKRs, or objectives and key results. Hopefully you've all come across them, because this is a masterclass, not a 101. Its power comes from thinking about the outcome and getting everyone moving towards it, and today we're going to unpack a bit of the magic around doing it the right way.
By the way, I'm loving the comments in the meeting chat. Please jump in, add questions and commentary. That's a really good way for me to get feedback as we go. Hopefully I've done an okay job there, Emre.
Emre Ok · 3:10
I'll just say to everyone who's come here: you're in luck, because I haven't seen anyone better than Tim at breaking down complex situations and terminology in the world of work. OKR Quick Start is such a fitting name for your organization.
As people are still rolling in, let me walk us through what this session will look like. Right now we're in the welcome phase. That will be followed by the OKR Masterclass with Tim Newbold, and then our very own Carlos Santana will give you a demo of Teamflect's OKR module. And it won't just be theory: Tim is going to walk you through real-world cases of how some of the best-known companies in the world have succeeded with OKRs. After the theory, we'll look at the practical side and how you can apply all of this using the best HR tech available. Then we'll have a Q&A session where Tim, Carlos and I will try to answer all of your questions.
If you run into any technical difficulties, our very own Casey will be in the chat, and you can also reach her at [email protected]. We also have a live Q&A running the whole time as a Microsoft Teams feature, so if you have any questions during the webinar, submit them there and we'll answer all of them.
As Tim said, we love keeping these interactive, so feel free to send messages in the chat. There will be polls throughout the webinar, so please take part. And if you stick around, there will be a giveaway at the end, so we'd love for all of you to stay for that.
With all of that out of the way, before we dive in: Carlos, why don't you come and say hi as well?
Carlos Santana · 5:53
Hello, everybody! Thanks for the introduction. I'm super excited to walk you through the demo in a bit. Just popping in to say hello.
Emre Ok · 6:03
Loving it. Tim, I think this is the right time to give the floor to you.
Tim Newbold · 6:16
Let's do it. Shall I take over presenting?
Emre Ok · 6:20
All yours, sir.
Tim Newbold · 6:23
There's always that awkward moment where I try to click the right thing. I think we can all see the screen, so let's get right into it.
A bit of background first. When I started talking to Emre and Teamflect about today's session, I wanted to make sure it wasn't going to be a tool pitch. He said no, it's about the lessons, and we talked about how the demo would show the practices I'm covering. And these practices aren't something I've come up with in theory and never applied. This is what leading organizations use. The stories are from our own customers applying this, not case studies I've only heard about. It's what I've lived and breathed, and it's all about accelerating how OKRs work for you.
We're a few minutes in, so I'll skip some of my warm-up questions. As Emre mentioned, we have a giveaway at the end of this session: a prize draw with a random name picked from everyone who's still here at the end. If you have to drop off early, I'm sorry. For everyone else, two people will win just under $1,000 worth of value, covering everything from leading OKRs to product management, plus classes from thought leaders and authors from around the world. We'll send the details to the winners at the end.
Emre Ok · 8:08
Amazing. Casey is sending the form to register for the giveaway in the chat right now. And even though we skipped the "where are you from" question, we did get an answer: Leanne from Sydney, Australia. Welcome on board.
Tim Newbold · 8:25
Good to see some Australians representing. Let's all add in the chat where we're from. We've got Poland, good evening to you. Wisconsin, Texas, excellent. USA, Canada. So we've got some afternoons and evenings here.
Emre Ok · 8:46
Grand Rapids, Michigan, that's where half my family is. Great to see Michigan represented.
Tim Newbold · 9:00
Amsterdam, Netherlands. My best friend is living there at the moment. Amazing to hear where you're all from.
One of the biggest complaints I hear from organizations is: "We're so busy, we're doing so much, but we're getting nothing done." I ask why, and they say they think they have enough people, but it just isn't working. When we get into the detail, we realize people are managing multiple projects and taking on far too much.
There's a lot of science behind this. I'm a bit of a research geek, so if you're interested, drop me a note afterwards and I'll send you some information. When we look at the cost of context switching: with one project, I can go deep, and the only time cost is things like a lunch break. With two projects, nearly half my time goes to context switching. With three, over half my time is context switching. I pick up a piece of work and think, "Hang on, what was I doing here? Who did I need to talk to?" That's all wasted effort.
This is where the power of OKRs comes in: getting us to focus on what really matters. It's not an easy conversation to have, but it's the one that gets you where you need to go.
A little about me, without boring you: I've worked with organizations around the world, including Greenpeace, HROnboard, Domino's and Matomo, the biggest analytics platform out there after Google. They all had great results, and if you apply these concepts, you'll see incredible benefits too.
Today's framework is an accelerator model. I'll drop the link in the chat so you can download it right away. Fill in where you think you are today, and take notes on what it would take for you to move one score higher. We'll cover three areas: focus (how we focus on what really counts), strategic context (one of the biggest things for team members to understand what they're doing and why), and rhythm (how we embed OKRs into the heartbeat of the organization so we can check in, track them and see the impact).
I'd also love you to join me in this Slido poll for some live activities. Use the QR code or the link I'm dropping in the chat. My question is: how well are OKRs working for your company right now? Are you crushing it, is it good, just okay, not good, or a dumpster fire?
Quite a few of you haven't started. Lucky you, you're about to kick off on the right foot. A good number are "just okay." And it looks like there's about one dumpster fire, so I'm sorry. I'll share my LinkedIn details at the end, and you can always reach out to me.
Emre Ok · 12:45
That's what we do. We put them out.
Tim Newbold · 12:48
That's it, we're here to put out the fires. So a good part of the group is "just okay," and we can boost you up to "good." For those who haven't started, this will set you up for success.
There are a few signs of a healthy versus an unhealthy OKR practice. When it's not working, OKRs are set and forgotten. You have three, four or five OKRs. Check-ins are just task updates, and nobody talks about the outcome you're trying to achieve. OKRs cascade down. (I'll unpack that language in the leadership section, because you might ask, "Shouldn't we be cascading?" We talk about aligning, and there's a difference in thinking.) Confidence never moves, or you never set a confidence score at all. And there's no scoring and no retro at the end: you set them, you miss them, and you move on to the next quarter.
When OKRs are working well, you review them weekly, and the executives do exactly the same. You ideally have one objective, maybe two at a stretch, with three to five key results measuring its success. You talk about problems, not tasks. Leaders step in to help early, so when there's an issue, support arrives right away. And at the end of the cycle, you review how it went and what you could do differently next quarter. If you have that rhythm down, you're looking pretty successful.
So the first area is focus with fewer OKRs. For those of you already doing OKRs, how many do you have per team: one, two to three, three to four, or five plus?
Oh, folks, we're going to have to have a conversation today. But this is good, and it's worth solving. Most of you have a whole bunch. To those with only one per team: that's magic, good on you. We've got some work to do here.
This is one of my favorite quotes. People think focus means saying yes to the right thing. What it really means is saying no to all the incredible ideas, the ones that keep you up at night, because something else is more important right now, or something needs to be brought to a conclusion. That's the big mindset shift: focusing on impact and narrowing down what you're trying to achieve.
Steve Jobs was incredible at this. When he came back to Apple after John Sculley's era, they had all sorts of products, including printers. He cut the product line right down to a couple of Macintosh computers. They went back to basics. Today Apple has a wider range of products, but they're all closely related. They don't make a printer or an Apple desk. They've been tempted, as with the Apple car, but couldn't see a way for it to fit, so it was dropped. That's the kind of clear decision you need to make as a business.
Let me share a quick story about Domino's. When I started working with them a few years ago, the chief people officer who brought me in said, "We're done with OKRs. They're not working. People hate them. It's over." I was sad to hear that, because that's not how it should be. They said, "We know, and that's why we're talking to you. This is our last-ditch attempt." They'd had training and worked with other tool providers, not Teamflect, which was one of their mistakes.
There are two Domino's, by the way. Those of you in America: this isn't your Domino's. I worked with Domino's global, which covers Europe, Asia and Australia. I joined their exec meeting, where they said they'd check in on their OKRs this time, which told me they didn't normally do it. They pulled up a page with seven OKRs, each with multiple key results. Imagine getting through that in an executive meeting with other topics on the agenda, maybe 20 to 30 minutes for OKRs, and 50 or 60 separate items to look at. There's no way to have a meaningful conversation about all of that.
So we started cutting it down. Some things were important for the organization, but not critical at the exec level, and didn't need to be communicated to everybody through an OKR. People often say, "If it's important, we want to capture it in an OKR." OKRs are a great communication tool, but if you dilute them with too many, you lose the impact. Over a number of quarters, we got them down to one OKR. In the quarter they focused on that single OKR, they had 30% sales growth. That's such a telling example of the impact brutal focus can have. The exec team checked in on that goal every week, and that's what got them there. The proof is in the pudding.
To make a goal work well, you also need a team collaborating on it. So the first point is focus, and the second is different parts of the business working together. This example is from engineering, but it could be a call center team with people from different parts of the call center, or a call center team working with legal on something that requires legal involvement. The concept is: get focused, bring a team together around solving that problem, and make sure the team is cross-functional so it has everything it needs to succeed. That's one of the big lessons I want you to take from today. OKRs should pull a thread through your organization and bring people together. I'll share another example of that later.
Tim Newbold (continued)
Next, we want to align through context. The first area was focus: have one thing to focus on. But what are we focusing on? That's where it can get unclear. Is it a list of ideas? Different things we should do? We want to get down to what really counts.
Let me draw a quick distinction between a few terms. We've all heard of vision statements. The vision is where you want to be in the future. The gap between where you are today and where you want to be is generally filled by strategy. The strategy might get you all the way there, but typically it's one step on the journey.
A strategy is a diagnosis of where your organization is focusing, what you're trying to achieve, and what you're not focusing on. That last part is a big piece of strategy. It should be unique to you, not something generic that could apply to any other organization. It describes your own plan and your own diagnosis of what's happening in your industry.
I know a lot of companies have a "strategy" that's a house diagram: success on the roof, then pillars like people, customer and experience. I hate to break it to you, but those aren't strategies. If you're an exec here, you need to communicate strategy in the way I've described. That's how you make the biggest impact.
So where do OKRs fit into this picture? An OKR takes a valuable slice out of that strategy. The context leadership needs to provide is: what's the right thing for this team to work on right now? We talk about problems to solve. Some people say that sounds negative, but as a business, you solve problems. You solve problems for customers or whoever uses your services. It's the nature of business: an endless set of problems to solve, and that's how you create value.
The problem might be that not enough customers are coming in the front door. It might be that customers aren't converting once they arrive. It might be that your call center is too expensive and takes too long to serve customers. Whatever the problem, the challenge is being very clear on what it is and why you're solving it. Setting that is the role of leadership.
Here's the structure we talk about. Strategy, mission and vision sit at the top. The problems we want to solve are the link to our objectives and key results, and then to the work we do. As I said at the start, an OKR is not a task list. A key result should never be about delivering a particular project. It should describe the impact: which number are you going to move?
Say you launch a project to reduce the time it takes to answer calls in the call center. Great. Remove the project name, talk about the number you're trying to reduce, and get everyone focused on that. Sure, you might have a project to put in a new phone system. But maybe we also need to train our people. And even as an individual, if I know we're trying to handle calls faster and stop customers calling back because their problem wasn't solved, I'll focus on serving the customer better on that call and checking before I wrap up: have I solved all your problems? That moves the needle too. That's how you unlock the power of the organization: everyone working on the problem together.
I couldn't run an OKR session without showing an actual OKR, so here's one to give you a taste of what good looks like. You can read it yourselves, but I want to point out a few things people often miss.
First, strategic context: why this matters. This is from a bank, based on a real OKR I worked on (the business has since been sold, so I can share it). We wanted business customers to get set up quickly. The problem was that they kept getting stuck, for example by having to go and get extra documentation. That's the strategic context. Analysis showed people were being held up during onboarding, which made them drop off. So we wanted to increase how quickly customers were up and running and transacting.
Notice that none of the key results say "finish project X" or "build this web page." The OKR only describes the numbers we want to move. Each key result has a starting metric at the beginning of the quarter and a target for the end of the quarter. We have three months to hit it. What happens if we don't? The whole team gets punished. No, that's a lie, the team doesn't get punished. I'll come back to that later, but here's a hint: we typically want to see about a 70% success rate.
So what matters is clear context (why this matters) and key results with a starting metric and a target metric. A tool like Teamflect captures all of this for you, including a description field where you can explain why the OKR matters. Some weaker tools don't let you do that, but most will give you this structure.
Once a team has context on what it needs to achieve, it doesn't help if they can't make changes, don't have permission, or need approval at every step. You need to create empowered teams. What's an empowered team? First, cross-functional, as I mentioned: people from across the business coming together. Keep that team together as long as possible, at least until the problem is solved. If a problem can be solved in a couple of weeks, it's probably not an OKR. But for a meaningful business problem, perhaps broken down so you can chip away at it over several quarters, you want a durable team working together.
Second, strategic context, which we've covered: where we're going and why, which problems we're solving along the way, and any data or business context that helps diagnose the strategy clearly.
Third, clear objectives. Look up Google's Project Aristotle, which studied what makes teams high-performing. Number one was psychological safety, which is a big part of an empowered team. But they also found clear goals mattered. That's been proven again and again. In this case, the clear goals are OKRs.
Finally, true accountability. We want people accountable for results. We don't just say, "We didn't move the needle, that's fine, on to next time." We also don't berate them. We hold people accountable to the numbers, and if we miss, we dig into why. That's enough to push people to improve and optimize. We don't need to give incentives, rewards or bonuses for achieving OKRs, and we don't need to punish people for missing them. It's about learning and improving together as an organization, and that only comes from empowered teams.
Now, an interesting AI example. I couldn't run this session without mentioning AI, Emre.
Emre Ok · 27:01
It would be sacrilege, Tim, if we didn't bring AI into the conversation.
Tim Newbold · 27:06
It would. People would be waiting until the end asking, "But what about the AI?" So, this is a real example from one of our customers. They're mid-flight on this work, so I can't name them, but they said I could share the case study. They run a medical learning website with thousands of visitors a day, and they wanted to help people find content. They didn't do much research beyond that. They could see how many people came to the page and how long they stayed, but not much more. So they built an AI system: a small chatbot on their content pages.
That's when the numbers started looking strange. They had 700 free learning resources, a huge library for people to trawl through, and about 90% of visitors came from Google, so they were searching for something and landing on the site. There's a hint there of where this ends up.
They ran the chatbot for about two months and improved it seven times, with lots of experimentation and testing. What they found was that only a fraction of people used it: about 0.2%, or one in every 565 visitors. That was 158 chats in total, and usage dropped over time, meaning people were becoming less engaged.
To be fair, they did OKRs somewhat right. They had clear numbers, they were checking in on them, and they were iterating. But were they solving the core problem? This is where the best OKR teams in any organization stand out: they're very clear on strategic context.
The data was already telling them what people were trying to do. Visitors came from Google after searching for a specific term, so most of the time they were landing on the right page. Almost nobody used the library search: about 10 searches every three months. And when people did use the AI, they asked deeper questions about the content. You might be on a page about a certain radiography procedure, and the questions were, "How do I hold the probe?" or "Is there a procedure for cleaning the probe afterwards?" Questions related to the article but not covered by it.
That gave them a real insight. The tool wasn't needed to help people find information on the page. It was needed to help them go deeper into the topic. That's where the real magic started. I can't go much further because it's a live example, but they've honed the tool to do exactly that: "You're on this page; here's how to enhance your learning on this topic, and here are common related questions." It even suggests things proactively: "You're looking at this page, so you're probably after this piece of information."
If they'd looked at that data beforehand, they'd have had clear context on why people were coming and what problem to solve. The problem wasn't a chatbot to summarize the page. It was helping people find more in-depth information.
So before you set your OKR, make sure you clearly understand why this is a problem. Do some discovery in the problem space so you know the numbers. You don't necessarily need to know the answer. In fact, you generally shouldn't have a solution like "we're going to build a chatbot." But you do need to understand the problem. Top organizations do this really well.
I'm curious: how much effort does your organization put into setting context today? Do you make goals up on the fly? Do you always have a result in mind that you're heading towards? Are you clear on the problem? Or is context a top priority for leadership, always defining the problem and why it matters? If you dropped out of the poll, here's the link again. I'll give you a moment.
So: "We always have a result in mind," "We back our goals up," "We're always clear on the problem." Those are all good, and it's a mix. The 5% of you with a leadership team that prioritizes context (what the problem is, who we're solving it for, why it matters, ideally with a result attached) are incredibly lucky. That puts you in a very strong position.
That's the leap. The default is having a result in mind: "We're trying to make this impact." The big shift is going deep on why we're doing it, what the problem is and what the data tells us. And it's leadership's responsibility to help you get clear on the problems you're solving as an organization.
Tim Newbold (continued)
So we've covered focus: if we choose one thing to move the needle on, we'll be very successful. And we've covered getting deep into context and what we're trying to achieve. To make this last, we need a rhythm. Get the rhythm right and you have the trifecta, with all the pieces in place.
There's nothing magic about it, and it looks different in every organization, but let me walk you through one version of the rhythm.
OKR setting actually starts at the mid-cycle review. That might sound odd, but remember this is a continuous cycle. The mid-cycle review happens halfway through the quarter. That's when we look at how we're progressing on the current OKRs and discuss what we should focus on next cycle. We're not coming up with the next OKR at the end of the quarter; we're discussing it in the middle of the quarter before. From there we have discussions, run surveys and do data research to land on the right OKR.
Then we get into reset territory. At the end of the quarter, we score our current OKRs, run a retrospective on how we did, and reset the company OKR. The leadership team refines it, makes sure it's ready to communicate (ideally sending it out straight away for feedback), and sets the strategic context: here's where every team fits in. If you're a large organization, that context setting is what we mean by alignment, rather than a cascade where "my boss's key result is my objective." That structure gets messy and forces you to work within the constraints of the org chart instead of focusing on the problem, which may need teams from different parts of the organization.
Once the company OKR is set, every team goes off and sets its own OKRs. This is designed to be lightweight and fast. There's no staggered approval process that goes all the way up the chain. It needs to be quick and efficient.
This next part comes from defense, where it's called a back brief. For OKRs, we call it the playback. In defense, you're given a mission and told to figure out how to make it happen. You bring together a cross-functional crew, maybe radio operators, marines and pilots depending on the mission, and map out the approach: where we'll drop people, when we'll make a radio call, and so on. Then you play that plan back to leadership. Even if leadership could write a perfect plan, it wouldn't be executed perfectly. But if the team has come up with the plan themselves, they're clear on it.
The OKR playback works the same way. The team comes back and says, "Here's what we heard the company OKR is, here's the context you gave us, and here's what we've come up with." If you're 100 or 200 people, you can typically review every team's OKRs in a one-hour session. Beyond that, you'll need to think about structure, because it won't be as efficient, but there are a few ways to run it.
Then we kick off the quarter. That's the whole rhythm for setting OKRs, and at mid-cycle we check in again, pressure-test the OKRs to make sure we're making progress, and talk about next quarter.
But here's the thing: if you only check in on your OKRs once, you'll barely make progress. That's where the weekly check-in comes in. It's maybe the second most important part of this whole structure. I'd say choosing what happens next quarter is the most important, because you're preparing early. But checking in on progress is absolutely critical, so let's unpack it.
In the weekly check-in, we get together as a team and say: here's what we're trying to achieve and the metrics we're trying to move. Where do you think we'll land? That's the confidence score, and I like to keep it simple. Say we need to make 100 sales this month, and I think we'll only get 50. That's halfway, so my confidence score is 50%, or 0.5. Someone else thinks we'll get 70 out of 100, so their confidence score is 0.7. The easiest way to think about it is: based on everything we know today, where will we actually land?
There's often a lag. Metrics take time to move. Halfway through the quarter, you've only had half a quarter to make sales, so the numbers won't be all the way there. But as a team, you want to know: does this feel like a good quarter? Are the new sales scripts working, or are we having issues? And if it feels like we're going off track, we want to talk about how to boost those confidence scores.
Here's an example executive meeting structure that you could tailor to your team. My key tip: this should not be a new meeting. If you're an executive team, it should be part of your existing weekly executive meeting. The OKR check-in should take 15 minutes at most. You cover the confidence scores and how you're tracking overall, what was achieved last week, the focus for the week ahead, and what's blocking your teams (or you, if you're a single team). It's about getting things unblocked.
The rest of the structure is fairly self-explanatory. What you don't want is to go too deep in the check-in. If you're stuck, have a separate conversation in the same meeting about what you need to do to move the needle. Otherwise your OKRs can quickly grow from a 5 to 15-minute topic into a one-hour topic that eats all your other agenda items.
Another point, which ties back to the AI example: make lots of small improvements. Don't work for a whole quarter and release at the end. If you're an HR team launching a new training program and you wait until the end of the quarter, you won't see the numbers move. Get it out early. Maybe run the training for one small part of the business, or only one part of the training for one specific problem. For a product team, it might mean releasing a basic version of a feature to get customer feedback. It depends on your business and your team, but break the work down. Big increments move the needle slowly; lots of small releases let you see it move.
Also, focus on the high-value work early. Say an HR team wants to run leadership training, and team members are complaining about the quality of one-on-ones. Focus on one-on-ones, not the whole leadership package. And if one part of the business has the biggest issues, run the training there first. That gives you the biggest benefit early, and once people are happy, you can roll it out more broadly. Teams that already run great one-on-ones won't show a big improvement, and their satisfaction scores won't rise much. So focus on the problem areas.
We're on the home stretch, and I'll move quickly through the last few slides because I want to see how this works in Teamflect. A strong tool that supports this way of working is what unlocks everything.
This is the National Registry, another organization we work with: an association in the US that handles paramedic certification. They do amazing work. One team had been trying to reduce the number of support issues for years. They'd even started using OKRs, but the numbers weren't moving. It was the weekly check-in that made the OKR a priority and part of their regular discussion, and that's when they saw the needle move. Operational teams are always hectic and busy, so that focus is really powerful. We saw a massive impact just from applying that simple weekly practice.
Quick question: how often do you check in on your OKRs right now? If you're not doing OKRs yet, skip this one. I should have added a "not doing OKRs" option.
Weekly or bi-weekly, monthly, none. Okay. Really? Cool. So there's a simple fix: get your OKR check-ins happening weekly, and you'll be looking fantastic.
I'll move through the next few slides quickly, because they're about the role of leadership, and I've already covered a lot of it. But there are a few key call-outs.
Bill Campbell is known as the trillion-dollar coach. He coached Steve Jobs and the Google founders, and ran Intuit for a number of years. He said coaching is no longer a specialty: you can't be a good manager without being a good coach. That's part of strategic context. A strong executive team gives people context, not control, and helps them solve problems as they go. They coach people to reach their destination by asking powerful, reflective questions that help them unlock themselves, instead of handing them the plan. Conditions change, people will get stuck, and they need to be able to work out how to get around roadblocks.
And when there are genuine roadblocks in the organization, leaders and executives need to listen to their people: where are things hard, where are the politics? They need to remove those roadblocks and create psychological safety. Big organizations like Google and Facebook give team members small missions as part of their development. They're still valuable missions, but they're challenges that help people grow within a safe boundary. Success isn't only achieving your OKRs. You can fail and still succeed through learning, and that's what they want to see.
This is a big theme with OKRs. As I mentioned, a 70% success rate is critical, and Inteleos nailed this. They had to work with their board, who come from a medical background. Their world is radiography equipment, where everything is precisely diagnosed, statistically based and exact. There's no "stretch and fail": you don't want a mammogram where a stretch goal means missing an important detail. That's not how that world works.
But if you want to innovate and succeed, stretching is exactly what you need. So they took their board on a journey until the board came to expect 70% as the success target. Whenever teams were achieving well above that on average, the board would ask, "Why are we hitting 90% of our goals?" The organization realized they weren't stretching enough and were setting the bar too low. It was a big journey to take the board on, but they got there, and you can too. Set 70% as success in your team. If your executives expect 100%, work with them to understand that innovation never comes with 100% success. That's the point of innovation: some of what you try should fail. It's a journey, but a worthwhile one.
After this session, we'll send you a thank-you gift from me: an accelerator pack. It includes the worksheet, an AI OKR coach (so you won't need me anymore, but it's very powerful), an OKR facilitation kit, and a book on how to launch OKRs quickly, hence OKR Quick Start. My hope is that with this kit and the topics we covered today, you can apply these practices right away. I've given you tangible examples of practices that unlocked massive growth and helped organizations get the most out of OKRs. Let's look at the tool next, and then, Emre, we'll jump into Q&A. Does that sound good?
Emre Ok · 45:33
Perfect, that's the plan.
Tim Newbold · 45:35
Love it. One last note from me. I'll drop some links in the chat, and if you want to reach out to me, I'm always keen to talk. Oh, that shouldn't say "strategy call." Sorry, that's awkward. It should be my LinkedIn. I'll drop my LinkedIn and my YouTube channel as well. That's the peril of asking Claude to make a wrap-up page for me.
Emre Ok · 45:54
Whoops, how did the strategy call get there?
Tim Newbold · 45:57
That really wasn't meant to be there. Anyway, the links in the chat are for my LinkedIn. If you have any questions, please feel free to reach out afterwards on LinkedIn. I'm always happy to chat. Ask your questions in a moment as well. I'll hand back to you, Emre.
Emre Ok · 46:15
Now, I'll say this: what you just got, everyone, was Tim Newbold Lite. Diet Tim Newbold. Tim Newbold in 45 minutes. In the chat right now, there's an entry to a raffle for a chance to join full training sessions with Tim Newbold and OKR Quick Start. Scan the QR code to enter. We'll draw it after the live Teamflect demo, so make sure you sign up and stick around until the end.
We also have a live Q&A inside the Teams meeting. After the demo, we'll move into the "lonely hearts and night owls" part of the webinar, where Tim will answer all of your questions, so send them in. We don't get this chance often.
Now let's put all that theory into practice and see how you can apply it with the right OKR software. To show us, I'll pass the floor to our very own Carlos Santana.
Carlos Santana · 47:29
Thank you so much, Emre. Hello, everyone. Let me share my screen and we'll kick things off. Can you see my screen?
Emre Ok · 47:39
Yes, sir.
Carlos Santana · 47:40
Perfect. What you're seeing is what people see when they access Teamflect in Microsoft Teams. On the left, you can see the different modules that come with Teamflect. For this demo we'll focus on OKRs, but I want to highlight that if some of these modules aren't relevant to you, the platform lets you turn them off depending on your needs.
This dashboard shows all the up-to-date actions we need to take and any information we need to be aware of, especially our current active objectives and where we stand on them.
When we click into the OKR module, we can see all of our objectives laid out, with progress percentages, statuses, start dates and due dates.
Creating a new objective is very straightforward. We'll use "Test objective" as the title. You can add a description, which is optional by default but can be made mandatory. You can also use AI to help generate descriptions, whether you want to make them SMART objectives or polish the language a bit.
Objective types help you structure how OKRs are mapped across the organization. They can be company-wide, department-level or individual, and you can customize them if your organization uses different terminology.
When you create an objective from scratch, you're added as the owner by default, but you can add other people. If you're a team lead, you can add your whole team in one click with this link. If several people on your team have the same key results, you can create a separate objective for each of them. Or, if it's a team objective, you can include everyone under a single objective.
There are several measurement types. First, the classic "reach" type, with a starting point and a target, using percentage, number or currency metrics. If you have metrics you need to stay above or below, you can use those measurement types to set thresholds, define your target, and track the current value over time. There's also a "completed / not completed" type for binary outcomes. And depending on how you align objectives and key results across your organization, you can have progress roll up from key results to objectives. Let me show you what that looks like.
Here's an objective we're working towards: launching HR initiatives based on engagement themes to improve our engagement scores. Below it are the key results. Let's say we want to update the progress on this key result. We're doing a great job and are close to the finish line, at 85% of our target. When we go back, the objective's percentage has jumped up, because this key result contributes a portion of the objective's overall progress.
If you want to save time on metrics that update daily or hourly, you can connect other data sources such as Excel or Power BI, and set up connections through Power Automate or the API. That keeps your metrics up to date so nobody has to update them manually.
Team leads can see all the objectives and key results their teams and direct reports are working on, with views that show real-time updates. They can also drill into each direct report and the objectives they're working on individually.
For company-wide visibility, for the leaders and C-suite on the call, there's a bird's-eye view of how all objectives and key results map across the organization. It makes it easy to spot where you might be hitting roadblocks and need to talk about how to overcome them.
On the topic of AI, you can also use AI to generate objectives. I'll set it up to create some objectives for us. While it works: our AI is great for ideating on objectives and key results, and for pulling data and information. For example, if you want to see which objectives or key results have gone stale and haven't been updated, it can find and highlight them for you. Here you can see it creates most of the template you're looking for, while leaving you the flexibility to make edits. If you want to move forward with it, it makes creating objectives very easy.
For updates and reminders, you can set how often reminders go out to the people using the tool. Here's a sneak peek at how those notifications appear in Teams. People can update their progress right in the card, add comments and hit save, without having to open Teamflect if they don't want to.
Finally, reporting. Managers have all the reporting they need in the tool to track OKR progress at the team level and the organization level. Here's a breakdown of the objectives and key results people across our team are working on, our completion rates, and our average progress.
And that concludes the demo.
Emre Ok · 55:27
Thank you so much, Carlos. And this was just scratching the surface of everything Teamflect's goals module offers. With the Teamflect MCP, you can check on your team's goals and OKRs without ever leaving the AI workspace you use, whether that's ChatGPT or Claude.
But I think we've had enough smooth talking, and it's time to give the people what they want. Without further ado, let's announce the winner of the raffle, live on air. This is live TV, so anything can go wrong. We have a lot of names on the wheel. There's an "RJ" right there, and Tim, I'm willing to bet that person is an Aussie. Let's spin the wheel.
Tim Newbold · 56:45
Usually if they're Australian, there's an "O" on the end, like Steve-O. And it's Jeremy!
Emre Ok · 56:48
Jeremy Sung, you've just won the training session with Tim Newbold. Congratulations! We'll reach out to you directly by email with your invitation. Thank you very much for attending, Jeremy.
Tim Newbold · 57:16
By the way, Jeremy, it's not actually a one-on-one session, but I'm happy to have one with you. You get access to our entire online business school, with hundreds of lessons, including all the core material on OKRs. Emre just twisted my arm there, but we're here to help. If you want to jump on a call and have a chat, I'm more than happy to. Back to you, Emre. Let's do the second draw.
Emre Ok · 57:40
Oh, we're doing round two?
Tim Newbold · 57:42
Why not?
Emre Ok · 57:45
Well, I did twist your arm into making it a session, so that one's on me.
Tim Newbold · 57:51
That's all right. I'll make you join the call as well. I'm happy to have a chat, Jeremy.
Emre Ok · 58:01
Our second winner is Victoria Parkinson!
Tim Newbold · 58:02
Victoria, nice work. Epic, I love it.
Emre Ok · 58:09
I'm beyond happy that we all made it this far, and I want to thank everyone for joining. Now it's time for my favorite part of the webinar: your questions. Oddly enough, we haven't had any questions in the Q&A yet. I think people were just locked in, listening non-stop.
We've reserved time for Q&A, so if you have any questions at all, now's the time. They can be for Tim about the OKR methodology, or for Carlos about Teamflect as OKR software. The floor is yours, and I'll let the awkward silence in while the questions come. If you can't find the Q&A section, it's right next to the chat icon in the Microsoft Teams window.
Tim Newbold · 59:30
We do have a question in the chat. And if you can't figure out the Q&A, just drop your question in the chat and we'll pick it up there. Maybe we can jump into Fiona's question while people add theirs. It's such a good question.
Emre Ok · 59:35
Exactly. Let's read it out for people watching the recording. Fiona asked about balancing operational work with OKR work, and the context switching that comes with it.
Tim Newbold · 59:53
The session was already packed, but I actually had a slide on this very topic. There will always be some cost of context switching. That's the reality of business. The idea is to minimize it as much as possible, and there are a few ways to do that.
Typically, we map out our change-based work, which is your OKR, and your operational work, which is the work that never ends. A simple example is email: your inbox will always be whirring away. But the balance looks different for different teams. On a software team building a mobile app, 80 to 90% of the work is change: building something new to drive an outcome. That's the OKR and your focus time. A bit of context switching on the side, like handling support tickets, has minimal impact, because it's more like an 80/20 split than 50/50.
For HR, which Fiona just added in the comments, it's trickier and depends on the part of HR and the size of the team. At Domino's, there was a training team in HR, and training was all they did. If you're a 40-person startup, you might be a chief people officer with an assistant. So it looks different.
Typically, some HR teams act as business partners working with different parts of the business. They can share a goal: what problem are we trying to solve? Much of their work should move towards solving it. When they talk to people around the business, maybe about leadership issues, it should be in service of solving something. For them, context switching has much less impact.
Other teams, especially in a small organization, might spend half their time on leave requests and the other half on increasing engagement. That team naturally has a 50/50 split, so there's some context-switching cost. The wheels come off when it's half leave requests, a quarter engagement and a quarter leadership capability uplift.
On the other end, call centers are about 95% operational. The OKR work is minimal, but context switching isn't a big issue because the work is phone calls, which isn't context switching. So it varies, but the guideline is always: work out what your operational work is and set it as a fixed measure, say 50% of your time. The other 50% is change. Keep that 50% to one piece of work, one OKR. Emre, do we have another one?
Emre Ok · 1:02:57
We've got a two-in-one special from Wendy. Wendy asks: how do you balance team or organizational goals with role-specific goals, and how should we think about OKRs in relation to annual goals and reviews?
Tim Newbold · 1:03:00
Very good question, and there are a few ways to play it. In my experience, team OKRs and organizational OKRs are the most impactful, because they get people working together to drive an outcome, and they should always focus on a business problem you're trying to solve.
With role-specific goals, purely for an individual, it's often harder to measure the outcome. So if you use OKRs at the individual level, keep them a bit more general. Team OKRs should always be metrics. For individuals, you'll have a blend.
Let's stick with the HR example. We're doing capability uplift to improve how our leaders operate, and we have a senior HR manager and an associate working with them. If leadership capability scores increase, did the associate really contribute to that? How would you measure that individual's contribution? What I can look at is whether the associate championed the goal, did a lot of work behind the scenes, put in the effort, and challenged the thinking when people got too comfortable and fell back into just following the bouncing ball. That's a different kind of measure.
So it's harder to measure for some roles. Others are naturally easy. In a call center, for example, you want a very low share of callers having to call back because their problem wasn't solved, and you can set that as a goal. It depends on the business and the role. For me, individual OKRs should be very simple. Use metrics if you can, though it's not always possible, and make sure the person actually has meaningful influence over the key result rather than just being on the receiving end of it. Hopefully that answers the question.
Emre Ok · 1:05:18
And Wendy, if you're using Teamflect, your goals and OKRs can appear right in your year-end performance reviews, like this.
There's a question for Carlos in the Q&A. Warren Carvey asks: "We're brand new to Teamflect and just setting things up. Is there a way to connect tasks or tickets from our Microsoft Planner board to our OKRs in Teamflect? Or can we build task boards right in Teamflect so we can ditch the Planner board?" Carlos, that one's for you.
Carlos Santana · 1:05:49
Yes, you can. Let me share my screen so you have some visuals. You can connect tasks directly to any objective or key result just by creating a new task. And with our Planner integration, updates you make to tasks in either Planner or Teamflect sync both ways. Emre, I might have missed part of that question. Did I cover it, or did I miss anything?
Emre Ok · 1:06:26
You covered it. So, Warren, you can do it either way: sync your existing Planner tasks, or just use the Tasks module inside Teamflect.
Next, a question from Chris Newell: "If we're avoiding cascading OKRs, should team-level objectives support or align with our org-level ones? For a leadership team that wants to see strategic progress across the org, how can we report on team progress if team OKRs aren't rolling up?" All right, Tim, the anti-cascade person is on the hot seat.
Tim Newbold · 1:07:07
I like it. I am anti-cascade, but you've asked a really good question: how do we know everything is adding up? I think it happens in two ways.
First, remember the first rule: focus. Not every team can contribute to one particular thing. This is the trap Domino's fell into: they had seven OKRs because they wanted that roll-up effect, and it diluted their focus. Even at the scale of Alphabet, a massive organization with multiple businesses like YouTube underneath it, there are four or five OKRs at the top executive level that everything else aligns to. For most organizations, you want that one focus.
That's where context comes in. Each executive should understand how their team supports the company focus, and they set the context: "Here's the problem I need this team to solve to help us achieve this company OKR." Through that, everything ladders up clearly to the focus. That's where alignment comes from. You can even say, "Here's the problem I want you to solve, and here's the number I want you to move." That gives the team at least one key result to consider. They'll probably have others. And it should be a two-way conversation: if the team says, "That's not the right key result," that's fine. We want that collaboration.
Teams that aren't part of the core focus won't show that same link. But with a tool like Teamflect, you can still see whether those teams are tracking okay and whether they need support. They might be doing foundational work for future quarters, and that's fine. It's just not the focus right now. You can still check in to make sure things are moving, just not all the time. The responsible executive should make sure that work, which isn't a company-level priority right now, keeps progressing. So you keep momentum and alignment, just not through a layer-by-layer cascade.
One more classic call-out. John Doerr's book Measure What Matters is a great gateway drug, but to be frank, it also teaches some really bad practices. It's due for a rewrite, as there's been a lot of change in how the industry thinks about OKRs. Going way back in my memory, his example involves a sports team: the head coach and the head of marketing. The head of marketing is trying to fill the stands, and the coach is trying to get the best players. What if the best player is widely disliked, has a criminal record, and doesn't represent the organization's values? The coach says, "I just need the scores," and signs them. Suddenly the marketing leader's goal is dead because of boycotts and backlash. That's the classic example of a cascade where people end up fighting each other, and we want to avoid that with OKRs.
I went deep there. Hopefully that answers it.
Emre Ok · 1:10:30
That's what we're here for. That's why this is the masterclass. If there are no more questions, I want to ask you the last one, Tim, because I'm curious. If, by the magic of Teamflect, we had the authority to say, "Tim, you're writing Measure What Matters 2: Electric Boogaloo, the rewrite," what would you change?
Tim Newbold · 1:11:00
There's a lot of really good material in there and a lot of good case studies. What I'd change is a lot of what we talked about today. It doesn't say much about how you track OKRs, how much focus you need, or context setting. I feel like I'm just repeating my talk here, but most of you have heard of OKRs. You know there's an objective and some key results. That's easy to understand. Doing it really well is the hard part, and it's why so many organizations struggle when they start. That's why I'm glad so many of you haven't started yet. Getting this right from the beginning makes your likelihood of success so much higher.
It's very hard. Domino's was ready to put a bullet in OKRs. They hated them, and I had to do a lot of work to turn things around. Now they love them, and they drove massive results, but it was close to the end.
So I'd want the core concepts in the book: really measurable key results, strategic context, and a clear rhythm people can follow, nice and simple, so nobody has to rethink it. I plan my OKRs for the year. I know when the meetings are, and they don't change unless a customer changes theirs and I have to work around them. The customer always comes first, remember. But we have a clear plan, and our weekly check-ins are at the same time every week. I don't have to think, "I'd better check in, set up a meeting, or invite that person." You want it to run on autopilot. Those are the key changes I'd make.
John Doerr is amazing. He was originally at Intel, then became one of the early VCs behind Google. I have a lot of respect for him, but the book needs an update.
Emre Ok · 1:12:43
There's no better way to end than with a shout-out to Big JD. With that, I can hear the Oscars music in my head. This has been wonderful. Thank you all for joining us and sticking with us to the very end. This is the last slide, so if you want to connect with Carlos or Tim and stay in touch, scan these QR codes. If you want to connect with me, well, good luck finding me. No, I'm on LinkedIn as well, as Emre Ok. It was really great having you all here, and this was a great masterclass. That's it from us. Thank you all so much. Good night, and drive safe.
Tim Newbold · 1:13:31
See you next time.

