Is Working Genius Worth It for Your Leadership Team

If you have ever watched a team complete a personality assessment, nod politely through the debrief, then return to exactly the same patterns two weeks later, you already know the gap between insight and change.

Working Genius sits somewhere different. It is not another personality framework. It is a lens on how people contribute to work, which makes the distance between the session and the behaviour shift shorter than most tools. But that does not mean the framework does the work for you.

The question is not whether Working Genius is worth it in theory. The question is whether it is worth it for your specific leadership team, in your specific moment, with your specific willingness to act on what the assessment reveals.

Here is what I have seen work, what I have seen fail, and what the investment actually returns when the conditions are right.

BEFORE THE FRAMEWORK

What most teams are trying to solve when they look at Working Genius

Working Genius enters the conversation when a leadership team knows something is off but cannot name the pattern. Talented individuals, poor collective output. Meetings that drift. Projects that start strong then stall halfway through. A vague sense that some people are energised while others are silently drained.

The framework addresses contribution, not personality. It does not tell you whether someone is introverted or dominant or analytical. It tells you which types of work energise them and which types deplete them. That distinction matters because depletion is not the same as incompetence. A leader can be excellent at execution but drained by it. Another can be brilliant at ideation but exhausted if that is all you ask of them.

• The team has talent but no rhythm to how work gets done

• Certain people are burnt out while others feel underused

• Projects start well but lose energy partway through

• Some voices dominate early discussions while others stay silent

• The same few people are always left holding the implementation

These are the signs that a contribution lens would help. Working Genius does not solve structural problems. It does not fix a broken strategy or replace a failing hire. But if the issue is energy, rhythm, and how work gets distributed, the framework gives you the map you need.

Most leaders come to this work after trying other frameworks first. They have done StrengthsFinder, Myers-Briggs, DISC, or Enneagram. Those tools gave insight. They did not give traction. The reason is altitude. Personality frameworks tell you who someone is. Contribution frameworks tell you what work they should be doing. The second question is closer to the daily friction a leadership team actually feels.

1. The Six Types of Working Genius

Working Genius maps contribution across six distinct types of work. Every person has two types that energise them, two that are competent but draining, and two that frustrate them. Patrick Lencioni created the model. The framework travels because the underlying pattern holds across industries, geographies, and team sizes. For a full overview of how to implement the model, see the Working Genius implementation guide.

Wonder sits at the start of any project. This is the person asking why things are the way they are, what could be different, what problem is worth solving. They are energised by questions. They bring discernment. They spot the opportunity everyone else walks past. Without them, teams spend months executing ideas that should have been questioned on day one.

The genius of Invention follows Wonder. Once the question is named, Invention creates the answer. These are the people who generate ideas, connect disparate concepts, and design solutions no one else saw coming. They thrive in brainstorming. They struggle when the team needs them to execute what they just invented.

Discernment evaluates what Invention produces. This is the person with the instinct for what will work and what will not. They cannot always explain why. They feel it. They save teams from bad ideas before those ideas consume resources. They are energised by assessment. They are drained by being asked to produce the ideas they are evaluating.

Galvanising moves from evaluation to momentum. This is the person who rallies the team, generates excitement, and makes people believe the idea is worth pursuing. They are energised by creating buy-in. They struggle when the project moves from launch energy into the repetitive grind of delivery.

Enablement supports the people doing the work. These are the people who respond to requests, coordinate resources, and remove obstacles so others can do their best work. They are energised by helping. They are drained when they are asked to set the direction or make the final call themselves.

Tenacity closes the loop. This is the person who finishes what the team started. They are energised by completion. They push through obstacles. They do not let projects die halfway through. Without them, the team generates brilliant ideas that never ship.

Your two Geniuses are the types of work that give you energy. You can do them for hours without feeling depleted. Your two Competencies are work you can do well but it drains you over time. Your two Frustrations are work that exhausts you and produces poor output even when you try. The framework does not suggest you avoid your Frustrations entirely. It suggests you stop building your role around them.

The practical shift happens when teams start designing work around energy, not just skill. A leader might be excellent at project management but drained by Tenacity. Another might generate ideas constantly but collapse when asked to Galvanise the room. The skill exists. The energy does not. That gap is what Working Genius names.

2. The assessment costs less than the debrief

The Working Genius assessment itself costs around 25 USD per person. That is the individual online tool. A leadership team of eight people pays 200 USD for the raw data. The number is not the barrier.

The cost sits in what happens after the assessment. If the team completes the tool, reads their own results, then moves on, nothing changes. The value lives in the facilitated debrief. That session costs between 3,000 and 8,000 AUD depending on the facilitator, the size of the team, and whether the work is a half-day or a full-day session.

• Individual assessment licenses at 25 USD per person

• Facilitated debrief session starting at 3,000 AUD for half-day work

• Full-day intensive sessions between 5,000 and 8,000 AUD

• Follow-up implementation support typically billed separately

Most organisations are not hesitating over the 200 USD. They are hesitating over the day out of the calendar and the facilitator fee. That hesitation is reasonable. A poorly run debrief is worse than no debrief. The team learns their types, feels momentarily interested, then returns to work with no change in behaviour.

The facilitator determines whether the investment returns anything. A good facilitator does not just explain the model. They surface the specific friction the team is experiencing, map that friction to the Working Genius patterns, and build a plan for what changes in the next 90 days. A mediocre facilitator teaches the framework then leaves. The first option is worth the cost. The second is not.

If you are considering this work, the question to ask is not whether Working Genius is worth it. The question is whether the facilitator you are hiring has seen enough teams to recognise your specific patterns and translate the framework into behaviour change.

3. What changes in the first 90 days if the debrief is done well

The teams that see real change from Working Genius make three shifts in the 90 days after the session. If none of these shifts happen, the investment did not return.

First, they stop assigning work purely on seniority or availability. Before Working Genius, the CFO might be running the strategy offsite because they are the most organised person on the exec team. After Working Genius, the team realises the CFO has Tenacity and Enablement, not Wonder and Invention. The offsite still needs running. The person running it changes. The CFO moves into a role that uses their actual Geniuses. The offsite improves. The CFO stops quietly resenting the work.

