top of page

25 Proven Tips for Using Working Genius for Staff Professional Development

  • Writer: Jonno White
    Jonno White
  • Jun 28
  • 16 min read

Last updated: June 2026


Working Genius for staff professional development is a facilitated experience, built on Patrick Lencioni's Table Group model, that replaces generic one-size-fits-all PD with a session grounded in how each person is actually wired to contribute. As of June 2026, global employee engagement has fallen to 20%, its lowest point since 2020, costing organisations an estimated $10 trillion in lost productivity (Gallup, State of the Global Workplace 2026). Most professional development does nothing to address that number. Working Genius does, because it does not ask people to learn something new and apply it uniformly. It asks them to understand what already energises them and to restructure work around that.


I am a Certified Working Genius Facilitator, certified through Patrick Lencioni's Table Group, and I run these sessions for schools, corporates, and nonprofits around the world. The 25 tips below come from real team rooms and from studying what makes a Working Genius staff PD day land versus what makes it drift into a workshop people forget by Friday.


Workshop table with seated team members examining printed Working Genius reports, one person pointing at team map poster.

Who This Is For and What You Will Get


This post is for principals, HR leaders, professional learning coordinators, and team leaders who want to run a Working Genius staff PD day, or who are evaluating whether to bring in a facilitator to run it for them. By the end, you will know how to plan the session, structure the day, facilitate the debrief, handle large groups, and sustain the framework after everyone goes back to their desks. Every tip is actionable. None of it is gated behind a pitch.


1. Start With the Problem You Are Actually Trying to Solve


Effective staff professional development begins by naming the real problem, not the symptomatic one. Most organisations book a PD day because staff feel disconnected, teams are misaligned, or a strategic initiative keeps stalling. Working Genius addresses all three. But the session lands differently when you can say at the opening, "We are here today because projects keep getting stuck at the approval stage, and we think genius mismatch is why." A focused problem gives participants a reason to pay attention beyond the assessment itself.


2. Understand the Model Before You Plan the Day


Working Genius is a model that identifies six types of work every project requires: Wonder (pondering possibility), Invention (creating ideas), Discernment (evaluating ideas), Galvanising (rallying people to act), Enablement (supporting the work), and Tenacity (driving to completion). Each person has two natural geniuses that energise them, two competencies they can do without much drain, and two frustrations that deplete them when sustained. The model is 80 percent about productivity and 20 percent about personality, which is what separates it from tools like Myers Briggs or StrengthsFinder. Understanding this distinction lets you frame the PD session accurately from the outset.


The Three Stages of Work


Work flows through three stages: ideation (Wonder and Invention), activation (Discernment and Galvanising), and implementation (Enablement and Tenacity). When a team is missing a genius at one of these stages, projects do not simply slow down. They break at a predictable point. The team map built during a Working Genius session makes that break visible for the first time.


3. Separate the Assessment From the Session


The Working Genius assessment takes 10 to 15 minutes online and costs around $25 per person through workinggenius.com. It should be completed before the PD day, not during it. When participants arrive already knowing their two geniuses, two competencies, and two frustrations, the session time can be spent on application rather than data collection. Sending assessments two to three weeks before the session also gives people time to sit with their results, which means the debrief conversation is richer from the first minute.


4. Pre-Debrief Every Participant Before the Group Session


For groups of up to about 20 people, individual pre-debrief conversations between the facilitator and each participant (15 to 20 minutes each) change the quality of the group session significantly. Pre-debriefs surface results that do not quite resonate, and they give the facilitator a read on the team dynamics before anyone enters the room. For whole-staff groups of 40 or more, individual pre-debriefs are not practical, but the team leader or the principal should always have one.


5. Brief the Leader Separately Before the Day


The leader's role in a Working Genius PD day is distinct from the participant's role. They need to know what the team map shows before anyone else does, because their reaction to it in the room sets the tone for how honestly everyone else engages. A leader who says, "I had no idea we had no Galvanising on this team, and looking at what stalled last year, that makes complete sense" gives permission for the team to have that same candid conversation. Briefing the leader 24 to 48 hours before the session is not optional.


