Leading with Discernment and Enablement: 25 Insights

Most leaders get stuck choosing between being the person who spots problems or the person who empowers others.

You don't have that problem. Your Working Genius pairing of Discernment and Enablement means you see what's truly worth pursuing AND you help people execute on it. You evaluate with precision, then support with generosity.

This combination creates what Patrick Lencioni calls the Insightful Collaborator. You bring clarity to chaos, then remove obstacles so others can move forward. You're the leader who says "here's what matters most" and then immediately asks "how can I help you make it happen?"

The challenge is that these two geniuses can pull you in opposite directions if you don't understand how to integrate them intentionally.

UNDERSTANDING YOUR DUAL GENIUS FOUNDATION

Before diving into application, you need to understand what makes this pairing both powerful and potentially conflicting. Discernment and Enablement occupy different stages of the Working Genius model, and their natural rhythms don't always sync up without intentional leadership.

1. Why Discernment and Enablement Create Natural Tension

Discernment lives in evaluation mode while Enablement lives in support mode, and these two states require fundamentally different mental postures.

The timing mismatch is real: Your Discernment wants to pause and assess whether something should move forward. Your Enablement wants to jump in and help it move forward right now. One pumps the brakes, the other hits the gas. Most Insightful Collaborators feel this internal tug-of-war multiple times per day.

Your Discernment genius activates when you need to sense whether an idea, plan, or direction aligns with what's truly needed. It's your internal radar for fit, timing, and quality. You intuitively know when something is off, when a project lacks the right resources, or when a team is pursuing the wrong priority. This genius makes you valuable in decision-making moments because you see what others miss.

Critical insight: Discernment without application becomes criticism. If you only evaluate without moving toward support, your team experiences you as a gatekeeper who blocks progress rather than a leader who guides it.

Your Enablement genius activates when you see someone struggling with logistics, resources, or momentum. You naturally move toward people who need assistance and you derive energy from removing their obstacles. You're the person who says "let me handle that so you can focus on this" or "here's the resource you're missing." This genius makes you a force multiplier because you help others perform at their peak.

The integration point most leaders miss is this: Discernment identifies what deserves Enablement. When you evaluate first, you know where to direct your supporting energy. When you enable without discerning, you waste your finite capacity helping people pursue things that shouldn't be pursued in the first place.

Use Discernment to filter what gets your Enablement energy

Reserve your support capacity for initiatives that pass your evaluation

Communicate your assessment before offering your help

Learn to say "I don't think this should move forward, so I can't enable it"

This is how you turn potential tension into strategic advantage. You evaluate ruthlessly, then support generously within the boundaries your evaluation creates.

2. The Competitive Advantage of Seeing and Supporting

Teams led by Insightful Collaborators move faster with fewer wasted efforts because evaluation and acceleration happen from the same source.

Most organisations separate these functions. Strategic leaders evaluate and decide. Operational leaders support and enable. This creates lag time, miscommunication, and misalignment. The evaluator doesn't understand execution constraints. The enabler doesn't understand strategic context.

You collapse that gap entirely: When one person holds both lenses, decisions account for execution reality and support aligns with strategic priority. You never greenlight something you can't realistically enable. You never enable something that hasn't passed your discernment filter.

Speed advantage: Your team doesn't wait for evaluation results to trickle down from leadership, then wait again for support systems to activate. You deliver both simultaneously, cutting decision-to-action time in half.

The trust factor multiplies this advantage. When your team knows you evaluate thoughtfully AND support generously, they bring you their biggest challenges. They're not afraid you'll just shoot down their ideas, and they're not afraid you'll blindly support bad ones. They know you'll help them figure out what's worth doing and then help them do it.

Here's what separates good Insightful Collaborators from great ones:

Good: They evaluate when asked and enable when needed.

Great: They proactively assess what their team is pursuing and proactively offer support before being asked, creating a leadership rhythm that feels like wind in the sails rather than a series of stop-and-go transactions.

Your competitive edge isn't just that you have both geniuses. It's that you learn to deploy them as an integrated system rather than two separate skills.

3. How Your Pairing Shapes Team Culture

The way you combine Discernment and Enablement directly creates the culture your team experiences every day, whether you intend it or not.

When you lead with Discernment first, your team feels guided and protected from wasted effort. When you lead with Enablement first, your team feels supported and empowered to experiment. Most Insightful Collaborators unconsciously default to one pattern based on personality, past experience, or current stress levels.

Discernment-first culture: High standards, clear priorities, protected focus. Risk of feeling restrictive if you don't enable what passes your filter.

Enablement-first culture: High energy, strong collaboration, empowered ownership. Risk of scattered efforts if you don't discern what deserves support.

The healthiest teams experience both in rhythm. You create clarity about what matters, then you create momentum toward those priorities. Your people know what's important AND they know you'll help them succeed at it.

Watch for these cultural warning signs:

Warning Sign	What It Means	The Fix
People stop bringing you new ideas	Your Discernment feels like a wall	Enable one "risky" idea fully
Team pursues too many priorities	You enable without discerning	Evaluate and cut bottom 40%
Projects stall after approval	You discern but don't enable	Actively resource what you approve
People ask you to decide everything	You own both gates exclusively	Teach your framework, delegate tiers

Your culture will always reflect your genius pairing, so you might as well architect it intentionally. Decide what percentage of your leadership energy goes to evaluation versus support, then hold that ratio consistently for 90 days and measure what shifts.

STRATEGIC DISCERNMENT APPLICATION

Your Discernment genius is most valuable when you apply it to high-stakes decisions, not every micro-choice your team makes. This section shows you where to aim your evaluation capacity for maximum impact.

4. Using Discernment to Set Strategic Boundaries

The highest use of your Discernment genius is defining what your team will NOT pursue so everyone can focus energy on what truly matters.

Most leaders try to evaluate everything equally, which dilutes discernment into generic gatekeeping. Your job isn't to judge every idea. Your job is to establish clear strategic boundaries that help your team self-evaluate most decisions without needing you.

Strategic boundaries look like this: "We don't launch features that require more than two weeks of dev time unless they directly impact our Q2 revenue goal" or "We don't take client projects that fall outside our three core service offerings." These aren't arbitrary rules. They're applications of your Discernment that your team can use independently.

When you set boundaries using Discernment, you free up your Enablement energy. Instead of constantly evaluating whether individual initiatives deserve support, you enable everything inside the boundaries and redirect everything outside them.

