You hired someone great. Three months in, they're not performing the way you expected. You're frustrated. They seem confused. You avoid bringing it up because you don't want to "be a jerk" or "micromanage." Six months later, you're doing their work yourself and wondering if you should fire them.

Most founders think: "If I hired the right person, they'll just figure it out. Good people don't need management." What they don't realize: even exceptional people need clear expectations, regular feedback, and structured performance conversations. Without these, your best hires will underperform or quit.

Poor performance management costs you in three ways: (1) Lost productivity from underperforming employees, (2) your time spent redoing their work or avoiding hard conversations, and (3) wrongful termination claims when you finally fire someone without documentation. The average wrongful termination lawsuit costs $160,000 in legal fees alone, before any settlement.

Here's how to manage performance like a leader, not avoid it like a founder who's scared of conflict.

The problem: You hire someone and tell them "you'll figure it out as we go." Then you're frustrated when they don't read your mind about what success looks like.

The solution: Define success in the first week, not after they've already failed.

Example - First Engineer:

Example - First Salesperson:

Example - First Marketing Hire:

Document this: Write it down and review it with them on Day 1. "Here's how we'll measure success in your first 90 days."

Why it matters legally: Clear written expectations are your defense if you need to terminate for performance. In California and New York (employee-friendly states), judges ask: "Did the employee know what was expected?" If you can't prove it, you're vulnerable to wrongful termination claims.

The founder mistake: You either say nothing for months (avoiding conflict), or you explode with frustration all at once (destroying the relationship).

Situation: Describe when/where specifically

Behavior: What they did (observable, not your interpretation)

Impact: The effect on the work/team/company

Good Feedback Example:

BAD: "You're not a team player and your communication sucks."

GOOD: "In yesterday's standup [Situation], you didn't mention the API issue that's blocking the frontend team [Behavior]. This meant they spent 4 hours working on something they couldn't complete, which delays our launch by a day [Impact]. Going forward, please flag blockers immediately so we can reroute work."

Why this works:

Give feedback within 24 hours of observing the issue. Not in the moment (too emotional), not weeks later (too late to be useful).

Exception: If you're angry, wait until you can be constructive. Feedback delivered in anger destroys trust.

The ratio: Aim for 5:1 positive to constructive feedback.

Bad positive feedback: "Good job!" (too vague)

Good positive feedback: "The way you handled that angry customer call yesterday by staying calm, acknowledging their frustration, then offering three solutions was exactly right. That customer is staying because of how you showed up."

Why it matters: Constructive feedback lands better when people trust you see their strengths, not just their failures.

Common Founder Mistake: "We're too small for formal reviews. We'll do them when we're bigger."

The reality: Without structured check-ins, small issues become big problems, and people quit because they feel unseen.

Frequency: Quarterly for first year, then twice a year once someone's established.

Duration: 30-45 minutes

Structure:

1. What's going well? (5 minutes) Ask them first. Listen for what they're proud of.

2. Where are you struggling? (10 minutes) "What's harder than you expected? Where do you need more support?"

3. Performance against goals (15 minutes) Review the 30/60/90 plan or last quarter's goals. What got done? What didn't? Why?

4. Forward-looking goals (10 minutes) "What are your goals for next quarter? How do they connect to company priorities?"

5. Career development (5 minutes) "What do you want to get better at? How can I support that?"

Document it: Write a 1-page summary. Both of you sign it. Keep it in their file.

Why this matters: In Texas and Florida (at-will employment states), you don't technically need performance documentation to terminate. But if that person files for unemployment or claims discrimination, documentation showing you addressed performance issues progressively is your defense.

If someone is surprised by negative feedback in a performance review, you've failed as a manager. Reviews should confirm ongoing conversations, not reveal new problems.

The framework that protects you legally while giving people a fair chance:

When: First time you notice a performance issue.

Approach: Curious, not accusatory.

Script: "Hey, I noticed [specific behavior]. What's going on? Is there something I should know about?"

Document: Note in their file: Date, issue discussed, what was said, agreed next steps.

Colorado/California/New York note: Document this conversation immediately. Employee-friendly states scrutinize whether you gave clear feedback before termination.

When: Same issue repeats OR new significant issue emerges.

Approach: Direct, with clear expectations.

Script: "We discussed [issue] on [date]. It's happening again. Here's what needs to change: [specific expectations]. Can you commit to this?"

Document: Written follow-up email summarizing conversation, expectations, timeline for improvement.

Action: Set 30-day check-in to assess progress.

When: No improvement after 30 days OR pattern of multiple issues.

Structure:

Document: Formal written PIP, signed by both parties.

Parallel action: Start recruiting their replacement. Don't wait to see if the PIP works.

Why PIPs matter legally:

California: Strong employee protections. PIPs show you gave a fair chance before termination.

New York: Similar to California. Document everything. PIPs demonstrate good-faith effort to help employee succeed.

Colorado: At-will state, but unemployment claims are common. PIPs help defend against claims.

Texas/Florida: More employer-friendly, but PIPs still demonstrate fairness and reduce litigation risk.

When: 30-day PIP period ends without sufficient improvement.

Process:

State-specific final paycheck requirements:

The scenario: Your top performer is toxic. They're rude to teammates, undermine decisions, create drama. But they ship more than anyone else.

The founder's dilemma: "Can I afford to lose their output?"

The brutal truth: You cannot afford to keep them.

The math:

Net result: You're worse off keeping them.

If someone is exceptional at their job but violates your values, they must go. No exceptions.

Common violations:

Step 1: Name the behavior specifically

Bad: "You're difficult to work with."

Good: "In last week's product meeting, you interrupted Sarah three times and said her idea was 'stupid' in front of the team. This violates our value of respectful collaboration."

Step 2: Set clear expectations

"Going forward, if you disagree with an idea, you say 'I see it differently' and explain your reasoning respectfully. Interrupting and dismissing teammates stops immediately."

Step 3: Make consequences clear

"This is non-negotiable. If this behavior continues, you will not continue here regardless of your technical output."

Step 4: Follow through

If behavior doesn't change, terminate. Quickly.

Why this matters: Keeping a brilliant asshole tells your team that values don't actually matter, only output. You lose credibility as a leader and lose your best people.

Performance management isn't about being "nice" or "tough." It's about being clear.

Clear expectations prevent most performance problems. When people know what success looks like, they can deliver it.

Regular feedback makes hard conversations easier. Small course corrections prevent big blowups.

Documentation protects everyone. You're protected legally. Employees know where they stand. No surprises.

Toxic high performers destroy teams. Choose culture over individual output every time.

Three actions this week:

Performance management is the skill that separates founders who build great teams from founders who wonder why everyone keeps quitting. It's learnable. Start practicing.

This content is provided for informational purposes only and does not constitute legal advice; for guidance on your specific situation, please consult with an employment attorney licensed in your state.