25 Ways to Combine Working Genius and OKRs

Your team sets clear objectives every quarter, tracks key results religiously, and still something feels off.

The numbers move but the energy does not. People deliver on their OKRs but the work feels like friction instead of flow. You have clarity on what needs to happen, but execution still feels like you are dragging the team across the line every 90 days. The problem is not your goal-setting framework. The problem is that OKRs tell you what to achieve without telling you who is wired to achieve it.

Working Genius solves the other half. It reveals the natural work patterns of every person on your team. It shows you who gets energy from ideation and who drains themselves trying to generate ideas. It shows you who belongs in the activation phase and who should never be the person chasing implementation. (Learn more in the Working Genius implementation guide.)

When you combine Working Genius with OKRs, you stop assigning goals to the wrong people and wondering why delivery feels hard.

UNDERSTANDING THE FOUNDATION

Before you can combine the two frameworks, you need to understand what each one actually does and where the natural overlap sits. OKRs give you the structure for goal-setting. Working Genius gives you the structure for talent deployment. Together, they close the gap between strategy and capability.

1. Know What OKRs Actually Measure

OKRs measure outcomes, not effort. They track whether the business moved forward, not whether people were busy. An objective is the directional goal. A key result is the measurable proof that you got there. Most teams understand this structure but still treat OKRs like a task list with numbers attached.

The gap most leaders miss: OKRs tell you what success looks like, but they do not tell you which type of person is wired to deliver each piece of that success.

The framework assumes that competent people will figure out how to hit the target. That assumption breaks when the person assigned to the OKR is competent but energetically mismatched to the work required. You get delivery that feels like effort instead of delivery that feels like flow.

• Objectives define the destination without prescribing the path

• Key results create accountability through measurable milestones

• The framework works when people know what to do and have the capability to do it

• It breaks when the work required drains the person responsible for it

OKRs are a measurement system, not a motivation system. They create clarity and accountability. They do not create energy. That is where Working Genius enters.

2. Understand the Six Types of Working Genius

Working Genius identifies six types of work that every project requires. Wonder asks the questions that expose what needs to change. Invention creates the solutions and ideas. Discernment evaluates those ideas and decides which ones are worth pursuing. Galvanising rallies people around the chosen direction. Enablement provides the support and resources that make execution possible. Tenacity pushes through to completion. (For a full overview, see the Working Genius assessment guide.)

Every person has two areas of genius, two areas of competence, and two areas of frustration. Your genius is the work that gives you energy. Your competence is work you can do but it does not fuel you. Your frustration is work that drains you even when you are good at it.

Here is what most teams get wrong: They assign work based on skill, not on energy. A talented project manager with Tenacity in frustration will deliver the milestone but resent the process. A strategist with Wonder in frustration will produce the three-year plan and feel dead inside doing it.

Working Genius	What It Does	Feels Like Frustration When
Wonder	Asks why and what if, exposes the need for change	You are forced to question everything for hours in ideation sessions
Invention	Generates ideas and solutions in response to problems	You are expected to brainstorm on demand with no problem to solve
Discernment	Evaluates ideas with instinctive gut-level clarity	You are asked to approve ideas you have no pattern recognition for
Galvanising	Rallies people and creates momentum around a decision	You are told to get people excited about something you do not believe in
Enablement	Provides support and removes obstacles for others	You are stuck responding to requests that feel endless and unappreciated
Tenacity	Pushes work across the finish line and ensures completion	You are assigned to chase down deliverables week after week with no end

When you map these six types to your OKRs, you stop assigning the wrong person to the wrong phase of work. You start placing people where their energy naturally matches the demand.

3. See Where the Two Frameworks Overlap Naturally

OKRs and Working Genius are not competing systems. They are complementary. OKRs define the destination. Working Genius defines who should lead each leg of the journey.

Every OKR moves through predictable phases. You question whether the objective is the right one. You invent the approach. You evaluate which ideas are worth resourcing. You rally the team. You enable the execution. You push it to completion. These six phases map directly to the six types of Working Genius.

Most teams skip this mapping step. They assign an OKR to a single owner and expect that person to carry it through all six phases. That expectation burns people out. The person with Wonder and Invention in genius should not also be responsible for Tenacity. The person with Galvanising and Enablement in genius should not be the one generating the strategy.

The unlock: When you assign different phases of the same OKR to people whose genius matches that phase, delivery stops feeling like effort and starts feeling like flow.

An objective that requires innovation belongs with someone whose genius includes Invention. A key result that requires sustained execution belongs with someone whose genius includes Tenacity. The same OKR can have multiple owners across different phases, and that is not a weakness. That is how high-performing teams actually work.

