How Do You Plan a Working Genius Retreat That Actually Changes Your Team?

Planning a Working Genius retreat that produces lasting change requires three things working together: a diagnostic phase before the day, a session design built around the team's real problem rather than generic activities, and a follow-through structure locked in before people leave the room. Miss any one of these and the retreat will feel good on the day and vanish by Tuesday.

Who this is for: Leadership team facilitators, CEOs, chiefs of staff, and school principals planning a Working Genius offsite for their executive team or senior leadership group.

The 25 steps below are organised into four phases: pre-retreat design and diagnostics, agenda design and session structure, session facilitation and conversation management, and post-retreat integration. Each step addresses a specific failure point that causes retreats to produce insight without change. For a practical guide to delivering the session itself, the article on how to run a Working Genius workshop covers the detailed session flow.

What Separates a Working Genius Retreat from a Generic Team Offsite?

A Working Genius retreat is built around a shared language that every participant already speaks before they arrive. Everyone has completed the 42-question assessment and received their individual report covering their two areas of genius, two areas of competency, and two areas of frustration. The retreat builds on that foundation, moving from individual self-awareness into team dynamics, workflow redesign, and honest conversation about what has been creating friction.

According to Gallup's State of the Global Workplace report released in April 2025, global employee engagement fell to 21 per cent in 2024, a confirmed historical decline. That drop was estimated to cost the global economy $438 billion in lost productivity. A well-designed Working Genius retreat addresses one of the root causes directly: people spending their working hours in areas of competency or frustration rather than in their areas of genius.

Research from the Emburse 2025 State of Corporate Offsites report found that high-performing companies host an average of 2.8 offsites annually, compared to 2.4 for underperforming companies. Frequency matters because the behaviours established in a retreat need reinforcing across multiple sessions.

Pre-Retreat Design and Diagnostics

1. Run the Diagnostic Before You Pick the Date

Start by identifying the specific problem the retreat needs to solve. Is the team stuck in Wonder and Invention without moving to execution? Is there unresolved conflict between two senior leaders blocking collaboration? Is a talented group failing to follow through because nobody owns completion? Each of these requires a different session design, and none of them is answered by a standard Working Genius debrief.

Book 20-minute one-on-one conversations with each leadership team member two to three weeks before the retreat. Ask the same three questions in every conversation: what is working well right now, what single change would make the biggest difference to how you work together, and what are you privately worried about that has not been said in a team meeting? Listen for patterns across the conversations, not individual complaints. The conversation itself has value before the retreat begins. People feel heard, which lowers defensiveness when the same issues surface in the room.

2. Complete All Assessments Well in Advance

Every person attending the retreat should complete the Working Genius assessment at least three to five business days before the session. This gives everyone time to review their individual report and sit with the results before discussing them in a group. If even one person has not completed the assessment by the time the retreat begins, the team map is incomplete and group-level discussions become awkward.

Send the link to workinggenius.com, set a firm deadline, and follow up directly with anyone who has not submitted their results. Encourage participants to review their results privately before the retreat. A brief pre-work prompt asking each person to note one insight and one question from their report creates a useful starting point for the opening discussion.

3. Build the Team Map Before the Day

The team map shows every participant's genius types in a single visual, making it immediately obvious where the team is strong and where it has gaps. If you have access to all individual reports before the day, building the map in advance means the team can spend retreat time discussing what it reveals rather than constructing it from scratch.

Look for patterns before the retreat begins. A team heavy in Galvanising and Tenacity but light in Wonder and Discernment will struggle differently than a team loaded with Wonder and Invention but lacking Enablement and Tenacity. Understanding these patterns in advance helps the facilitator design discussions that are specific and relevant rather than generic.

4. Identify the Working Genius Gaps in Your Current Team Composition

Every leadership team has structural gaps. Some teams are heavy on Wonder and Invention but light on Discernment and Galvanising. Others have multiple people strong in Enablement and Tenacity with nobody naturally wired for Wonder. These gaps explain recurring frustrations that feel like personality conflicts but are actually mismatches in how the team's genius types are distributed.

Once you have the results, look for three patterns: clustering (four Discerners who are excellent at critique but slow to move into action), absence (no natural Galvanisers means ideas stall before activation), and mismatch (a leader responsible for driving new initiatives whose frustration is Galvanising). These patterns should shape your retreat agenda. The composition analysis tells the team what it cannot see about itself.