The boundary-setting process that works:

Identify the 3-5 strategic priorities that matter most for the next 90 days

Use your Discernment to evaluate what types of work support those priorities

Articulate clear boundaries that separate aligned work from distraction

Communicate the boundaries with reasoning so your team understands the "why"

Enable everything inside boundaries aggressively, redirect everything outside them firmly

Your team will test the boundaries. That's healthy. When someone brings you an opportunity outside your stated focus, your response becomes simple: "This doesn't fit our current boundaries. Here's why those boundaries exist. If you believe we should change the boundaries, let's have that conversation separately, but I can't enable work outside them right now."

This approach does three things simultaneously: It protects your team's focus, it demonstrates that your Discernment serves strategy rather than personal preference, and it preserves your Enablement capacity for work that actually moves your mission forward.

Most leaders struggle with saying no because they lack a framework. Your Discernment IS the framework. Use it to draw lines, then hold them.

5. Discerning Between Good Ideas and Right-Now Ideas

Timing is the dimension of Discernment most leaders ignore, and it's where Insightful Collaborators create disproportionate value.

An idea can be genuinely good and simultaneously wrong for this moment. Your Discernment genius should evaluate fit across three dimensions, not just one: Is this a good idea conceptually? Do we have capacity to execute it well right now? Does it align with what matters most in this season?

Conceptual fit: Does this idea solve a real problem or create meaningful value?

Capacity fit: Can we resource this properly without breaking what's already working?

Seasonal fit: Is this the right priority given our current organisational stage and market conditions?

Most teams only evaluate the first dimension. They debate whether ideas are "good" in a vacuum. You bring all three lenses, which is why people experience your discernment as wisdom rather than just opinion.

Here's the language that helps your team understand your evaluation:

"This is a strong idea, but we don't have capacity to execute it properly until Q3. Let's table it with a specific review date."

"This solves a real problem, but it's not one of our top three priorities right now. If we pursue this, what are we willing to stop?"

"This aligns with our mission, but the market timing isn't right. Here's what needs to shift externally before this makes sense."

When you articulate your Discernment across all three dimensions, your team stops experiencing "no" as rejection and starts experiencing it as strategic guidance. You're not killing their ideas. You're protecting their capacity and directing it toward what will actually succeed.

Build a "right idea, wrong time" parking lot: Create a visible system where genuinely good ideas that don't fit current priorities get captured with context. Review it quarterly. This honours your team's creativity while maintaining focus, and it leverages your Discernment to create a strategic pipeline rather than just a series of rejections.

The best Insightful Collaborators become known for resurrecting ideas at exactly the right moment. Someone pitched something six months ago that you discerned wasn't ready. Conditions shift. You bring it back: "Remember that idea you had? Now is the time. Here's what's changed. Let me help you launch it."

6. How to Discern What Deserves Your Enablement Energy

Your Enablement capacity is finite, which means your Discernment must protect it ruthlessly by directing support only toward initiatives that meet specific criteria.

The trap most Insightful Collaborators fall into is enabling everything their team attempts because supporting people feels good. Your Enablement genius creates a dopamine hit when you help someone succeed. That positive reinforcement loop can override your Discernment, leading you to support initiatives that shouldn't be pursued in the first place.

You need a filter system: Before you offer support, evaluate the initiative against your strategic boundaries. If it doesn't pass your Discernment screen, your job is to redirect the person, not enable their effort. This feels uncomfortable at first because you're wired to help, but enabling misaligned work is actually a disservice to your team and your organisation.

The Enablement triage framework:

Tier 1 (Full support): Initiatives that directly advance top priorities and have strong likelihood of success. You enable these proactively with time, resources, and problem-solving.

Tier 2 (Conditional support): Initiatives with potential but missing key elements. You enable these only after specific gaps are addressed. "I'll support this once you have buy-in from operations."

Tier 3 (Redirect): Initiatives outside strategic boundaries or without realistic success paths. You don't enable these. Instead, you help the person understand why and redirect their energy toward Tier 1 or 2 work.

Your Discernment determines the tier. Your Enablement activates only for Tier 1 and conditionally for Tier 2. Tier 3 gets Discernment feedback but zero Enablement energy.

When someone asks for your support, run this quick evaluation:

Does this align with our strategic boundaries?

Does this person have clarity about what success looks like?

Are the foundational pieces in place for this to succeed?

Will my support actually increase the likelihood of success, or am I just making someone feel better about pursuing something that won't work?

If the answer to any of these is no, don't enable. Use your Discernment to provide clarity instead. "I don't think this is ready for my support yet. Here's what needs to shift first" or "This doesn't align with our priorities, so I'm going to redirect you toward something that does."

This discipline protects three things: your finite capacity, your team's focus, and your credibility. When people know you only enable what you genuinely believe in, your support becomes exponentially more valuable.

7. Teaching Your Team to Develop Their Own Discernment

The ultimate expression of the Insightful Collaborator pairing is enabling others to evaluate decisions effectively so they need you less.

If your team constantly brings you decisions for evaluation, you've become a bottleneck rather than a force multiplier. Your Discernment should be building discernment capacity in others, not creating dependency on your judgment.

Start making your evaluation process visible: When someone brings you a decision, don't just tell them your conclusion. Walk them through how you're evaluating it. "Here's what I'm looking at. Does this align with our Q2 priorities? Do we have the capacity to execute this properly? What's the opportunity cost? Based on those factors, here's my assessment."

When you externalise your Discernment process, you're enabling your team to internalise it. After three or four repetitions, they start evaluating their own decisions using your framework before they bring them to you.

Create decision-making tiers with clear ownership:

Decision Tier	Criteria	Who Decides
Tier 1: Operational	Inside established boundaries, reversible, low cost	Team member independently
Tier 2: Tactical	Inside boundaries, moderate impact, some risk	Team member with notification
Tier 3: Strategic	Touches boundaries, high impact, significant resource commitment	Collaborative with your Discernment input
Tier 4: Directional	Changes boundaries, irreversible, organisation-wide impact	You decide with team input

When your team knows which decisions they own and which require your input, they develop confidence in their own discernment for Tier 1 and 2 decisions while appropriately leveraging your expertise for Tier 3 and 4.

The teaching moment most leaders miss: When someone brings you a Tier 1 decision asking for approval, don't just give it. Ask them "What tier is this decision? Why? Based on that, who should be making this call?" Then send them back to own it. This feels inefficient in the moment but compounds into massive leadership leverage over time.

