Speed was a constraint, not a strategy
At small companies I shipped in weeks. Research on Monday, prototype Wednesday, in front of users inside the sprint. That velocity was real and I miss it. What I noticed later is how little of it was new. Almost every pattern I reached for was borrowed from a product that had already proven it, because there was no budget to find out whether something better would hold, and a wrong guess cost a quarter we did not have. Speed was not a strategy.
The research matches this. When Xu and Ruef tested people actively starting businesses against non-entrepreneurs, the founders came back measurably more risk-averse, not less. The risk-loving founder is mostly a story told after the exit.
What the enterprise budget actually buys
Working for large organizations, everything takes longer. A change that would have taken three weeks at a startup takes two quarters, and most of that time passes in rooms I am not in. But the work that makes it through is larger than anything I touched before, and the organization pays to know it is right before it moves. Discovery a startup would have skipped. Access to users I would not have been given. Planning cycles that come back around, so an idea that does not fit this year is not dead, it is next year's line item.
That is the part people have backwards. Enterprises are assumed to lack appetite for new ideas. In my experience they have more of it, because appetite tracks capacity. When a call is wrong at that scale it is wrong across the entire organization, so nobody guesses. The same balance sheet that raises the stakes also funds the work that removes the guess. Startups do not take risks because they love them. They take them because certainty costs money.
Size the decision to the room
This changed how I scope internal systems. When an ambitious redesign of a review workflow or a data collection tool stalls, the constraint is rarely imagination.
So shrink the decision instead of the idea. Build iteratively and be correct in stages. Each stage is small enough for the person in front of you to approve, and complete enough to verify before the next one starts. Ambition survives that way.
Read the capacity before deciding how ambitious to be. A small company will move on your idea quickly and keep it small. A large one will answer slowly and hand you more surface area than you asked for. Neither is a culture problem. Both are a math problem, and the math sits on the balance sheet.
The question was never how much risk an organization wants. It is how much it can absorb, and whether what you brought is sized to the person who has to approve it.