Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Management & Leadership

Micromanaging and competence

Too many leaders are so afraid of micromanaging that they become completely hands off.

But giving instruction to build competence is not micromanagement. Neither is providing feedback. Avoiding instruction or feedback because you fear the micromanager label does a disservice to your employee.

If I’m driving with Frank and I say he should check his mirror more often, that sounds like obvious micromanagement. But what if I told you that Frank is my nephew and has only been driving for a week?

The context is important. Now I’m not micromanaging, I’m giving instruction to build competence. If I’m still telling him to check his mirrors 2 years later when he’s an otherwise competent driver, that’s micromanaging.

Competence is context dependent. I might trust Frank to drive me to the airport. But that doesn’t mean I’d trust him to fly the plane when we got there.

You can also provide detailed instruction without micromanaging if you have more information than the other person, as long as you also explain why you’re doing it. It’s It would be obnoxious to tell a friend who regularly drives a certain route that they should take the freeway instead of surface streets. But it’s informational to tell them they should take the freeway because this morning you saw a lot of new construction closing the surface streets.

Providing feedback can be seen as micromanagement unless you provide context. Without context, this sort of feedback is criticism. It’s criticism to tell Frank he drives too fast and changes lanes too often. But it’s feedback if you tell him that because he drives this way, all his friends are afraid to ride with him. If you didn’t provide this feedback, he might never know why his friends always seem to be busy when he offers to drive somewhere.

When building competence, providing new information, or giving feedback, you cannot be hands off.

Recently Written

Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.
What branding can teach about culture
Jan 8: Culture is your company’s point of view in action—a framework guiding behavior, even in the unknown. You can’t copy it; it must reflect your unique perspective.
Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.

Older...

What I'm Reading