Pressure is not itself a force in the Seven Forces framework. It is a condition acting on the room — a deadline, a competitor, a regulator, a board cycle. But pressure has a predictable effect on which forces activate inside the room, and a predictable failure pattern when it is left to compound.
The force pressure amplifies is the Driver. The pattern unchecked pressure produces is the Speed Trap.
The Driver under pressure
The Driver is the force that wants the decision moment. It values pace, conviction, and forward motion. When the Driver is active, agendas close out, choices get made, and people leave the room with something to do. When the Driver is too quiet, options multiply, deliberation feels productive, and the meeting ends with another meeting on the calendar.
External pressure activates the Driver. That part is healthy. Pressure-aware rooms move faster than pressure-blind rooms, and most of the time that speed is appropriate.
The trouble starts when the Driver is the only force the room can hear.
The Speed Trap
I have watched this play out enough times to call it by name. A senior leader brings a half-formed answer into the room, presents it as a working hypothesis, and runs the meeting as though hypothesis-testing is what is happening. The questions are framed for confirmation. Alternatives surface, briefly, only to be redirected back to the answer the leader brought in. The deadline is described as immovable; the case against rushing is described as caution; caution is described as cowardice. Forty minutes later, the decision is made and signed for. To everyone in the room it looked like a brisk, confident meeting.
That is the Speed Trap: too much Driver, not enough Constraint Holder. The decision arrives quickly. Whether it arrives well is a different question, and one that surfaces a quarter or two later, when the assumptions the room never tested catch up with the team that has to deliver against them.
Speed Trap rooms produce three predictable shifts:
The option set collapses. Pressured rooms drop down to one or two alternatives quickly. The Boundary Breaker’s question — is there a reframe we have not considered? — feels like delay and gets dismissed.
The incumbent wins. The default supplier, the existing strategy, the current team. Switching costs feel larger when the room cannot afford to pay them.
Time horizons compress. Rooms in a hurry decide for the next quarter at the price of the next three years. This is rational at the margin and ruinous in aggregate.
None of those shifts is automatically wrong. The option set genuinely is sometimes binary; sometimes the incumbent really is the right answer. The problem is when the room undergoes the shifts without noticing, and then later cannot reconstruct why its decision came out the way it did.
Real pressure versus manufactured urgency
The diagnostic is uncomfortable but useful. Ask: what specifically is the cost of waiting another day, another week, another month?
For real pressure, the answer is concrete. A regulatory cut-off. A funding round closing. A counter-party who has stated, on the record, that they will move on if no answer is given by Friday.
For manufactured urgency, the answer becomes vague. We need to move. We will lose momentum. These are not costs. They are framings designed to short-circuit deliberation.
A skilled chair or Decision Architect can tell the difference. Real pressure can be named, sourced, and worked with. Manufactured urgency does not survive being asked to specify what exactly is at stake.
The fix is a missing force
The Speed Trap does not get solved by slowing down the meeting. It gets solved by activating the Constraint Holder — the force that surfaces the boundaries the room is being asked to ignore: budgets, regulators, capacity, commitments already made to other people. Sounds like what does this conflict with that we have already promised? In a Driver-heavy room, that question feels like an obstruction. That is precisely why the room needs to hear it.
A second activation that helps is the Systems Thinker. If we do this here, what else moves? That question buys the room a few minutes of context the pressure was about to skip past. Most Speed Trap disasters were not impossible to anticipate. They were skipped over because the room could not afford the time to look sideways.
How pressure interacts with the rest of the framework
Pressure stresses every force in the room, not just the Driver. It compresses the time available for the Challenger to test premises. It makes the Integrator’s bridging work feel slow. It pushes the Boundary Breaker’s reframing questions out of bounds. The Decision Architect’s job under pressure is not to lift the pressure but to make sure the full set of forces still gets a turn in whatever time the room has.
Often that takes one well-placed sentence. Before we close — what are we about to break elsewhere if we do this? A pause. The Systems Thinker activates. The decision improves.
The book Decision Shapers develops the practice of working with pressure rather than being run by it. The Speed Trap is one of the five recurring failure patterns. The pattern at the other end of the spectrum — the room that never decides at all — is the one described in the alignment illusion.