Your goal is a team that brings you fewer decisions because they've internalised your Discernment framework, freeing you to enable their execution instead of evaluating their every move.

STRATEGIC ENABLEMENT APPLICATION

Your Enablement genius multiplies impact when you apply it systematically rather than reactively. This section shows you how to enable at scale without burning out or becoming a crutch your team can't function without.

8. The Difference Between Enabling and Rescuing

Enabling removes obstacles so people can succeed. Rescuing removes consequences so people can avoid failure. Understanding this distinction is critical for Insightful Collaborators.

Your Enablement genius feels rewarding when you help someone overcome a challenge. The emotional payoff is immediate: they're grateful, the problem is solved, progress resumes. But not all help is enabling. Sometimes what feels like support is actually preventing someone from developing the capacity to solve their own problems.

Rescuing looks like support but creates dependency: You take over someone's task when they're struggling instead of coaching them through it. You provide the answer instead of helping them find it. You shield them from the natural consequences of their decisions instead of letting them learn from outcomes.

Enabling builds capacity: You remove systemic obstacles outside their control. You provide resources, access, or context they genuinely don't have. You connect them with expertise they need to develop. You clear organisational friction that's blocking their path.

Ask yourself before offering support:

Is this obstacle something they should learn to handle themselves?

Am I stepping in because they truly need help or because I want to feel useful?

Will my intervention make them more capable or more dependent?

Is this a skill gap, a resource gap, or a motivation gap?

If it's a skill gap, enable by teaching or connecting them to someone who can. If it's a resource gap, enable by providing access or removing barriers. If it's a motivation gap, don't enable at all. Use your Discernment to determine whether the initiative should continue, and if so, address the motivation issue directly.

The rescuing trap hits Insightful Collaborators hardest in three scenarios:

Scenario 1: Someone is struggling with work that doesn't align with their Working Genius. Your Enablement kicks in to help, but you're actually enabling a poor role fit that should be addressed structurally.

Scenario 2: Someone repeatedly struggles with the same type of challenge. Your Enablement keeps solving the immediate problem instead of addressing the pattern, which prevents growth.

Scenario 3: Someone asks for help but hasn't attempted problem-solving themselves first. Your Enablement rewards the request instead of requiring ownership, training learned helplessness.

When you catch yourself in a rescuing pattern, shift your approach. Instead of solving the problem, enable their problem-solving capacity. "I'm not going to handle this for you, but here's how I would think through it. Walk me through your approach and I'll help you refine it."

9. Creating Systems That Enable Without Your Constant Presence

The scalability ceiling for Insightful Collaborators is low unless you systematise your Enablement so it works when you're not in the room.

If you enable person-by-person, conversation-by-conversation, your impact maxes out at the number of hours you have available. Your goal should be enabling your team's success through systems, documentation, and resource access that function independently of your direct involvement.

Audit where your Enablement energy currently goes:

Track every enabling action you take for two weeks

Categorise them: Is this a one-time problem or a recurring need?

For recurring needs, ask: What system, resource, or process could address this without requiring me?

Build or document that solution once, then point people to it instead of re-solving it individually

Example: If you constantly help people navigate approval processes, create a visual flowchart with decision trees and contacts. Your Enablement happened once when you built it, but it enables infinitely without ongoing energy from you.

The highest-leverage Enablement systems to build:

Resource libraries: Templates, examples, and frameworks your team needs repeatedly. Build these once, update them quarterly, point people to them proactively.

Access maps: Who to contact for what, how to get budget approvals, where to find information. Removes the "I don't know who to ask" friction that stalls projects.

Decision frameworks: Clear criteria for common decision types so people can self-evaluate without needing your input. This combines your Discernment and Enablement into a tool others can use.

Obstacle escalation paths: Clear triggers for when someone should solve something themselves versus when they should loop you in. Prevents both learned helplessness and people spinning their wheels on problems outside their scope.

When someone asks for your help with something a system should handle, resist the urge to just solve it in the moment. Instead, solve it once in a way that scales. "I'm going to help you with this right now, and then I'm going to document the solution so anyone who hits this in the future can self-serve."

This approach feels slower initially but creates exponential leverage: Your Enablement energy shifts from reactive firefighting to proactive system-building, and your team becomes less dependent on your constant availability while still feeling fully supported.

10. How to Enable Without Creating Dependency

The best Enablement makes itself progressively less necessary by building capability in the people you support.

Your Enablement genius can accidentally create a team that can't function without you if you're not strategic about how you help. Every time you support someone, you should be asking: How do I help them succeed at this while simultaneously helping them need me less next time?

Dependency forms when you consistently provide fish instead of teaching fishing: You give answers instead of frameworks. You solve problems instead of coaching problem-solving. You provide resources directly instead of showing people how to access resources themselves.

The shift from dependency-creating Enablement to capacity-building Enablement happens in your approach, not your effort level. You can invest the same amount of energy but structure it differently to create growth instead of reliance.

Capacity-building Enablement follows this pattern:

First time: I do it, you watch. I narrate my thinking process so you understand the how and why, not just the what.

Second time: You do it, I coach. You take the lead, I provide real-time guidance and fill gaps, but you own the execution.

Third time: You do it independently. I'm available for questions but you don't need me to move forward.

Fourth time and beyond: You teach someone else. Now your capability is scaling beyond both of us.

Most Insightful Collaborators skip straight to "I do it" mode because it's faster and feels more helpful. That's the trap. Short-term speed creates long-term bottlenecks.

Watch for these signs you're creating dependency instead of capacity:

The same people ask you for the same types of help repeatedly

Your team's productivity noticeably drops when you're unavailable

People wait for your input before taking action even when they have authority to decide

Team members say "I don't know how to do this without you" more than "I learned how to handle this from you"

When you spot these patterns, resist the urge to interpret them as proof that you're valuable. They're actually proof that your Enablement approach needs adjustment. Value comes from building a team that succeeds because of what you've enabled them to become, not because you're personally removing every obstacle in real time.

11. Enabling Strategic Priorities Versus Enabling Everything

Your Enablement energy is finite, so where you direct it determines whether you multiply impact or diffuse it across too many fronts.

The default mode for most Insightful Collaborators is enabling whoever asks for help. Someone needs support, you have the capacity to provide it, you jump in. This reactive approach feels responsive but leads to scattered impact and eventual burnout.