5. Set a Single Measurable Outcome for the Retreat

Retreats fail when they try to solve everything. A day-long session cannot rebuild trust, align the strategy, fix three underperforming hires, and redesign the meeting cadence. It can do one of those things well, or all of them poorly.

Pick the one outcome that, if achieved, would make the investment worthwhile. Frame it as a measurable statement, not a vague aspiration. Vague: improve team communication. Measurable: by the end of this retreat, every person on the leadership team will be able to name the Working Genius profile of every other person and identify one specific way they will change how they work with that person in the next 30 days. Write the outcome at the top of your planning document, share it with the facilitator, and email it to the team a week before so they know what success looks like before they arrive.

6. Communicate the Why Before People Arrive

Leaders sometimes underestimate how much anxiety a team assessment session can generate. Some people arrive worried that their results will expose a weakness, or that the retreat is a veiled performance management exercise. A short communication from the team leader before the retreat, explaining the purpose and framing Working Genius as a tool for better collaboration rather than individual evaluation, makes a measurable difference to how openly people engage on the day.

Emphasise that there are no good or bad genius types. Every type contributes something essential to the work cycle. A team of all Tenacity geniuses would execute brilliantly but produce nothing new. A team of all Wonder geniuses would ask great questions but deliver nothing. The framework is specifically designed to show interdependence, not hierarchy.

7. Choose the Right Facilitator or Decide to Run It Yourself

You have two options: facilitate the retreat yourself or bring in an external facilitator who knows the Working Genius model and has led senior team sessions before. Both approaches work, and both carry trade-offs.

If you facilitate it yourself, you save cost and keep full control. The risk is that you cannot participate fully while also holding the process. If the retreat needs to surface tension between you and another team member, facilitating and being in the conversation at the same time is very difficult. An external facilitator brings neutrality. A skilled facilitator will name dynamics you cannot see from inside the team and push the conversation further than you would feel comfortable pushing it yourself. Vet any external facilitator with these specific questions: what is the hardest conversation you have facilitated in a leadership team retreat, how do you manage a session when the senior leader in the room is part of the problem the team needs to address, and can you walk me through a sample agenda from a previous Working Genius retreat and explain why you structured it that way?

8. Schedule the Retreat at a Time When People Can Actually Focus

Timing determines attention. A retreat scheduled the week before a board meeting or two days after a major launch will not receive the focus it requires. Look for a window where no major deadlines fall in the 72 hours before or after the retreat, no one on the leadership team is about to go on extended leave, and the business is not in active crisis mode. If you cannot find a window where all three conditions are true, consider splitting the session into two half-days rather than one long day.

Agenda Design and Session Structure

9. Open With the Problem, Not the Framework

Most Working Genius retreats open with a 30-minute explanation of the six types. The facilitator walks through Wonder, Invention, Discernment, Galvanising, Enablement, and Tenacity. The team listens politely, and the session moves into application. This is backwards.

Start with the problem the team is experiencing right now. Name it specifically, using the language from your pre-retreat diagnostic conversations. If three people told you privately that the leadership team agrees in meetings and then does its own thing afterward, say that sentence out loud in the opening five minutes. That opening earns attention because it tells the team the session is not theoretical. Only after you have named the problem do you introduce the framework. The framework becomes the explanation for the problem, not the starting point.

10. Run the Individual Reflection Stage First

Open the retreat by giving each participant a structured opportunity to share their genius types and their initial reaction to them. A simple format works well: each person names their genius types, shares one work situation where they noticed their genius operating, and names one area of frustration they have been quietly carrying. Keep each person's contribution to two to three minutes.

Do not skip the frustration conversation. The areas of frustration are where teams often discover the root cause of persistent friction. Someone who has been producing excellent work while quietly dreading certain meetings has a story that their colleagues need to hear. When the senior leader goes first and speaks candidly about both their genius and their frustration, it creates permission for everyone else to do the same.

11. Use the Assessment Debrief to Surface Surprises, Not Just Confirm What People Already Knew

Everyone in the room has already completed the Working Genius assessment and knows their results. The debrief session should not simply be a read-through of what people already know about themselves. It should surface gaps, surprises, and mismatches that individuals could not see without the whole team's data in front of them.

