A harsh comment in an executive review turned into a week of thinking about trade-offs, who names them, and why addition without subtraction reads as capacity.
A senior stakeholder recently told a room, in so many words, that the product wasn’t keeping pace with the market. Rooms go silent after a comment like that, and this one did. I’ve been thinking about it a lot since, because I think the comment was wrong on the facts and right about something underneath them.
One of my design directors offered the generous reading first, and it’s a genuinely useful one. What she heard was a request for evidence. More qual, more quant, a clearer answer to why the value isn’t landing with the people trialing it. She’s already moving on it, standing up research weighted toward the high-usage cohort where the signal will be strongest. That’s the right response to harsh feedback: treat it as a question you can answer with data, and go answer it.
The shelf
My reflection implicates a better approach from leadership, myself included. Over 20 years I’ve seen this pattern at every company I’ve worked for, and no org I’ve been part of has been fully immune. Teams fall behind on craft when they don’t have the time to be best in class, and the way that happens is straightforward: mandates land on top of committed roadmaps, and nothing comes off. The squads that manage to do both tend to fund the strategic work with nights and weekends (that’s burnout with a roadmap). You can’t demand best-in-class output and fund it with leftover hours.
If something gets added, something else must be dropped, and that swap needs to be stated out loud, in the room, at the moment of the ask.
Here’s the principle I keep circling back to: unless leadership sees a painful trade-off named explicitly, it isn’t ruthless prioritization, it’s addition. And addition reads as capacity. Every time a team absorbs new work without a word, they teach the org that the ask was free. If something gets added, something else must be dropped, and the swap has to be stated in the room, at the moment of the ask, not discovered at the retro.
The good news is that this behavior is teachable, and some of the best people I work with already model it. A PM partner of mine told me his strongest design counterpart pushes back on him exactly this way. She’s no shrinking violet, in his words, said with real admiration, and he credited that pushback with helping him reframe a retention problem in a better way. The pushback made the work better and the relationship stronger. That’s the pattern to scale.
So here’s what I’m asking of my leads, and honestly of anyone reading this who runs a team: the next time a mandate lands, respond with the swap. We can do this, and here’s what comes off. Whether leadership accepts the trade is their call to make, and that’s fine, because making that call visible is the entire job. A roadmap where everything fits is a roadmap where someone is lying, usually to themselves.
The teachable part
When new work gets added without anything coming off, that’s addition, and addition reads as capacity. Teach your leads to answer every mandate with the swap: we can do this, and here’s what drops.