Strategic Enablement works differently: You use your Discernment to identify the 3-5 initiatives that matter most, then you concentrate your Enablement energy there. Everything else gets minimal support regardless of who asks or how urgent it feels.

This requires you to disappoint people. Someone will ask for your help on something that doesn't align with top priorities. Your answer needs to be "I can't support this right now because I'm concentrating my energy on X, Y, and Z. If this becomes a strategic priority, I'll go all-in on enabling it, but right now I need to protect my capacity for what matters most."

The concentration principle produces disproportionate results: When you enable strategic priorities with full focus, they succeed faster and more completely. When you spread yourself across everything, nothing gets sufficient support to reach full potential.

Here's how to operationalise this:

Start each quarter by identifying your top 3-5 strategic priorities based on organisational goals

Allocate 80% of your Enablement capacity to those priorities exclusively

Reserve 20% for emergencies and opportunistic support

Communicate your focus areas transparently so your team knows where you're concentrating energy

Ruthlessly protect your 80% allocation by redirecting non-strategic requests

When someone outside your focus areas asks for support, acknowledge the request and provide an alternative. "This isn't in my current focus zone, but here's a resource that can help" or "I can't enable this directly right now, but let me connect you with someone who can."

Your team will adjust their expectations based on your actual behaviour, not your stated intentions. If you say strategic priorities matter but still enable everything anyone asks for, they'll learn that everything is actually a priority and your focus areas don't receive special treatment. If you consistently direct your best Enablement energy toward strategic work and provide minimal support to everything else, your team will align their requests and efforts accordingly.

This focused approach feels uncomfortable for natural enablers because it requires saying no frequently. The discomfort is the price of impact. You can be helpful to everyone and accomplish little, or you can be strategically helpful to the right initiatives and accomplish a lot.

12. The Art of Enabling People Outside Your Direct Authority

Insightful Collaborators often need to enable peers, partners, or people in other departments where you have influence but not authority, and that requires a different approach.

When you enable your direct reports, you have positional power to remove obstacles, allocate resources, and make decisions. When you enable laterally, you're working through influence, which means your Enablement must be offered, not imposed, and it succeeds only when the other person recognises and wants your support.

The mistake most people make when enabling laterally: They jump in to help without establishing permission or understanding context. They assume their support is welcome because their intentions are good. This often backfires because unsolicited help can feel like criticism or overstepping.

Effective lateral Enablement starts with asking, not doing: "I notice you're working on X and it looks like you're hitting friction around Y. I have some experience with that. Would it be helpful if I shared what's worked for me?" or "I have a resource that might help with what you're tackling. Want me to send it over?"

When you ask permission to enable, three things happen. First, you confirm that your help is actually wanted. Second, you learn what specific support would be most valuable. Third, you establish yourself as someone who respects boundaries, which makes people more likely to accept your help in the future.

Your Discernment becomes critical in lateral Enablement because you're reading social dynamics, not just project needs:

Is this person receptive to input right now or are they in heads-down execution mode?

Will my help be perceived as support or as interference from someone outside their area?

Do I have credibility in this domain or will my offer seem presumptuous?

What's the political dynamic? Will helping this person create friction with someone else?

When your Discernment senses that direct Enablement won't land well, look for indirect paths. Instead of offering to help personally, you might connect them with a resource, make an introduction to someone better positioned to assist, or share relevant information without framing it as advice.

The highest-leverage lateral Enablement often involves removing organisational friction: You have a relationship with someone who can approve their budget request. You can advocate for their project in a meeting they're not in. You can provide context about leadership priorities that helps them position their work more effectively. These enabling actions don't require you to do their work or even work directly with them, but they meaningfully increase their likelihood of success.

When lateral Enablement works, it creates alliance capital that benefits you strategically over time. People remember who helped them succeed when they needed it, and that goodwill translates into collaboration, support for your initiatives, and access to resources controlled by other departments.

INTEGRATING DISCERNMENT AND ENABLEMENT IN PRACTICE

This section addresses the practical integration challenges Insightful Collaborators face when applying both geniuses simultaneously in real leadership situations.

13. Leading Effective Evaluation Meetings That Don't Kill Momentum

Meetings where you need to evaluate ideas or decisions are where your dual genius either shines or creates frustration, depending on how you structure them.

The common failure pattern looks like this: Someone presents an idea or plan. Your Discernment immediately spots issues. You share your concerns. The presenter gets defensive. The meeting becomes a debate about whether the idea is good rather than a collaborative evaluation that improves it. Momentum dies and your Discernment feels like criticism instead of guidance.

The structure that works combines evaluation with enablement in the same conversation: You acknowledge what's strong, you identify what needs work, and you offer specific support to close the gaps. This prevents evaluation from feeling like rejection and activates your Enablement to help ideas reach their potential.

The three-part evaluation meeting framework:

Part 1 (Acknowledge): Start by naming what's working. "The core insight here is strong. The timing aligns with our Q2 priorities. You've clearly thought through the customer impact." This establishes that your Discernment sees value, which makes people receptive to hearing concerns.

Part 2 (Evaluate): Share your discernment about gaps, risks, or misalignments. Be specific and tie concerns to strategic context rather than personal preference. "My concern is that we don't have operational capacity to execute this properly until we finish the system migration. The risk is we launch something half-built and damage trust."

Part 3 (Enable): Immediately shift to problem-solving mode. "Here's how we could address that. What if we phase this in two stages? We launch the core feature now with limited scope, then expand after migration completes. I can help you map that phasing and get buy-in from operations."

When you combine all three parts in sequence, your Discernment provides clarity and your Enablement provides path forward. The person leaves with useful feedback and tangible support rather than just criticism.

Critical language shifts that change how your evaluation lands:

Instead of "This won't work because..." say "For this to work, we'd need to address..."

Instead of "I don't think this is the right approach" say "I'm concerned about X. Help me understand how you're thinking about that"

Instead of "This isn't a priority" say "This doesn't align with our current top three priorities, which are..."

Instead of "You're missing..." say "What would it take to add..."

These aren't semantic games. They're structural reframes that position your Discernment as collaborative truth-seeking rather than judgment from authority. When people experience your evaluation as helping them think more clearly rather than telling them they're wrong, they actively seek your input instead of avoiding it.

End every evaluation meeting with a clear next action and a specific way you'll enable it. "Based on this conversation, your next step is to get operational approval for the modified timeline. I'll introduce you to the right person this afternoon and brief them on why this matters." Your Discernment set direction, your Enablement created momentum.