Ask three questions in the debrief: where did your results surprise you, what did you expect to see that did not show up, and who in this room is currently being asked to work in their area of frustration more than 30 per cent of the time? The third question produces the most valuable conversation. Almost every leadership team has at least one person spending most of their time in work that drains them who has not said it out loud because they assume it means they are failing. Give people permission to name the mismatch. The retreat is the place to say these things.

12. Map Current Responsibilities Against Working Genius Profiles

Give each person a blank sheet of paper. Ask them to list the five to seven major responsibilities that take up most of their time in their actual role, not the responsibilities listed in their position description. Then ask them to mark each responsibility with a W, I, D, G, E, or T based on which genius type that work primarily requires.

Now ask the question that matters: how much of your current workload sits in your areas of working genius versus your areas of competency or frustration? If someone discovers that 60 per cent of their role requires Enablement and Tenacity but both are areas of frustration, you have just diagnosed why they are burning out. This exercise does not solve the problem in the moment, but it names it with a clarity that makes follow-through possible.

13. Run a Live Case Study Using a Real Project the Team Is Stuck On

Theory only lands when it connects to something real. Pick a project or decision the team is currently stuck on and use it as a live case study to demonstrate how Working Genius applies in practice. The project should be real and current, should matter enough that people care about the outcome, and should be genuinely stuck or stalled.

Walk the project through the six stages of Working Genius. Ask the team to identify which stages have been handled well and which have been skipped or rushed. In most cases, you will find the team spent weeks in Wonder and Invention, skipped Discernment entirely, jumped straight to Galvanising, and then stalled in Enablement because nobody wanted to own the execution. Then ask: who in this room has the natural genius to do the stage the team skipped, and why were they not involved earlier? A single live case study demonstrating the pattern will do more to shift behaviour than three hours of explanation.

14. Build a Team Genius Map That Shows Who Owns What

Create a simple grid with the six types of Working Genius down the left side and each team member's name across the top. In each cell, mark whether that type is a genius, a competency, or a frustration for that person. The grid shows you three things immediately: where you have redundancy, where you have gaps, and where you have mismatches between a person's genius and the work they are responsible for.

Print the grid and put it on the wall in your leadership team meeting room. Refer to it every time you assign a new project or restructure a responsibility. The map is not just a diagnostic tool, it is a decision-making tool. The article on practical steps after Working Genius with your team covers how to keep the team map visible and active in the 90 days after the retreat.

15. Create a Shared Language for Calling Out Genius Gaps in Real Time

The retreat will end and the team will return to work. Within two weeks, someone will assign a task to the wrong person, a project will stall because nobody owns Discernment, or a meeting will spiral because the team is stuck in Wonder and cannot move to Galvanising. If the team does not have a shared language for calling out those moments in real time, the patterns will repeat.

Build the language during the retreat. Agree on phrases the team can use to name what is happening without it feeling like personal criticism. Try: "I think we are missing Discernment on this. Who in the room is strong there, and what are we not seeing?" or "This feels like we have done Wonder and Invention but skipped Galvanising. Who is actually going to move this forward?" Practice using the language in the retreat by role-playing a scenario where the team is stuck in one stage and someone has to call it out.

16. Design the Follow-Through Structure Before the Retreat Ends

This is the step most retreats skip, and it is the reason most retreats do not produce lasting change. The team leaves energised, returns to work, and within two weeks the urgency of the day-to-day drowns out everything that felt important in the session.

You need a follow-through structure, and you need to build it before people leave the room. The structure requires three things: a 30-day check-in meeting where the team reviews what has changed since the retreat and what has stayed the same, a 60-day review where each person shares one specific example of how they used the Working Genius framework to make a decision or reassign a responsibility, and a 90-day retrospective where the team assesses whether the measurable outcome was achieved. Schedule all three before the retreat ends. Put them on the calendar. Assign someone to own the agenda for each one.

Logistics and Environment Setup

17. Pick a Venue That Removes Distractions Without Feeling Like a Vacation

The venue signals what kind of session this is. A resort with a golf course signals relaxation. A conference room in your office signals another meeting. Neither sends the right message for a Working Genius retreat. You need a space that feels different enough to create focus but professional enough to signal serious work.