The natural overlap sits here: OKRs give you the what and the when. Working Genius gives you the who and the how. Stack them and you get a goal-setting system that respects how people are actually wired.

4. Map the Six Types to the OKR Lifecycle

Every OKR moves through a lifecycle. It begins with the question of whether the objective is worth pursuing. It moves into ideation, evaluation, activation, support, and completion. Each phase demands a different type of energy. When you map Working Genius to that lifecycle, you can assign the right person to each phase instead of burning out one person across all of them.

The OKR lifecycle maps to Working Genius like this:

Objective Setting Phase needs Wonder. This is where you ask whether the goal is the right goal, whether it addresses the real problem, and whether pursuing it will actually move the organisation forward. People with Wonder in genius thrive here. People with Wonder in frustration will deliver a goal but resent the process.

Strategy and Ideation Phase needs Invention. Once the objective is clear, someone has to generate the approach. This is where ideas, solutions, and creative pathways get built. Assign this phase to someone with Invention in genius and they will energise the team. Assign it to someone with Invention in frustration and you get generic plans that feel copied from last quarter.

Evaluation and Decision Phase needs Discernment. Not every idea is worth resourcing. Someone has to evaluate which approach will actually work and which ones sound good but will fail in execution. People with Discernment in genius do this instinctively. People with Discernment in frustration will approve things they do not believe in just to end the meeting.

Activation and Rallying Phase needs Galvanising. Once the decision is made, someone has to get the team bought in and create momentum. This is not about managing the work. This is about making people care. Galvanising energy turns a strategy document into a movement. Without it, the OKR sits on a shelf.

Support and Resourcing Phase needs Enablement. Execution always hits obstacles. Someone has to provide the support, remove the blockers, and make sure the people doing the work have what they need. Enablement energy makes other people successful. People with Enablement in frustration will help but quietly burn out doing it.

Completion and Delivery Phase needs Tenacity. This is where the work gets pushed across the finish line. Tenacity energy does not give up when the project gets hard or boring. People with Tenacity in genius will chase the last 10 percent. People with Tenacity in frustration will deliver it and then disengage for a month.

When you map these phases to your team, you stop expecting one person to carry an OKR through all six stages. You start building relay teams where each person hands off to the next at the point where their genius ends and someone else's begins. For practical steps to take after running a Working Genius assessment, see what to do after Working Genius.

5. Identify Which Phase of Work Each OKR Demands Most

Not every OKR requires equal energy across all six phases. Some objectives are execution-heavy and live in the Tenacity zone for months. Others are idea-heavy and need sustained Invention energy. Some are momentum-heavy and die without Galvanising.

Before you assign an OKR, ask which phase will demand the most sustained energy. That tells you which Working Genius profile should own it.

• If the OKR is about launching something new, it will demand Invention and Galvanising energy for months

• If the OKR is about improving an existing process, it will demand Wonder and Discernment energy upfront, then Tenacity energy for the build

• If the OKR is about scaling something that already works, it will demand Enablement and Tenacity energy almost exclusively

• If the OKR is about culture change or adoption, it will demand Galvanising energy over and over, not just once at the start

Most teams assign based on job title instead of energy demand. The head of product gets the innovation OKR because innovation lives in product. The head of operations gets the efficiency OKR because efficiency lives in ops. That logic works when the person's genius matches the phase demand. It breaks when it does not.

Try auditing your current OKRs against the six types. For each objective, ask which phase will require the most sustained energy over the next 90 days. Then ask whether the person currently responsible has that type of work in their genius. If the answer is no, you have just identified why delivery feels harder than it should.

ASSIGNING OKRS BASED ON WORKING GENIUS

Once you understand the mapping, the next step is using it. This is where most teams stop at theory and never change how they assign goals. The shift is simple. Stop assigning OKRs based on job title or hierarchy. Start assigning based on which phase of work the OKR will demand most, then match that phase to the person whose genius aligns.

6. Assign Objectives to People Whose Genius Matches the Dominant Phase

Every OKR has a dominant phase. The phase that will demand the most energy, the most time, and the most sustained focus over the quarter. That phase should determine who owns the objective.

If the OKR is about creating a new service offering, the dominant phase is Invention. Assign it to someone with Invention in genius. If the OKR is about completing a multi-month project that is already scoped, the dominant phase is Tenacity. Assign it to someone with Tenacity in genius.

What changes when you do this: Execution stops feeling like you are pushing the team uphill. People start delivering on their OKRs without needing constant check-ins because the work energises them instead of draining them.

Match objective to genius phase: If your objective requires sustained questioning and problem identification, give it to someone with Wonder in genius. If it requires rallying a skeptical team over three months, give it to someone with Galvanising in genius. If it requires relentless follow-through on a defined plan, give it to someone with Tenacity in genius.