14. How to Give Feedback That Evaluates and Empowers Simultaneously

Feedback delivery is where Insightful Collaborators either integrate their genius pairing brilliantly or let Discernment dominate in a way that feels deflating rather than developmental.

Your Discernment naturally activates during feedback situations because you're evaluating performance, decisions, or work quality. The risk is that evaluation without enablement feels like criticism with no path forward. The person knows what's wrong but not how to fix it, and they don't feel supported in making the change.

Integrated feedback follows a specific structure that uses both geniuses: You evaluate clearly (Discernment), you explain why it matters (context), you show the path to improvement (guidance), and you offer specific support (Enablement). Each component is necessary for feedback to land as developmental rather than demoralising.

The feedback structure that works:

Observation (Discernment): "In yesterday's client meeting, you jumped to solutions before fully understanding their core problem. That's the third time I've noticed that pattern."

Impact (Context): "When we do that, clients don't feel heard and we often solve the wrong problem. It damages trust and leads to rework."

Guidance (Direction): "The skill you're building is diagnostic questioning. Instead of moving to solutions in the first ten minutes, spend that time asking clarifying questions to understand root causes."

Enablement (Support): "I'm going to be in your next two client meetings. I'll model the diagnostic questioning approach, and then we'll debrief after. I'll also send you the question framework I use."

This structure takes longer than just pointing out the problem, but it creates actual behaviour change because the person leaves with clarity, direction, and support rather than just awareness of a deficit.

Your Discernment identifies the gap. Your Enablement closes it. When you separate these by giving evaluative feedback in one conversation and enabling improvement in a different conversation later, the feedback feels like criticism. When you combine them immediately, feedback feels like coaching.

Watch your ratio of evaluative statements to enabling statements: If you spend ten minutes diagnosing what's wrong and thirty seconds offering support, your Discernment is dominating. Aim for balance. Spend equal time identifying the issue and enabling the solution.

The language pattern that signals integrated feedback: You follow every evaluative observation with "and here's how I'll help you develop that" or "and here's the resource that will address this" or "and here's what I'll do to support you improving in this area."

When feedback conversations go sideways, it's usually because you activated Discernment without Enablement. The person feels judged rather than developed. If you catch yourself in an evaluation-heavy feedback conversation, pause and explicitly shift: "I've been focused on identifying the issue. Let me shift to how we'll address it together, because that's actually more important."

15. Managing the Energy Drain of Constant Evaluation

Discernment is cognitively expensive, and Insightful Collaborators often underestimate how much energy evaluation consumes, leading to decision fatigue and burnout.

Every time you evaluate something, your brain is running complex pattern matching, weighing tradeoffs, considering second-order effects, and filtering through strategic context. This mental work is invisible but exhausting, especially when you're evaluating constantly throughout the day.

The energy management challenge for Insightful Collaborators is asymmetric: Enablement often gives energy because helping feels good and provides immediate positive feedback. Discernment drains energy because evaluation requires sustained focus and often involves delivering difficult truths.

If you're not strategic about when and how much you evaluate, you'll hit decision fatigue by midday and your Discernment quality will degrade exactly when you need it most.

Energy protection strategies that work:

Batch evaluation work: Instead of evaluating decisions reactively throughout the day, create specific times for evaluation work. "I review proposals from 10am to 11:30am daily. Submit anything needing my evaluation before 9:30am and you'll get feedback by noon."

Create evaluation tiers: Not every decision needs your full Discernment capacity. Reserve deep evaluation for strategic decisions and use lightweight frameworks for operational ones. This prevents you from applying the same cognitive load to everything.

Limit evaluation volume: Set a realistic maximum for how many things you can evaluate well in a day. Maybe that's five major decisions or ten smaller ones. When you hit the limit, you're done evaluating. Everything else waits until tomorrow when you have capacity.

Alternate between Discernment and Enablement throughout your day: Structure your schedule so evaluation work and support work are balanced. If you spend the morning evaluating proposals, spend the afternoon enabling project teams. The cognitive modes are different enough that switching between them provides recovery.

Your Discernment quality degrades when you're tired, stressed, or overloaded. This is dangerous because poor evaluation creates downstream problems that require more fixing later. Protecting your Discernment capacity is protecting your team from bad decisions.

Signs you've exceeded your sustainable evaluation capacity:

You approve things you normally wouldn't to avoid thinking harder about them

Your evaluations become more negative because you lack energy to see possibilities

You delay decisions because evaluation feels overwhelming

Your feedback becomes less specific and more generically critical

When you notice these signs, you're not managing evaluation energy well. Pull back on evaluation volume, delegate more decisions, or block dedicated recovery time where you're not making any evaluative judgements at all.

The counterintuitive reality is that doing less evaluation often improves your overall impact because the evaluation you do perform is higher quality and you preserve energy for Enablement work that moves things forward.

16. Building a Team That Compensates for Your Frustrations

Every Working Genius pairing has corresponding frustrations, and the Insightful Collaborator's frustrations with Wonder, Invention, and Galvanising can create blind spots you need to staff around.

Your Discernment and Enablement genius means you're likely frustrated by the ideation phase where people are wondering about possibilities (Wonder), the invention phase where people are creating solutions (Invention), and the activation phase where people are rallying others to action (Galvanising).

Frustration doesn't mean incompetence. You can perform frustrated activities when necessary, but they drain you and they're not where you create the most value. The strategic move is building a team strong in your frustration areas so you're not forcing yourself to operate there.

What this looks like in practice:

Wonder frustration: You get impatient during open-ended brainstorming or exploratory conversations that don't have clear direction. You need someone on your team who loves asking "what if?" and exploring possibilities without judgement. This person feeds your Discernment by generating options for you to evaluate.

Invention frustration: You're not naturally excited about creating new solutions or designing systems from scratch. You need someone who gets energised by building and solving problems. This person takes what your Discernment approves and creates solutions, which you can then enable.

Galvanising frustration: You don't naturally rally people to action or create enthusiasm around initiatives. You need someone who loves generating momentum and getting people excited. This person takes what you've discerned as important and what you've enabled with resources, then creates the energy that drives adoption.

