Doing less to get more done
If you're involved in every decision, you're the reason things are slow. Stepping back feels like slacking off for about a month, and then it starts to look like the only way the team gets faster.
A product manager who dictates every detail to a skilled team gets worse output. That’s the trap, and it’s counterintuitive enough that people fall into it repeatedly. The pull is to have a hand in everything: the design tweaks, the marketing copy, every line of the spec. Usually the highest-leverage thing you can do is step back and let the people who are better at the task get on with it.
Trust is the mechanism
Think about the last time someone micromanaged you. Then think about the last time someone handed you a problem and left you alone to solve it. Almost everyone does their best work in the second situation. Trusting your team gets you output you couldn’t have produced yourself, and it buys back the resource you have least of, which is your attention.
Two worked examples
Design. A new feature hits the design phase and you have ideas about it.
- Option A: spend hours on detailed wireframes and hand them over with instructions.
- Option B: run a short kickoff covering the problem and the constraints, then let the designers solve it.
Option B wins. You get their expertise and you see solutions you wouldn’t have reached on your own. Get the brief to 80-90% clarity and trust the implementer with the rest.
Development. You want to see progress, so you’re tempted to check in constantly.
- Option A: daily stand-ups, frequent reports, regular pings.
- Option B: clear expectations up front, defined milestones, and trust that the team will tell you when they’re stuck.
Option B again. Developers who aren’t interrupted get into flow and ship faster. The relationship between autonomy and performance isn’t linear either; it accelerates as people feel more invested in the outcome.
Staying available is still part of the job
The skill is balance. You stay available to give direction, clear roadblocks, and keep everyone pointed the same way. One-pagers, light wireframes and kickoff calls do most of that work, because they align people while leaving room for their judgement.
A useful sort is leverage, neutral, overhead. Take each task and ask how much your personal input multiplies the result:
- Leverage. Your input makes a real difference. Do it yourself.
- Neutral. Needs doing, but you add nothing. Delegate it.
- Overhead. Costs more than it returns. Automate it or kill it.
Next time you feel the urge to dive into something outside your wheelhouse, check whether it’s the best use of your time or whether someone else should own it. Often the most useful thing you can do is give the team room to surprise you.