Second, they name the energy cost of certain roles. A leader with Galvanising and Wonder is brilliant at the front of the room launching ideas. Put that same leader in charge of quarterly reporting and budget tracking, work that demands Tenacity and Enablement, and they will deliver poor output while feeling drained. The team learns to say the quiet part out loud. The role is draining you. That is not a character flaw. It is a mismatch between the work and your Geniuses.

Third, they build pairing strategies. Projects improve when the person with Invention is paired with someone who has Discernment. The ideas get better because the Discernment partner filters in real time. The Invention partner does not have to second-guess their own output. The pairing creates better work with less friction.

Pairing strategies show up in three ways after a strong Working Genius debrief:

Meeting roles get reassigned. The person with Wonder and Discernment starts running problem diagnosis sessions. The person with Galvanising and Enablement runs the implementation check-ins. The person with Tenacity takes ownership of follow-through. The meetings stop feeling like the same person is doing all the work.

Project teams get designed around contribution. A new initiative is not assigned to whoever has capacity. It is assigned to the combination of Geniuses the project needs. Early stage ideation pulls in Wonder and Invention. Mid-stage evaluation brings in Discernment. Launch brings in Galvanising. Delivery brings in Enablement and Tenacity. The project moves faster because the right energy is in the room at each phase.

One-on-one coaching conversations shift. A manager stops telling a direct report to be more strategic when that person has Enablement and Tenacity. The conversation becomes: your Geniuses are in delivery and support, so let us build your role around that and stop pretending you will suddenly develop Wonder. The honesty creates relief. The performance improves because the person is finally working in their zone. For a practical guide to building on this, see what to do after a Working Genius assessment.

None of these shifts require a year-long change programme. They require a leadership team willing to act on what the assessment revealed. The teams that see value in the first 90 days are the teams that treat the debrief as the start of the work, not the end of it.

4. Where Working Genius does not help

Working Genius is not a universal fix. It solves a specific kind of problem. If your team's issue sits outside that problem, the framework will disappoint.

It does not solve a talent problem. If the issue is that you have the wrong people in senior roles, Working Genius will not fix that. The framework assumes the people in the room are capable. It helps you deploy that capability better. If the capability is not there, no amount of energy mapping will close the gap.

It does not replace a performance conversation. A leader who is underperforming because they lack skill, discipline, or accountability will not suddenly improve because you discovered their Working Genius. The framework helps high performers work in their zone. It does not turn poor performers into good ones.

It does not fix structural dysfunction. If your leadership team does not trust each other, if two senior people are in open conflict, if the CEO is bypassing the exec team and making decisions alone, Working Genius is the wrong tool. You need a different intervention. Contribution mapping works when the relationships are intact but the work distribution is broken. It does not work when the relationships themselves are broken.

What else sits outside the Working Genius scope:

• Strategy clarity. The framework will not tell you what your organisation should be doing.

• Cultural repair. It will not rebuild trust or fix a toxic environment.

• Leadership development. It does not teach someone how to give feedback, run meetings, or manage conflict.

• Succession planning. It will not tell you who should be promoted or who should leave.

If you are hoping Working Genius will solve any of these, the investment will feel wasted. The framework does one thing well. It maps how people contribute to work and helps teams reorganise around energy. That is it.

Most disappointment with Working Genius comes from mismatched expectations. A leadership team brings in the framework hoping it will fix morale, clarify roles, improve performance, and rebuild culture. The session reveals some useful patterns. Nothing fundamental changes. The team concludes the framework does not work. The real issue is the framework was asked to do work it was never designed for.

5. The real cost is the time after the session

The debrief session is half a day or a full day. That is the visible cost. The hidden cost is the 90 days after, when the leadership team has to translate insight into action.

Most teams do not budget for this part. They treat the debrief as the deliverable. The session ends. Everyone goes back to work. Two weeks later, the insights are forgotten. Three months later, someone mentions Working Genius in a meeting and half the team has to be reminded what their own Geniuses are.

The teams that get value from Working Genius build a cadence of follow-through. They revisit the framework in every quarterly planning session. They use it when assigning new projects. They reference it in performance reviews. They build it into how the team talks about work. The framework stops being a session they attended once and becomes the language they use to design roles, pair people, and distribute energy.

Here is what follow-through looks like in practice:

Monthly exec meetings include a Working Genius check-in. Ten minutes at the start of the meeting. The team scans current projects and asks: who is working outside their Geniuses right now, and what needs to shift? It is not a formal review. It is a pattern check. The conversation surfaces mismatches before they become burnout.

New project briefs include a Genius map. Before assigning a project, the leadership team lists the types of work the project will demand. Early ideation needs Wonder and Invention. Stakeholder engagement needs Galvanising. Delivery needs Tenacity. The project is assigned to a team whose combined Geniuses match the work. The output improves and the energy cost drops.

Role design conversations reference Working Genius directly. When a direct report is struggling, the manager asks: what percentage of your current role sits in your Geniuses versus your Frustrations? If the answer is 30 percent Geniuses and 50 percent Frustrations, the role is the problem, not the person. The conversation shifts to redesigning the work.

The leadership team revisits their own pairings every six months. Who is paired with whom on standing projects. Whose Geniuses are underused. Whose Frustrations are dominating their week. The review does not take long. It prevents drift. The team stays aligned to the contribution map they built in the original debrief.

The real investment is not the session cost. It is the discipline to keep using the framework after the facilitator leaves. That discipline is what separates the teams who see lasting change from the teams who get temporary insight then revert.

6. When to bring Working Genius in versus when to wait

Timing matters. Bringing Working Genius into a team at the wrong moment wastes the investment. The framework works when certain conditions are already in place.

The team needs psychological safety before contribution mapping helps. If people are afraid to name what drains them, or if admitting a Frustration feels like admitting weakness, the debrief will produce polite dishonesty. People will claim they are energised by work they actually hate. The facilitator will build a plan on false data. Nothing improves.

