The best way to manage strong individual contributors (ICs) is simple: hire self-sufficient people, set SMART goals, and let them execute. When they fail, ask why—if they take ownership and adjust, they’re coachable. If they blame external factors and offer no solutions, cut them loose. Micromanagement is unnecessary; accountability and autonomy drive results. This cycle—hire, set goals, observe, refine, and replace when needed—builds a high-performance team with minimal managerial effort.

---

Managing individual contributors (ICs) doesn’t have to be complicated. In fact, over-managing can be counterproductive. The best approach is simple: hire the right people, set clear expectations, and let them figure things out. When they succeed, great. When they fail, they learn. Once it’s clear they lack the skill, drive, or capacity, let them go. Rinse and repeat.

Here’s my method for developing high-performing ICs while keeping my own workload light:

1. Hiring the Right People

I prioritize hiring professionals who possess the skills and motivation to take ownership of their work. I look for candidates who demonstrate independence, problem-solving ability, and a proactive mindset. If someone needs constant direction or reassurance, they are not the right fit for my team. Strong ICs thrive in an environment where expectations are clear, but the execution is up to them.

Some key indicators of a strong IC during the hiring process:

• They ask questions that show they are thinking about impact, not just tasks.
• They have a track record of self-directed problem-solving in previous roles.
• They can explain their own process—how they approach challenges and adapt.

If I have to micromanage someone, I see that as a failure in the hiring process. My goal is to bring in people who can operate with autonomy from day one.

2. Setting SMART Goals

Once the right person is in place, I ensure they define their goals using the SMART framework—Specific, Measurable, Achievable, Relevant, and Time-bound. Vague ambitions like “grow sales” or “improve marketing” don’t cut it. Instead, I break things down into clear, incremental objectives.

For example, instead of saying: “Increase revenue this quarter.”

I push for: “Bring in 15 qualified leads per week, with at least 5 progressing to proposals.”

By setting smaller, trackable goals, I make sure ICs always have a concrete target in sight. This also allows for weekly accountability, reducing the risk of someone drifting off course for months before issues are caught.

3. Allowing Implementation Freedom

Once goals are in place, my job is simple: step back and let them execute. I don’t micromanage their process or tell them exactly what to do. If they ask for advice, I provide guidance, but I never dictate every step.

This autonomy forces them to:

• Think critically about their own approach.
• Experiment and refine their strategies.
• Learn from real-world execution, rather than waiting for instructions.

The best ICs appreciate this freedom, while those who struggle with ambiguity quickly show their limits.

4. Encouraging Reflection on Challenges

Failure isn’t something to avoid—it’s part of the process. When an IC doesn’t meet a goal, I don’t rush to “fix” it for them. Instead, I ask two simple questions:

• What happened?
• What will you do differently next time?

This forces them to analyze their own performance and adjust accordingly. A strong IC will acknowledge mistakes, identify learning points, and refine their approach. A weak IC will blame external factors or look for excuses.

5. Observing Their Response to Failure

I don’t just listen to what they say—I watch how they respond. When someone takes ownership of a failure and proactively makes adjustments, I know they have long-term potential. If they constantly shift blame, deflect, or wait for someone else to solve the problem, that’s a red flag.

A few common responses I’ve seen:

• Strong IC: “I realized I wasn’t prioritizing high-value leads. Next week, I’ll focus on decision-makers first.”
• Weak IC: “The leads just weren’t good this week.”

The former is coachable. The latter? Probably not worth the effort.

But there’s an even bigger red flag: blaming an external factor they have no control over and making no attempt to fix it.

• Instant-Termination IC: “Marketing isn’t generating enough leads, so I can’t hit my target.”

This is an excuse disguised as logic. The right response would be: “Marketing leads have been slow, so I’m testing outbound strategies and leveraging my network to generate my own pipeline.” If someone blames another department, the economy, or a bad tool—but offers no solution—they’re not problem-solvers, they’re passengers. Unless they take ownership of finding workarounds, they won’t last on my team.

6. Cut Your Losses Quickly

At a certain point, failure isn’t learning—it’s a sign they’re not the right fit. If someone consistently underperforms, can’t adjust, or lacks the drive to improve, let them go.

Dragging out the process benefits no one:

• The IC feels stuck in a job they’re not succeeding in.
• The team suffers from underperformance.
• You waste time managing someone who will never be self-sufficient.

A simple test: If you’re spending more time managing an IC than they’re spending producing results, they’re not an IC—they’re a liability. Cut your losses and move on.

7. Rinse and Repeat for Continuous Improvement

This isn’t a one-time process—it’s an ongoing loop. I keep running this cycle, and over time:

• The best ICs refine their approach and become self-sufficient.
• The weaker ones make it clear they aren’t cut out for the role.

By keeping only strong performers, the overall team gets sharper, faster, and more efficient.

Why This Works

This method isn’t about being hands-off—it’s about focusing only on what actually matters:

• Hiring the right people.
• Setting clear, measurable goals.
• Providing room for them to execute.
• Holding them accountable through self-reflection.
• Letting go of those who can’t meet the standard.

Everything else? Unnecessary noise.

By following this approach, I’ve built teams that are self-sufficient, results-driven, and require minimal oversight. And as a bonus? It saves me a ton of time and energy. If you’re tired of babysitting employees and want a simpler way to build strong ICs, try this out. You might be surprised at how effective it is.

…