Look for these three characteristics: off-site but within 30 minutes of your office, natural light with space to move, and minimal interruptions from staff or external noise. Avoid venues with too many recreational amenities. A large wall or movable whiteboard that can show the team map visually for the full group makes the mapping discussion dramatically more engaging than a map visible only on a laptop screen. Confirm AV requirements with the venue well in advance.

18. Design the Room for Discussion, Not Presentation

Theatre-style seating, where participants face a screen or presenter, is the wrong configuration for a Working Genius retreat. The most productive discussions happen when participants can see each other. A horseshoe or U-shaped table arrangement, a round table, or cabaret-style seating all support the kind of dialogue the retreat requires. Communicate seating preferences to the venue in advance and arrive early enough to arrange the room before participants enter.

19. Schedule Breaks That Reset Energy, Not Just Fill Time

A six-hour retreat without strategic breaks produces declining attention and surface-level conversation by hour four. Plan 15-minute reset breaks every 90 minutes and a full lunch break of at least 60 minutes. Do not use lunch as a working session. Build in a five-minute pause after any hard conversation.

If the session just surfaced unresolved conflict or named a difficult truth, do not immediately move to the next agenda item. Track energy in the room. If attention drops 20 minutes before the scheduled break, call the break early. Breaks are not wasted time. They are the moments when people integrate what they have just learned and prepare for what is coming next. Some of the most valuable Working Genius conversations happen during a walk or over lunch, when the frame of the formal session is still fresh.

20. Provide the Right Materials Without Overcomplicating the Setup

You need printed copies of each person's Working Genius assessment results, large sticky notes or flip chart paper for group exercises, markers that actually work, and a printed one-page agenda that every person has in front of them. The agenda should show the sequence of sessions, the scheduled breaks, and the measurable outcome for the day.

What you do not need: slides for every point, elaborate workbooks that nobody will open after the retreat ends, or branded retreat materials that add cost without improving the quality of the conversation. The materials should disappear into the background. If people are thinking about the tools instead of the content, the setup is wrong.

21. Set Ground Rules That Make Hard Conversations Possible

A retreat only produces real change if people are willing to say things they do not normally say in team meetings. That requires ground rules named at the start of the day. Try these four: what is said in this room stays in this room unless the person gives permission, no devices during sessions except during breaks, directness is expected and if you see a problem you name it, and listening to understand comes before jumping to solutions. Write the ground rules on a flip chart and leave them visible throughout the day.

Session Facilitation and Conversation Management

22. Start Every Session With a Clear Question, Not a Topic

Sessions structured around topics produce wandering conversations that feel productive but go nowhere. Sessions structured around specific questions produce focus and decisions. Instead of "let us talk about team alignment," try "what is the one decision we keep revisiting because we have never fully aligned on it?" Instead of "let us discuss how we use Working Genius in our roles," try "where are you currently being asked to work in your area of frustration, and what is it costing the team?"

Write the question on a flip chart at the front of the room and leave it visible for the entire session. When the conversation drifts, point back to the question and refocus. Questions create boundaries. Topics create drift.

23. Use Breakout Pairs to Surface What People Will Not Say in the Full Group

Some insights only appear in smaller conversations. Structure breakout pairs intentionally. Do not let people choose their usual partner. Pair the CEO with someone further down the hierarchy. Pair the person who talks most with the person who talks least.

Give pairs a tight question and a strict time limit, for example: "You have eight minutes. Each person gets four minutes to answer this question: where in your current role are you being asked to work against your genius, and what would need to change for that to stop?" Bring the group back together and ask for themes that surfaced across multiple conversations, not full reports from every pair. Breakout pairs surface honesty. Full group discussions surface patterns.

24. Manage the Person Who Dominates the Conversation Without Shutting Them Down

Every leadership team has at least one person who takes most of the airtime. They are processing out loud, or they are energised by the conversation, or they genuinely believe their point is the most important in the room. Your job as facilitator is to create space for other voices without making the dominant person feel punished.

Try three moves: use their name and redirect ("that is a useful point; before we go further I want to hear from people who have not spoken yet"), set a structure that limits airtime ("we have six people and 15 minutes, so roughly two minutes per person"), or assign them a different role ("I am going to ask you to listen to the next three responses and summarise what you are hearing without adding your own point yet"). If one person takes 60 per cent of the airtime, the other five disengage.

