Most Management Decisions Are Bets

It is easy to believe that becoming a manager means becoming someone who knows what to do.

After all, your past managers probably seemed like they always knew what to do.

This misconception is one of the biggest sources of frustration for new managers. Suddenly, you’re faced with decisions where no amount of thinking seems to give you the confidence you expected to have.

• Should you reorganize the team now or wait?
• Should you give someone more autonomy, or more structure?
• Should you push for speed, even if the work will be rougher?

You look for the right answer. You think harder. You ask someone more experienced. Sometimes you hire someone who seems more likely to know.

Or you try everything at once: more meetings, a new process, more pressure, more autonomy, a reorganization. If something improves, you still do not know why.

The underlying assumption is that the answer will reveal itself if you think long enough or find the right person.

Usually, it will not.

Most management decisions are not hard because the choice itself is complicated. They are hard because you lack direct, validated, on-the-ground information about what is actually happening.

Is the team slow because the process is broken, or because the work is unclear? Is someone underperforming because they need feedback, context, support, or a different role? Is morale low because of workload, lack of trust, or a decision you have not explained?

You cannot reason your way to that answer from a distance. You need a way to learn.

That is why management is less about finding the right decision and more about making tactical bets.

Make the smallest tactical bet first

A tactical bet is a small, targeted action with a belief behind it. It should improve the situation if you are right—and give you clearer information either way.

Go with something like “We think unclear task assignments are causing rework. For the next two weeks, we’ll add a ten-minute quick check ups at the start of each project and see whether rework drops.”

Not: “Let’s change everything and see what works.”

The goal is not merely to improve the situation. It is to learn whether your explanation of the situation is true.

If rework drops, you have evidence that check ups matter. If it does not, you have ruled something out—and can make a better next bet.

This is why small, frequent bets beat one big decision.

A big decision is expensive, difficult to reverse, and often produces muddy results. When you reorganize a team, hire a new leader, and introduce a new planning process at the same time, you cannot tell which change helped—or hurt.

Small bets keep the cost of being wrong low and the signal clear. They move you closer to the real problem.

Management Has No Tutorial

Management rarely has textbook solutions. The problems are messy, the information is incomplete, and what works for one team may fail for another.

Without better ways to think through these problems, it’s easy to reach for shortcuts—often at the expense of the teams we’re supposed to help.

That’s why I feel compelled to write this newsletter. Over eight years of building software, I’ve gone from writing code to leading technical teams as a CTO, working directly with clients and helping deliver millions of pesos worth of projects. I’ve made plenty of mistakes along the way, changed my mind, and learned that the lessons that matter most rarely come from a textbook.

I want to share those lessons here, not as prescriptions, but as field notes from someone doing the work too.

If you’ve found this article valuable thus far, subscribing costs nothing, but it’s a small way you can help me keep this going. It only takes a few seconds, but it helps these ideas reach more managers—and, hopefully, helps build better teams along the way.

And you’ll get the next one straight to your inbox.

If you choose to subscribe, thank you. It genuinely means a lot that you’re willing to support this little project and give me a reason to keep writing.

Now, let's get back into our discussion.

What makes a useful bet

Before acting, make four things explicit.

1. The belief

What do you think is causing the problem?

“We think people are missing deadlines because priorities change after work begins.”

2. The smallest test

What is the smallest viable version of this idea that puts it in contact with reality?

Do not jump to a conclusion before validating whether your belief is true. Make a version small enough to run now, but real enough that people’s behavior can teach you something.

For example:

• Instead of purchasing new software, prototype the workflow in Excel. You will learn what the software actually needs to do before paying for it.
• Instead of changing a policy across the organization, test it with one person first.
• Instead of building a new component, run it in a simulator first.

The effort should match the insight you expect to gain. A bet should be cheap enough to discard, but real enough to expose what your plan is missing.

3. The signal

What would you expect to see if you are right?

“Fewer mid-cycle changes and fewer deadline slips.”

4. The review point

When will you decide what you learned?

“We’ll look at the next two cycles, then keep, change, or stop the practice.”

At the review point, choose what happens next:

• Discard the bet. Because it was cheap, you saved yourself from going further down the wrong rabbit hole.
• Level up to a bigger bet. You can now commit more time, money, or people—with new insight to back the decision.

Without a signal and a review point, a bet becomes a hope. You keep investing without knowing whether you are getting closer to the real problem.

Small bets compound into better judgment

One tactical bet gives you one insight. Make them frequently, and those insights begin to compound.

Because each bet is small and cheap, you can learn faster than someone waiting for enough confidence to make one big decision. You start noticing patterns, constraints, and second-order effects that other people gloss over.

Then, when a boss or client asks what you think, you are no longer offering an opinion from a distance. You can say: “We tried this. Here is what happened. Here is what it tells us. And here is the next bet I would make.”

Your value increases because you bring information that did not exist before. Your confidence increases too—not because you suddenly know everything, but because your convictions are increasingly backed by evidence from the ground.

This week, choose one problem you have been trying to solve in your head.

Ask: What is the smallest tactical bet we can make that will give us a clearer view of the real problem?

Then make it, set a review point, and let what happens change your next move.

Hit reply with the decision you are circling. I’d love to read it—and, if I can, help you design a small bet.