When you staff around your frustrations intentionally, you create a complete team cycle. Wonder generates possibilities. You apply Discernment to evaluate which ones matter. Invention creates solutions for those priorities. You apply Enablement to resource them properly. Galvanising creates momentum. You enable sustained execution. For more on how specific pairings complement yours, see how the Judicious Accomplisher leads with Discernment-first energy and how the Loyal Finisher pairing brings Enablement and Tenacity that extends what you start. For practical guidance on building these complementary teams, the Working Genius team building guide covers exactly this.

The mistake Insightful Collaborators make is trying to perform all six functions themselves or criticising team members who operate in Wonder, Invention, or Galvanising because those activities feel inefficient to you. They're not inefficient. They're necessary. You just don't need to be the one doing them.

Hire specifically for your frustration zones and give those people explicit permission to operate in ways that might feel chaotic to you. Your Discernment will want to shut down lengthy brainstorms or creative tangents. Resist that urge when someone with Wonder genius is doing their best work. Let them explore, then apply your Discernment to what they produce.

COMMUNICATION STRATEGIES FOR INSIGHTFUL COLLABORATORS

How you communicate your Discernment and Enablement determines whether people experience you as a valuable leader or a frustrating bottleneck. This section addresses specific communication patterns that make your genius pairing land effectively.

17. How to Share Discernment Without Sounding Like a Gatekeeper

Your Discernment is valuable, but the way you communicate evaluation can make people feel supported or blocked depending on your framing.

When you share discernment feedback, you're often highlighting problems, gaps, or misalignments. This is necessary and helpful, but if you communicate it without context or connection to support, people experience you as someone who only says no without helping them find yes.

The framing shift that changes everything: Position your Discernment as protecting the person's success rather than judging their idea. Instead of "This won't work," say "I want this to succeed, and for that to happen, we need to address these three things."

That small reframe changes the emotional dynamic completely. In the first version, you're the barrier. In the second version, you're the ally helping them navigate barriers. The substance of your evaluation is identical, but the relational impact is opposite.

Three communication patterns that make Discernment land as guidance rather than gatekeeping:

Connect evaluation to strategy: "Based on our Q2 priorities, this doesn't fit right now" is better than "I don't think we should do this." The first version explains the evaluation criteria. The second version feels like personal preference.

Separate idea quality from timing/fit: "This is a strong concept that doesn't fit our current capacity" is better than "We can't do this." The first version honours the thinking while addressing constraints. The second version sounds like flat rejection.

Pair evaluation with support offers: "I see three gaps we'd need to close. I can help with two of them if you can handle the third" is better than "This has three major problems." The first version shifts immediately to enablement. The second version leaves them alone with problems.

Your tone matters as much as your words. Discernment delivered with curiosity sounds like collaboration. Discernment delivered with certainty sounds like judgement. Even when you're confident in your evaluation, phrase it in a way that invites dialogue. "I'm concerned about X for these reasons. What am I missing?" opens conversation. "X won't work" shuts it down.

Watch the ratio of yes to no in your communication: If every time someone brings you an idea your first response is identifying problems, you train people to stop bringing ideas. Balance critical evaluation with acknowledging strengths. "Here's what's working in this proposal... and here's what needs adjustment..." gives people both validation and direction.

The goal isn't to soften your Discernment or avoid sharing hard truths. The goal is to communicate evaluation in a way that people experience it as helpful rather than obstructive, which makes them receptive to your feedback instead of defensive against it.

18. The Language of Proactive Enablement

How you offer support determines whether people feel empowered or patronised, and proactive Enablement requires specific communication approaches to land well.

Reactive Enablement is easy to communicate: someone asks for help, you provide it. Proactive Enablement is trickier because you're offering support before being asked, which can feel like you're implying they can't handle it themselves or overstepping their ownership.

The language pattern that makes proactive Enablement welcome: Frame your offer around removing obstacles rather than fixing their work. "I noticed you're working on X and you might need Y. I have access to that. Want me to handle getting it for you?" This positions your help as removing friction, not as judging their capability.

Proactive Enablement language that works:

"I have a relationship with the person you need approval from. Want me to make an intro and provide context?"

"I've done something similar before and hit these three obstacles. Want me to walk you through how I navigated them?"

"This type of project usually needs X resource at this stage. I can facilitate getting that if it would help."

"I'm hearing your update and it sounds like [specific obstacle] might be slowing you down. I can address that on my end if you'd like."

Notice the pattern: You identify a specific obstacle, you explain why you're positioned to help, you offer rather than impose, and you wait for permission. This respects their ownership while making your support available.

Proactive Enablement language that backfires:

"You should really get help with that" (implies incompetence)

"Let me just do it" (takes ownership without asking)

"You're going to struggle with this without..." (predicts their failure)

"I'll take care of it" (removes their agency entirely)

These versions, even if well-intended, make people feel diminished rather than supported. The communication pattern matters as much as the substance of your help.

When someone declines your proactive Enablement offer, respect that boundary. "No problem. The offer stands if circumstances change." Don't be offended or keep pushing. Proactive support is most valuable when the person wants it. Forced help isn't enabling.

The confidence calibration is subtle but important: Offer help from a place of available resources, not from a place of assumed superiority. "I happen to have access to X" is better than "You need X and I can provide it." The first acknowledges circumstance. The second implies hierarchy.

Your Enablement is most effective when people experience it as a resource they're grateful to access rather than a judgement about their limitations.

19. Managing Up When Your Leaders Don't Understand Your Pairing

If your manager or organisational leaders don't speak Working Genius language or understand your Discernment and Enablement pairing, you need to translate your value in terms they recognise.

The challenge is that Discernment and Enablement are behind-the-scenes geniuses. You're not generating flashy ideas, building visible products, or leading high-energy rallying moments. You're evaluating quietly and supporting in the background. This work is essential but often invisible, which means you need to make your impact explicit.

How to communicate your Discernment value to leaders:

Track decisions you influenced and outcomes that resulted: "I evaluated the Q1 project portfolio and recommended we cut three initiatives. That freed capacity that led to the successful X launch."

Highlight problems you prevented: "I flagged resource constraints in the Y proposal before approval. That prevented a failed launch that would have cost [specific amount/impact]."

Quantify your evaluation impact: "I review approximately 15 strategic decisions per week. My evaluation process has a 90% alignment rate with successful outcomes based on six-month retrospectives."

How to communicate your Enablement value to leaders:

Connect support to results: "I enabled the Z project by removing three operational obstacles. That team delivered two weeks early as a result."