25. Plan for the Conversation That Will Derail the Agenda

Every retreat has a moment where the planned agenda collides with the conversation the team actually needs to have. Someone names an issue you did not anticipate. The room goes quiet. The energy shifts. You have a choice: stick to the agenda or follow the conversation.

Follow the conversation. The best retreats are not the ones that execute the agenda perfectly. They are the ones that create space for the conversation the team has been avoiding for months. Here is how to spot it: the energy in the room changes and people lean in, someone says something that makes others uncomfortable and nobody rushes to smooth it over, and the conversation touches on something real and current rather than theoretical. When that moment arrives, pause the agenda and name what is happening. The planned agenda is a scaffold. The real work happens when the scaffold holds the conversation the team could not have anywhere else.

26. Call Out the Dynamic When the Room Goes Performative

There is a moment in almost every retreat where the conversation shifts from real to performative. People start saying what they think they are supposed to say. The language gets careful. The energy flattens. Everyone is agreeing, but nothing of substance is being said.

When you notice it, call it out. Try: "I am noticing the conversation just shifted. It feels like we are being polite instead of honest. What is the thing we are not saying right now?" Then pause. Do not fill the silence. The shift to performative usually happens for one of three reasons: someone in the room has positional power and people are self-editing, the team just touched something uncomfortable and instinctively pulled back, or people are tired and reverting to safe statements.

27. End Every Major Session With a Commitment, Not Just a Summary

Summaries feel productive but produce nothing. Commitments produce action. At the end of each major session, ask every person to name one specific thing they are committing to do differently in the next 30 days based on what was just discussed.

The commitment must be specific and observable. Vague: I am going to be more mindful of Working Genius when assigning tasks. Specific: before I assign a new project, I will check the team genius map and confirm the person I am assigning it to has that type of work in their area of genius or competency; if it is in their area of frustration, I will reassign it or pair them with someone strong in that area. Write every commitment into a shared document, list them by name, and email the document to the team the day after the retreat.

Post-Retreat Integration and Accountability

28. Send a Same-Day Summary That Captures Decisions, Not Just Discussions

Send a summary within 24 hours of the retreat ending. It does not need to be long. It needs to be clear. Include: the measurable outcome the retreat was designed to achieve and whether it was achieved, the key decisions made during the day (not the discussions, the decisions), the individual commitment each person made listed by name, and the dates of the 30-day, 60-day, and 90-day follow-up meetings.

Keep it to one page. If the summary is three pages of dense paragraphs, nobody will read it. The summary is not a record of everything that was said. It is a reference document that reminds the team what they agreed to do and when they agreed to do it by.

29. Integrate Working Genius Language Into Regular Leadership Team Meetings

The retreat introduces the framework. The regular leadership team meetings are where the framework becomes part of how the team operates. When assigning a new project, pause and ask who in the room has the genius that matches what the project requires. When a project is stalled, ask which stage of Working Genius the team is stuck in. When someone is visibly frustrated or disengaged, ask privately after the meeting whether they are currently working in their area of frustration.

Keep the team genius map visible in every leadership meeting and refer to it when decisions are being made. The retreat is a single day. The meetings are where the framework becomes the team's operating system. For deeper guidance on embedding the framework, the article on practical steps after Working Genius with your team walks through how teams keep momentum past the 90-day mark.

30. Revisit the Team Map at Major Team Transitions

Teams change. People join, leave, or move into different roles. Each significant change to the team composition is an opportunity to revisit the team map and understand what the new profile means for how work should flow. A new member with a genius in Wonder joining a team that has been light in that type changes what is possible in strategy conversations. A departure that removes the team's primary Tenacity genius creates a gap that needs conscious management.

Revisiting the team map annually, or at every significant team change, keeps Working Genius as a living tool rather than a one-time event. Working Genius results can shift when a person's context changes significantly. A leader who completes the assessment while running at maximum capacity may have different results when they complete it a year later in a different role or with a different workload.

31. Run a 90-Day Retrospective to Assess What Changed and What Did Not