Bring Working Genius in when the team already trusts each other enough to tell the truth. Not perfect trust. Not zero conflict. But enough safety that someone can say: I am good at this work but it is draining me, and I need help. If that sentence cannot be said out loud in your leadership team, delay the Working Genius session and work on trust first.

The team also needs decision authority over how work gets distributed. If roles are locked, if the org chart is rigid, if no one has permission to reassign projects based on energy, the Working Genius insights sit unused. The team learns their Geniuses. They cannot do anything with that information. The frustration compounds.

Bring Working Genius in when the leadership team has real agency to redesign work. That might mean a CEO who is willing to let roles shift. It might mean an exec team with genuine delegation authority. It does not mean total freedom. It means enough flexibility that discovering someone is drained by Tenacity can lead to reassigning some of their Tenacity work without waiting for the next restructure.

Signs the team is ready for Working Genius:

• The team can name specific friction but cannot diagnose the root cause

• Performance reviews keep surfacing energy and motivation issues

• Projects are delivered but key people are quietly burning out

• The team has tried other frameworks and nothing has stuck

• The leadership group is willing to act on what the assessment reveals

If these conditions are present, Working Genius will return value. If they are not, the framework will give insight but no traction. The session becomes another thing the team tried that did not change anything.

7. The difference between a good facilitator and a mediocre one

The facilitator you hire determines whether Working Genius is worth it. A great facilitator does not just teach the model. They translate the model into your specific team's dynamics.

A mediocre facilitator explains the six types, walks through each person's results, answers questions, then leaves. The team understands the framework. They do not understand what to do with it. Two weeks later, nothing has changed.

A great facilitator starts by naming the friction the team is already experiencing. Before explaining Working Genius, they ask: what is not working right now? Where is the energy draining? Which projects feel harder than they should? The team names the patterns. The facilitator maps those patterns to Working Genius. The model stops being abstract and starts being the diagnosis the team needed.

The facilitator also builds the 90-day action plan before the session ends. Not a vague commitment to use the framework. A specific list of what changes. Which projects get reassigned. Which pairings get tested. Which roles get redesigned. The plan is written down. Someone owns follow-through. The session ends with clarity, not just insight.

Here is what to look for when deciding to run a Working Genius workshop and hire a facilitator:

Ask how many leadership teams they have debriefed. If the answer is fewer than ten, they are still learning. The patterns that make Working Genius useful only become visible after you have sat in the room with dozens of teams. A facilitator who has done five sessions can teach the model. A facilitator who has done fifty can read your team's specific dysfunction and map it to the framework in real time.

Ask what happens after the session. If the answer is "you will have your results and a better understanding of the model," walk away. A good facilitator includes follow-up. A check-in call 30 days later. A written summary of the action plan. Access to ask questions when implementation stalls. The debrief is the start, not the finish.

Ask what they do when someone's results do not match their behaviour. This happens often. A leader scores high in Wonder but behaves like pure Tenacity in meetings. A facilitator who takes the results at face value misses the real issue. A good facilitator digs deeper. Why is this person working outside their Geniuses? What is the role demanding that the assessment is not capturing? The conversation matters more than the score.

Ask for a reference from a previous client in your sector. Working Genius works across industries, but the language and examples that land in a school are different from the ones that land in a corporate exec team. A facilitator who has worked with teams like yours will translate the framework faster.

The facilitator is not a luxury. They are the reason the framework works or does not. Budget for the best facilitator you can access. If that means waiting an extra quarter to afford someone with real depth, wait.

8. What your leadership team needs to bring to the session

The facilitator carries the framework. The leadership team carries the willingness to act. Without the second part, the session produces nothing.

The team needs to show up ready to name what is broken. Not in a blame way. In a diagnosis way. If the exec team sits in the debrief pretending everything is fine, the facilitator cannot help. The value of Working Genius is in mapping real friction to contribution patterns. If the friction is hidden, the map is useless.

Bring honesty. If someone is drained by their current role, say it. If a project is stalling because the wrong person is leading it, name it. If two people are paired badly and everyone knows it, surface it. The session is the safe place to say what the hallway conversations have been whispering for months.

The team also needs to bring time. Not just the half-day or full-day for the debrief. Time in the 90 days after to implement what the session reveals. If the leadership calendar is so packed that no one has capacity to redesign work, reassign projects, or test new pairings, the Working Genius insights die on contact with reality.

Before booking the session, audit your next quarter. Do you have space to act on what the debrief will reveal? If the answer is no, delay the session. A mediocre debrief you have time to implement beats a brilliant debrief you cannot act on.

What to prepare before the facilitator arrives:

• A written list of the friction the team is experiencing right now

• A clear sense of which roles, projects, or pairings feel misaligned

• Permission from the CEO or board to redesign work based on what the session reveals

• A commitment from every person in the room to attend the full session

• Time blocked in the next 90 days for implementation conversations

If you bring these five things, the facilitator has what they need to make the session land. If you bring none of them, the session becomes a theoretical exercise that changes nothing.

9. The mistake most teams make after the debrief

The most common failure pattern is treating the debrief as the end of the work. The session happens. Everyone feels energised. The facilitator leaves. Life returns to normal. Three months later, someone mentions Working Genius and half the team has forgotten their own results.

The mistake is assuming insight produces change. It does not. Insight produces the map. Change requires using the map. If the leadership team does not build a follow-through cadence, the map sits in a drawer.

Here is what derails most post-debrief momentum:

No one owns the follow-through. The session ends with a plan. The plan has no owner. Two weeks later, no one remembers who was supposed to reassign the project or test the new pairing. The default state reasserts itself.

Fix this by assigning ownership before the facilitator leaves. One person on the exec team owns Working Genius implementation for the next 90 days. That person runs the monthly check-ins, tracks which changes are happening, and surfaces when the team is drifting back to old patterns. The ownership is explicit, not assumed.

The team waits for a restructure to act. The debrief reveals someone is working outside their Geniuses. The team decides to fix it in the next org redesign. The redesign is six months away. Six months later, the redesign gets delayed. A year passes. Nothing changes. The person is still drained. The insight is wasted.