The person does not need to personally execute every task inside the OKR. They need to carry the energy that the OKR demands most. When that energy match is right, delivery becomes easier for everyone around them.

Try this with your next planning cycle. Before you assign any OKR, write down which of the six Working Genius types that objective will demand most over 90 days. Then assign it to someone who has that type in their genius. Watch what happens to execution speed.

7. Split OKRs Across Multiple Owners When Phases Shift

Some OKRs move through distinct phases over the quarter. Month one is about ideation. Month two is about decision-making and activation. Month three is about execution and delivery. When the phases are that distinct, split ownership.

Assign the first phase to the person whose genius matches ideation. Assign the second phase to the person whose genius matches activation. Assign the third phase to the person whose genius matches completion. Build a handoff into the OKR structure.

Most teams resist this because it feels like fragmented accountability. The assumption is that one person should own the whole thing from start to finish. That assumption works when the person has genius across all the required phases. It breaks when they do not.

OKR Phase	Owner Genius Profile	Handoff Trigger
Month 1: Ideate new pricing model	Wonder + Invention	Three options ready for evaluation
Month 2: Decide and rally team around chosen model	Discernment + Galvanising	Decision made, team briefed, rollout plan approved
Month 3: Execute rollout and track adoption	Enablement + Tenacity	Full implementation complete, metrics tracking live

When you structure OKRs this way, each person gets to work in their genius for the phase they own. The objective moves faster because no one is forcing themselves through work that drains them. Handoffs become clean because each owner knows exactly when their phase ends and the next begins.

The key is defining the handoff trigger upfront. Do not leave it vague. Name the specific deliverable or decision point that signals the handoff. That clarity prevents the first owner from hanging on too long and the second owner from starting too early.

8. Use Working Genius to Predict Where OKR Execution Will Stall

If you know the Working Genius profiles of your team, you can predict where an OKR will stall before you even start. Every team has gaps. Types of work that no one on the team has in their genius. When your OKR requires sustained energy in one of those gap areas, execution will drag.

A team with no one in Tenacity will struggle to finish anything. A team with no one in Wonder will set the wrong objectives. A team with no one in Galvanising will build great strategies that never get adopted. These are not motivation problems. These are wiring problems.

Audit your team for genius gaps:

• If no one has Wonder in genius, your objectives will default to incremental improvements instead of addressing root problems

• If no one has Invention in genius, your strategies will feel generic and borrowed from competitors

• If no one has Discernment in genius, your team will pursue too many ideas and waste resources on the wrong ones

• If no one has Galvanising in genius, your best plans will die in the announcement phase because no one creates momentum

• If no one has Enablement in genius, your people will hit blockers and sit waiting for help instead of escalating

• If no one has Tenacity in genius, your OKRs will hit 80 percent completion and then drift for weeks

When you spot the gap, you have three options. Hire or contract someone with that genius. Reassign the OKR to a different team that has the required genius. Or accept that this OKR will require extra leadership attention in the phase where the gap sits.

The worst option is pretending the gap does not exist. Assign the OKR anyway, hope someone figures it out, then act surprised when execution stalls in the exact phase you had no genius coverage for. That is avoidable.

9. Design Key Results That Match the Genius of the Person Tracking Them

Key results are not neutral. The way you define success shapes who can deliver it. A key result that measures creative output will energise someone with Invention in genius. A key result that measures completion rate will energise someone with Tenacity in genius. A key result that measures adoption will energise someone with Galvanising in genius.

Most teams write key results without thinking about who will be responsible for moving the number. The result is technically measurable but energetically mismatched. You assign a completion-focused key result to someone with Invention in genius and wonder why they keep reprioritising it.

Try writing your key results with the owner in mind. If the person responsible has Tenacity in genius, define success as tasks completed or milestones hit. If they have Galvanising in genius, define success as adoption rate or engagement level. If they have Invention in genius, define success as new solutions tested or concepts validated.

Genius-aligned key results:

For someone with Wonder in genius: Number of core assumptions tested, problems reframed, or strategic questions answered.

For someone with Invention in genius: New ideas generated, prototypes built, or solution options developed.

For someone with Discernment in genius: Decisions made, options evaluated, or low-value ideas killed.

For someone with Galvanising in genius: Team members activated, stakeholder buy-in secured, or momentum milestones hit.

For someone with Enablement in genius: Blockers removed, resources provided, or support requests resolved.

For someone with Tenacity in genius: Tasks completed, deliverables shipped, or finish-line milestones crossed.

When your key results align with the genius of the person tracking them, those metrics become motivating instead of obligatory. People check their numbers because they want to, not because you told them to.