6. Plan the Day Around Four Blocks, Not Slides


A Working Genius staff PD day works best when it is structured around four blocks rather than a slide presentation. Block one covers understanding the model and individual results. Block two covers the team map and what it reveals about how work currently flows and where it breaks. Block three covers application: redesigning meetings, reassigning tasks, and structuring projects around the team's actual genius profile. Block four covers commitments, the specific changes each person or team will make in the next 30 to 90 days. This structure gives the day momentum and leaves participants with something actionable, not just insight.


7. Build Time for Silence Into the Debrief


Most facilitators rush the debrief because silence feels awkward. It is not. When participants are looking at their results for the first time in a group setting, the three to five seconds of quiet after you ask "Does this resonate?" is where the real processing happens. Rushing to fill the silence with explanation cuts off the moment when people are actually making sense of the data. Build silence deliberately into the debrief structure and resist the urge to interpret results before participants have had a chance to claim them.


8. Use the Team Map to Drive the Conversation, Not to Explain It


The team map is the most powerful visual in a Working Genius session. It shows every person's two geniuses, two competencies, and two frustrations in one place, making visible the geniuses the team has in abundance, the ones spread thin, and the ones nobody has. The facilitator's job is not to interpret the map for the team. It is to ask the questions that help the team interpret it for themselves. "Looking at this map, which projects make more sense now?" and "Where do you think we are most exposed?" are far more useful than a lecture on what the map means.


9. Address Frustration Zones Without Pathologising Them


The frustration zones are where most PD facilitators get this wrong. When someone discovers that Tenacity is in their frustration zone, the instinct is to treat this as a weakness to fix. The Working Genius model is explicit that this is not the goal. Frustrations are not character flaws. They are types of work that drain energy when sustained. The session should name this clearly and then move quickly to the question of how to structure work so people spend less time in their frustration zones. The goal is redistribution, not remediation.


10. Scale the Format to the Group Size


Working Genius sessions for small teams (six to 15 people) allow for deep individual debrief, extended team map discussion, and granular application to specific projects. Whole-staff PD days for 40 to 200 people need a different format. Large groups work well with a plenary introduction to the model and the team map, followed by breakout groups of six to ten where each breakout builds its own mini team map and applies it to a real shared challenge. The plenary closes with each group reporting one insight and one commitment. The large-group version delivers different but equally real outcomes.


A Note on Keynote Format


Working Genius also works as a conference keynote or a plenary session where participants each have their own assessment results in hand. This is different from a team workshop in that the team map cannot be built (results are personal), but the individual insight is still powerful and the model is introduced in a way that gives participants a clear next step.


11. Handle the "I Got This Wrong" Reaction With Care


Some people finish the assessment and feel the results do not fit. Before you explain the result, ask the participant to describe a recent project where they felt most energised and most drained. In the vast majority of cases, the results do surface accurately once you connect them to real work rather than abstract self-description. If results still do not resonate after that conversation, the assessment can be retaken. Do not insist that the result is correct and the participant is wrong.


12. Map the Team's Geniuses to Current Projects Before the Day Ends


The session should not end with insight alone. Before participants leave the room, spend at least 30 minutes mapping the team's genius profile to one or two live projects. Take a project that is currently stalling or underperforming and ask: which stage of work is this stuck at, and which genius is missing at that stage? This exercise moves Working Genius from a personality-adjacent tool to a genuine productivity diagnostic. Teams leave with a specific hypothesis about why the project stalled and who should be involved differently.


13. Redesign at Least One Meeting Structure on the Day


One of the highest-leverage applications of Working Genius is meeting design. Most meetings mix all six geniuses and all three stages of work in the same hour, which is why they drain energy rather than generate it. During the PD day, take one recurring meeting the team dreads and restructure it around the stages of work. If the meeting is for ideation, invite Wonder and Invention and release Enablement and Tenacity from the room. If it is an implementation check-in, put Tenacity in the lead. Teams that leave the session with at least one meeting redesigned are far more likely to keep using the framework.