Ninety days after the retreat, gather the team for one final session to assess whether the retreat produced the outcomes it was designed to produce. The retrospective has three questions: what has changed in how this team works together since the retreat, what has stayed the same and where are the old patterns still showing up, and what did the retreat surface that the team is not yet using and what would it take to start using it? The retrospective closes the loop and turns the retreat from a one-time event into a milestone in an ongoing process. Planning a leadership retreat more broadly? The guide to planning a leadership retreat covers the full retreat planning process across different frameworks and team contexts.

What Are the Most Common Working Genius Retreat Mistakes?

The most common mistakes are skipping the pre-retreat diagnostic, designing the agenda around the framework instead of the team's actual problem, running the assessment on the day rather than days before, failing to schedule follow-through meetings before people leave the room, over-engineering the agenda with no breathing room, and measuring success by how good the day felt rather than by what changed in the team's behaviour over the next 90 days.

Approach that produces change	Approach that produces only a good day
Pre-retreat one-on-one diagnostics with each team member	Jumping straight to the agenda without interviewing the team
Single measurable outcome as the filter for every agenda decision	Multiple vague goals that try to fix everything in one day
Live case study using a real stalled project	Generic hypothetical exercises the team cannot connect to real work
Follow-through meetings scheduled before people leave the room	Action items emailed out after the retreat and never reviewed
Team genius map visible in every regular leadership meeting	Team genius map filed away and never referenced again
90-day retrospective that holds the team accountable	No formal review of what the retreat was supposed to achieve

Which Retreat Format Works Best for Working Genius?

The Half-Day Format (3 to 4 Hours)

A half-day session works well when the whole team has already completed the assessment and has some familiarity with the six types. It suits a team that wants to map their geniuses, surface one or two specific areas of friction, and identify actionable changes. The limitation is time: a half-day session can produce insights and one or two concrete decisions, but it cannot cover the depth of application that a full day allows. Half-day formats work particularly well as follow-up sessions for teams that have previously done a full Working Genius workshop.

The Full-Day Format (6 to 8 Hours)

A full day gives the retreat room to breathe. All three stages, individual reflection, team mapping and discussion, and application to real work, can be run at full depth, with proper breaks and time for informal conversation between sessions. A full-day format can also incorporate a second application block in the afternoon, allowing the team to work through multiple scenarios or to begin drafting practical changes to meeting rhythms, role descriptions, or project workflows. End with a structured commitment exercise where each participant names one change they will make to how they work within the team over the next month.

The Multi-Day Offsite Format

For teams undergoing significant change, for new leadership groups, or for executive teams carrying unresolved friction, a multi-day offsite gives Working Genius the space to do its deepest work. In this format, the Working Genius session typically occupies a dedicated half-day or full day within a broader offsite agenda that might include strategic planning, culture work, or leadership development. The shared language of the framework becomes a resource throughout the whole offsite, not just during the Working Genius session itself.

Implementation Timeline: From Planning to Post-Retreat Follow-Up

Four to Six Weeks Before the Retreat

Book and confirm the venue. Confirm the facilitator and agree on the session design. Send assessment invitations to all participants with a clear completion deadline at least five business days before the retreat. Define the one or two primary outcomes the retreat is designed to achieve and communicate those outcomes to participants alongside the invitation.

One to Two Weeks Before the Retreat

Follow up with any participants who have not completed the assessment. Build the team map from all available results. Prepare the facilitation materials, including the visual display of the team map and any application scenarios from recent team work. Send a brief pre-work prompt asking participants to review their individual reports and note one insight and one question to bring to the retreat.

On the Day

Arrive early enough to arrange the room, test all technology, and set up the team map display before anyone else arrives. Run the session in the three-stage sequence: individual reflection, team mapping and discussion, and application to real work. Assign documentation to someone who is not facilitating. Close with a structured commitment exercise and ensure every commitment is captured in writing before participants leave.

Within 48 Hours After the Retreat

Circulate the retreat summary to all participants while the day is still fresh. The summary should include the key insights from the team map discussion, all commitments made, the name of who owns each commitment, and the agreed date for the first progress check. A summary delayed by more than a week loses the momentum it is designed to sustain.

Three to Six Months After the Retreat

Schedule the follow-up session at this point, or earlier if the team has made significant progress and is ready to go deeper. At the follow-up, review the commitments made at the original retreat, surface any new friction that has emerged, revisit the team map if the team has changed, and identify the next set of changes the team will make to embed Working Genius more deeply into how they work.