10. Run OKR Check-Ins as Working Genius Retrospectives

Most OKR check-ins focus only on the numbers. Did the key result move. Is the objective still on track. What are the blockers. This approach treats execution like a technical problem when it is often an energy problem.

Add a Working Genius lens to your check-ins. Ask which phases of the OKR are energising the team and which phases are draining them. Ask whether people are working in their genius or being forced into their frustration. Ask where the handoffs are breaking down because the next phase needs a different genius profile.

What this reveals: An OKR that is behind schedule is often behind because the person responsible is working in their area of frustration, not because they are incompetent or uncommitted.

When you name that dynamic in the check-in, you create space to reassign the work or bring in support from someone whose genius matches the current phase. The conversation shifts from "why are you behind" to "who should be leading this phase instead."

Try adding these questions to your next OKR review:

• Which phase of this OKR has felt energising this month and which has felt draining

• Are you working in your genius or are you forcing yourself through work that frustrates you

• If you could hand off one part of this OKR to someone else, what would it be and who has the genius to take it

• Where is the current phase stalling and what type of Working Genius does that phase need most

These questions surface the real blockers. Not the task-level blockers. The energy-level blockers. Once those are visible, the fixes become obvious.

STRUCTURING TEAMS AROUND OKRS AND WORKING GENIUS

The way you structure your team determines whether OKRs accelerate execution or just create more reporting. When team structure ignores Working Genius, you end up with talented people assigned to work that drains them. When you structure teams around genius, OKRs become easier to deliver because people are working in their natural zone. (See also: Working Genius for team building.)

11. Build OKR Pods With Complementary Working Genius Profiles

Instead of assigning OKRs to individuals, assign them to small pods of two to four people whose Working Genius profiles complement each other. One person brings Wonder and Invention. Another brings Discernment and Galvanising. Another brings Enablement and Tenacity. Together, they cover all six phases.

This is not the same as a cross-functional team. Cross-functional teams are built around job roles. OKR pods are built around energy profiles. The pod exists to deliver a specific objective over 90 days, then disbands or reforms for the next quarter.

Each person in the pod owns the phase that matches their genius. The Invention person generates the approach. The Discernment person evaluates it. The Galvanising person rallies the wider team. The Tenacity person drives it to completion. No one is forced to carry the full OKR alone.

How to structure an OKR pod:

• Identify the objective. Write down which phases that objective will move through over the quarter.

• Map each phase to a Working Genius type. Be specific. If month one is ideation-heavy, that phase needs Invention energy. If month two is decision-heavy, that phase needs Discernment energy.

• Assign one person per phase based on their genius. Do not assign based on seniority or job title. Assign based on who has the required genius in their top two.

• Define handoff points between pod members. Each person knows when their phase ends and the next person's begins. Handoffs are clean, not assumed.

• Run weekly pod check-ins focused on energy, not just progress. Ask who is working in genius this week and who is being pulled into frustration. Reassign work inside the pod when needed.

When you structure OKR delivery this way, execution feels collaborative instead of isolating. People get to work in their genius for their assigned phase, then hand off cleanly to someone whose genius matches the next phase.

12. Assign Strategic OKRs to People With Wonder or Discernment in Genius

Not all OKRs are created equal. Some are execution-focused. Hit the number, ship the feature, close the deal. Others are strategic. Decide whether to enter a new market, evaluate whether the current model still works, question whether the organisation is solving the right problem.

Strategic OKRs require sustained Wonder or Discernment energy. Wonder energy asks the hard questions. Discernment energy evaluates the options and decides which path to take. If you assign a strategic OKR to someone without those types in their genius, you get surface-level thinking dressed up as strategy.

The pattern most teams miss: They assign strategic work to the most senior person in the room, assuming seniority equals strategic capability. Seniority gives you context and authority. It does not give you Wonder or Discernment. A senior leader with Galvanising and Tenacity in genius will deliver operational excellence but struggle with strategic ambiguity.

When strategic OKRs land with the wrong genius profile: You get strategies that look like last year's strategy with the numbers changed, or you get no strategy at all because the person keeps reprioritising it in favour of work that energises them.

Strategic OKRs belong with these profiles:

Wonder in genius: Assign OKRs that require deep questioning, reframing core assumptions, or exposing problems the organisation has not yet named.

Discernment in genius: Assign OKRs that require evaluating multiple strategic options, deciding between competing priorities, or killing initiatives that are not working.

Wonder plus Discernment in genius: Assign the most ambiguous, highest-stakes strategic OKRs where the right question and the right decision are both unclear.

When you match strategic work to these profiles, your strategies stop feeling generic. They start reflecting the actual complexity of the decision in front of you.

