There’s a version of productivity advice that goes something like this: focus on the positive, visualize the outcome, and don’t let fear talk you out of your goals. It sounds reasonable. It’s also, in practice, a little bit useless.
Not because optimism is wrong, but because vague optimism doesn’t give you anything to work with. It doesn’t tell you what to do when something starts to unravel. It doesn’t help you prepare. And it definitely doesn’t close the gap between intention and follow-through.
What Kyle Austin Young argues in Success is a Numbers Game is something more honest and more actionable: the anxiety most people carry around isn’t the problem. The problem is that it’s unnamed. And unnamed anxiety tends to stay that way — ambient, draining, and completely unaddressed.
His alternative is a tool he calls a success diagram. Write down the goal. Write down everything that has to go right. Then, beneath each of those, write down the potential bad outcomes — the things that could actually derail you. Not to catastrophize. Not to talk yourself out of pursuing the goal. But to give yourself something concrete to push back against.
What struck me most in our conversation was the way Kyle reframes this entire process. He’s not asking you to become a pessimist. He’s asking you to get specific enough about your risks that you can actually do something about them. There’s a meaningful difference between worrying about what could go wrong and naming what could go wrong. One keeps you stuck. The other gives you options.
He uses a marathon training example that I keep coming back to. Say you need to do three things to be ready on race day: eat, sleep, and train according to a coach’s plan. And say you feel reasonably good about each — 70% confident across the board. A lot of people would do a quick mental average and feel optimistic: 70% is pretty solid. But the math doesn’t work that way. You don’t average your odds when outcomes depend on multiple things going right simultaneously. You multiply them. And 70% multiplied three times across gives you about a 34% chance of being ready on race day.
That’s not a reason to give up on the marathon. It’s a reason to get specific about where the 30% lives and what you can actually do about it. That’s probability hacking — not in the life-hack sense of a clever shortcut, but in the very literal sense of changing your odds through intentional action.
Kyle’s own story of landing a product development director role at 21 makes this concrete. He identified three ways the interview could go wrong — looking too young, lacking experience, not fitting with an older team — and addressed each one directly: grew a beard, prepared a vision document so thick it had to be spiral-bound, and read every book the existing team had recently finished. He didn’t change the facts of his situation… he changed the odds within it.
This is where the framework connects with something I’ve been thinking about in the context of TimeCrafting: the value of the deliberate pause. Not slowing down for its own sake, but slowing down enough to get focused — so that when you return to the pace of your actual life, you’re filtering your inputs more productively. Kyle says something similar about the success diagram. You don’t have to sit at a whiteboard for three hours. You just need to get clear enough on the goal that you can recognize the right moment when it shows up. He found a Ben and Jerry’s story for his book by walking through an airport. The preparation made him attuned; the living did the rest.
The deeper idea here is that probability isn’t something you create or destroy. It’s something you rearrange. The odds you want are already embedded in your potential bad outcomes. Make those less likely, and the success you’re after becomes more likely — not as a matter of wishful thinking, but as a matter of structure.
That’s not pessimism. That’s just paying attention.