Fix this by making small moves fast. You do not need a restructure to reassign a project. You do not need board approval to change who leads the quarterly planning session. Find the lowest-friction change the debrief revealed and make it in the next two weeks. The momentum from that small win creates permission for the next change.

The framework gets used once then forgotten. The debrief happens. Roles get adjusted. The team feels good. Then Working Genius disappears from the conversation. Six months later, new projects are assigned the old way. No one is referencing Geniuses. The language fades.

Fix this by embedding the framework into standing meetings. Add Working Genius as a ten-minute agenda item in monthly exec meetings. Not a full review. Just a check: who is working outside their Geniuses this month, and what shifts next month? The repetition keeps the language alive.

The expectation is set that Working Genius will fix everything. The debrief happens. Some things improve. Other things do not. The team concludes Working Genius did not work. The real issue is the framework was expected to solve problems it was never designed for. A contribution lens improves work distribution. It does not fix strategy, culture, or talent.

Fix this by naming what Working Genius will and will not address before the session. Be explicit. The framework will help you pair people better, distribute energy better, and reduce friction in how projects get staffed. It will not fix underperformance, rebuild trust, or clarify your strategy. Set the scope clearly. The disappointment drops.

10. How to know if the investment returned

Six months after the debrief, the leadership team should be able to name specific changes that happened because of Working Genius. If they cannot, the investment did not return.

The simplest test is energy. Are the people on your leadership team working in their Geniuses more often than they were six months ago? If the answer is yes, the framework worked. If the answer is no, something in the implementation failed.

A second test is project velocity. Are projects moving faster because the right Geniuses are in the room at each phase? Are ideation sessions producing better ideas because Wonder and Invention are paired? Are delivery timelines shortening because Tenacity is closing loops instead of getting pulled into early-stage brainstorming?

A third test is conflict reduction. Has the leadership team stopped having the same friction conversations? The person who used to resist every new idea is now understood as someone with Discernment, not someone being difficult. The person who used to bail on projects halfway through is now understood as someone with Galvanising, not someone who lacks commitment. The reframe reduces tension.

Signs the investment returned value:

• Roles have been redesigned around people's Geniuses

• Projects are staffed based on contribution needs, not just availability

• The leadership team uses Working Genius language in regular conversations

• Energy and burnout issues have decreased across the exec team

• New hires are onboarded with Working Genius as part of role design

If three or more of these are true, the framework delivered. If none of them are true, the debrief was insight without traction.

The ROI is not immediate. Working Genius does not produce a revenue spike or a performance jump in month one. The return shows up in reduced friction, better energy distribution, and faster project velocity over quarters, not weeks. If you are looking for a quick fix, this is the wrong tool.

IMPLEMENTATION REALITY

11. The teams that get the most value from Working Genius

Not every team sees the same return from Working Genius. Some teams transform. Others see modest improvement. The difference is not the framework. It is the team's readiness to use it.

The teams that get the most value are the ones who treat Working Genius as a design tool, not a personality insight. They do not just learn their Geniuses. They redesign work around what the framework revealed. Roles shift. Projects get reassigned. Pairings change. The team structure after the debrief looks different from the structure before it.

These teams also build Working Genius into their operating rhythm. The framework is not a one-time session. It is the lens they use for quarterly planning, project staffing, and performance conversations. Working Genius becomes the language the team speaks when talking about contribution.

They also have a leader who models using the framework. The CEO or principal references their own Geniuses in team meetings. They name when they are working outside their zone. They ask for help. The permission to admit drains and mismatches flows from the top. The rest of the team follows.

Teams that see transformational results share these traits. For more detail on designing sessions around these patterns, see the guide on Working Genius team building:

• They act fast on small changes. The debrief reveals someone is drained by a standing project. The project is reassigned within two weeks. The speed matters. It signals the framework is not just theory. It is how the team now makes decisions.

• They revisit the framework every quarter. Working Genius is an agenda item in quarterly leadership offsites. The team reviews current projects, scans for mismatches, and adjusts. The repetition keeps the insights live.

• They use Working Genius in hiring. When a new role is designed, the team maps the work to the Geniuses the role demands. When interviewing, they assess not just skill but energy fit. The person hired is more likely to thrive because the role was designed around contribution, not just competence.

• They pair people intentionally. Projects are staffed with complementary Geniuses. Wonder pairs with Invention. Discernment pairs with Galvanising. Enablement pairs with Tenacity. The pairings are deliberate, not accidental. The output improves and the energy cost drops.

• They name when the framework is not helping. If Working Genius is not solving a specific issue, they say so. They do not force the tool into every problem. They use it where it fits and use other tools where it does not. The clarity keeps the framework credible.

The teams that see modest improvement are the teams that understand Working Genius but do not redesign work around it. They know their Geniuses. They reference them occasionally. But roles stay the same. Projects are staffed the same way. The framework becomes trivia instead of structure.

12. What happens if you skip the facilitator and just use the assessment

Some teams try to save money by skipping the facilitated debrief. They buy the assessments, distribute them to the leadership team, and ask everyone to read their own results. The plan is to discuss the findings in the next team meeting.

This approach almost never works. The assessment gives each person their own Geniuses, Competencies, and Frustrations. What it does not give is the team-level patterns. Who is working outside their zone. Which pairings are broken. Which projects are staffed wrong. Those insights require a facilitator who can read the whole team's results together and surface what the group cannot see on their own.

Without the facilitator, the conversation drifts. The team reads their results. Someone says: oh, that is interesting. Someone else says: that makes sense. The meeting moves on. No work gets redesigned. No projects get reassigned. The assessment produces curiosity but not change.

The facilitator also creates psychological safety for the hard conversations. A leader might be drained by their current role but unwilling to admit it to their peers. The facilitator names the pattern. The leader feels permission to agree. The conversation shifts from personal failure to role mismatch. That reframe only happens when a neutral third party is in the room.

What you lose by skipping the facilitator:

• Team-level pattern recognition that individuals cannot see

• A structured debrief that connects results to real work friction

• The psychological safety to name drains without fear of judgment