13. Assign Operational OKRs to People With Enablement or Tenacity in Genius

Operational OKRs are the opposite of strategic ones. The direction is clear. The path is defined. The work is about execution, support, and completion. These OKRs belong with people who have Enablement or Tenacity in genius.

Enablement energy thrives on making other people successful. Operational OKRs that require coordinating resources, removing blockers, or supporting multiple workstreams will energise someone with Enablement in genius. Tenacity energy thrives on pushing work to completion. Operational OKRs that require sustained follow-through, tracking dozens of tasks, or ensuring nothing falls through the cracks will energise someone with Tenacity in genius.

What happens when you assign operational OKRs to people with Wonder or Invention in genius: They deliver, but they resent it. The work feels like admin. They will deprioritise it the moment something more interesting appears. You get late delivery, not because they are incapable, but because the work drains them.

Operational OKRs belong with these profiles:

Enablement in genius: Assign OKRs that require supporting multiple people, coordinating resources, or ensuring teams have what they need to execute.

Tenacity in genius: Assign OKRs that require relentless follow-up, completion of multi-step processes, or tracking deliverables across a long timeline.

Enablement plus Tenacity in genius: Assign the most complex operational OKRs where success requires both sustained support and sustained completion energy.

When you assign operational work to these profiles, delivery becomes predictable. The person responsible does not need reminders. They chase it because the work energises them.

14. Rotate OKR Ownership Across Quarters Based on the Type of Work Required

The work your organisation needs this quarter is not the same work it will need next quarter. Q1 might demand innovation and ideation. Q2 might demand execution and delivery. Q3 might demand evaluation and decision-making. When the type of work changes, the person leading it should change too.

Most teams assign the same person to the same OKR area every quarter. The head of product owns the product OKRs. The head of ops owns the operational OKRs. That logic works when the type of work required stays consistent. It breaks when the phase shifts.

Imagine your product OKR in Q1 is about ideating a new feature set. That objective needs Invention energy. In Q2, the OKR shifts to building and shipping that feature set. That objective needs Tenacity energy. If the same person owns both quarters and they have Invention in genius but Tenacity in frustration, Q2 will drag.

Try rotating ownership based on phase demand:

• Q1 OKR demands ideation: Assign to someone with Invention in genius.

• Q2 OKR demands decision-making and activation: Reassign to someone with Discernment and Galvanising in genius.

• Q3 OKR demands execution: Reassign to someone with Tenacity in genius.

• Q4 OKR demands evaluation and iteration: Reassign to someone with Wonder and Discernment in genius.

This is not about instability. This is about matching energy to demand. The person who leads ideation does not need to be the person who leads execution. When you let them hand off at the natural phase break, both people get to work in their genius.

The handoff becomes a feature, not a bug. The ideation leader finishes their phase energised and ready for the next idea-heavy OKR. The execution leader takes over energised because they finally get to push something across the line.

15. Use Working Genius to Decide Which OKRs to Pursue and Which to Kill

Not every possible OKR is worth pursuing. Your team has limited energy. When you try to execute too many objectives at once, nothing gets the sustained attention it needs. The question is not just what to do. The question is what to stop doing.

Working Genius helps you kill OKRs before they waste time. If an objective requires sustained energy in a type of work that no one on your team has in their genius, that OKR is a bad fit. You can still pursue it, but you need to acknowledge upfront that execution will require extra support, external help, or a much longer timeline.

The honest conversation most teams avoid: We do not have the right genius profiles on this team to deliver that objective without burning people out. Either we resource it differently or we kill it.

Try auditing your proposed OKRs against your team's genius profiles before the quarter starts. For each objective, ask which phases will require sustained energy and whether anyone on the team has that type in their genius. If the answer is no, you have three options.

• Kill the OKR. Admit it is not the right fit for this team at this time.

• Bring in external support. Hire a contractor or partner whose genius matches the missing phase.

• Extend the timeline. Accept that delivery will take longer because people will be working in their area of competence or frustration, not genius.

The option you do not have is pretending the gap does not exist. When you assign an OKR that requires sustained Tenacity energy to a team with no one in Tenacity, you are setting that OKR up to fail. Better to kill it now than six weeks in.

USING WORKING GENIUS TO IMPROVE OKR CONVERSATIONS

The quality of your OKR outcomes is determined by the quality of the conversations that set them. Most OKR conversations focus on what needs to happen. Almost none of them focus on who is wired to make it happen. When you bring Working Genius into the conversation, the whole discussion shifts.

16. Start OKR Planning Meetings by Naming Each Person's Working Genius Profile