Track who you've helped succeed: "I directly supported five major initiatives this quarter. Four exceeded their goals and one met target."

Quantify your force multiplication: "Team members I enable directly show 30% faster project completion on average based on historical comparison."

Your leaders care about results. Frame your Discernment as decision quality and risk mitigation. Frame your Enablement as acceleration and success rate. These are the translations of your genius into business value language.

When your leader asks you to operate outside your genius, use this approach: "I can do that, but I create the most value when I'm evaluating strategic decisions and removing obstacles for the team. Would it make sense to structure my role more around those strengths?" This isn't refusing work. It's educating your leader about where you deliver disproportionate impact.

If your organisation doesn't value Discernment and Enablement, you might be in the wrong organisational culture. Some environments reward visible action and charismatic energy above everything else. Insightful Collaborators thrive in cultures that value strategic thinking and team development. If you're constantly fighting for recognition in a culture that doesn't value your genius, consider whether it's a fit issue rather than a performance issue.

20. How to Ask for What You Need From Others

Your Working Genius pairing means you need specific things from teammates to operate at your best, and most people won't provide them unless you ask explicitly.

Your Discernment works best when you have complete information, clear strategic context, and sufficient time to evaluate properly. Your Enablement works best when people tell you specifically what obstacles they're facing and what support would actually help.

Most people won't provide these things automatically because they don't know you need them. They'll bring you decisions without context, ask for evaluation under time pressure, request vague support, or not tell you they're struggling until it's crisis mode.

What Insightful Collaborators need to ask for from their teams:

For Discernment to work: "When you bring me a decision for evaluation, include the strategic goal you're trying to achieve, the options you're considering, and what factors you've already evaluated. That context helps me provide better input."

For Enablement to work: "Tell me specifically what obstacle you're facing and what would help. 'I need support' is hard for me to action. 'I need budget approval and I don't know who to ask' gives me a clear way to help."

For integration: "I work best when I can evaluate whether something should move forward and then immediately help it succeed. Don't separate those asks. Bring me both the decision and the support need in the same conversation."

For capacity management: "I can only evaluate a certain number of decisions well per day. If something needs my evaluation, get it to me by [time] so I can give it proper attention. Last-minute evaluations get lower quality thinking."

These aren't demands. They're instructions that help people get the best work from you. Most teammates want to work well with you but don't know how. Telling them explicitly makes collaboration easier for everyone.

When someone doesn't follow these guidelines, remind them gently: "I'll evaluate this, but I'd be able to give you better input if you included the strategic context we talked about. Can you add that and resubmit?" This trains people over time without creating friction.

Your needs aren't weaknesses. They're the operating conditions that let your genius function at full capacity. Advocate for them clearly.

SCALING IMPACT AS AN INSIGHTFUL COLLABORATOR

As you grow in leadership responsibility, your approach to Discernment and Enablement must evolve or you'll hit a ceiling. This section addresses how to scale your impact beyond what you can personally evaluate and enable.

21. Moving From Personal Discernment to Building Discernment Culture

At a certain scale, you can't personally evaluate every decision, which means your job shifts to building organisational discernment capacity that functions when you're not involved.

The transition from individual contributor to leader requires moving from "I evaluate" to "I teach others how to evaluate using my framework." If you try to maintain personal evaluation control as your scope grows, you become a bottleneck that slows every decision.

Scaling discernment means codifying your evaluation framework so others can apply it: What criteria do you use when evaluating decisions? What patterns do you look for? What red flags trigger deeper analysis? What strategic priorities filter which opportunities you pursue? These need to exist as documented frameworks your team can use independently.

The framework documentation process:

Track 20-30 of your recent evaluations across different decision types

Reverse-engineer what criteria you actually applied, even if it was intuitive in the moment

Organise those criteria into a decision framework with clear factors and weightings

Test it by having team members apply it to decisions and comparing their conclusions to yours

Refine based on where the framework produces different results than your intuition

Train your team on using the framework explicitly

Once your team can apply your Discernment framework independently, your role shifts to evaluating only high-stakes strategic decisions and auditing whether the framework is being applied consistently.

This feels uncomfortable for most Insightful Collaborators because evaluation is your genius. Letting go of personal control over decisions feels like giving up your value. Actually, it's multiplying your value. When five people can evaluate decisions using your framework, your Discernment is operating at 5x scale even when you're not in the room.

The quality concern is valid: Their application of your framework won't be as good as your personal evaluation initially. Accept that. The tradeoff is scale. Ten decisions evaluated at 85% quality creates more organisational value than three decisions evaluated at 100% quality because you were the bottleneck.

Reserve your personal Discernment capacity for the decisions where your specific judgement creates disproportionate value: strategy shifts, major resource allocation, critical hires, partner relationships. Delegate everything else to your team using the framework you've built.

22. Moving From Personal Enablement to Building Enabling Systems

Just as Discernment must scale beyond your personal evaluation, Enablement must scale beyond your personal support or you'll exhaust yourself while limiting your team's growth.

The pattern is the same: move from "I enable people" to "I build systems that enable people without requiring me." This requires analysing what obstacles you repeatedly remove and creating structures that prevent those obstacles from forming in the first place.

The system-building approach to scaled Enablement:

Identify recurring obstacles: What do you help people with repeatedly? Approvals, resource access, information gaps, skill development, cross-functional coordination?

For each category, build a system: Process documentation, resource libraries, approval workflows, training programs, communication channels. The system handles the enabling that your personal intervention used to provide.

Transition people from you to the system: Next time someone asks for help that a system now addresses, point them to it. "I used to handle this directly, but now we have a system. Here's how to access it."

Maintain and improve systems: Collect feedback on where systems aren't working and refine them quarterly. Systems require maintenance to remain effective.

The psychological hurdle is that building systems feels less immediately rewarding than personal Enablement. When you directly help someone, you get instant gratification. They're grateful, the problem is solved, you feel valuable. Building a system that enables hundreds of people over time is more impactful but less emotionally satisfying in the moment.

Your identity as an enabler might resist this transition. If your self-worth is tied to being the person people come to for help, scaling Enablement through systems feels like making yourself unnecessary. Reframe it: You're not making yourself unnecessary. You're freeing yourself to enable at a higher level. Instead of solving individual problems, you're solving systemic friction that affects everyone.

The scaling pattern for Enablement:

Year 1: You personally enable 10 people through direct support

Year 2: You build systems that enable 50 people while you personally enable 5

