If Every Decision Needs You, You're the Problem... sorry.
Robby Amaro ·
Better decisions need clear ownership and a way to learn, not perfect certainty.
People talk about decision making in business like the job is to get more sure before you move. I don't think that's the real problem.
From what I've seen, many of the decisions that stall a team aren't missing another spreadsheet. They're missing a line: who owns the call, and how you'll learn after you make it.
The question I care about is simpler. Where's the line?
If everything runs upstream, everything slows down
When the work depends on someone else, I want this clear early. If every call has to run by one person, everything slows down. So where's the line? What can someone decide on their own, and what needs to come back?
That question isn't about grabbing control. It's about making the boundary explicit so people can actually move.
Without a line, two things happen. Either nothing moves because everyone is waiting for permission. Or everything funnels through one person, and that person becomes the reason work piles up. Both can feel careful. Neither helps you make better decisions.
The line can be simple. You own these calls. Ideas from other people are welcome if they're useful. They're just not the decision. For the bigger ones, or the ones you can't easily undo, those come back. The point is saying it out loud instead of leaving people to guess.
It's easy for a team to treat "let's stay aligned" like a decision process. Alignment is useful. It's not a substitute for an owner.
You won't know everything until you're in the seat
This shows up around new roles. It's easy to want the job carved perfectly before anyone starts.
The truth is, you might not know what the role really needs until someone is in it. I wouldn't spend forever trying to perfect it first.
That isn't permission to be sloppy about who you bring in, or what the job is for. It's a reminder that some of the information you want only shows up after the decision is live. You can sketch the role. You can be clear about the outcome. You probably cannot whiteboard your way into a finished version of a job nobody has done yet.
Waiting for a complete picture can look responsible. Sometimes it's just delay dressed up as diligence.
The same drag shows up in other places too. If you need every detail locked before you start, you'll spend a long time designing a version of the work that won't survive contact with the real thing.
Match your caution to what you can undo
I want to be clear about this, because "just move faster" is easy to misunderstand.
I'm not saying you should swing at everything. Some calls are hard to reverse, and the downside is real. Those deserve more care, more math, and more time. When the upside and the risk both get big, you should feel that weight.
When I can test something and roll it back, I want to learn sooner. If a test looks strong, I can keep going. If I stop it, I can undo it. The faster you find out your problems, the better.
When I'm about to put rules in place that other people will follow, I slow down. I want to double-check the math first. I also want danger lines: alerts that ping me before a call has to be made. That isn't hovering. It's a tripwire, so the person doing the work can move, and I still hear about it early if something starts heading the wrong way.
I think about new products in a similar way. Once the core offer is clear, sitting around validating every other detail doesn't help much. Crack the offer first. Then you can swing. Until that part is clear, nothing else matters as much.
Here's how I think about it:
- If you can undo it, decide with what you know and watch what happens.
- If you can't, or the downside is big, check the math and give it more care.
- Either way, set a point where you'll look again, so you aren't surprised.
A test with limits and a way to watch it is not the same thing as being reckless. Unreviewed testing can be. Reckless is making a hard-to-reverse call without looking. Reckless is also pretending that if you wait long enough, certainty will show up and do the job for you.
Show how you got there, and let people push
Even with a clear owner, you will miss things.
I want people to question how we make decisions. If I don't explain how I got to a conclusion, nobody can catch the miss. I want that kind of pushback.
That only works if the owner stays the owner. Pushback is useful. It doesn't mean every decision goes back to a group vote. You want people close enough to the work to say they think you're off, and one person who still makes the call.
I've also learned to say what needs to happen, not what people want to hear. The comfortable answer feels kind in the moment. I think it makes for a slower, messier decision later.
If you hide your reasoning, people can't help you catch the miss. If you share it and still own the call, you get the benefit of other eyes without turning the company into a committee.
I don't think better decision making is a hunt for more certainty. Draw the line on who decides. Match your caution to how reversible the call is. Check the math on the things that will stick. Then show your reasoning and let people challenge it.
You still won't get every decision right. You'll just find the problems sooner, with fewer things stuck waiting for a perfect answer that was never coming.
That's where I'm at.