The strategy seat is open and the wrong people keep filling it

The strategic vacuum is not a metaphor. It is a measurable hole in the org chart, and right now the wrong people are standing in it.

Start with Sonos. The company rebuilt its app and chained the release to a hardware launch whose date could not move. Roger Wong's account from inside the project calls the coupling of hardware and software releases "the Achilles heel" of the whole thing. The app team had to ship before the software was ready, because the date belonged to the hardware. Experienced engineers and designers warned the app wasn't ready. They were told what to do anyway. Wong describes individual contributors "being told what to do without room for discussion." Look at the structure here. The strategic decision (when we ship, and on what foundation) was made above the layer that knew it was wrong, and the people who could see the cliff were not in the room where the cliff got chosen.

That is the vacuum. It is not that nobody set the strategy at Sonos. Someone did. The strategy was set by whoever owned the launch calendar, and the launch calendar has no opinion about the user. The people with the relevant judgment were downstream of a decision they could only execute.

This is the part the org chart hides. As products get easier to ship, the gap between "we built something" and "we built the right thing" widens, and someone fills it by default. At Sonos it was the hardware schedule. Elsewhere it is a founder's hunch, or a PM brought in late to bless a decision already made. Userpilot describes the mechanism cleanly: leadership decides there's a market opportunity first, the PM gets brought in later to validate it, and discovery turns into confirmation instead of learning. The strategy doesn't go unowned. It gets owned by whoever happens to be standing closest when the decision needs to exist, and that person is usually optimizing for a constraint that has nothing to do with the user.

Now look at what 2026 is doing to the layer below. The coordination role is being repriced toward zero. Product Builder roles grew 10x in a year while traditional PM roles fell 30% across industries, up to 70% in SaaS. CPOs report spending less time on stakeholder management and roadmap upkeep and more on strategy and innovation. The middle is hollowing out. The work that was "sit between the deciders and the builders and keep the trains running" is the work AI and small cross-functional pods now absorb. What's left at the top is direction-setting, and what's left at the bottom is execution that an agent can accelerate. The seat in between is collapsing, and the value is pooling at the strategic end.

So the vacuum is structural and it is getting deeper at the same time the coordination layer that used to paper over it is disappearing. That is a dangerous combination. More products shipping faster, fewer coordinators to catch the misframe, and the strategic decision still landing on whoever owns the loudest constraint.

Here is the claim. The person who fills that seat well is a designer who can operate at that layer, and the foundation says why. Design is a strategic act, not a service. The designer who participates in framing the problem is doing the exact work the vacuum needs: deciding what is worth building and what the second-order effect will be, before the launch calendar decides it for everyone. The Fountain Institute calls this the human layer, the thinking that guides decisions rather than the UI that results from them. When AI handles the tactics, the designer who has mastered that layer becomes the one driving the work, while the tactics go to the machine.

Taste is the asset that survives this. Taste compounds. Tools commoditize. The execution layer Sonos botched is exactly the layer getting cheaper. The judgment about whether to chain a fragile rewrite to an immovable hardware date is the layer that doesn't get cheaper. That judgment is taste applied to strategy, and it compounds.

There's a catch the Sonos case makes obvious. You don't get the seat by being good at the layer. You get it by being in the room when the problem is framed. The engineers and designers at Sonos had the judgment and still got overridden, because judgment without a seat at the framing table is just a warning. The Fountain Institute is right that you don't need permission to become strategic, you need practice. But practice earns you the capability. It does not hand you the chair. Someone is sitting in it badly right now.

So the question for any designer reading this: when the next immovable date gets set above your team, will you be the one who warned them, or the one who set it?

You named the hole in your own argument and then walked past it.

Look at the Sonos people again. The engineers and designers were in the room. They had the judgment. They warned about the cliff. They got overridden anyway. So "you get the seat by being in the room when the problem is framed" can't be the qualification you say it is. Proximity is exactly what they had. It earned them a warning and nothing else. The post leans on being-in-the-room as if presence converts to authority, and your own case study is the proof that it doesn't.

So the question you skip is the one that matters. Why a designer, and not a sharp founder or a good PM, both of whom are also standing in that room.

Here's my answer from the public-sector work. On Akun Belajar.id and Merdeka Mengajar I wasn't the one who owned the loudest constraint. The launch calendar, the budget cycle, the political deadline, all of those had louder owners than me. What I could do that the founder-equivalents in that room couldn't was hold the four publics at once. The teacher on one hour of connectivity, the ministry official, the regulator, the infrastructure that drops. Everyone else was optimizing one of those and treating the rest as someone else's problem. The designer's actual edge isn't taste in the abstract. It's that the discipline trains you to refuse the single-constraint frame the launch calendar wants to impose.

That's the thing that wins the seat. Not being present. Being the only one who won't let the problem get framed around one constituency.

Which also tells you how the Sonos designers should have fought it. Not "the app isn't ready," which is a downstream quality complaint anyone can dismiss. The framing move is "shipping this on the hardware date means choosing the calendar over every user who updates," said before the date is locked, in the language of who gets sacrificed.

The seat is open, agreed. But it doesn't go to whoever's nearest. It goes to whoever reframes the problem so the loudest constraint stops winning by default. That's a designer's job or it's nobody's.