The best companies are based on novel ideas, but having too many ideas can sometimes be counterproductive.
In a revealing anecdote, Amazon founder Jeff Bezos recounts a moment early in the company’s history when a senior colleague pulled him aside with a warning that stopped him cold: that Bezos’s own ideation was a threat to Amazon’s survival.
“Put me in front of a whiteboard and I can come up with a hundred ideas in half an hour,” Bezos recalled. Early in Amazon’s history, Jeff Wilke — who would go on to spend a quarter of a century at the company — came to him with a stark observation. At the time, Wilke had probably known Bezos for only a year. “Jeff, you have enough ideas to destroy Amazon,” he told him.
The remark shook Bezos. As a founder, he said, he had always enjoyed the luxury of being able to hire people who could teach him — experienced senior executives like Wilke. “And I would listen to them and they would teach me.”
Wilke’s point was precise: “You have enough ideas per minute, per day, per week to destroy Amazon.” When Bezos pushed back — what do you mean? — Wilke was direct: “You have to release the work at the right rate that the organisation can accept it.”
Wilke came from a manufacturing background, and his mental model was operational. Every idea Bezos released created a backlog — a queue of work in process. Because the ideas kept stacking up faster than the organisation could absorb them, they were adding no value. Worse, they were creating distraction. The fix: release new ideas only at the rate the organisation could actually act on them.
“This sounds so obvious,” Bezos admitted, “but it was not obvious to me at the time.” He called it a profound insight. He began prioritising ideas more carefully, keeping lists, and holding ideas back until the organisation was ready for them. Simultaneously, he started asking a different question: how do you build an organisation that can absorb more ideas? The answer, he said, was having the right senior team with enough executive bandwidth to execute more per unit of time.
The discipline of rationing ideas also sharpened them. Forced to be selective, Bezos found himself stress-testing ideas more rigorously before releasing them. “It forces you to prioritise them better. You end up sharpening the ideas better.” The result was a company that became, in his words, “very good at inventing and doing more than one thing at a time” — operationally effective without sacrificing inventiveness.
The tension Bezos describes — between a founder’s generative instinct and an organisation’s finite capacity — is one of the more underappreciated failure modes of fast-growing companies. The instinct to keep generating is often what made the founder successful in the first place, which is precisely why the habit is so hard to regulate.
Wilke’s framing as a manufacturing expert is telling: he translated a creative problem into an operational one, treating idea flow the way a factory manager treats production scheduling. Too much work-in-process doesn’t just slow things down — it obscures priorities, demoralises teams, and can cause an organisation to lose focus entirely.
This maps directly onto how Bezos has described his broader decision-making philosophy: not all decisions are equal, and treating every passing idea as equally urgent is a fast road to institutional paralysis. Slowing down on consequential choices — while moving fast on reversible ones — requires the same kind of editorial judgment Wilke was urging Bezos to apply to his idea output.
Amazon’s later trajectory suggests Bezos internalised the lesson well. The company’s willingness to pursue genuinely distinct, high-stakes bets — AWS, Prime, Alexa, its own logistics infrastructure — while executing each with sustained focus, reflects an organisation that learned to sequence ambition rather than scatter it. Bezos has said he is now spending 95% of his time on AI since returning to an active role, suggesting the same discipline applies to how he currently allocates his own attention. As he co-founds new ventures in an era of extraordinary technological possibility, the lesson a manufacturing executive taught him three decades ago may be more relevant than ever.