Urgency is not always a cultural flaw. Sometimes it is a rational adaptation to the environment. When infrastructure is unreliable, ownership is unclear, and institutional memory lives mainly in people, the organisation naturally rewards the person who can act under pressure.
Chapter 1 names this clearly: the systems were fragile, even when they were ambitious. That combination matters. Ambition creates pressure. Fragility limits the tools available to absorb that pressure.
Momentum over optimisation
In such environments, optimisation often comes later. What matters first is momentum. The working solution delivered now can be more valuable than the elegant solution that arrives too late.
This is why many high-performing developers and leaders learn to decide with partial information. They are not being careless. They are being trained by a system where waiting can cost more than moving.
What must be unlearned
The danger is carrying urgency into every room as if every system operates under the same constraints. Mature systems may still have urgency, but they usually expect urgency to travel through process, documentation, and shared decision logic.
The professional shift is learning when urgency is the right response and when urgency is hiding missing architecture.
Operating lesson: Urgency can be adaptive, but it should not become the only way you know how to create value.