Working Genius Communication Styles That Actually Work

If you have ever sat through a meeting where talented people talked past each other for an hour and walked away with no decision, Working Genius communication styles hold the answer.

The problem is not that your team lacks talent. The problem is that Wonder processes information through questions, Invention through possibilities, Discernment through gut response, Galvanize through energy tests, Enablement through concrete support needs, and Tenacity through completion tracking. When you speak to a Discernment person using Wonder language, they hear noise. When you pitch an idea to Enablement using Galvanize energy, they hear risk.

Most leaders assume communication breaks down because of personality clashes or unclear expectations. The actual reason is simpler. Each Working Genius has a preferred communication channel. When you ignore that channel, your message does not land. When you match it, resistance drops and alignment happens faster.

Here is how each genius type communicates, what they need to hear from you, and how to adjust your approach before your next conversation.

THE IDEATION GENIUSES

Wonder and Invention live in the world of ideas, but they speak two different dialects. Wonder asks the questions that unlock new thinking. Invention builds the answers. If you treat them the same way in conversation, you lose both of them.

WONDER COMMUNICATION STYLE

Wonder does not make statements. Wonder asks questions. This is not a personality quirk. This is how Wonder processes the world. Where most people see a problem and start solving, Wonder sees a problem and starts wondering. Why does this exist? What are we missing? What if the question itself is wrong?

The communication pattern shows up in three specific ways. First, Wonder will reframe your question before answering it. You ask about execution and they ask whether the goal itself still makes sense. Second, Wonder introduces ideas as possibilities, not proposals. They float an option to see how the room reacts. Third, Wonder uses hypothetical language constantly. What if we tried this? Have we considered that? Could there be another angle?

What Wonder needs from you in conversation:

Time to think out loud without being asked for a final answer

Permission to question the premise of the discussion itself

Space to explore tangents that might unlock the real insight

Patience when they circle back to an earlier question you thought was settled

Wonder is not being difficult when they do this. They are doing the work only they can do.

What frustrates Wonder: Being told the question is already answered. Being pushed to move from wondering to deciding before they have explored the problem space. Being treated like their questions are stalling when they are actually preventing the team from solving the wrong problem.

How to communicate with Wonder effectively: Start conversations with open questions, not closed decisions. Frame updates as inquiries. Instead of saying here is what we are doing, try here is what we are seeing, what are we missing? Give Wonder explicit permission to question assumptions, and make space in your agenda for them to do it. If you cut Wonder off too early, you lose the insight. If you let them run too long without focus, the team loses patience. The balance is naming the question you need them to explore and giving them a container to do it in.

INVENTION COMMUNICATION STYLE

Invention does not wonder. Invention builds. Where Wonder opens the question, Invention closes it with a possibility. The communication style is faster, more declarative, and more solutions-focused. Invention hears a problem and within seconds is sketching an answer.

The pattern looks like this. Invention speaks in concepts and prototypes. They do not describe the problem at length. They describe what could be built to solve it. Invention uses phrases like what if we, we could try, here is an idea. The language is generative, not evaluative. Invention does not tear down your idea. They offer three alternatives in the time it took you to explain yours.

Invention shows up in meetings as the person who:

Interrupts mid-problem with a potential solution

Draws diagrams, frameworks, or rough sketches on the whiteboard

Suggests combinations nobody else has considered

Builds on the last idea offered rather than critiquing it

Invention moves fast because they are not attached to any single idea. They generate options. Someone else picks.

What Invention needs from you: Recognition that their ideas are starting points, not final proposals. Freedom to suggest five possibilities without being held accountable for all five. A clear signal about when you need more ideas and when you need them to stop generating and let the team decide.

What frustrates Invention: Being asked to defend an idea they offered as a rough sketch. Being told to slow down when the team has not generated any alternatives yet. Being treated like idea volume is the same as lack of focus.

How to communicate with Invention effectively: Separate ideation from evaluation. When you need options, tell Invention to run. When you need a decision, tell them the ideation window is closed and now the team is choosing. Invention thrives when they know their role is to create possibilities, not to pick the right one. If you ask Invention to generate and evaluate at the same time, they stall. Give them a clear lane and they will fill it.

THE DISCERNMENT GENIUS

Discernment does not generate ideas. Discernment evaluates them. This is the genius that feels whether something is right or wrong, often before they can explain why. The communication style reflects that. Discernment speaks in gut responses, instinctive reactions, and pattern recognition that sounds like opinion but is actually insight.