• A 90-day action plan that translates insight into behaviour change

• Expert guidance on which changes to prioritise first

If budget is genuinely constrained, delay the Working Genius work until you can afford the facilitated debrief. A self-guided session is not half the value. It is closer to 10 percent of the value.

13. How Working Genius compares to other team frameworks

Most leadership teams have tried other frameworks before they get to Working Genius. StrengthsFinder, Myers-Briggs, DISC, Enneagram, Five Dysfunctions. Each tool serves a different purpose. Understanding where Working Genius sits in that landscape helps you know whether it is the right next move.

Working Genius vs StrengthsFinder: StrengthsFinder tells you what someone is naturally good at. The framework is excellent for individual development. It helps people understand their talents. What it does not do is map how those talents contribute to team-level work. Two people can both have Strategic as a strength and still contribute in completely different ways.

Myers-Briggs and DISC map personality and communication style. These tools are useful for understanding how someone prefers to process information, make decisions, or interact with others. What they do not map is energy. A person can have a personality that fits the role perfectly and still be drained by the work the role demands.

Enneagram maps core motivations and fears. It is a powerful tool for self-awareness and personal growth. It helps people understand why they react the way they do. What it does not map is contribution. Knowing someone is a Type 3 does not tell you whether they should be leading ideation or driving execution.

Five Dysfunctions addresses team health and trust. It diagnoses whether the team can have conflict, hold each other accountable, and commit to decisions. It is the right tool when the relationships are broken. It is not the right tool when the relationships are intact but the work distribution is off.

Working Genius maps contribution and energy. It tells you which types of work energise someone and which types drain them. That makes it the right tool when the issue is not skill, personality, or trust. The issue is that talented people are working outside their zone and the team cannot figure out why performance is suffering.

The frameworks are not mutually exclusive. A leadership team might use Five Dysfunctions to rebuild trust, then use Working Genius to redesign work distribution. They might use DISC to improve communication, then use Working Genius to staff projects. The tools solve different problems. Choose the one that matches the friction you are actually experiencing.

14. When to bring Working Genius back for a second session

Most teams treat Working Genius as a one-time session. They complete the debrief, implement the changes, and move on. But some teams benefit from a second session 12 to 18 months later.

A second session is worth it when the team composition has changed. If three new people have joined the leadership team since the original debrief, those people missed the shared language the rest of the team built. They do not know each other's Geniuses. They are not thinking in contribution terms. Bringing them into a refresher session levels the field.

A second session also helps when the team has drifted back to old patterns. The original debrief produced change. Six months later, the changes held. Twelve months later, the team is back to assigning work based on availability instead of Geniuses. The drift is subtle. No one notices until burnout starts creeping back. A second session resets the frame.

A third reason for a return session is when the organisation's work has changed. The team completed Working Genius while running steady-state operations. Now the organisation is in a growth phase, or a turnaround, or a major strategic shift. The types of work the leadership team is doing are different. The Geniuses required for the new phase might not match the ones the team has. A second session maps the new reality.

Signs the team would benefit from a second Working Genius session:

• More than 30 percent of the leadership team has turned over since the original debrief

• The team is no longer using Working Genius language in regular conversations

• Projects are being staffed the old way despite the original plan

• New burnout or energy issues are surfacing that were not present after the first debrief

• The organisation has entered a new phase that demands different types of contribution

A second session is shorter than the first. The team already knows the model. The facilitator focuses on recalibration, not education. The session might be three hours instead of a full day. The cost is lower. The value is in preventing drift.

15. How to explain Working Genius to your board when requesting budget

If you need board approval to hire a facilitator, the way you frame the request determines whether the budget gets approved.

Do not frame Working Genius as team-building. Boards hear team-building and think trust falls and personality quizzes. They do not see the ROI. They see soft skills and subjective outcomes. The request gets declined or delayed.

Frame Working Genius as an operational efficiency tool. The board cares about execution velocity, burnout reduction, and whether the leadership team is structured to deliver the strategy. Working Genius addresses all three. The request is not about making people feel good. It is about reducing friction in how work gets done.

Language that lands with boards:

• We have talented people underperforming because they are working outside their strengths. This names the problem as a resource allocation issue, not a morale issue. Boards understand resource allocation.

• Projects are taking longer than they should because the wrong people are leading them. This connects Working Genius to delivery timelines. Boards care about delivery.

• We are seeing burnout in key roles and the root cause is energy mismatch, not workload. This frames burnout as fixable through better role design, not through adding headcount. Boards prefer efficiency over expansion.

• The framework will help us staff projects faster and with better outcomes. This connects Working Genius to project success metrics. Boards care about outcomes.

• We will see measurable improvement in leadership team velocity within 90 days. This gives the board a timeline and a success metric. Boards approve requests that come with accountability.

What to include in the board request:

• The specific friction the leadership team is experiencing right now

• The cost breakdown for assessments, facilitation, and follow-up

• The expected outcomes in the first 90 days

• How success will be measured six months post-debrief

• A brief explanation of what Working Genius is and who created it

Keep the request to one page. Boards do not read three-page proposals. Lead with the problem and the cost. Follow with the expected return. Close with the timeline.

16. What mid-level managers need to know if the exec team has done Working Genius

When a leadership team completes Working Genius, the framework often stops at the exec level. The senior team learns their Geniuses. The rest of the organisation never hears about it. That creates a language gap.

The exec team starts making decisions based on Working Genius. A project gets reassigned. A role gets redesigned. A meeting structure changes. Mid-level managers do not understand why. They were not in the debrief. They do not have the context. The changes feel arbitrary.

If your exec team has done Working Genius, cascade the framework down. Not necessarily full debriefs for every manager. At minimum, share the language. Teach the six types. Explain what Geniuses, Competencies, and Frustrations mean. Give managers permission to think about their own roles through the contribution lens.

What mid-level managers need after the exec team completes Working Genius:

• A summary session that explains the model. Thirty to sixty minutes. Walk through the six types. Show how the exec team is using it. Invite questions. The session does not need to include individual assessments. It needs to create shared language.

