When we launched Digg v4, the old site turned off,
but the new site didn’t turn on.
There was a lot of pressure to get things working,
but no one knew what to do about it. It took almost a month
to get it wholly functioning. It was not a pleasant month,
with many false starts while we tried to dig out of launching
an unfinished, desperate product.
That launch was a foundational early career experience for me.
However, it was not a unique one, as many leaders inject that sort of pressure into their teams
as a routine management technique.
Some examples of the pressure without a plan pattern that I’ve seen:

Lethain, authored by Will Larson, offers a unique perspective on engineering management, leadership, and organizational dynamics. Developers and engineering leaders can explore topics such as team building, career growth, and organizational design, gaining insights into building high-impact engineering organizations. With thoughtful reflections and actionable advice, Lethain serves as a resource for those navigating the complexities of engineering leadership.

Irrational Exuberance

Applying pressure to teams without a clear execution plan creates chaos and leads to failure. The pattern appears in various contexts: failed product launches, poorly planned service migrations, and metrics-driven AI adoption initiatives. Effective leaders transform external pressure into actionable plans through iterative strategy refinement. The anti-pattern often stems from misapplied management by objectives, where executives set targets for low-agency teams without involving them in goal-setting or implementation planning.

Pressure Without a Plan.