DISCERNMENT COMMUNICATION STYLE

Discernment does not build a case before offering a verdict. Discernment offers the verdict first and builds the case when pressed. You pitch an idea and Discernment says I do not think this is it. You ask why and they pause. The reasoning comes slower than the response because the response comes from instinct, not analysis.

This creates tension in teams that value evidence-based decision making. Discernment sounds like they are being negative or resistant when they are actually doing the one thing only they can do. They are filtering. Without Discernment, teams execute ideas that sound good in the room but fail in reality. With Discernment, bad ideas get caught early.

The communication pattern shows up as:

Early resistance to ideas others are excited about

Statements that start with I do not think or something feels off

Questions that probe weak points in the plan

Silence in brainstorming sessions followed by clarity in evaluation sessions

Discernment does not perform well under pressure to be positive. They perform well under permission to name what is wrong.

What Discernment needs from you: Explicit permission to say no. Time to articulate why their gut is saying what it is saying. Protection from being labelled as negative when they are filtering. A clear understanding that their role is to evaluate, not to generate, and that evaluation without options is just criticism. For more on how pairings shape these dynamics, see the guide to Working Genius pairings.

What frustrates Discernment: Being asked to brainstorm before they have something to evaluate. Being told their concerns are not valid because they cannot immediately explain them. Being pressured to support an idea when their instinct is telling them it will not work. Being grouped with Wonder when their thinking processes are opposite. Wonder opens questions. Discernment closes options.

How to communicate with Discernment effectively: Give them something to react to. Discernment cannot evaluate a blank page. They need a proposal, a prototype, a plan. Once they have it, ask them directly what feels wrong. Do not ask them if they like it. Ask them what will break. When Discernment offers a gut response, give them space to reverse-engineer the reasoning. The instinct is usually right. The explanation takes longer. If you dismiss Discernment because they cannot defend their position in the first thirty seconds, you lose the filter that saves your team from costly mistakes.

THE ACTIVATION GENIUSES

Galvanize and Enablement are both activation geniuses, but they activate in opposite directions. Galvanize rallies people to the idea. Enablement removes the obstacles so the idea can happen. The communication styles reflect that difference. Galvanize speaks to energy and momentum. Enablement speaks to practicality and support.

GALVANIZE COMMUNICATION STYLE

Galvanize is the genius that makes people care. They do not analyse the idea. They sell it. The communication style is energetic, urgent, and momentum-focused. Galvanize does not say this could work. Galvanize says we need to do this now.

The pattern is consistent. Galvanize speaks in declarative, action-oriented language. They use we, not I. They frame ideas as movements, not tasks. Where Invention offers possibilities, Galvanize picks one and makes it feel inevitable. Where Discernment filters, Galvanize amplifies.

Galvanize shows up in conversation as the person who:

Interrupts planning discussions with let us just start

Reframes hesitation as momentum loss

Names who else needs to be in the room or on the team

Uses urgency language even when the timeline is flexible

This is not hype. This is Galvanize doing the work only they can do. They generate the belief that moves an idea from concept to reality.

What Galvanize needs from you: A decision. Galvanize cannot rally people to seven possibilities. They need you to pick one so they can make others care about it. Once the decision is made, give Galvanize permission to run. They will find the stakeholders, build the coalition, and create the energy the idea needs to survive first contact with reality. For practical application of this inside Working Genius for executive teams, the Galvanize and Enablement interplay is where most teams find their biggest communication gains.

What frustrates Galvanize: Endless ideation with no decision. Being told to wait when momentum is available now. Being asked to tone down their energy when energy is their contribution. Being treated like urgency is impatience when urgency is the tool that prevents ideas from dying in committee.

How to communicate with Galvanize effectively: Make a decision and tell them to move. Galvanize does not need perfect information. They need enough clarity to start building momentum. When you communicate with Galvanize, frame updates as progress, not problems. Tell them what is moving, who is on board, what happens next. If you bring Galvanize a problem without a direction, they will create one. If you give them a direction, they will make it happen faster than you expected.

ENABLEMENT COMMUNICATION STYLE

Enablement does not rally the room. Enablement removes the barriers so the room can do the work. The communication style is practical, specific, and support-oriented. Enablement does not speak in vision language. They speak in how language. How will this actually work? Who needs what? What is missing?