14. Avoid Genius Stereotyping in the Room


The Working Genius model is not a label system. The session should never arrive at "you are the Tenacity person" or "we need more Wonder on this project." People have two geniuses, two competencies, and two frustrations, which means there is always nuance. Over-simplifying into genius labels creates a new version of the silos and stereotyping the session is meant to dissolve. Facilitators need to hold this line actively, especially in team map discussions where it is tempting to assign people to a single type for ease of conversation.


15. Connect Working Genius to Professional Development Planning Itself


One of the most underused applications of Working Genius in a staff PD context is redesigning how the organisation approaches professional development. Generic PD sends everyone to the same workshops regardless of their wiring. A school or organisation that has mapped its staff's geniuses can begin offering professional learning that aligns with what each person is built to do. People whose geniuses are Wonder and Invention are energised by strategic thinking workshops and design thinking labs. People whose geniuses are Enablement and Tenacity are energised by project management training and operational excellence courses. When PD aligns with a person's genius, they engage deeply and apply it immediately.


16. Plan for the 90 Days After the Session


The most common failure mode in Working Genius PD days is that the session itself is excellent and then the framework disappears within six weeks. The 90 days after the session matter as much as the day itself. At minimum, the team should reference the team map in the next three to five team meetings, use genius language when assigning tasks on at least two projects, and revisit the map when a new team member joins or a major project kicks off. Build these specific practices into the commitments block at the end of the session so people leave with a schedule, not just an intention.


17. Give People the Language to Use After They Leave


The Working Genius framework only survives in an organisation if people have shared language to keep using it. At the close of the session, give every participant a one-page genius reference card that shows their geniuses, competencies, and frustrations along with the six genius types and the three stages of work. The reference card is what they pull out when assigning tasks at the next team meeting. Without it, the session lives in memory, and memory is unreliable.


18. Repeat the Team Map Conversation Quarterly


A team map is a snapshot, not a permanent record. Over time, new projects, new roles, and new team members shift how geniuses are distributed across the work. Run a short team map review quarterly (15 to 20 minutes in an existing meeting is enough) to ask whether work is still aligned with genius zones and whether any new frustration points have emerged. Organisations that build this cadence report the clearest long-term outcomes from Working Genius.


19. Use Working Genius in Hiring and Onboarding


Professional development does not start at a PD day. It starts at the point of hire. When a team knows its genius map, it can identify which geniuses are underrepresented and hire toward those gaps deliberately. In onboarding, having a new team member take the assessment in their first week and sharing the result with the team updates the map and signals that genius alignment is part of how this organisation operates. This is particularly powerful in schools where teacher turnover and role misalignment are persistent problems.


20. Do Not Run It the Week Before School Holidays or Exam Blocks


The timing of a Working Genius PD day matters more than most coordinators acknowledge. Running a Working Genius session the week before major exams, mid-semester reports, or the end of term means participants are in implementation mode at a cognitive level. Their capacity for ideation and activation, the stages that open up the insight conversations, is compressed. The best time for a Working Genius PD day is at the start of a term, a new project cycle, or a new school year, when participants have the cognitive space to think beyond their immediate execution tasks.


21. Combine Working Genius With a Real Team Challenge, Not a Hypothetical


Facilitation exercises that use hypothetical scenarios to practise applying Working Genius are useful for training purposes but less useful for a staff PD day. The team's real, live challenges are far more engaging and far more likely to produce lasting application. Use a current strategic challenge, a programme that is underperforming, a meeting that everyone dreads, or a hiring decision that is looming. When the Working Genius framework is applied to something that is already on the table, the outcome is a concrete recommendation or a concrete redesign, not just a workshop output.


22. Facilitate the Team Map With Questions, Not Answers