• Access to the assessment if they want it. Some managers will want to complete their own Working Genius. Make the assessment available. Let them self-fund if budget is tight. The individual insight is valuable even without a full team debrief.

• Permission to redesign their own roles. If a manager discovers they are working outside their Geniuses, they need agency to shift the work. That might mean swapping projects with a peer. It might mean delegating differently. The permission needs to come from the exec team explicitly.

• Examples of how the exec team is using Working Genius. Do not keep the changes secret. When a project gets reassigned because of Genius fit, tell the organisation why. When a role gets redesigned, name the Working Genius reasoning. The transparency builds trust and spreads the language.

• An invitation to bring their own team into the framework. A mid-level manager who finds Working Genius valuable will want to use it with their own direct reports. If budget allows, offer to fund facilitated debriefs for high-performing teams one level down. The cascading effect multiplies the investment.

The mistake is keeping Working Genius locked at the exec level. The framework is most powerful when it becomes the organisation's shared language for how work gets done. That only happens if the language spreads beyond the leadership team.

17. How Working Genius shows up in performance reviews

After a leadership team completes Working Genius, performance reviews start to shift. The conversation is no longer just about what someone delivered. It is also about whether they were working in their Geniuses while delivering it.

A leader might hit every target and still be drained. Before Working Genius, that leader gets a positive review. After Working Genius, the manager asks: you delivered, but how much of your work was in your Frustrations? If the answer is 60 percent, the performance is unsustainable. The review becomes a role redesign conversation.

Another leader might underperform because they are working entirely outside their zone. Before Working Genius, that underperformance gets framed as a skill issue or a motivation issue. After Working Genius, the manager asks: what percentage of your role matches your Geniuses? If the answer is 10 percent, the underperformance is a role mismatch, not a talent problem.

Questions to add to performance reviews after Working Genius:

• What percentage of your current role is in your Working Geniuses? If the answer is below 40 percent, the role needs redesign. High performers thrive when at least half their work sits in their Geniuses.

• Which projects energised you this quarter and which drained you? This question surfaces energy patterns the performance data alone cannot show. A leader might excel at budget management and hate every minute of it. That insight matters.

• Are there tasks in your Frustrations we can move to someone else? Not every Frustration can be eliminated. But some can. Asking the question opens the conversation about what is movable.

• What type of work would you like more of? This invites the leader to name their Geniuses without using the framework language. The answer reveals where they want to lean in.

• How can we pair you with others to complement your Geniuses? This shifts the review from individual performance to team design. The best performance often comes from better pairing, not from individual effort alone.

The performance review after Working Genius is not softer. It is more precise. The conversation distinguishes between poor performance caused by lack of skill and poor performance caused by role mismatch. The first requires coaching or exit. The second requires redesign.

18. What to do when someone's self-assessed Geniuses do not match their behaviour

The Working Genius assessment is self-reported. Most people answer honestly. Some people answer aspirationally. They score high in the Geniuses they wish they had, not the ones they actually have.

A leader might score high in Wonder because they want to be a strategic thinker. But in meetings, they never ask the big questions. They jump straight to execution. Their behaviour shows Tenacity, not Wonder. The mismatch creates confusion when the team tries to staff projects based on the results.

When someone's results do not match their behaviour, do not ignore it. The facilitator should name the gap in the debrief. The conversation might reveal the person is suppressing their real Geniuses because the role has never allowed them. Or it might reveal they do not understand what Wonder actually is. Or it might reveal they are burned out and their natural energy has shifted.

How to address mismatched results:

• Ask what the person was thinking when they answered each question. The assessment includes scenarios. Walk through the ones where the person scored unexpectedly. Ask them to explain their reasoning. The conversation usually surfaces the disconnect.

• Compare the results to observed behaviour. If the team has worked together for years, they know each other's patterns. A leader might score high in Invention but the team has never seen them generate a new idea. Trust the observed behaviour more than the score.

• Retest after six months. Sometimes the mismatch is because the person was in the wrong headspace when they took the assessment. They were stressed, burned out, or distracted. Six months later, in a different state, the results might shift. A second test clarifies whether the first one was accurate.

• Name the mismatch openly in the debrief. Do not let the team build a plan on false data. If a leader's results do not match their behaviour, say so. The conversation is uncomfortable for thirty seconds. The honesty prevents months of misaligned staffing decisions.

The facilitator's job is to catch these mismatches during the debrief. A good facilitator has seen enough teams to recognise when a result does not fit the person. A mediocre facilitator takes the scores at face value and moves on. The first option protects the team from bad decisions.

19. How to use Working Genius when hiring externally

Most organisations use Working Genius after someone is already in the role. But the framework is even more powerful when used before the hire. For a detailed guide on this, see the post on Working Genius for hiring.

Before posting a new role, map the work to the Geniuses it demands. A head of operations role might require Enablement and Tenacity. A head of strategy role might require Wonder and Discernment. A head of marketing role might require Galvanising and Invention. Naming the Geniuses the role demands clarifies what you are actually hiring for.

During interviews, ask questions that reveal the candidate's Geniuses. You cannot ask someone to take the Working Genius assessment before hiring them. But you can ask questions that surface their energy patterns. Tell me about a project that energised you. Tell me about work that drained you even though you were good at it. Describe a time you had to push through a task you hated. The answers reveal whether the candidate's natural Geniuses match the role's demands.

Questions that reveal Working Genius in interviews:

• What type of work do you find yourself volunteering for? People volunteer for work that sits in their Geniuses. The answer tells you where their energy lives.

• When you are working on a team project, what role do you naturally fall into? Do they generate the ideas, evaluate the options, rally the team, support others, or finish the work? The answer maps to a Genius.

• Tell me about a time you were good at something but hated doing it. This surfaces Competency. The work they describe is probably outside their Geniuses even though they can do it well.

• What part of your current role drains you the most? The answer reveals their Frustrations. If the new role demands more of that same work, they are a bad fit no matter how skilled they are.

• If you could design your ideal role, what would you spend most of your time doing? This is an aspirational question but it reveals where they want to work. If their ideal does not match the role's reality, the hire will fail.

