TLDR: Difficult feedback conversations feel dangerous to ADHD operators because they attempt to deliver correction without an underlying reservoir of safety. By building the Trust Jar, applying the Nice vs. Kind operational standard, and shifting from heroic control to clear delegation, neurodivergent leaders can address performance gaps directly, protect their team relationships, and scale execution without emotional burnout.
In Part 1 of this series, we dismantled the myth that managers are villains and established that internal execution is genuine leadership. In Part 2, we unmasked the Gargoyle: the hyperactive threat detector that weaponizes Rejection Sensitive Dysphoria into Empathetic Avoidance.
Knowing your anxiety is neurological helps explain the dread. It does not run the performance review for you.
When an operational gap surfaces, the instinct for many ADHD leaders is to search for the perfect script. The magical phrase that delivers the hard truth while guaranteeing zero relational tension.
That phrase does not exist.
Scripts fail when they lack structural support. What makes difficult conversations safe, clear, and productive is not verbal gymnastics. It is the Architecture of Trust you build before the conversation ever takes place.
The Trust Jar: How Daily Deposits Create Psychological Safety
Most leaders think of trust as an abstract feeling: Do my people like me? Do they think I’m approachable? Am I too tough? Not tough enough?
For an Anchored Operator, trust is an operational bank account.
Building on Brené Brown’s marble jar concept from Daring Greatly (2012), the Trust Jar serves as a foundational operational tool, though with one critical reality check for high-growth teams. Standard leadership advice treats deposits and withdrawals as roughly equal. In the day-to-day trenches of managing teams and navigating ADHD wiring, they are not. Not even close.
Deposits go in as pennies. Withdrawals come out as nickels, dimes, or quarters.
Trust is a two-way street. You maintain a Trust Jar for each member of your team, and each keeps one for you on their desk, metaphorically speaking, I hope. Every interaction is either adding to copper reserves or withdrawing from them.
The Manager’s Jar: Building Credibility Penny by Penny
Every time you show up with consistency, clarify an ambiguous workflow, protect your team from a founder’s sudden pivot, or give specific praise for work you actually observed, you place a penny in their jar. These are small, unglamorous, daily habits that compound slowly over time.
Where operators get blindsided is realizing how easily they make withdrawals from their team’s jar.
When you get overwhelmed and become the idea tornado yourself, when you change priorities mid-week without context, when you drop a commitment because of a calendar fire drill, or when emotional reactivity leaks into a Slack channel, a nickel leaves the jar. It is rarely a single catastrophic event that empties a team member’s trust; it is the friction of unpredictable leadership.
The Math of Relational Capital
| The Two Jars | Deposits: Pennies In (Daily Habits) | Withdrawals: Nickels & Dimes Out (Friction Points) |
| Their Jar for You (Your Leadership Credibility) | • Keeping operational commitments • Setting clear criteria for “Done” • Protecting team calendars & focus blocks • Maintaining emotional regulation under stress | • Changing sprint goals mid-week without context • Becoming the idea tornado • Dropping 1-on-1s for fire drills • Taking over tasks without explanation |
| Your Jar for Them (Their Execution Reliability) | • Proactive communication on blockers • Delivering work that matches agreed criteria • Asking clarifying questions early • Flagging timeline risks before deadlines hit | • Unannounced missed milestones • Hiding errors or waiting to be asked for updates • Repeated process drift after training • Unaddressed friction compounding silently |
The Silent Leaks of Unshared Expectations
Here is what most ADHD operators miss: when you avoid holding a standard for weeks out of fear of conflict, you believe you are preserving relational capital. You are not.
The unaddressed issue is quietly draining the jar. Every day, an uncommunicated expectation drains away a fraction of a penny. Over a week or a month, that silence bleeds out full nickels.
Unshared expectations breed quiet resentment, and resentment is the bedrock of executive burnout. When you finally address the issue because your patience has broken, the jar is already empty. What could have been a calm coaching moment lands as a destructive confrontation.
Bad news doesn’t get better over time.
The ADHD Nervous System: RSD and Justice Sensitivity
Navigating trust is uniquely charged for the neurodivergent operator because of two neurological realities:
- Rejection Sensitive Dysphoria (RSD): When you realize you made a withdrawal from someone’s jar (dropped a ball, reacted sharply, or delivered clumsy feedback), RSD registers that misstep as a devastating moral failure rather than simple operational data. The instinct is to either hide in shame or overcompensate with people-pleasing, both of which destabilize your leadership.
- Justice Sensitivity: When a team member makes a withdrawal (misses a deadline, skirts an SOP, or fails to follow through), your brain’s intense need for fairness and integrity can cause that single miss to feel like intentional sabotage. You might find yourself wanting to pull quarters out of their jar for a nickel-sized mistake.
Recognizing these neurological reflexes allows you to pause and evaluate the data objectively. A missed deadline is not a relational catastrophe; it is an operational signal that a workflow, a handoff, or a standard needs recalibration.
When you consistently fill the jar with clear expectations and steady deposits, a direct correction is no longer an attack. It lands inside a container of established safety.
⚡ ADHD Power-Up: ADHD brains possess exceptional pattern recognition. Put that antenna to work auditing the Trust Jars across your team. When you notice a direct report pulling back, turning quiet in Slack, or hesitating before speaking up, do not wait for a formal review. Make an intentional penny deposit: send a brief message recognizing a specific operational win, clarify an ambiguous priority, or validate their effort on a difficult task. Steady micro-deposits eliminate the need for sudden, painful course corrections.
Nice vs. Kind: The Operational Standard for Team Care
To lead tough conversations with confidence, operational leaders must resolve a fundamental misunderstanding about empathy.
Nice protects the moment. Kind protects the relationship.
Nice is conflict avoidance dressed up as professionalism. Nice tells an underperforming team member, “Don’t worry about the late deliverable, you’ve been working hard,” while you stay up until 1:00 AM fixing their errors in silence. Nice protects your comfort in the short term. It robs the team member of the feedback they need to calibrate their performance, and it robs you of the operational capacity you cannot afford to keep giving away.
Kind is the harder, more courageous path. Kind tells the truth clearly: “The client deck missed the 2:00 PM milestone, which delayed our staging review. Let’s look at the workflow together and find where the handoff broke down.”
Kind holds the standard. It respects the person enough to treat them as a capable adult. It gives them the tools to succeed rather than the illusion that everything is fine.
Brené Brown puts it plainly in Dare to Lead (2018): “Feeding people half-truths or bullshit to make them feel better (which is almost always about making ourselves feel more comfortable) is unkind.” She is not writing specifically about managers. She is writing about every leader who has ever chosen the path of least resistance over the path of honest investment.
The Nice choice is almost never about protecting the other person. It is about protecting yourself.
Before any accountability conversation, ask yourself this diagnostic question: “Am I withholding this data to protect their growth, or to protect my own comfort?”
Choosing your comfort is Nice. Choosing their growth is Kind.
Nice vs. Kind in Practice
| “Nice” (Short-Term Ease) | “Kind” (Long-Term Growth) |
| Softens the core truth | Delivers high clarity |
| Avoids immediate tension | Invests in future agency |
| Protects manager comfort | Focuses on team growth |
| Compounds into burnout | Builds lasting trust |
🪞 Real Talk: RSD makes conflict feel dangerous, so you convince yourself that letting a missed standard slide is an act of mercy. It isn’t. When you lower the bar in secret, you carry the emotional weight while your team operates in confusion. Clarity is the highest form of operational kindness. The gargoyle that is keeping you out of the conversation is the same one keeping your team member from the feedback they actually need to grow.
Angela’s Story: Moving from Heroic Control to High-Trust Delegation
Angela (not their real name), an operational leader at an early-stage agency, came to coaching trapped in the classic Fixer’s Dilemma.
For years, she had managed interns and contractors by doing the heavy lifting herself. She built systems, yes, but she built them around her own execution. Every deliverable ran through her. Every client email received her final review. The systems assumed she was the one at the keyboard.
When the company scaled and hired two full-time operational specialists, Angela found herself working eighty hours a week, reviewing every spreadsheet, rewriting every draft she could have trusted someone else to own.
Her bottleneck was not a lack of tools. It was a failure of trust, aimed in two directions simultaneously: she didn’t fully trust her team members to meet the standard, and she didn’t fully trust herself to define the standard clearly enough that someone else could meet it.
Her inner gargoyle supplied the narrative: if she handed off complete ownership and a project failed, it would prove she was an incompetent manager. Maintaining quality required personal control. Letting go was the same as letting the whole thing collapse.
Together, we rebuilt her delegation framework from the ground up. Three shifts made the difference:
Define Done, not the steps. Instead of dictating how to execute, Angela documented explicit acceptance criteria for the final outcome. Not “handle the client onboarding” but “the client onboarding checklist is complete, the welcome email is sent within two hours of contract signature, and the project brief is in the shared drive by end of day.”
Install milestone checkpoints, not surveillance. Rather than reviewing work continuously, she set two structured weekly check-ins to review progress against the defined criteria. Her team knew exactly when she would look and what she would look for. The ambiguity that had driven her to hover disappeared.
⚓ Pro Tip: Micromanaging is like pressing every button in an elevator on your way to the 20th floor. Pick two milestone floors to inspect progress, then step out of the doorway so execution can move.
Separate the person from the process. When a deliverable missed the standard, Angela stopped logging in at midnight to fix it herself. She brought it to the next check-in, walked through the checklist with the team member, and asked where the handoff had broken down. Every miss became a system audit rather than a performance verdict.
🪞 Real Talk: I know how hard this can be when you are feeling like you are jumping from fire to fire and everything feels urgent. Taking time now to let your team learn and grow, knowing that it might mean some things get dropped, is challenging for us – the leaders who care. But this is how you build trust and teams that don’t need you to solve every problem. That is being an Anchored Operator.
Angela’s breakthrough came during a major client onboarding workflow. A team member missed an automation step. She felt the familiar pull toward her keyboard. She resisted it. The next morning, they walked through the checklist together, identified an ambiguous handoff rule, and the team member updated the SOP.
Angela reclaimed significant deep-work capacity — she told me she got back close to twelve hours a week. More importantly, her team reported feeling trusted, respected, and empowered in a way they hadn’t before. The quality held. The standard didn’t drop. What dropped was the midnight rescue habit that had been quietly emptying her Trust Jar with every silent fix.
⚓ Pro Tip: When delegating a project, close the briefing with this confirmation question: “So that we’re completely aligned, what is your understanding of what Done looks like for this outcome?” Hearing the team member describe the finish line in their own words catches misalignment before work begins. It is the single most effective minute you can spend before any handoff.
💡 Consider This Post: If Angela’s story sounds familiar and the friction lives upstream — in the partnership between you and your CEO rather than between you and your team — the Friction to Focus Playbook addresses the partnership dynamic that turns delegation into a recurring battle. It is worth reading before any conversation about swimlanes and decision rights.
The Anchored Conversation Playbook: Structure Over Scripts
Most difficult conversations fail not because the leader lacks courage but because they lack structure.
When the Gargoyle is running the risk assessment, the absence of a clear sequence means the conversation either never happens or collapses under its own emotional weight. The leader improvises, the words come out wrong, and the gargoyle files the result as evidence for why the conversation should never happen again.
What changes with a framework is not the content. It is the container.
The Anchored Conversation Playbook is a four-step sequence built specifically for ADHD-wired operators. It separates observable facts from emotional interpretation, names the downstream impact without assigning blame, inspects the system before evaluating the person, and closes with a mutual commitment rather than a verdict.
The core principle is worth holding onto before you see the full framework: lead with data, not drama.
Observable facts without adjectives. “The invoice batch went out Thursday at 4:00 PM, two days after the Tuesday 9:00 AM deadline” is a fact. “You keep dropping the ball on time-sensitive work” is a verdict. One opens a productive conversation. The other fires the Gargoyle in both of you simultaneously, and now you are managing two RSD responses instead of one operational gap.
The full Playbook, including the complete four-step sequence and ready-to-use scripts for the moments that matter most, lives in the Anchored Leader’s Effective Feedback Scripts & Cheat Sheet.
🎁 Grab This: Download the Anchored Leader’s Effective Feedback Scripts & Cheat Sheet
Verbal templates and exact scripts for accountability conversations, performance corrections, and boundary resets — built for ADHD-wired leaders who need the language to be clear, Kind, and ready before the conversation starts.
Rebuilding Trust: When the Jar Takes a Hit
Nickels happen. Even the most intentional Anchored Operator has moments when the tone is off, the correction lands harder than intended, or a boundary is enforced in a way that feels more reactive than grounded.
The jar took a hit. Now what?
Here is what most leaders do: they freeze. They over-apologize in a way that creates new confusion, or they double down and pretend nothing happened, or they disappear into their work and hope the moment dissolves on its own.
None of those responses redeposit anything. They either remove more nickels or leave the balance exactly where it was.
Here is what actually works: address it. Directly, calmly, and without beating yourself up.
“I want to come back to that conversation yesterday. I think my delivery was off, and I want to be clearer about what I was actually trying to say.”
That sentence, said genuinely and without drama, puts a penny back. Not a nickel. Not a dollar. A penny, and in a jar that just took a hit, a penny matters more than it sounds.
The same principle applies when you are the one who missed a commitment, shifted a priority without notice, or stepped in and took over work that should have stayed with your team member. You do not need a grand gesture. You need a calm, specific acknowledgment and a clear correction.
“I should have let you work through that. Next time, I’ll flag my concern at the check-in instead of jumping in.”
One sentence. One penny.
The Anchored approach to repair is not about erasing what happened. It is about demonstrating that you can see clearly, own what’s yours, and stay regulated while you do it. That behavior — calm ownership without blame or theater — is itself a trust signal. It tells your team: this leader does not disappear when things get hard. They come back, and they say the true thing.
That is worth at least a penny.
⚓ Pro Tip: If you find yourself in a pattern of making the same nickel withdrawal repeatedly — reactive tone in check-ins, taking over work without explanation, shifting priorities without context — the problem is not your character. It is your system. A repeating withdrawal is almost always a signal that something structural needs to change: the check-in cadence, the way priorities are communicated, the clarity of Done criteria. Fix the system and the withdrawals stop happening. That is the Anchored Operator’s first question every time: is this a people problem or a process problem?
What You’ve Built Across This Series
Three articles. One complete arc.
Part 1 established the role. Managing execution is not inferior to casting vision. The COO, Integrator, and Operations Leader is the internal leader of the organization — the person who turns abstract ideas into scalable operational reality. The binary was always a myth. The tasks were always the point.
Part 2 named the mechanism. The Gargoyle on your desk is an overactive threat detector, not a truth-teller. Rejection Sensitive Dysphoria is neurology, not weakness. Naming the pattern — giving your inner critic a face, a name, and a separate identity — is what creates the gap between the alarm and your response. That gap is where leadership lives.
Part 3 built the architecture. Real team trust is built through daily operational pennies: kept commitments, clear criteria, protected time, and honest recognition. Choosing Kind over Nice is how you deliver the hard conversations that develop your people and scale your business. Clear delegation, defined by outcomes rather than methods, is not the absence of care. It is care, expressed operationally.
You are not Bill Lumbergh. You are not the villain of the desk card. You are the Anchored Operator: walking the hard line between care and execution, every day, often without acknowledgment, frequently without a roadmap built for your brain.
The crow told you that you don’t belong in the room. The Gargoyle told you that the conversation would destroy the relationship. Neither of them was right.
You are not broken. You belong in the room. The team you’re building deserves the version of you that knows it.
Next Steps: Anchor Your Operational Authority
🚀 Next Step: If you haven’t taken the COO Stability Compass yet, now is the right moment. It is a free 10-minute assessment that identifies which of the four operational quadrants is costing you the most right now. After three articles of the framework, it gives you a specific, personalized starting point.
⚓ Work Directly with Josh: If you’re ready to eliminate role ambiguity, align with your Visionary CEO, and lead from the middle seat with ADHD-friendly systems, Book Your Clarity Call to explore private 1-on-1 coaching.
Frequently Asked Questions About Difficult Conversations and ADHD Leadership
Ready to Lead Tough Conversations with Anchored Confidence?
Your team doesn’t need a conflict-avoidant fixer or an unapproachable taskmaster. They need an Anchored Leader who creates clarity, builds genuine trust, and holds standards with calm authority.
If you are ready to stop carrying the company on your shoulders and start building the communication architecture that lets your team thrive, let’s connect.
In a complimentary 30-Minute Clarity Call, we will look at where conflict avoidance or delegation breakdowns are creating bottlenecks in your operation, audit your weekly communication rhythms to establish safe containers for direct feedback, and map the step-by-step transition from overwhelmed operator to confident, anchored leader.
No pitch. No pressure. Just an honest look at what’s running in the background and what one structural change would make the biggest difference.