The questions that unlock the most value from a Working Genius team map are not complex. "Where on this map do you see our biggest strength?" "Where are we most exposed?" "Which of these results surprised you?" "What does this explain about the last time we failed to implement a plan?" These questions hand the interpretive work back to the team. The facilitator's job is to create the conditions for the team to arrive at its own insight, then to name what it just discovered so the insight has a label it can carry forward.


23. Track What Changes in the 30 Days After the Session


The best evidence for the value of a Working Genius staff PD day is not the participant satisfaction score at the end of the day. It is what is different 30 days later. Ask the team leader to note, in the first month after the session, three things: at least one task or meeting that was reassigned based on genius zones, at least one conversation that used the Working Genius language to resolve a frustration rather than escalate it, and at least one project that moved faster because the right genius was leading it. These three data points are more valuable than any evaluation form and more compelling for any future leadership buy-in conversation.


24. Know When to Bring In a Certified Facilitator


Running a Working Genius session for your own team is possible if you are already a certified facilitator. Running it for a whole-staff group of 40 or more, for an executive team with a lot at stake, or for a team that is in genuine conflict is a different matter. An external certified facilitator brings something that an internal facilitator cannot: no stake in the outcome and no relationship history with the dynamics in the room. For high-stakes groups, the cost of the external facilitator is the lowest-risk line item in the session budget. To find a certified facilitator who fits your context, the directory of certified Working Genius facilitators is a useful starting point.


25. End Every Session With a Single Shared Commitment


The final act of a Working Genius staff PD day should be a single shared commitment, not a list of follow-up action items. The commitment should name one specific change the team or organisation will make in the next 30 days that it would not have made without this session. It might be a meeting structure change, a project assignment shift, or a new hiring question. One commitment, owned publicly, shared with the group, is worth more than ten vague intentions. It is also the thing that the leader references at the next team meeting to signal that the session was real, not performative.


Why Working Genius Works Where Generic Professional Development Fails


Generic professional development operates on the assumption that the problem is a knowledge or skills gap. Working Genius operates on the assumption that the problem is a mismatch between the type of work people are doing and the type of work they are built for. According to Gallup's State of the Global Workplace 2026, manager engagement has dropped nine points since 2022, reaching a global average of 22% in 2025. The same report finds that in best-practice organisations, 79% of managers are engaged. The difference is not a better training programme. It is alignment.


Patrick Lencioni, creator of Working Genius, has put it plainly: people need to "tap into your inner genius" to find fulfilment in their work. The model he built is the fastest practical tool I have found for helping a staff team do exactly that in a single day.


The comparison below maps three approaches to the same problem: low staff engagement and misaligned roles.


Approach

What it addresses

Time to visible change

Sustained impact

Generic PD (same content for everyone)

Knowledge gaps

Weeks to months

Low (content fades)

Working Genius PD day

Role alignment, shared language, genius map

Days to weeks

High when followed up

No structured PD

Nothing

None

None


Note: Engagement research alignment column from Gallup 2026 State of the Global Workplace. 70% of team engagement variance driven by manager behaviour and role fit, not training content.


Every organisation that uses Working Genius consistently over 90 or more days reports three outcomes: cleaner task assignment, fewer energy-draining meetings, and faster project completion. The single PD day is the start, not the end.


Common Mistakes in Working Genius Professional Development


Running a Working Genius staff PD day without pre-completing the assessments is the most common logistical mistake. It wastes the first hour on data collection that should have happened before the room assembled.


Running the session without briefing the leader separately is the most common facilitation mistake. A leader who is surprised by the team map in front of their team creates a defensive dynamic that is hard to recover from in a single day.


Using the results to label people is the most common cultural mistake. The genius types are not identities. They are descriptions of what energises someone when doing certain kinds of work. Framing them as fixed identities locks the team into exactly the kind of rigid thinking the model is designed to dissolve.


Failing to follow up is the most common organisational mistake. A team that does a brilliant Working Genius PD day and then never references it again has spent a day on self-awareness with no return. The value is in the changed behaviour, not the insight.