After the hire, complete the Working Genius assessment in the first 30 days. Use the onboarding period to confirm the Genius fit. If the results show a mismatch, you can adjust the role before the person is locked in. Early course correction prevents later performance issues.

20. The long-term benefit most teams do not expect

The immediate benefit of Working Genius is better work distribution. Projects get staffed better. Energy improves. Friction drops. But the long-term benefit is something else.

Over time, Working Genius becomes the team's shared language for diagnosing problems. When something is not working, the team does not spiral into blame or confusion. They ask: is this a Genius mismatch? The framework gives them a neutral diagnostic tool. The conversation stays focused on the work, not the person.

A project stalls. Before Working Genius, the team might blame the leader, question the strategy, or assume the timeline was wrong. After Working Genius, the team asks: who is leading this, and does their Genius match the phase the project is in? If someone with Tenacity is trying to lead ideation, the stall makes sense. The fix is pairing, not blame.

A new hire is struggling. Before Working Genius, the team might assume the hire was a mistake. After Working Genius, the team asks: is this person working in their Geniuses, or did we build the role around the wrong types of work? The reframe opens the possibility of redesign instead of exit.

A leader is burned out. Before Working Genius, the team might assume the leader is weak or the workload is too high. After Working Genius, the team asks: how much of this leader's work is in their Frustrations? The question shifts the conversation from personal failure to structural problem.

The long-term benefit is not just better decisions. It is a team culture where people feel safe naming when work is draining them. Where asking for a different assignment is not a sign of weakness. Where role design is treated as an ongoing conversation, not a fixed structure. That culture reduces burnout, improves retention, and makes the team more adaptable when the organisation's needs shift.

Working Genius creates permission to talk about energy in a professional setting. Most workplace cultures treat energy as a personal problem. If you are drained, work harder. If you are struggling, push through. Working Genius reframes energy as a design problem. If you are drained, we might have put you in the wrong type of work. That reframe changes everything.

21. What happens when two people on the team have the same Geniuses

Most Working Genius debriefs reveal diversity across the leadership team. One person has Wonder and Discernment. Another has Invention and Galvanising. Another has Enablement and Tenacity. The team has coverage across all six types. The work gets distributed cleanly.

But sometimes two people have identical or near-identical Geniuses. Two leaders both have Wonder and Invention. Or two both have Enablement and Tenacity. The overlap creates a different kind of problem. The team has a gap in other areas, and the two people with the same Geniuses end up competing for the same types of work.

When this happens, the facilitator should name it explicitly. The overlap is not a failure. It is a design constraint. The team needs to decide how to handle it. Do the two people share the work that matches their Geniuses? Does one of them stretch into adjacent Competencies to fill the gap? Does the team hire someone with the missing Geniuses?

What to do when two people have the same Geniuses:

• Map the coverage gaps first. If two people both have Enablement and Tenacity, the team might be missing Wonder or Invention. Identify which types of work are underserved. That is the bigger problem than the overlap.

• Pair the two people on projects where their shared Geniuses add value. Two people with Invention can co-create better than one person working alone. Two people with Tenacity can push through obstacles faster. The overlap becomes an advantage if you use it intentionally.

• Ask one person to develop their Competencies to cover the gap. If the team is missing Discernment and one of the two people with shared Geniuses has Discernment as a Competency, ask them to lean into it. They will not be energised by it, but they can do it well enough to fill the gap until the team structure shifts.

• Consider whether the team composition needs to change. If the overlap is severe and the gaps are large, the team might need a different mix of people. That does not mean firing someone. It might mean shifting someone into a different role, or hiring someone new with the missing Geniuses.

• Name the reality without blame. Two people having the same Geniuses is no one's fault. It is just the reality of the current team composition. The conversation should focus on how to work within that constraint, not on who should change.

The overlap is easier to manage on a large team. A leadership team of ten can absorb two people with the same Geniuses. A leadership team of four cannot. The smaller the team, the more each person's Genius mix matters.

22. How to use Working Genius with remote or hybrid teams

Working Genius was designed for in-person teams. Most debriefs happen in a room with everyone present. But remote and hybrid teams can still use the framework effectively. The delivery changes. The value does not.

The debrief session works well over video. A skilled facilitator can run a Working Genius debrief on Zoom or Teams. The session takes the same amount of time. The breakout room feature handles small group discussions. The facilitator shares slides. The team discusses their results. The core mechanics translate cleanly to remote delivery.

What is harder in a remote debrief is reading the room. A facilitator in person can see when someone shuts down, when two people exchange a look, when the energy drops. Those cues are harder to catch on video. The facilitator has to name more explicitly. Ask more questions. Invite quieter voices. The session requires more active facilitation than an in-person one.

Adjustments for remote or hybrid Working Genius debriefs:

• Send the assessments a week before the session. In-person debriefs can sometimes complete the assessment during the session. Remote debriefs work better when everyone completes the assessment in advance. The session time is used for discussion, not data entry.

• Use a shared document to capture insights live. As the team discusses their results, capture key insights in a shared Google Doc or Miro board visible to everyone. The live documentation keeps remote participants engaged and creates a record the team can reference later.

• Schedule breaks every 60 to 90 minutes. Remote sessions are more draining than in-person ones. Build in short breaks. The session might run longer than an in-person debrief because of the break time, but the breaks prevent fatigue.

• Follow up with one-on-one coaching calls. Some people process better in one-on-one settings than in group video calls. Offer optional 20-minute follow-up calls with the facilitator for anyone who wants to dig deeper into their results. The individual attention increases the value for remote participants.

• Use asynchronous tools for follow-through. After the debrief, create a Slack channel or Teams thread dedicated to Working Genius. Post weekly prompts. Share articles. Invite the team to name moments when they noticed themselves working in or out of their Geniuses. The asynchronous conversation keeps the framework alive between synchronous meetings.

Hybrid teams need extra care. If half the team is in the room and half is remote, the remote participants will feel like second-class citizens. Either bring everyone into the room or put everyone on video. Do not run a hybrid session where some people are physically together and others are dialling in. The experience quality drops too far.