Before you discuss a single objective, put every person's Working Genius profile on the table. Write it on the whiteboard. Include it in the slide deck. Make it visible to everyone in the room. This is not about labeling people. This is about creating shared language for how work gets assigned.

When profiles are visible during planning, three things change:

People stop volunteering for work that will drain them out of obligation or guilt. They can point to their profile and say this phase is in my area of frustration, someone else should lead it.

Leaders stop defaulting to the usual suspects. When you can see that the person who always takes the hard projects has Tenacity in frustration, you pause before assigning them another execution-heavy OKR.

The conversation shifts from who is available to who is wired for this. Availability is logistics. Wiring is energy. Energy determines whether the OKR gets delivered with momentum or gets dragged across the line.

Run your next planning session this way:

• Start with profiles. Every person shares their two areas of genius, two areas of competence, and two areas of frustration. If the team has done Working Genius assessments before, this takes five minutes. If not, do the assessments before the planning meeting.

• Introduce the proposed OKRs. For each one, name which phases that OKR will move through over the quarter.

• Map each phase to a Working Genius type. Be explicit. This phase needs Wonder. This phase needs Invention. This phase needs Tenacity.

• Assign based on genius, not hierarchy. Let the person whose genius matches the phase volunteer to own it. If no one volunteers, that is a signal the OKR does not fit the team.

When you run OKR planning this way, assignments become collaborative instead of top-down. People take ownership because the work energises them, not because they were told to.

17. Use Working Genius Language to Name Why OKRs Are Stalling

When an OKR stalls, the default response is to ask what is blocking progress. That question assumes the problem is external. A dependency, a resource gap, a technical issue. Sometimes the blocker is external. More often, the blocker is internal. The person responsible is working in their area of frustration and the work is draining them.

Working Genius gives you language to name that dynamic without making it personal. Instead of saying you are not delivering, you can say this phase of the OKR is living in your area of frustration and we need to bring in someone whose genius matches it. The conversation stays about the work, not the person.

The shift this creates: People stop defending why they are behind and start asking for the right kind of help. The energy in the room changes from blame to problem-solving.

Try using this framing in your next OKR review. When someone is behind, ask which phase of the work is draining them most. Ask whether that phase sits in their area of frustration. If it does, ask who on the team has that phase in their genius and could take it over.

The conversation sounds like this:

Instead of: Why is this OKR only at 40 percent when we are halfway through the quarter.

Try: This OKR is behind, and I am wondering if the current phase is sitting in your area of frustration. Where is the energy draining you most right now.

Instead of: You committed to this deliverable and you are not delivering.

Try: The phase we are in now requires sustained Tenacity energy and I know that is in your area of frustration. Who on the team could take over this phase while you focus on the next idea-heavy piece.

When you name the energy mismatch, people stop feeling attacked and start feeling understood. The fix becomes obvious. Reassign the phase or bring in support. Do not force someone to keep grinding through work that drains them.

18. Teach Your Team to Self-Assign Based on Genius, Not Guilt

Most people assign themselves work out of guilt, obligation, or the belief that saying no makes them a bad team player. Someone has to do it. No one else is volunteering. I will take it. That logic produces a team full of people working in their area of frustration while the work that matches their genius goes undone.

Working Genius gives people permission to say no to work that drains them and yes to work that energises them. When the whole team understands the framework, self-assignment becomes about energy fit, not obligation.

Try teaching your team to ask two questions before they take on a new OKR or project:

• Does this work sit in my area of genius. If yes, take it. If no, pause.

• Is there someone on the team whose genius matches this work better than mine. If yes, suggest them. If no, take it but acknowledge upfront that it will require extra energy.

When teams adopt this habit, three things happen:

• The right work lands with the right people more often.

• People stop burning out on work they should never have been doing.

• The team starts having honest conversations about genius gaps instead of pretending everyone can do everything.

This does not mean people only do work they love. Competence still matters. But when you have a choice between assigning work to someone whose genius matches it and someone whose frustration matches it, choose genius. The OKR will move faster and the person will stay energised.

19. Frame OKR Retrospectives Around Energy, Not Just Outcomes

Most OKR retrospectives focus on what got delivered and what did not. Did we hit the key results. Did we achieve the objective. What blocked us. This approach treats execution like a technical problem. It misses the human element.

Add an energy lens to your retrospectives. Ask which OKRs energised the team and which ones drained them. Ask where people were working in their genius and where they were forced into their frustration. Ask whether the right people were assigned to the right phases.

Energy retrospective questions:

• Which OKRs felt energising to work on this quarter and which felt draining

• Where were you working in your genius and where were you working in your frustration

• If you could reassign one piece of your OKR to someone else, what would it be and why

• Which phases of the OKR moved quickly because the right genius was assigned and which phases stalled because the genius was mismatched