Year 3: Your systems enable 200 people while you personally enable 3 at a strategic level

Your direct Enablement footprint decreases while your total Enablement impact increases exponentially. That's what scaling looks like.

23. Training Others to Lead With Discernment and Enablement

The ultimate scaling move is developing other Insightful Collaborators who can multiply your leadership approach across the organisation.

Not everyone on your team will have the Discernment and Enablement pairing naturally, but you can teach people to strengthen those capacities even if they're not natural geniuses. The goal isn't to make everyone a clone of you. It's to build evaluation and support capacity broadly so your organisation has those capabilities distributed instead of concentrated in one person.

Teaching Discernment capacity:

Bring people into your evaluation conversations as observers so they learn your thinking process

After you evaluate something, explain your reasoning: "Here's what I was looking for and why"

Give people small evaluation decisions with clear criteria and debrief their choices

Gradually increase decision-making authority as their evaluation quality improves

Create feedback loops so they learn from outcomes whether their discernment was accurate

Teaching Enablement capacity:

Model proactive support by narrating what you're doing: "I'm reaching out to operations now to remove this obstacle for Sarah before she hits it"

Assign people to support specific projects or teammates and coach them on effective enabling

Teach the difference between rescuing and enabling through specific examples

Celebrate when someone successfully helps another person succeed

Make support an explicit part of role expectations, not just implicit culture

When you develop these capacities in your team, several things happen: Decision quality improves across the organisation. People get support faster because they don't have to wait for access to you. Your team becomes more self-sufficient. You free capacity for higher-level strategic work.

Look for people with natural aptitude in either Discernment or Enablement and help them develop both. Someone strong in Discernment but weak in Enablement can learn to follow evaluation with support. Someone strong in Enablement but weak in Discernment can learn to filter where they direct their support energy.

The goal is creating a leadership team where multiple people can evaluate strategically and enable effectively, making your organisational capacity for both functions far greater than what you could provide alone.

24. Knowing When to Step In Versus Let Your Team Handle It

As you scale, the hardest judgement call is determining which situations require your direct involvement and which your team should handle independently.

Your instinct will be to jump in whenever you see a decision being evaluated poorly or support being provided ineffectively. Resist that instinct. Every time you take over, you prevent your team from developing capacity and you reinforce dependency on you.

The intervention criteria that actually work:

Step in when: The decision is genuinely strategic with irreversible consequences. When your team's evaluation missed something critical that creates significant risk. When the situation is outside their authority or expertise level. When failure would cause harm beyond acceptable learning cost.

Stay out when: The decision is tactical within established boundaries. When their evaluation is good enough even if not perfect. When failure would provide valuable learning at acceptable cost. When your intervention would prevent necessary skill development.

The question isn't "Could I do this better?" The answer is almost always yes. The question is "Does this require my level of capability or is it a development opportunity for my team?" That reframe changes your intervention threshold significantly.

Create explicit escalation criteria with your team: "Here are the types of decisions you own completely. Here are the types where you should notify me but still decide. Here are the types where we decide together. Here are the types I own." This prevents both under-involvement where you should engage and over-involvement where you shouldn't.

When you're tempted to intervene, ask yourself three questions first:

What's the actual risk if this proceeds without my involvement?

Is that risk acceptable as a learning investment?

Will my involvement build capacity or create dependency?

If the risk is acceptable and your involvement would create dependency, stay out. Coach afterward if needed, but let your team experience the full cycle of decision and outcome.

The uncomfortable truth is that your team will make worse decisions and provide less effective support than you would in many situations. That's not failure. That's development. The gap between their current capability and your expert capability is exactly what you're trying to close through experience, and experience requires doing, not watching you do.

Your job at scale isn't to make every decision perfectly. It's to ensure the organisation develops enough Discernment and Enablement capacity to function well even when you're not involved.

25. Measuring Your Impact as an Insightful Collaborator

Traditional performance metrics don't capture Discernment and Enablement impact well, which means you need to define and track metrics that actually reflect your contribution.

Most organisations measure visible output: revenue generated, products shipped, projects completed. Your genius pairing operates behind those outcomes, influencing quality and success rate rather than creating countable deliverables. If you let others define your metrics, you'll be measured on things that don't reflect your actual value.

Discernment impact metrics that matter:

Decision quality rate: Percentage of decisions you evaluated that achieved intended outcomes

Resource efficiency: Projects you approved versus projects you declined, measured by success rates of each group

Problem prevention: Initiatives you redirected before launch that would have failed based on post-analysis

Strategic alignment: Percentage of team effort directed at top priorities versus scattered across low-value work

Enablement impact metrics that matter:

Acceleration rate: How much faster projects move when you enable them versus baseline

Success rate of enabled initiatives: Percentage of projects you supported that hit or exceed goals

Obstacle removal speed: Time from identification to resolution for friction you address

Team capacity: How much more work your team handles effectively because of your support systems

These metrics require intentional tracking because they don't emerge automatically from standard reporting. You need to instrument measurement specifically for your genius pairing.

Create a quarterly impact review where you document:

Major decisions you evaluated and their outcomes

Initiatives you enabled and their results

Systems you built and adoption rates

People you developed and their growth trajectories

Strategic shifts you influenced and downstream effects

This becomes your track record of impact that you can reference in performance discussions, promotion conversations, or when educating leadership about your value.

The meta-metric that matters most is leverage: How much organisational value is created per unit of your time and energy? As you scale your Discernment and Enablement through systems, frameworks, and developed team capacity, your leverage should increase dramatically. You're doing less direct evaluation and enabling but creating more total impact through what you've built.

If your leverage isn't increasing year over year, you're not scaling effectively. You're just doing more of the same direct work, which eventually hits a ceiling. Track your leverage ratio explicitly and make strategic decisions to improve it by investing in systems, delegation, and development.

Your value as an Insightful Collaborator is real and significant. Make sure you're measuring and communicating it in ways that capture what you actually contribute.

Leading with Discernment and Enablement gives you a rare combination that most leaders don't have. You see what matters and you help people succeed at it. That pairing creates clarity, momentum, and results when you integrate both geniuses intentionally.

The key is using your Discernment to filter where your Enablement goes, building systems that scale both capacities beyond your personal involvement, and communicating your value in ways that make your behind-the-scenes impact visible. For your next steps after sharing this framework with your team, see the practical steps after your Working Genius session. When you master this integration, you become the leader people trust to tell them the truth and help them win.