23. When Working Genius conflicts with org chart realities

The ideal Working Genius outcome is that every person's role aligns with their Geniuses. But most organisations have fixed structures, existing hierarchies, and roles that cannot be redesigned without triggering a full restructure. The framework reveals a mismatch. The organisation cannot immediately fix it. The tension sits unresolved.

A CFO might have Galvanising and Invention. The CFO role demands Tenacity and Enablement. The Working Genius debrief reveals the mismatch. The CFO is drained. The team knows why. But the organisation cannot move the CFO into a different role without disrupting the entire exec team. What happens next?

When Working Genius conflicts with org chart realities, start with the smallest possible shifts. You cannot redesign the role. But you can redesign how some of the work inside the role gets done. The CFO might not be able to leave the finance function, but they could hand off budget tracking to a direct report and take on innovation projects within finance. The shift is not total. It is directional.

Strategies when role redesign is not immediately possible:

• Shift tasks within the role. Even a fixed role has discretionary tasks. Identify which tasks sit in the person's Geniuses and which sit in their Frustrations. Move the Frustration tasks to someone else on the team if possible. The role title stays the same. The daily experience improves.

• Add a side project that uses their Geniuses. If someone's primary role does not match their Geniuses, give them a secondary project that does. A CFO with Galvanising might lead the organisation's culture initiative. The side project gives them energising work even though their main role still drains them.

• Pair them with someone whose Geniuses complement theirs. If the CFO has Invention but the role demands Tenacity, pair the CFO with a chief of staff who has Tenacity. The CFO generates the ideas. The chief of staff drives them to completion. The pairing compensates for the role mismatch.

• Create a transition timeline. If the mismatch is severe and cannot be resolved in the current structure, build a 12 to 24-month plan to move the person into a role that fits. The timeline gives the organisation space to prepare. The person knows the mismatch is temporary.

• Name the constraint openly. If the organisation cannot fix the mismatch right now, say so. Do not pretend the problem does not exist. Acknowledge the person is working outside their Geniuses and name what is preventing the fix. The honesty preserves trust even when the structure cannot immediately change.

The worst outcome is ignoring the mismatch because the org chart is rigid. The person stays drained. Performance declines. Eventually they leave. The organisation loses a talented leader because it would not make small adjustments within a fixed structure.

24. How to keep Working Genius relevant two years post-debrief

Most frameworks fade over time. The team completes the session. The first year, the insights are fresh. The second year, people still remember the language. The third year, Working Genius becomes something the team did once.

Keeping Working Genius relevant long-term requires intention. The framework will not maintain itself. Someone on the leadership team needs to own the language and keep it active.

Ways to keep Working Genius relevant beyond the first year:

• Add new team members through a Working Genius lens. Every time someone joins the leadership team, have them complete the assessment in their first 30 days. Debrief their results with the full team. The onboarding ritual keeps the framework alive for existing members and brings new members into the shared language immediately.

• Run an annual refresh session. Once a year, bring the facilitator back for a half-day refresh. The session is not a full re-teach. It is a recalibration. The team reviews what has changed in the past year. Which roles shifted. Which new projects launched. Whether the Genius distribution still matches the work. The refresh prevents drift.

• Use Working Genius as the lens for quarterly planning. When the leadership team plans the next quarter, map upcoming projects to the Geniuses they will require. Assign projects based on Genius fit, not just seniority or availability. The repetition every 90 days keeps the framework embedded in decision-making.

• Reference Working Genius in leadership team retrospectives. After a major project finishes, run a retrospective and include a Working Genius lens. What went well from a Genius perspective? Where did people work outside their zone? What would we staff differently next time? The reflection reinforces the framework as a continuous tool, not a one-time event.

• Create a Working Genius resource library. Compile articles, podcast episodes, and tools related to Working Genius in a shared folder. When someone on the team wants to go deeper, they have a curated starting point. The library signals that the framework is still active, not archived.

The two-year mark is when most frameworks die. The team is no longer talking about it. New people have joined who were not in the original debrief. The language fades. Preventing that fade requires deliberate repetition. The team that still references Working Genius in year three is the team that built it into their operating rhythm, not just their onboarding.

25. The single most important factor in whether Working Genius is worth it

The framework is the same for everyone. The facilitator quality varies but good facilitators exist. The cost is fixed. The assessment is solid. So why do some teams transform while others see minimal return?

The single most important factor is whether the leadership team has permission to redesign work. Not in theory. In practice. If roles are locked, if the org chart is rigid, if projects get assigned based on hierarchy instead of fit, Working Genius produces insight that cannot be acted on. The team learns their Geniuses. They cannot change how work gets distributed. The insights sit unused.

Before investing in Working Genius, audit your team's agency. Can you reassign a project based on Genius fit without needing board approval? Can you adjust someone's role without triggering a restructure? Can you pair people differently without HR pushing back? If the answer is yes, Working Genius will return value. If the answer is no, delay the work until you have the structural flexibility to act on what it reveals.

This is why Working Genius works better for founder-led organisations, independent schools, and nonprofits with strong CEOs. These environments typically have more flexibility to redesign work. The leadership team has real authority. Decisions can be made quickly. The framework lands because the team can implement immediately.

This is also why Working Genius sometimes disappoints in large corporates or highly regulated environments. The leadership team completes the debrief. They see the mismatches. They want to change how work is distributed. But every change requires approvals, policy reviews, or union negotiations. Six months later, nothing has shifted. The framework was sound. The environment was not ready.

If you are asking whether Working Genius is worth it, ask this first: does my team have the authority and flexibility to redesign work based on what the framework reveals? If yes, invest now. If no, build that flexibility first, then return to Working Genius later.

Your team already has the talent. Working Genius helps you deploy it better. But deployment requires permission to change how work gets done. Without that permission, the framework becomes expensive insight with no path to action.

Is Working Genius worth it? Yes, when the conditions are right. The framework works. The question is whether your team is structured to use it. If you are ready to redesign work around energy instead of assumptions, reach out at jonno@consultclarity.org. The conversation will clarify whether this is the right next move for your leadership team.