• What would you assign differently next quarter based on what you now know about energy fit

When you ask these questions, you surface patterns you would never catch in a traditional retrospective. The same person keeps getting assigned execution-heavy OKRs even though Tenacity is in their frustration. The ideation phases always move fast but the completion phases always drag because no one on the team has Tenacity in genius. These patterns are fixable once they are visible.

The retrospective becomes a planning tool for the next quarter. You do not just review what happened. You use what happened to assign the next round of OKRs more intelligently.

20. Use Working Genius Profiles to Predict Which OKRs Will Need Executive Attention

Some OKRs will run themselves. The right people are assigned, the genius matches the work, and execution feels like flow. Other OKRs will need sustained executive attention because the work required does not match the genius available.

If you know the genius profiles of your team, you can predict which OKRs will need you before the quarter starts. An OKR that requires sustained Tenacity energy on a team with no one in Tenacity will need weekly check-ins. An OKR that requires sustained Galvanising energy on a team with no one in Galvanising will need you to create the momentum yourself.

Try auditing your OKRs at the start of the quarter and flagging the ones where genius coverage is weak. Those are the OKRs that will need your time. Schedule your check-ins accordingly.

Predict attention needs based on genius gaps:

• No Wonder on the team: The objectives will default to safe, incremental goals. You will need to push the team to ask harder questions.

• No Invention on the team: The strategies will feel borrowed and generic. You will need to bring in external thinking or create space for creativity yourself.

• No Discernment on the team: The team will pursue too many ideas at once. You will need to force prioritisation and kill low-value work.

• No Galvanising on the team: The plan will be solid but adoption will stall. You will need to create the momentum and rally people yourself.

• No Enablement on the team: People will hit blockers and wait instead of escalating. You will need to actively remove obstacles.

• No Tenacity on the team: OKRs will hit 80 percent and drift. You will need to drive completion yourself.

When you predict attention needs upfront, you stop being surprised when certain OKRs need more of your time. You can resource them properly or decide not to pursue them at all.

SCALING WORKING GENIUS AND OKRS ACROSS THE ORGANISATION

Once the approach works at the team level, the next question is how to scale it. How do you structure OKRs and Working Genius across multiple teams, departments, or divisions without losing the energy fit that makes it work.

21. Cascade OKRs Down the Organisation and Assign Based on Genius at Every Level

Most organisations cascade OKRs from the executive level down to teams and individuals. The CEO sets company-wide objectives. The executive team translates those into departmental objectives. Teams translate departmental objectives into individual key results. That structure is sound. The problem is how the assignments happen at each level.

At every level of the cascade, apply the Working Genius filter. Do not just ask what this team needs to deliver. Ask which phases that delivery will move through and whether the people on the team have the genius to cover those phases.

When a departmental OKR requires sustained Invention energy, assign it to the team with the most Invention profiles. When a departmental OKR requires sustained Tenacity energy, assign it to the team with the most Tenacity profiles. The structure stays the same. The assignment logic changes.

Cascade with genius in mind:

Company OKR: Launch new service line by Q4.

Departmental OKR for Product: Ideate and validate three service concepts by end Q2. Assign to the team with the most Wonder and Invention profiles.

Departmental OKR for Operations: Build delivery infrastructure and processes by end Q3. Assign to the team with the most Enablement and Tenacity profiles.

Departmental OKR for Marketing: Create go-to-market plan and rally early adopters by end Q3. Assign to the team with the most Discernment and Galvanising profiles.

When you cascade this way, each team gets work that matches their collective genius. Execution feels easier because people are working in their natural zone.

22. Build a Genius Map of Your Organisation and Use It to Assign Cross-Functional OKRs

Some OKRs cannot be owned by a single team. They require collaboration across departments. A product launch needs product, marketing, sales, and operations. A culture initiative needs HR, leadership, and every team lead. These cross-functional OKRs are the hardest to execute because accountability gets diffused.

Working Genius helps you assign ownership within cross-functional OKRs more clearly. Instead of saying everyone is responsible, assign each phase of the OKR to the team or individual whose genius matches that phase.

Start by building a genius map of your organisation. For each team or department, identify which Working Genius types are most represented. Some teams will skew heavily toward Invention and Wonder. Others will skew toward Enablement and Tenacity. Map those patterns.

Then assign cross-functional OKR phases based on the map:

• Ideation phase: Assign to the team with the most Wonder and Invention profiles.

• Evaluation phase: Assign to the team with the most Discernment profiles.

• Activation phase: Assign to the team with the most Galvanising profiles.

• Support phase: Assign to the team with the most Enablement profiles.

• Completion phase: Assign to the team with the most Tenacity profiles.