FAQ


What is Working Genius for staff professional development?


Working Genius for staff professional development is a facilitated team session that uses Patrick Lencioni's six-genius model to identify each staff member's natural areas of energy and frustration, map the team's collective genius profile, and redesign how work is structured so people spend more time in their areas of strength. The assessment takes 10 to 15 minutes per person and the facilitated session typically runs two to four hours for small teams and a full day for larger groups.


Can Working Genius replace generic professional development?


Working Genius does not replace domain-specific training (such as curriculum PD for teachers or technical upskilling for engineers). It replaces generic whole-staff sessions designed to improve culture, communication, or team effectiveness. For those goals, it outperforms generic PD because it addresses role alignment rather than knowledge gaps. The research on why people disengage at work consistently points to misalignment, not ignorance.


Is Working Genius good for school staff professional development?


Working Genius works well for school staff professional development days because it is practical, non-threatening, and produces a visible team map that school leadership can use to make real decisions about role design, meeting structures, and professional learning pathways. The related post on Working Genius in schools covers school-specific applications in depth.


How does Working Genius compare to Myers Briggs or StrengthsFinder for staff PD?


Myers Briggs focuses on personality type and communication style. StrengthsFinder maps natural talent themes. Working Genius focuses specifically on what type of work energises or drains a person and maps that directly to the six types of work that every project requires. For staff professional development focused on improving team productivity and role alignment, Working Genius is more directly actionable because it translates results into task design, meeting structure, and project assignment without requiring extensive interpretation.


Can a Working Genius staff session run virtually?


Yes. Working Genius sessions run effectively virtually, using the assessment link sent in advance, a virtual team map built in a shared document or whiteboard, and breakout rooms for small-group debrief. The loss of in-room reading (body language, spontaneous sidebar conversations) is real but manageable. For whole-staff groups that are geographically distributed, virtual is often the only practical format and it delivers the core outcomes.


How do I find a certified Working Genius facilitator for a staff PD day?


The official Table Group directory at workinggenius.com lists certified facilitators globally. The compiled directory of certified Working Genius facilitators covers a range of facilitators verified for different regions and contexts, with honest descriptions of what each is best for. When evaluating a facilitator, ask specifically about their experience with groups of your size and sector, and ask for a reference from a similar engagement.


What should we do in the 90 days after a Working Genius staff PD day?


Reference the team map in the first three to five team meetings after the session. Assign at least two tasks or projects explicitly based on genius zones rather than availability. Run a 15-minute team map check-in at the end of the first month to ask what is working and what frustrations have surfaced. Update the map when any team member joins or leaves. These four actions are the difference between a Working Genius PD day that sticks and one that becomes a fond memory with no lasting change.


If you would rather have a Working Genius staff professional development session run for your team than run it yourself, that is exactly what I do. If your school, organisation, or team is planning a PD day and wants a Working Genius session that gets people engaged, produces a real team map, and gives your team something to work with long after the day ends, I would be glad to help. You can reach me at jonno@consultclarity.org.


Next Read


If you found this useful, the related post on how to run a Working Genius workshop covers the step-by-step facilitation process in detail. If you are looking for a certified Working Genius facilitator rather than running it yourself, the directory of 

certified Working Genius facilitators is a good starting point. For school-specific applications, the post on 

Working Genius in schools covers the phased rollout from leadership team to whole staff.


Sources


Gallup. (2026). State of the Global Workplace: 2026 Report. gallup.com/workplace/349484

Global Leadership Network. Patrick Lencioni Quotes. globalleadership.org

The Table Group. The 6 Types of Working Genius. tablegroup.com/product/the-working-genius-book

The Table Group. How to Introduce Working Genius to Your Team. tablegroup.com/how-to-introduce-working-genius-to-your-team

Working Genius. Official Assessment and Model. workinggenius.com

Dale Carnegie. Working Genius Assessment Certification. dalecarnegie.com/en/courses/6578

 
 
bottom of page