Working Genius Team Building: A Practical Guide
Updated: Aug 3
Last updated: August 2026.
By Jonno White.
Working Genius team building is a practical way to map how a team moves work from questions to completion, then redesign meetings, roles and handoffs around that pattern. The strongest sessions use assessment results, a shared team map, one live project and a clear follow-through rhythm, rather than stopping at self-awareness.
The official Working Genius site says nearly one million people have used the model. That reach matters less than what your team does with the results: a useful session turns six labels into better choices about who should spark work, rally people, support progress and bring tasks across the line. Working Genius explains the model and its reach.
Jump to: what the model is, how to prepare, how to run the session, the worked example, limitations, or your next action.
What this guide adds
Many Working Genius pages explain the six types or offer a menu of activities. This guide adds a decision path for choosing the right session, a practical sequence built around live work, a four-layer application test and a follow-through rhythm that keeps the workshop from becoming a pleasant conversation with no operational change.
The advice is designed for a leader, team coach or internal facilitator who already knows the team has a workflow problem but does not want to overstate what one personality-style model can solve. It uses official sources for the model, current Consult Clarity pages for related guidance and clearly labels the worked example as hypothetical.
What Working Genius team building is
Patrick Lencioni and The Table Group created the Working Genius model around six activities that appear as work moves from possibility to completion. Wonder asks whether something could be better. Invention creates an idea, Discernment tests it, Galvanising rallies people, Enablement provides responsive support and Tenacity pushes the work to completion. The official model overview explains the six types.
Each person receives two Working Geniuses, two Working Competencies and two Working Frustrations. Those results are not a verdict on character or ability. They describe where work tends to bring energy, where someone can contribute capably and where sustained effort may carry a higher cost.
The model is most useful for team building when it becomes shared language for real work. It can help a team notice why a promising idea never attracts support, why meetings circle without a decision, or why a well-supported plan repeatedly stalls near completion.
Working Genius is not a ranking system and there is no ideal combination that makes one team superior. The point is to make the full workflow visible, then decide how the team will cover each stage without expecting every person to love every kind of work.
Choose the right starting point
Start with the problem, not the activity. If people mainly misunderstand one another, begin with individual results and a shared team map. If a project keeps stalling, map that project across the six types and find the missing transition. If meetings feel wasteful, trace which type of work each agenda item actually needs.
Use a facilitated session when trust is low, seniority may silence people, the results could affect roles, or the team needs a neutral person to challenge an easy explanation. A self-led session can work when the team is psychologically safe, the leader will participate honestly and everyone understands that the profile is a conversation tool rather than a label.
Do not begin with a competitive game that rewards speed or performance. Working Genius team building should reveal contribution patterns without turning strengths into status. The safest starting point is a real piece of work that everyone recognises and can discuss without exposing confidential personal detail.
Prepare the team before the session
The official assessment uses 42 statements and normally takes about 10 to 15 minutes. Each participant needs their own licence, and the official guidance recommends completing the assessment before the team conversation. The Working Genius FAQ confirms the format and timing.
Send a short written brief that explains why the team is using the model, what will happen with the results and what the assessment cannot decide. Make it clear that the session will not be used to rank performance, remove accountability or force an immediate role change.
Choose one live project before the session. It should matter enough to make the exercise useful, but it should not involve an active grievance or a decision that requires private evidence. Write down the current goal, the point where work slows and the next decision the team must make.
Prepare a team map showing each person’s two Geniuses, two Competencies and two Frustrations. Keep the map descriptive. A gap on the map is a workflow risk to manage, not proof that the team needs to hire someone.
Run the session around real work
The Table Group’s official team application guide uses four broad moves: complete the assessment, share results, map the team and reorganise work. Its suggested timing is about 10 minutes for the assessment, 15 to 30 minutes to share, 15 to 30 minutes to map and 30 to 60 minutes to reorganise around the results. The official team application guide provides that sequence.
Those ranges are a useful minimum, not a promise that every team issue can be resolved in one sitting. A complex leadership team may need more time for the live-project discussion and less time for model explanation.
Open with the model and the purpose
Explain the six types as a workflow, then name the practical question the session must answer. A clear purpose might be: “Where does this project lose energy, and what will we change in the next two weeks?” This keeps the conversation close to observable work.
Patrick Lencioni developed the model, and The Table Group owns the framework. Jonno White is a Certified Working Genius Facilitator. Keeping those roles clear prevents a facilitator’s interpretation from being confused with the source model.
Share results without labelling people
Ask each person what felt accurate, what surprised them and where they see the pattern in their work. Let people describe their own results before teammates interpret them. Treat disagreement as useful information rather than resistance.
The language should stay tentative. “This task may be draining because it sits in your Frustration” is safer than “You cannot do this.” Competence, responsibility and energy are related, but they are not the same thing.
Read the team map
Look for clusters, gaps and handoff risks. A team rich in Wonder and Invention may produce many possibilities but struggle to mobilise and finish. A team rich in Enablement and Tenacity may deliver reliably while leaving too little space to question whether the work is worth doing.
Then test the map against evidence from the live project. Ask where decisions slowed, where ownership became unclear and where support arrived too late. If the map does not explain the actual pattern, do not force the pattern to fit.
Apply the map to one live project
Place the live project at its current stage and trace what has already happened. Name the next kind of work required, the person who will lead it and the people who will support it. A person can lead work outside a Genius, but the team should recognise the likely energy cost and provide cover.
Keep ownership explicit. “The team will galvanise stakeholders” is vague. “Aisha will prepare the case, Marco will test it with two affected teams, and Priya will make the go or stop decision on Thursday” makes the handoff visible without pretending the profile made the decision.
Turn insight into named changes
Finish with a small operating change that can be observed. The team might add a Discernment question before approving new ideas, separate invention from decision-making in meetings, or pair a strong Galvaniser with someone who has Tenacity for the final delivery stage.
Record who owns the change, where it will appear and when the team will review it. The official Working Genius workshop describes an action plan as a core outcome, which is why a session should end with more than a team map. The official workshop page describes the intended team outcomes.
Use the four-layer application test
I use a simple four-layer test to stop Working Genius team building at the point where it is still useful. This is an original analytical framework based on the public model and facilitation judgment, not a validated Table Group diagnostic or a claim of measured client results.
The awareness layer asks whether people can explain their own results without using them as excuses. The map layer asks whether the team can see a credible pattern across the six types. The work layer asks whether that pattern explains a real delay, decision or handoff. The rhythm layer asks whether the team has changed a recurring meeting, project step or review habit.
If awareness is strong but the map is weak, gather more examples before redesigning roles. If the map is clear but the live work does not match it, investigate other causes. If the work insight is useful but no rhythm changes, the session is likely to fade.
This test also provides a stopping rule. Working Genius should remain one input when the evidence points instead to unclear strategy, weak capability, missing capacity, unresolved conflict, unsafe behaviour or a decision that leaders are avoiding.
Worked example: a project that keeps stalling
The following scenario is hypothetical and is included to show the method, not to imply a client result. Imagine a six-person leadership team launching a new staff onboarding process. The team has produced several strong ideas and consulted widely, but the launch date has moved twice because nobody feels ready to commit.
The team map shows plenty of Wonder, Invention and Enablement, with less natural energy in Galvanising and Tenacity. That pattern is a useful hypothesis, but it is not yet the conclusion. The facilitator checks the project record and finds that proposed decisions repeatedly return for more input, while final tasks have no named owner.
The team decides to separate consultation from commitment. One leader with strong Discernment will recommend the final design after a fixed review, another will Galvanise managers around the reason for change, and a leader who can contribute Tenacity will own the launch checklist. The team will review the new handoff at its next project meeting.
The useful outcome is not that the team has “balanced” every Genius. It is that the team has named the missing work, assigned ownership and created a point where it can test whether the change helped. If progress still stalls, the team should investigate scope, authority, capacity and stakeholder conflict rather than adding more profile language.
What to change after the session
Revisit the map while the work is still fresh. At the next relevant meeting, ask which stage the project is in, which Genius the next task needs and whether the current owner has enough support. Keep the question attached to a real agenda item rather than creating a separate ritual that people must remember.
After a few weeks, review the operating change rather than retaking the assessment. Look for a clearer decision, faster handoff, better ownership or a more honest conversation about energy. Do not invent a success measure after the fact.
When a change works, write it into the team’s normal process. When it does not, say what the model failed to explain. The Working Genius implementation guide and steps to take after Working Genius offer related follow-through ideas.
When Working Genius team building will not solve the problem
Working Genius does not replace role clarity, performance management, clinical support, conflict resolution or a sound strategy. It cannot prove why a person is disengaged, and it should not be used to diagnose personality, mental health or motivation.
The model can also become a convenient excuse. A Working Frustration does not remove responsibility for essential work. Leaders still need to decide which tasks can be reassigned, which must be shared and which remain part of a role.
Be cautious when the team lacks trust or when results may influence employment decisions. Use a qualified facilitator, separate development from assessment and keep private information private. If a safety, conduct or legal issue is present, address that issue through the right process rather than through a team-building exercise.
How to choose between self-led and facilitated
Choose self-led delivery when the team has a clear purpose, enough trust for candid discussion and a leader who can hold the model lightly. The official application guide gives a usable starting structure, and a small team can apply it to one project without turning the session into a major event.
Choose facilitation when the stakes are higher than the model. A neutral facilitator can slow down premature conclusions, protect quieter voices and keep senior leaders from defining everyone else’s experience. Facilitation is also useful when the session must produce a written operating plan rather than awareness alone.
Before choosing, ask for the written outcome, the planned use of assessment data, the way live work will be included and the follow-through method. A facilitator should be able to answer those questions in writing. You can also read how to run a Working Genius workshop or compare Working Genius group activities.
Your next action
Choose one live project and write down where it currently stalls. Then map the next two stages of work against the six Working Geniuses and name one handoff to test. That small exercise will tell you whether the team needs a simple internal conversation or a more carefully facilitated session.
If you want a written plan for a practical Working Genius team-building session, email me at jonno@consultclarity.org. I can help you shape the session around the real work your team needs to move.
I'm Jonno White, a Brisbane-based leadership consultant, keynote speaker and Certified Working Genius Facilitator, certified through Patrick Lencioni's Table Group, and the author of Step Up or Step Out, with more than 10,000 copies sold. I host The Leadership Conversations Podcast and work with schools, corporates and nonprofits around the world.