Each team knows which phase they own. Handoffs between teams are clean because each team is working in their collective genius for their assigned phase. The cross-functional OKR stops feeling like everyone's problem and starts feeling like a relay race.

23. Use Working Genius to Build Balanced Leadership Teams

Your leadership team sets the OKRs for the entire organisation. If that team is missing key Working Genius types, the OKRs will reflect those gaps. A leadership team with no Wonder will set incremental objectives. A leadership team with no Tenacity will set ambitious objectives and never finish them. A leadership team with no Discernment will pursue too many priorities at once.

Audit your leadership team for genius coverage. Do you have at least one person with each of the six types in their genius. If not, you have a structural gap that will show up in your OKRs.

The pattern that plays out: Leadership teams hire for functional expertise and end up with five people who all have the same Working Genius profile. They are all strong in Galvanising and Discernment but weak in Tenacity. The result is a team that sets great goals, rallies the organisation, and never finishes anything.

When you build or reshape your leadership team, add Working Genius to the hiring criteria. (See also: Working Genius for hiring.) You still need functional expertise. But you also need genius balance. If your current team is heavy in Wonder and Invention, your next hire should bring Enablement or Tenacity.

Balanced leadership teams cover all six types:

Wonder: Ensures the organisation is asking the right questions and solving real problems.

Invention: Ensures the organisation generates new ideas and creative solutions.

Discernment: Ensures the organisation evaluates options clearly and kills bad ideas fast.

Galvanising: Ensures the organisation creates momentum and gets people bought in.

Enablement: Ensures the organisation provides the support and resources people need to execute.

Tenacity: Ensures the organisation finishes what it starts and does not let things drift.

When your leadership team has this balance, the OKRs you set will be more realistic, more energising, and more likely to get delivered.

24. Train Managers to Assign Work Based on Genius, Not Just Capacity

Managers are the ones assigning work day to day. They are the ones deciding who gets which task, which project, which OKR. If they are assigning based only on who has capacity, they will burn people out. If they assign based on genius, work gets done faster and people stay energised.

Most managers have never been taught to assign work based on energy fit. They default to the person who is available, the person who did it last time, or the person who will say yes without pushing back. That logic produces teams where the same people carry all the hard work and quietly burn out.

Teach your managers to ask two questions before they assign any piece of work:

• Which phase of work does this task require most. Is it ideation, evaluation, activation, support, or completion.

• Who on my team has that phase in their genius. Assign to that person first. If they are at capacity, ask if someone in their area of competence can take it. Only assign to someone in their area of frustration as a last resort.

When managers adopt this habit, the whole organisation shifts. Work starts landing with people who are wired to do it. Energy improves. Execution speeds up. Burnout decreases.

Run a Working Genius workshop for your managers on Working Genius and work assignment. Give them the language. Give them the questions. Give them permission to reassign work when they realise the fit is wrong. The structure of your OKRs will improve because the people executing them will be better matched to the work.

25. Make Working Genius Profiles Visible in Your OKR Tracking System

Most OKR tracking tools show you the objective, the key results, the owner, and the current status. They do not show you whether the owner is working in their genius or their frustration. That information should be visible.

Add Working Genius profiles to your OKR tracking system. Include each person's two areas of genius next to their name. When you look at the OKR board, you should be able to see at a glance whether the person assigned to each objective has the genius that matches the work required.

This small addition changes how you use the tracking system. Instead of just checking whether the number moved, you start checking whether the right person is assigned. When you see an OKR stalling and notice the owner has the required phase in their frustration, you know the fix. Reassign or bring in support.

Make genius visible in three places:

• Next to each person's name on the OKR tracker. Include their two genius types in parentheses.

• In the OKR assignment view. When you are assigning a new OKR, the system should surface who on the team has the required genius for that objective.

• In the retrospective dashboard. After the quarter, you should be able to filter OKRs by genius match and see which ones were aligned and which were mismatched.

When genius is visible in your tracking system, it stops being a side conversation and starts being part of how you manage execution. The data is right there. You can act on it.

Your OKRs will only deliver what your team has the energy to deliver. You can set perfect objectives with measurable key results and still fail if the people responsible are working in their area of frustration. Working Genius fixes that gap. It shows you who is wired for which phase of work, so you can assign goals to people who will be energised by them instead of drained.

The combination is simple. OKRs define what success looks like. Working Genius defines who should lead each phase. When you stack them, execution stops feeling like effort and starts feeling like flow.

Ready to combine Working Genius with your team's OKR process? Jonno White is a Certified Working Genius Facilitator who works with corporates, nonprofits, and schools around the world. Email jonno@consultclarity.org to explore how to bring this framework to your team.