Aricò: “Nobody will give you the mandate, you claim it in writing

Every leadership guide covers the parts of the job that have steps. The parts that don't have steps are where you actually get stuck. Prioritizing when the spreadsheet says everyone agrees but nothing moves. Speaking up in a company that never gave you the seat. Telling your own story without sounding like AI slop. This week the sharpest writing was about those gaps. Let me catch you up.

The deep cut

• The hard part of the job has no framework. Cutler, Aricò, and Lowe all write past the steps to the parts that stall.
• Accountability comes first, authority is the leftover. Aricò says take one unowned decision in writing, not present a problem deck upward.
• A recurring argument is your real priority. Cutler tells teams to hunt the tension, not rerun the spreadsheet.

When the spreadsheet lies

You know this room. Everyone agrees the far-off threat matters. Every pre-mortem names it. Every quarter gets a half-hearted stab at it. Nothing happens. John Cutler says the problem was never the framework. In retros he never hears "we scored it a 3 instead of a 4." He hears "we just didn't have the conviction to stop."

So stop reranking things. Look for where the same argument keeps surfacing, where conviction keeps failing, where momentum keeps winning against everyone's better judgment. That is the real decision hiding under the fake one. Cutler's line: "Good prioritization isn't simply choosing the right work. It is recognizing the traps and tensions that prevent your portfolio of bets from panning out."

He offers fill-in-the-blank prompts to surface it. "We keep coming back to ___, but no one has a clear solution." "No one debates that ___ is important, and that is part of the problem." Run those with your team instead of another scoring session.

The seat nobody hands you

Marzia Aricò spent years telling designers to move upstream into decision rights. Then she reread her own work and admitted the advice was "nearly useless." It says where to stand without saying how to get in the building.

Here is what she got right the second time. The mandate is not withheld, it is unclaimed. Authority does not come first. Accountability does. "Authority is the residue." Unowned decisions sit unowned because owning them is unappealing, not because there is a line for them.

Her move is small and concrete. Find one decision you could survive owning. Not the biggest one, the one where you understand the tradeoff well enough to defend a call on a bad Thursday. Then claim it in writing: name the decision, say what good looks like, define what triggers escalation, say what you will do when it goes wrong. Send it to someone senior as a notification, not a proposal. Nobody stops you.

The story only you can tell

Building a company is cheap now. Getting anyone to care that you did is the hard part. Kristen Lowe found that the top reason founders hired a ghostwriter was not that they hated writing. It was "I have no idea what to say."

Her answer is simpler than the vulnerability theater everyone dreads. You do not need to be contrarian or entertaining in every post. You need one answer: why did you start this? People root for humans, not widgets. If the reason was strong enough to rearrange your life, it is strong enough to make others care.

Then get specific. Lowe calls it the Taylor Swift method: scene-based detail that evokes a universal feeling. Not "existing options weren't working for me." More like "I was crying in my car during lunch." Sara Blakely cutting the feet off her pantyhose. That is the register that connects.

Why the intangible always loses

The through-line across all three: the work that stalls is the work you cannot make concrete. Cutler's teams can name the existential threat but cannot picture what action today looks like, so they defer it. Aricò's designers can see exactly what needs fixing upstream but have no language or path to do it. Lowe's founders have a real reason they started but freeze at turning it into words.

The fix in each case is the same shape. Make the abstract thing small and specific enough to act on this week. One tension to hold. One decision to own in writing. One vivid scene to post. The framework was never the blocker. The blocker was that you kept the hard thing vague enough to avoid.

Three questions for your team

• What argument keeps coming back in our planning that we never actually resolve? That is the priority, not the thing you keep reranking.
• Which unowned decision could you claim in writing this week and survive owning on a bad day?
• If a founder or lead on your team had to answer "why did we start this" in one vivid scene, could they? If not, that is the comms work.