This post expands on something I tweeted recently: "A startup's real strength isn't speed of decision-making — it's the alignment between strategy and implementation."

What "speed is everything" really means

"Speed of decision-making is everything in a startup" is a common belief, but it's dangerous if interpreted as "everything else being equal, faster is always better."

A startup's reason for existing is to build the future of an industry. The reason that future hasn't arrived yet is always the same: multiple trade-offs exist that prevent it from happening.

For example, seamless, low-cost money transfers between banks and individuals are blocked by regulation, legacy central systems, and behavioral inertia — multiple overlapping trade-offs. (I'm personally reminded of this every time I pay ¥800 in bank transfer fees for payroll or expense reimbursements.)

When I think about decision-making at its best, it's not "make the highest-quality decision as fast as possible, repeat." It's: "commit enough resources to understand the trade-offs deeply, hold multiple possibilities in tension, and develop a position that resolves them."

Eliminating uncertainty while correcting direction — that's what actually leads to speed. A decision that's good for users but bad for the business, or good for the business but bad for the industry, isn't fast. It's just wrong in a different direction.

Where decision speed actually comes from

Speed emerges when strategy and implementation are aligned. Conversely, when they're misaligned, speed disappears.

A correct strategy that isn't executed because of organizational or technical debt: failure. A brilliant team that executes an incorrect strategy perfectly: also failure.

A startup's unique advantage is that it starts from nothing — making it much easier to align strategy and implementation from the beginning. A large company with existing products, organization, and infrastructure faces enormous pain when pivoting. Misalignment accumulates and becomes harder to correct. Speed erodes.

Only when strategy and implementation are aligned can a team move toward resolving trade-offs correctly. The right direction is the only real form of speed.

The hardest problem: divergence becomes debt

Even when strategy and implementation start aligned, the business accrues knowledge that demands adjustments — to strategy, to implementation, or both simultaneously.

What was "the best strategy and product" with three people may be misaligned with the same company at fifty. Every release creates the potential for divergence. When divergence happens, it becomes debt.

How teams handle this debt determines how far they can go:

  • Bottom path: Ignore it. Correct direction becomes harder. Speed disappears.
  • Middle path: Address debt as it accrues. Maintain speed through ongoing effort.
  • Top path: Anticipate divergence. Build prevention into early design decisions.

The clearer you can see the future, the better the decisions you can make today. The pressure to keep strategy and implementation aligned is constant. For startups, the moment they stop applying that pressure, they lose their reason to exist.

Conclusion: why product management exists

Product management, as a function, is essentially about maintaining the alignment between strategy and implementation over time.

When the target market shifts, strategy shifts. When strategy shifts, the product needs to change. Since products are built by people, you either convince people or change the people.

Adjusting the supply chain to match the strategy, using that supply chain to build the product, feeding the results back into the strategy — the person who manages the middle of that loop is who I'd call a product manager.