Robust decisions: don’t bet the next step on one right guess

Recently I properly got to know a word for the first time:

robust.

In English it maps to robustness, which is common in engineering, optimization and AI. Put simply, if a system only works when every condition matches expectations, and breaks as soon as reality drifts a little, it’s fragile; conversely, if it keeps performing reasonably well when the environment changes, the information has errors, or the original assumptions don’t fully hold, it’s more “robust.”

Later I found this concept works well in everyday decisions too.

In reality we often don’t have enough information but still have to keep moving. Where it’s easy to get stuck: always feeling you first have to work out what’s really going on before you can decide the next step.

But these two things don’t necessarily have to happen in that order.

You don’t have to guess right first to act

Say a project has been going for a while and the results have stayed poor.

Maybe the direction isn’t wrong and it just needs time; or maybe the direction itself doesn’t hold up, and you just don’t want to stop because you’ve already put in so much.

If you insist on first proving which explanation is true, you may have to keep analyzing for a long time. But the next step doesn’t necessarily have to wait for that answer. You can first give the project a clear, short cycle, and define in advance what this period should test, what evidence would mean it’s worth continuing, and what results, if still absent, mean you should scale back or stop investing.

If the direction turns out to be right, this move didn’t cost much delay; if it’s wrong, you haven’t kept betting on it without limit.

That’s a relatively robust action.

Or take a job opportunity.

Before you actually join, it’s hard to know fully what the team is really like, whether the boss is a good fit, or whether the decision rights written in the JD really exist. At this point there’s no need to prematurely judge it a “perfect opportunity,” nor to decide “there’s definitely a catch here” from a few vague signals.

You can keep interviewing while specifically testing the questions that would really change your decision: why are they hiring for this? Why did the last person leave? What can this role actually decide? Are the resources enough? How is success measured?

The interview itself can also become part of gathering information.

We don’t necessarily have to explain the world clearly before deciding the next step.

Sometimes it’s more useful to first pick an action that doesn’t depend much on guessing right.

There really is a formal method behind this

“Robust action” isn’t a standard term; I just call it that to make it easier to understand. The more formal concepts include Robustness, Robust Optimization, and Robust Decision Making.

The traditional way of deciding easily goes: first predict what’s most likely to happen, then choose the best option under that prediction.

Robust decision-making cares more about another question:

if reality doesn’t go as predicted, does this option still work?

It doesn’t necessarily aim to be the best in one particular scenario; it wants an option that, placed into different possible situations, won’t perform too badly in any of them.

That’s also why I find it especially suited to real life. Much of the time our difficulty isn’t a lack of analytical ability, but that the world simply isn’t giving an answer yet.

Thinking more won’t make the missing information appear on its own.

A fairly robust action usually has four traits

1. It doesn’t depend much on one judgment being right

You can first ask yourself:

if my current explanation is wrong, does this move still make sense?

If a decision only holds up when you’ve guessed right, it’s fragile. Especially when information is scarce, decisions like that deserve a bit more caution.

2. Reversible

Can you pause, go back, adjust, or start smaller?

The less information you have, the more carefully you should treat decisions that are hard to undo once made. Conversely, if a move is cheap and easy to adjust, there’s no need to wait until all the information is in before starting.

3. The loss has a cap

Reversible doesn’t mean free.

A decision may in theory be undone, but time, money and attention may already be spent. So you also need to know: if I guess wrong in the end, what’s the most I’m prepared to pay?

As long as that cost is within what you can bear, the room for action gets much bigger.

4. Afterwards, you know more

This is my favorite one.

A good next step isn’t just one that “doesn’t go badly wrong”; ideally it also reduces later uncertainty.

Build a prototype, find a few real users, go to one more interview, run a small pilot, or do a dry run first. What they have in common is that they don’t require you to think the problem through completely first, but once done, you’ll be a bit closer to reality than you are now.

So if I had to compress it into one sentence, I’d say the ideal robust action is:

reversible, with capped losses, and able to bring new information.

Robust doesn’t mean conservative

This is easy to confuse.

Robust isn’t “the less risk the better,” nor always choosing the safest option. Sometimes never acting is actually a very fragile choice.

A role closes in two weeks, and you never apply because you haven’t fully thought it through; a product gets optimized internally for half a year without ever letting real users touch it. Both look cautious, but the unknowns that really matter never get tested.

What robustness really cares about isn’t doing less, but:

not letting the whole decision rest on an assumption you can’t confirm for now.

So sometimes the more robust move is precisely to act fast, just making the action smaller first, not pushing all your chips in on the first try.

AI systems are actually dealing with the same problem

Put this concept back into AI and it’s easy to understand.

A good AI system can’t only consider how much it can do if the model judges correctly. It also needs to consider the other side:

what happens if it judges wrong?

Say a coding agent isn’t sure whether a database migration is safe. The fragile approach is to run it directly based on its current judgment; a more robust flow might be to inspect the schema first, generate the migration, dry run it, check the diff, verify the impact, and ask a person to confirm at high-risk steps.

This doesn’t suddenly make the model smarter.

It just doesn’t require the model to judge right the first time, while keeping in check the loss one mistake could cause.

It’s the same when a model isn’t confident enough about a question. The best behavior isn’t necessarily to keep trying to generate a complete-sounding answer; it can also ask for more information, clearly express uncertainty, narrow the scope to what it can confirm, or hand the decision back to a person.

There’s a very close concept in AI too, called graceful degradation.

As conditions get worse and worse, a good system doesn’t suddenly fall from “normal” to “out of control”; it gradually shrinks its capabilities: complete automatically when confident, ask the user to confirm when unsure, only offer suggestions when the risk is high, and stop when beyond its abilities.

The logic behind it is actually very plain:

don’t assume you’ll always judge correctly.

I now think “robust” is a very useful decision reminder

It’s easy for us to spend a lot of time explaining the world.

Why exactly is this person like this? Does this project actually have a future? Is this opportunity good or not? Is now the best time?

Some questions are of course worth continuing to study, but very often the evidence just hasn’t appeared yet. More analysis won’t suddenly turn unknown information into known.

At times like this, you can switch to a different question:

if several explanations are all still possible right now, what next step would still be reasonable in all of these cases?

You don’t have to settle things all at once. You can first keep a bit of room, cap the worst loss, get a bit of real feedback, then keep going based on the new information.

That’s probably my favorite understanding of “robust decisions” right now:

when information is short, you don’t necessarily have to guess right first.

First make a choice that still mostly holds up even if you guessed wrong.