Ten orders a minute. That was what the checkout platform could take on the day it was handed to me at a global clothing brand in Tokyo, and the number I was asked to reach was more than a thousand. A hundred times more traffic, on a platform that did not exist yet, with a team that did not exist yet either. I have been in a few rooms where a number like that gets said out loud. There is always a pause afterwards, and the pause is doing something useful.
In that pause, somebody is deciding the goal is unreasonable. Sometimes that somebody is me, for the first few seconds. I have learned not to argue with the reaction and not to obey it either, because it is usually carrying information that the confident half of the room does not have.
- Most of what makes an ambitious goal look impossible is not the goal. It is the set of habits standing between you and it, wearing the costume of a constraint.
- The doubt in the room is not pessimism. After enough years it is pattern recognition, and it usually knows something before it can explain itself.
- A hundredfold jump turned out to be mostly one bottleneck. Finding out which one took four questions.
Two Kinds of Obstacle
The first thing I do with a goal like that is stop treating the obstacles as one pile. They are always two piles, and almost nobody separates them out loud.
The second pile is nearly always bigger than the first, and it is the one that makes an ambitious number sound absurd. When people say a goal cannot be done, they are usually describing the second pile with the certainty appropriate to the first. That is not dishonesty. It is just what happens when you have been inside a system long enough that its conventions have stopped looking like choices.
Sorting the two takes an afternoon and changes the conversation completely, because the honest version of the sentence is rarely this is impossible. It is this is impossible if we keep working the way we work. Those are very different problems, and only one of them is about ambition.
The Doubt Is Data
My own first reaction to a hard target is not enthusiasm. It is a short, unglamorous this may not work. For a long time I treated that as something to suppress and perform past. I think that was wrong, and I think a lot of leadership advice quietly teaches people to make the same mistake.
The reaction is not usually pessimism. After eighteen years of watching things break, it is pattern recognition. Something in the shape of the problem resembles something that failed before, and the recognition arrives well before the explanation does. Treating it as weakness throws away the earliest signal you will get.
So I let it speak, and then I make it specific, because that is the whole move. "This is hard" is a mood. "This is hard because of X" is a work item. One of those you carry around; the other you can put on a board, assign, and test. I write it down as a named risk, and more often than not the risk tells me exactly where to start.
Dreams and fears sit in the same mind. They always have, and I have stopped expecting that to change. The line I actually live by is that the fear does not get a vote. It gets a hearing, because it is often the most experienced voice in the room. It does not get to decide.
Four Lenses, One Bottleneck
Back to the hundredfold jump. It stayed unreasonable exactly as long as it stayed a single number. The way out was to stop looking at it as one problem and look at it through four questions instead, each of which asks something different about the same system.
Run those four over a system and something useful happens: the impossible number stops being one number. It becomes a set of parts with different ceilings, and the parts are not equally guilty. In our case most of the jump turned out to be sitting in a single bottleneck. Not a hundred problems. One serious one, plus a lot of work that was smaller than it looked once the serious one was named.
That is the pattern I have seen often enough to expect it now. Big multiples usually resolve into one dominant constraint and a tail of ordinary engineering. The intimidating part is not the size of the number. It is that before you take it apart, you have no idea which part is carrying it.
One Piece at a Time
Japan gave me the working method, and it has outlasted every framework I have picked up since. Build one piece properly. Then look hard at what building it taught you, before you touch the next one. Then take the next piece.
It sounds slow. It is not, and the reason is that the second step is where the value hides. A piece built properly does not just deliver its own function; it tells you something true about the system that no design document knew. Skip the looking, and you carry your original assumptions all the way to the end, where they are expensive. That is a puzzle solved one piece at a time, and a hundredfold jump is a puzzle, not a leap.
Keep the Sceptics Close
The instinct with an ambitious goal is to gather the believers and route around everyone else. I do the opposite now, and it is the single most practical thing in this essay.
The people who think it will not work usually know exactly where it breaks. That is the most useful thing anyone can tell you at the start.
A sceptic who has been close to the system for years is not producing an opinion. They are producing a fault list they have never been asked for. Push past the verdict and ask the follow up question, where specifically does this fall over, and what comes back is a map of the real obstacles, drawn by somebody who has walked the ground. The believers cannot give you that map. Their confidence is genuinely useful later, when the work gets long, but at the start it is the doubters who know the terrain.
It also does something to the room. Somebody who expected to be dismissed and instead gets asked for detail tends to stop being an obstacle and start being an early warning system. I have never once regretted spending the first week with the people who said it could not be done.
The Number, Afterwards
The platform got there. Ten orders a minute became more than a thousand at peak, on a checkout system built from nothing with a team assembled across three countries. What I remember is not the launch. It is how ordinary the path looked in hindsight: sort the obstacles honestly, make the doubt specific, take the number apart with four questions, build one piece properly, and keep the people who said no close enough to hear.
None of that is daring. Which is the actual point. A disruption mindset is not a personality, and it is not appetite for risk. It is a refusal to accept that the way things currently work is the same thing as the way things must work. Everything else is method.
If there is no possibility, create one. If there is no paradigm, invent one. If there is no tool, build one.
I have carried that line for most of my career, and I want to be precise about what it is not. It is not a slogan about self belief. It is a working instruction for the moment you find yourself blocked by something that turns out, on inspection, to be a habit. Somebody built the tool you are missing. Somebody decided the paradigm you are working inside. They were not more entitled to do that than you are. Read it beside what it means to take your work as craft and the two say the same thing from opposite ends.