Leading Without the Title

The job is all responsibility and no authority. Here's what actually worked for me, after a lot of getting it wrong.

TL;DR 👀

• The PM job: all the responsibility, none of the authority. That's the role, not a bug.
• Being "more right" doesn't win rooms. Designing how decisions get made does.
• Two things I stole: Amazon's writing culture, Netflix's "context, not control."
• The real unlock: prep for the people, not just the plan. That's why I built StakeholderSync.
• Say no with a visible rationale. Protect your strategic thinking time, treat it like a metric you track.

Hey everyone ☕

It's been a while. A lot of product work, a lot of leading, not a lot of typing.

My last piece went out at the end of last year. Then I went quiet, and here's the honest reason: I shifted.

This year I've been helping companies put AI to work in the places they still do everything by hand. And with a partner, building the dashboards and internal tools businesses actually run on, the ones that show you your money in real time. Where it's going. Where it's leaking. What just happened, this second.

Alongside that, I kept doing fractional product leadership. Leading without a title, from the outside, as the person who doesn't even work there. The hardest, most interesting version of the job I know.

That's what pulled me back here. Because leading without authority is exactly what I want to talk about today.

So, a meeting I still think about.

Early in my 12 years in product, I walked into an exec review with a roadmap I was proud of. Tight logic. Clean slides. I knew I was right.

I got taken apart in about ten minutes. (Kar'u oti le-gzarim.)

Not because the plan was bad. Because I'd prepared for the plan, and the room was full of people, each with a KPI to protect, a fear, a thing they needed to hear first. I brought an argument. They brought agendas.

That meeting taught me the actual job:

You own the outcome. You command no one. Welcome to product.

---

What I kept getting wrong ✍️

For a while I thought the fix was being more right.

Better data. Tighter decks. A bulletproof case. So I doubled down on logic, and kept losing rooms to people with worse ideas and more confidence.

Then I went the other way. Relationships. Coffees, small talk, reading the politics. That helped more than I expected. But it didn't entirely scale.

Neither was leadership. Both were me trying to win the room inside the room. By then it's already too late.

What finally changed things came from two companies I never worked at (but do enjoy their products!).

---

The two things I stole and never gave back 🎚

The first was Amazon's obsession with writing.

No slides. A six-page memo, read in silence, then discussed. The first time I tried my own version, a written one-pager instead of a deck, something clicked. The conversation was about the idea, not my delivery. I'm not the loudest person in most rooms (I listen more), and the page leveled it for me.

Two more Amazon habits stuck:

• Working backwards. Write the launch announcement before you build the thing. If it reads boring on paper, it'll be boring shipped. I've killed my own features this way, cheaply, before they cost a quarter.
• Disagree and commit. I learned to say, out loud, "I'd have chosen differently, and I'm fully in." It ended so many silent hallway rebellions.

Further reading: Amazon's writing culture, explained (Quartr), plus the book Working Backwards by Colin Bryar and Bill Carr.

The second company was Netflix, and one line: context, not control.

It named something I'd been reaching toward for years. The teams that moved fastest with me were never the ones I managed tightest. They were the ones who understood the why as well as I did. So I started over-sharing: the strategy (transparency at its highest level!!), the trade-offs, the stuff that scared me. Turns out context is the one kind of authority a PM can hand out for free.

🎥 Watch: Reed Hastings on the 3 secrets behind Netflix's culture (TED)

Further reading: Lead with Context, Not Control (Marty Cagan, SVPG), plus the book No Rules Rules by Reed Hastings and Erin Meyer.

I was never going to win a room by being the loudest voice in it. So I stopped trying, and started designing how the decision got made instead.

---

The unlock nobody assigns you 🤝

Here's the part that finally changed things for me. And honestly, it's pretty boring.

I started preparing for the people, not just the plan.

People. People. People!

It's the key.

Before a review, I'd write down, for each person in the room: what they actually care about (their KPI, not mine), the thing they'd push back on, and the one sentence that would open them up in their own language. The VP of Eng didn't want vision. He wanted to know the auth migration wouldn't blow up his team's quarter. So I led with that.

My win rate climbed. Not because I got smarter. Because I stopped surprising people.

The catch: doing this by hand took forever. I had a messy Google doc, then a Notion doc, then a spreadsheet, then a worse spreadsheet. I kept rebuilding it. I worked like this for years. Recently I finally wrapped it into a proper product, for my phone, two minutes before any meeting, so other people could use it too.

That's StakeholderSync.

A profile per stakeholder (their KPIs, their comms style). A pre-meeting brief for the 1:1, the exec update, the steering committee. And the part I lean on most: a heads-up on what they'll push back on, before they do. The briefs come out looking like this:

Brief · Sarah (VP Eng)
Open with: timeline risk on the auth migration.
Cares about: team load, tech debt.
Avoid: scope words ("quick," "small").
Pushback: Q3 dates, given hiring.

I use it every week. It's the closest thing I've found to walking into a room already knowing how it ends.

(It's one of six tiny tools I ended up building out of this kind of pain. The other five cover time, user interviews, prioritization, metrics, and PRDs. They live here if you're curious.)

---

Two more things I learned the hard way 🚫

A couple of lessons that never got their own app, but earned their place:

Saying no is a leadership act, not a personality trait. I used to fear it. Then a manager, not even my direct one, said something that stuck: the managers in that room are judged by how they take in what you bring them, and what they do with it. And voicing a different opinion isn't a problem. It's usually where the gold is hidden. ❗

After that, no got easier. I just learned to make the trade-off visible. Put it in a framework everyone already agreed to, and the fight stops being you-versus-them. It becomes us-versus-the-priorities. The no stops being personal.

Protect your thinking time like it's a number, because it is one. My worst quarters were the busiest ones. Weeks of pure reacting that felt productive and moved nothing. Now I watch the ratio of strategic to reactive time the way I'd watch a burn rate. When deep work drops, the roadmap drifts. Quietly. Until it's a problem.

---

Lessons for Product Managers 🎯

1. Win the room before the room.
The meeting is the last place to start influencing people. Do the work on each person beforehand, one on one. People want to be heard, to feel like they matter. Give them that, and your odds in the room climb.

2. Write it down.
A clear one-pager beats a confident voice. If you're not the loudest in the room, the page is on your side.

3. Over-share the why.
This is my mantra. Always over-share. Make everything you're allowed to share transparent, even the half-formed, in-progress stuff. Let people get ahead of the final decision, they'll help you sharpen it. And if they don't, at least their voices were in the room.

4. Make your no legible.
Defend priorities with a shared framework, not willpower.

5. Budget your judgment.
Strategic time doesn't survive on good intentions. Guard it like a metric.

---

Final Thoughts

For years I waited to be handed leadership. A title, a team, a box on the org chart.

It never arrived the way I pictured. What came instead was a slow realization. I'd been leading the whole time. In the prep, in the writing, in the context I shared, in the rooms I left clearer than I found them.

You don't need anyone's permission for that. You can start on a Tuesday.

Authority gets given. Leadership you just... start.

---

Let's connect 🤝

If you're leading product without the authority to match (most of us are), that's the work I do with teams. Turning fuzzy influence into a system that moves rooms and ships roadmaps.

→ Book a call

→ Connect on LinkedIn

And the six little tools I built along the way (StakeholderSync from today's story, plus five more for time, interviews, prioritization, metrics, and PRDs) are in the PM Toolkit. One-time, yours forever, built for your phone.

P.S. If someone forwarded you this, you can subscribe right here, where UX, business models, and strategy meet. No fluff. Just lessons you can apply tomorrow.