FAQ

How long should a Working Genius retreat be?

A half-day session covers the basics of the assessment and team map but leaves little time for the deeper conversations that produce behaviour change. A full day allows for the pre-retreat diagnostic to be addressed properly, a live case study, and a structured follow-through design. Two days is appropriate when the team has significant trust issues or strategic decisions that need to be worked through alongside the Working Genius content.

Do all team members need to complete the Working Genius assessment before the retreat?

Yes, without exception. The retreat's most valuable sessions rely entirely on having complete data for the whole team. Completing the assessment on the day wastes time and produces less honest reflection than when people have had time to sit with their results beforehand. Build in a firm deadline five business days before the retreat and follow up directly with anyone who has not submitted.

Can you run a Working Genius retreat without an external facilitator?

You can, particularly if you are a Certified Working Genius Facilitator with experience facilitating your own team and there are no significant trust or conflict issues that require a neutral third party. The risk is that you cannot simultaneously hold the process and participate fully. If any session needs to surface tension involving you as the facilitator, bring in external support for that segment at minimum.

Can Working Genius be combined with other assessments at a retreat?

Yes, and it is often highly effective to do so. Working Genius complements tools like DISC and CliftonStrengths because it addresses a different dimension: not personality style or general strengths, but the specific types of work that energise and drain people. Teams that combine frameworks report richer conversations and more nuanced understanding of individual differences. The key is to give each framework adequate time rather than rushing through multiple assessments in a single short session.

How do we handle team members who disagree with their assessment results?

Invite them to treat their results as a working hypothesis for the day rather than a permanent label. Most participants who arrive sceptical find that the team map discussion shifts their perspective, because they see their genius types operating in others and recognise the pattern. If a participant genuinely believes their results are wrong, a brief private conversation during a break usually resolves the uncertainty. Working Genius can produce different results depending on the context the person was thinking about when they completed it.

What should a Working Genius retreat cost?

The cost depends primarily on whether you use an external facilitator, the venue choice, and whether any additional assessments or materials are needed beyond the assessment cost from workinggenius.com. The more useful question is whether the investment is worth the problem it solves. A team whose structural genius gaps are producing recurring dysfunction is losing that value every week the retreat does not happen.

How do you measure whether a Working Genius retreat was successful?

Measure against the single measurable outcome you set before the retreat. At the 30-day check-in, ask whether everyone on the leadership team has changed at least one specific behaviour based on the retreat. At the 90-day retrospective, ask whether the recurring dysfunction the retreat was designed to address is still showing up at the same frequency and intensity.

What is the biggest reason Working Genius retreat insights do not stick?

The absence of a follow-through structure. When commitments are not written down and reviewed, when the team genius map is not made visible in regular meetings, and when no formal 30-day check-in is scheduled, the insights from the retreat compete with day-to-day urgency and lose. The framework requires environmental reinforcement to become operational rather than theoretical. The guide on Working Genius in the workplace covers how to build that reinforcement into everyday team rhythms.

How is a Working Genius retreat different from a standard team-building day?

A standard team-building day is typically designed to improve relationships through shared experience. A Working Genius retreat is designed to diagnose why work stalls, why talented people burn out, and why meetings drain energy rather than produce decisions. The output is not stronger social bonds but a clearer shared understanding of who contributes what and how to structure work around collective genius rather than against it.

About the Author

Jonno White is a leadership consultant, keynote speaker and Certified Working Genius Facilitator, and the author of Step Up or Step Out. Through Consult Clarity he works with corporates, nonprofits and schools around the world. He has facilitated Working Genius retreats and executive offsites across multiple continents and brings a diagnostic-first approach that addresses the specific dysfunction a team is experiencing rather than running a generic session. Learn more at the about page or connect on LinkedIn.

Your next step is simple. Pick the one element from this guide that addresses the biggest gap in how your team currently plans and runs retreats. Start there. A retreat that executes one of these steps well will land harder than a retreat that attempts all 31 and executes none of them properly. If you are planning a Working Genius retreat for your leadership team and want help designing the session, reach out at jonno@consultclarity.org. Working Genius retreats work best when the day is built around your team's specific profile, not a generic agenda.