Where Galvanize asks who is in, Enablement asks what do they need. Where Galvanize builds energy, Enablement builds infrastructure. The genius is equally critical, but the communication style feels slower, more cautious, more detailed.

Enablement communicates by:

Asking logistical questions that sound like resistance but are actually preparation

Identifying resource gaps before the team hits them

Offering to take on support tasks nobody else has noticed yet

Slowing down momentum conversations to address practical concerns

This makes Enablement the genius most likely to be misread. Galvanize hears their questions as doubt. Invention hears their caution as bureaucracy. What Enablement is actually doing is building the conditions in which the idea can succeed.

What Enablement needs from you: Clarity about what the team is trying to do and what success looks like. Permission to ask the practical questions without being told they are overthinking. Time to build the support structures before the team moves to execution. Recognition that their contribution is not visible in the same way Galvanize contribution is, but it is just as necessary.

What frustrates Enablement: Being told to just figure it out when the resources are not in place. Being rushed into execution before the infrastructure exists. Being labelled as a blocker when they are identifying real obstacles the team will hit later. Being paired with Galvanize and expected to match their energy when their role is to provide the practical foundation Galvanize energy requires.

How to communicate with Enablement effectively: Slow down long enough to answer their questions. Enablement is not stalling. They are building. When Enablement asks what do we need or who is responsible for this, they are doing the thinking that prevents execution failure. Give them specifics. Tell them what the team is doing, what resources are available, where the gaps are. Enablement will fill those gaps if you give them the clarity to do it. If you skip this step and move straight to execution, Enablement will spend the entire project in reactive mode, fixing problems that could have been prevented. This dynamic is one of the core reasons why reviewing the practical steps after Working Genius matters so much for sustained team performance.

TENACITY COMMUNICATION STYLE

Tenacity does not start projects. Tenacity finishes them. The communication style reflects that. Tenacity speaks in timelines, tasks, and completion tracking. Where Wonder opens questions and Galvanize builds momentum, Tenacity asks what is left and when will it be done. For teams looking to build on this understanding, see the guide to Working Genius in the workplace for a broader look at how these dynamics play out day to day.

This is the genius that moves an idea across the finish line. Without Tenacity, projects stall at ninety percent. With Tenacity, the last ten percent gets the same attention as the first ten. The communication style is direct, task-focused, and oriented around closure.

Tenacity shows up in conversation as:

The person who brings the team back to the original goal when scope creep starts

The person who tracks what was decided and who committed to what

The person who follows up when others forget

The person who pushes for completion when the team wants to move to the next idea

Tenacity does not generate new ideas in the final stretch. They protect the current idea from abandonment.

What Tenacity needs from you: A clear finish line. Tenacity cannot complete what has not been defined. Tell them what done looks like and they will get the team there. Once the goal is clear, give Tenacity authority to hold people accountable. They will track progress, identify delays, and push for completion in ways that feel relentless because they are.

What frustrates Tenacity: Moving to a new idea before the current one is finished. Changing the goal mid-project without acknowledging the cost. Being told to let it go when the finish line is visible. Being treated like their focus on completion is rigidity when it is actually the discipline that prevents half-finished work from piling up across the organisation.

How to communicate with Tenacity effectively: Be specific about what needs to be completed and by when. Tenacity does not need inspiration. They need clarity. When you update Tenacity, tell them what is done, what is in progress, what is blocked. Frame conversations around next steps and timelines. If you bring Tenacity a problem, bring a proposal for how to close it. Tenacity will execute on clarity. They will resist ambiguity. If your communication is vague, Tenacity will ask the questions that force specificity, and the team will benefit from it.

The teams that work best together are not the ones where everyone communicates the same way. They are the ones where each genius type knows what the others need to hear and adjusts accordingly. Wonder needs questions. Invention needs possibilities. Discernment needs something to evaluate. Galvanize needs a decision. Enablement needs clarity about resources. Tenacity needs a finish line.

Your next step is simple. Audit the last meeting where communication broke down. Map each person to their Working Genius. Ask whether the message you sent matched the communication style they needed to receive it in. If you have been speaking Galvanize language to an Enablement person, you now know why your message did not land.

If you need help mapping this across your team or building a communication strategy that actually works with how your people think, reach out at jonno@consultclarity.org. Your Working Genius pairing is not the whole story. But it is a powerful place to begin.