Key Takeaways

  • Joe Hudson monitors company health using two exact metrics: how fast leaders initiate a difficult conversation, and how fast they resolve it.
  • Avoiding workplace conflict stalls operational progress, because resolving tension is where teams capture organizational efficiency.
  • Handing answers to underperforming reports backfires by turning managers into operational bottlenecks who own the problem instead of the employee.
  • Pointing out character defects creates defensiveness, whereas stating your personal loss of trust invites mutual problem-solving.
  • Founders can run tough conversations cleanly using Hudson's 3-Step Hard Conversation Framework.

The Hudson's 3-Step Hard Conversation Framework

Step 1: Delegate the Solution

Never solve the problem for the employee. Clearly state the performance gap and require them to present a solution: “Hey, sales are off. I need a plan. Please present it to me tomorrow about how we're going to get sales back on track.”

Step 2: Probe Context with Open-Ended Inquiry

Ask open-ended questions to genuinely understand their operational reality before judging or prescribing fixes: assess whether they are clear on expectations and satisfied with their own output.

Step 3: Express Vulnerability Over Blame

Share your internal state and loss of trust rather than making accusatory statements about their character: “I notice that I'm not trusting that this is going to get done and I'm not having confidence around this, which sucks for me and has to suck for you. How are we going to fix it?”

When This Works (and When It Doesn't)

Hudson's method works well when managing experienced executives, department heads, and direct reports who possess domain skills but are missing targets. In these setups, telling a leader how to fix their department strips away their agency and forces the founder to do their job for them. By delegating the plan back to the executive, you force them to take full ownership while maintaining accountability.

This framework fails when applied to junior hires or early-career individual contributors who lack the baseline knowledge to diagnose their own mistakes. If a junior engineer or entry-level salesperson is failing because they were never properly trained on systems or processes, demanding that they present a turnaround plan tomorrow will only produce panic. In those specific cases, leaders must step in with direct tactical instruction before expecting self-directed problem-solving.

What to Do With This

Pick one direct report whose output has slipped over the past month. Schedule a 20-minute meeting with them tomorrow morning.

Do not enter the room with a bulleted list of operational fixes. Instead, state the concrete performance gap in the first two minutes: "Our enterprise pipeline dropped 30 percent this month." Hand them the problem by asking them to bring a written correction plan by 4:00 PM tomorrow. Follow up by exploring their working context with open questions: "Are you satisfied with where this project sits right now, and what blockers are in your way?" Finish by sharing your internal reaction plainly: “I notice that I'm losing confidence that this will hit our target date, which is frustrating for me and painful for you. What needs to shift so we fix it?”