KDR Team • April 10, 2024

Leading with Confidence: Strategies for Addressing Performance and Behavior

Running your own practice or business sure comes with its highs and lows, doesn't it?

One of those challenges we often face is dealing with performance and behavior issues within our teams. But fear not, because at KDR Solutions, we've been there, done that, and we're here to lend you a helping hand.


So, let's dive into some strategies to tackle these tricky situations:


1. Slow Thinking


One of the quickest ways to lose credibility as a leader is to either under-react or overreact. So first, take a breath, slow yourself down, and think about the best approach before diving in. Not every issue requires the same level of response.


We get it; accountability and feedback can sometimes feel like punishment. But let's reframe that mindset. Instead, think of it as an opportunity for growth and improvement—for both you and your team members. If it’s still scary, please borrow our confidence, you’ve got this!


Remember, there's a fine line between coaching and criticism. Focus on the behavior, not the individual's feelings or attitudes. Self-reflection is key here. Have you been crystal clear with your expectations? Does your team member have the necessary skills, training, and resources to succeed?


2. Tailor Your Approach to the Situation


Ever heard of matching the intensity of the approach to the intensity of the problem? It's like using the right tool for the job. When addressing performance or behavior issues, it's essential to gauge the severity of the situation and respond accordingly.


At KDR, we've developed a handy four-part progressive interaction framework we call Tap/Poke/Swing/Slam. It's like a scale to measure the level of directness and seriousness needed in a conversation with an employee. Here's a basic rundown:


  • Tap: A gentle approach, like a light tap on the shoulder. Use this when addressing minor issues or offering constructive feedback.
  • Poke: Slightly firmer than a tap, like giving someone a gentle nudge. Use this when the issue requires a bit more attention but isn't a major concern.
  • Swing: A more direct approach, similar to swinging a bat. Reserve this for more serious issues that need immediate attention and clear resolution.
  • Slam: The most assertive approach, like slamming down the hammer. Use this sparingly for severe issues that require urgent action.


3. The Basic Formula


Regardless of whether you're tapping gently or swinging a hammer, following a structured approach during performance conversations ensures clarity and consistency in your communication. Here's an overview of the steps we use:


  1. Assume mutual agreement on a goal
  2. State the incorrect behavior
  3. Set clear expectations for correct behavior
  4. Seek a commitment to improvement


So, there you have it—a helpful guide to navigating performance and behavior challenges in your small business or healthcare practice. Remember, you're not alone in this journey. If you're craving more insights or personalized support tailored to your unique situation, why not visit our website or reach out to us directly? At KDR Solutions, we're passionate about helping businesses like yours thrive. Let's tackle these challenges together!

By David Bauer January 15, 2026
One of the most common leadership challenges we see across organizations is under-communication. It rarely shows up as silence. It shows up as assumptions.
By David Bauer December 22, 2025
If you’ve ever been in the middle of managing something truly urgent and had a team member approach you with what felt like a small concern, you know the tension I’m talking about. You’re triaging an urgent patient situation. A serious operational decision is unfolding. Your brain is fully in Fast Think mode. And suddenly, someone is standing next to you asking about next week’s schedule, a minor process question, or a frustration they want to talk through right now. So you told the truth, you didn’t have time. Later, you find out they felt dismissed. Or unheard. Or confused about why you didn’t seem willing to help. No one did anything “wrong,” but the disconnect still created friction. This is exactly where shared language matters. In earlier blogs , we talked about why a common language on a team is essential and how understanding Slow Think versus Fast Think helps teams work more effectively together. This tool builds on both of those ideas. The reality leaders don’t always say out loud: Many leaders, especially in healthcare, wear multiple hats at the same time. For example, you’re often switching between three distinct roles: Doctor Entrepreneur Leader The challenge is that those hats don’t always change on command. When you’re deep in your doctor role, managing a retinal concern, an acute red eye, or an unexpected complication, it can be genuinely hard to pivot immediately into your leader role and give a team member the time and attention they deserve. That doesn’t mean their concern isn’t important. It means the timing isn’t aligned. Most frustrations on teams come down to misaligned expectations, not bad intentions. I ntroducing the “Now, Soon, Later” language: “Now, Soon, Later” is a simple prioritization tool that gives teams shared language around timing without minimizing importance. The core question is: “Is this a now, a soon, or a later thing?” That’s it. Simple. Powerful. When leaders consistently use this language, a few important things happen. First, it reminds your team that you are balancing multiple roles and responsibilities in real time. If you can’t address something immediately, it’s not because it doesn’t matter. Second, it reassures them that there is a reason you may need to wrap up a conversation quickly or defer it altogether in that moment. Third, it gives them a framework to think through when and how they bring things to you. Over time, people naturally start to self-prioritize before interrupting. What this sounds like in real life: You might say: “I want to hear this. Is this a now, soon, or later thing?” “I’m in a now situation clinically. Can we put this in the soon bucket and circle back?” “This feels like a later conversation. Let’s find a time where we can both be present.” And yes, sometimes you may need to gently recalibrate expectations after the fact. That could sound like, “I’m not sure we’re on the same page yet about what counts as a now versus a soon. Let’s talk through that.” For this tool to work, follow-through matters. If you put something in the “soon” or “later” bucket and never come back to it, trust erodes quickly. The language only works when your actions reinforce it. Circling back doesn’t have to be elaborate. Even a quick: “Hey, you mentioned this earlier. I wanted to make sure we reconnect on it.” This language isn’t just for deflecting interruptions. It’s also a powerful way to show respect for your team’s workload. For example: “Susie, I have a few projects I’ll need from you, but none of them are a now. Let’s find a time that works with your current priorities to talk through them.” This approach acknowledges their capacity, avoids urgency inflation, and sets the tone for thoughtful planning instead of constant reaction.
By KDR Team October 13, 2025
Discover the power of "Slow-Think/Fast-Think" to transform your communication and build trust.
Image of a dictionary page, defining the word dictionary
By KDR Team September 17, 2025
Communication can feel threatening. But what if your team had the same playbook for conversations? That’s the power of a “common language.”
By KDR Team August 15, 2025
What does emotional recovery look like for leaders?
By KDR Team July 16, 2025
Why Fixing Everyone's Problems Is Holding Your Team Back
By KDR Team June 20, 2025
Great leaders schedule what's important; they don't just hope to find time.
By KDR Team May 13, 2025
Ever feel like you're running circles and getting nowhere fast with your team?
By KDR Team April 22, 2025
Hey friends, I want to talk about two words that get tossed around quite a bit, responsibility and accountability.
By KDR Team March 20, 2025
Why Your Onboarding Process is Broken (and How to Fix It)