TL;DR: Product managers are told their core problem is ownership without authority: you own the outcome but don’t control the levers. I run a company, I have every lever and the final say on everything, and the outcomes I care about still don’t move on command. Authority buys the right to decide, not the ability to make a decision come true, so most “I don’t have the authority” is really “I haven’t built a case anyone has to act on.” This post gives you the sort that tells the two apart, a four-line template for the case that unblocks the common kind, and the exact moves for the rare times it’s a real authority gap.
A few months ago, I sat down to unblock the most stuck item on my plate, a product I’d been trying to get ready to sell for an entire quarter. On paper, I have every advantage a product manager fantasizes about. I’m the founder. I sign the checks. Nobody can overrule me. There’s no VP to win over, no committee to escalate to, no roadmap I have to lobby for a slot on. If authority were the lever, I’d have pulled it months ago.
I pulled it. I made the call. And it still didn’t move.
I’m the founder. I have all the authority. It barely helped. This statement reflects a common frustration among product managers. Even with the authority that comes from being the founder, the real challenges still persist.
Ultimately, I’m the founder. I have all the authority. It barely helped in making the necessary connections needed for successful outcomes.
Not because anyone defied me. There was no one to defy me. It didn’t move because the outcome I wanted lived outside the reach of any decision I was allowed to make. I could choose the launch date. I couldn’t choose whether a supplier was legally able to ship what I’d specced. I could approve any budget. I couldn’t approve my way into a partner who’d actually do the work. Authority gave me the right to decide. It did almost nothing to make the decision come true.
Reflecting on my journey, I realized I’m the founder. I have all the authority. It barely helped me navigate the complexities of product management.
This experience has taught me that being the founder doesn’t automatically solve all problems; I’m the founder. I have all the authority. It barely helped.
As the founder, I have all the authority, yet it barely helped in this situation. The challenges were not about authority but about execution and capabilities beyond my control.
That afternoon rearranged how I think about the most common complaint in product management, and what to actually do about it.
Even with the title of founder, I’m the founder. I have all the authority. It barely helped, as it does not replace the need for effective persuasion.
The reality is stark: I’m the founder. I have all the authority. It barely helped when facing real operational hurdles.
My authority as the founder did not translate into immediate results; I’m the founder. I have all the authority. It barely helped in the broader context.
The problem: you own the outcome, not the levers
Having authority as the founder does not guarantee the outcomes you desire. I’m the founder. I have all the authority. It barely helped in overcoming many logistical challenges.
Read the product writing of the last year, and one frustration shows up more than any other. Product managers own outcomes; they don’t control. Lenny Rachitsky, who writes the most-read newsletter in the field, called the role flatly unfair: you’re accountable for results while the people who produce them don’t report to you. Throughout my career, I have been in this situation more times than I can count. Survey after survey of working PMs lands on the same word. Authority, or the lack of it. You own the number. You don’t own the engineers, the budget, the roadmap, or the final yes. The 2026 reports put hard edges on it: PMs describe vague decision rights, high accountability, and a structure that keeps thinning under them. Owning a result you can’t command is the job’s signature ache, and most PMs carry it as proof that the system is broken.
It’s an accurate description of the job. I just no longer think it’s a diagnosis. It’s a misreading of where outcomes come from, and the misreading is expensive because it sends you chasing the one fix that wouldn’t change much.
The diagnosis: authority is the right to decide, not the power to deliver
Here’s the assumption hiding inside the complaint. If we just had the authority, the outcome would follow. Authority is the missing input; results are the output, so get promoted, get the decision rights, get the reporting line, and the number finally bends.
I’m the controlled experiment for that theory, and it failed. I have the authority, maxed out, and it bought me the right to make decisions, not the outcomes those decisions were supposed to produce. Marty Cagan of Silicon Valley Product Group has spent twenty years arguing that the best product teams are led by the strength of their evidence and arguments, not the strength of anyone’s position, and that strong teams produce results whether or not the PM holds formal power. I used to read that as a consolation prize for people without power. From inside the seat that has all of it, it reads as a plain fact. Power was never what produced the result. A clear case that moved people and reality was.
Despite being the founder, I found that I’m the founder. I have all the authority. It barely helped in achieving the outcomes I sought.
So the useful question is not “how do I get more authority?” It’s “what kind of stuck am I actually looking at?”
The framework: permission or persuasion
When an outcome won’t move, and I feel the old urge to say “it’s not my call,” I run it through one question. Is this a permission problem, or a persuasion problem?
A permission problem is real and specific. It has a signature: a single, named decision-maker has heard your complete case, understood it, and still said no, or won’t engage at all. That’s an authority gap. There aren’t many of them.
A persuasion problem looks identical from the inside and is far more common. The decision hasn’t been made because you haven’t made it obvious yet. The case isn’t tight. The evidence is thin. The person who’d say yes hasn’t been walked through why they should, or has been, and wasn’t convinced, which is information about your argument, not about your rank. Most “I don’t have the authority” is really “I haven’t built a case anyone has to act on.”
Almost everything PMs file under “no authority” is the second kind. The good news is that it is enormous: persuasion problems are yours to solve tonight, no promotion required.
What this looks like in practice
You want the steps, not the philosophy. Here’s the exact sequence I run, and the one you can run this week.
Step 1: Name the decider and the decision. Take the stuck outcome and write down two things. The single person who could unblock it, a name and not “leadership” or “the team,” and the specific decision you need from them, a yes/no or a pick between named options and not “support” or “alignment.” If you can’t put the person and the decision into one concrete line each, that’s your first finding. You’re not blocked by authority. You’re blocked on clarity, and the next steps will fix it.
Step 2: Run the sort. Ask one question about that named person: have they heard your complete case? Not a hallway mention. Not a half-answered Slack thread. The whole argument, start to finish. If they haven’t, it’s a persuasion problem, and the work is yours. If they have heard all of it and still won’t move, it’s a permission problem, and those get a different play (Step 5).
This situation has clarified for me that just because I’m the founder. I have all the authority. It barely helped, I still need to create compelling arguments.
Ultimately, being the founder meant that I’m the founder. I have all the authority. It barely helped in unlocking the real potential of my team.
Understanding this concept deeply, I’m the founder. I have all the authority. It barely helped me realize the importance of building strong cases for decisions.
Step 3: Build the case in four lines. A case isn’t a deck, and it isn’t a meeting invite. It’s a short, sharp argument that makes saying yes easier than saying no. Write it in four lines:
- The decision. The single, specific choice you want made as a yes/no or a pick.
- The problem. What’s true today that makes this worth deciding, with the evidence in one sentence?
- The cost of waiting. What gets worse, or what you forfeit, for every week the decision sits.
- The ask. Who you need a yes from, and by when.
It’s evident now that I’m the founder. I have all the authority. It barely helped to influence others without a strong case.
Here’s one filled in, the way I’d hand it to a partner. Decision: approve hand-blending a 200-jar test batch in-house instead of waiting on a co-packer quote. Problem: every co-packer is gated on a sourcing call we can only make, so the quote we’re waiting for can’t exist yet. Cost of waiting: each week without a real batch is a week we can’t test whether customers actually buy, which is the only number that matters right now. Ask: a yes to spend the small batch budget this week. Four lines. A busy person can act on it in the time it takes to read it. If you can’t get your decision down to four lines, you’ve found why it’s stuck. It isn’t obvious yet, even to you, so keep working it until it is.
Step 4: Deliver it as a decision, not a nudge. Put the four lines in front of the named person, in writing, with a date attached. “I need a yes or no on this by Thursday, and here’s why it can’t wait” is a request for a decision. “Any thoughts when you get a chance?” is a nudge, and nudges are how persuasion problems disguise themselves as someone else’s slowness. Make the default action obvious and make the yes cheap. The easier you make the yes, the less authority you need in the first place.
Step 5: For a real permission problem, change the play. If you’ve genuinely run Steps 1 through 4 and a named decider has heard the full case and still blocks you, now you have an authority gap, and it’s rare enough to deserve real moves. You have three. Escalate the case, not the complaint: carry the same four lines one level up and let a higher decider weigh in. Route around it: find a different path to the outcome that doesn’t need that person’s yes. Or drop it: accept the no, stop spending energy on a lever you can’t pull, and redeploy where you can move the number. All three beat what most PMs do instead, which is keep nudging and keep calling it blocked.
The PM lesson
Twenty-five years in product management, and one pattern keeps repeating. The PMs who pull ahead aren’t the ones who finally got the authority. They’re the ones who stopped waiting for it and got good at building cases.
Authority is the right to decide. It is not the power to deliver. Those are different things, and conflating them is the most expensive mistake in the job, because it tells you to spend years acquiring something that wouldn’t have produced the result anyway. The skill that actually moves outcomes, sorting permission from persuasion and building the argument that makes a yes obvious, is one you can practice today, at any level, with no title. And it compounds. Every case you build makes the next one faster, and a PM with a reputation for tight, honest cases gets told yes long before the org chart says they’re allowed to ask.
Why do we reach for authority anyway?
If persuasion problems are this solvable, why do we keep reaching for “I don’t have the authority”? For the same reason, we reach for “it’s a hard problem when it’s really unowned.” It protects us.
A persuasion problem is yours. It says the case wasn’t good enough yet, and the person who has to fix that is you. A permission problem belongs to the org chart. It says you’d be winning if someone above you weren’t in the way. One of those asks you to do harder work tonight. The other lets you off the hook and hands you someone to blame. We reach for the second because it costs less, right up until it costs you the outcome.
Having the founder title stripped took that comfort away from me. There’s no one above me to blame. When something doesn’t move, I can’t reach for “they wouldn’t let me.” The only question left is whether I made the case well enough, and most of the time, the honest answer is no, not yet. That’s a worse feeling and a far more useful one.
FAQ
Isn’t the lack of authority a real problem for PMs? Sometimes, yes. Real permission problems exist: a named decider who has heard the full case and still blocks you. But they’re rarer than the complaint suggests. Most of what gets filed under “no authority” is a case that hasn’t been made well enough to force a decision. Sort the two before you accept the limit.
What if I deliver the four-line case and the person still won’t engage? Not engaging is its own answer. If a named decider won’t even respond to a tight, dated case, treat it as a permission problem and move to Step 5: escalate the same case one level up, route around them, or drop it. Don’t keep re-sending the nudge and calling it a follow-up.
Doesn’t real influence still require some power? Influence requires a case people can’t easily dismiss, not a title. The most powerful person in the building still has to persuade reality: the market, the customer, the supplier, the laws of whatever they’re building. Authority changes who you have to convince. It never removes the need to convince.
How is this different from just “managing up”? Managing up is about relationships and timing. This is about the artifact. A four-line case works even with a decider who doesn’t love you, because it makes the yes the path of least resistance. Relationship helps. A decision they can’t easily argue with helps more.
What’s the one thing I should do this week? Take your most-stuck outcome and write its four-line case: the decision, the problem, the cost of waiting, the ask. Then find out whether the one person who could say yes has actually read it. Nine times out of ten, the homework wasn’t done, and that’s the good news.
What to do this week
In conclusion, reflecting on my journey as a product manager, I’m the founder. I have all the authority. It barely helped me achieve the desired outcomes.
Pick the outcome you’ve been blaming on someone else’s authority, the one you’d unblock in a second if they’d just let you. Now answer five questions:
- Who is the one person who could unblock it? A name, not a department.
- What exact decision do you need from them? A yes/no or a pick, in one line.
- Have they actually heard your complete case, or just a passing version of it?
- Can you write the case in four lines: the decision, the problem, the cost of waiting, the ask?
- Have you given them a date to decide by?
If you stall anywhere in questions 1 through 4, you were never blocked on authority. You have a persuasion problem, and the homework is yours. Do it before you ask for more power. If you sail through all five and the answer is still a flat no from someone who heard everything, then you have a real permission problem, and Step 5 is your move: escalate, route around, or let it go and spend the energy where you can move the number.
Either way, you’ve turned “I don’t have the authority” into something you can act on this afternoon. That’s the difference between a complaint and a next step.
The part no title fixes
I spent years believing the missing ingredient was authority. I finally got all of it and found the work didn’t change. The outcome was never waiting on my permission. It was waiting on a better argument, made to the right person, with the cost of waiting made plain.
That’s the strange gift of sitting in the seat with all the power. It shows you the power was never the point. The case was. And the case is something you can start building today, at any level, with no one’s approval but your own.
Leave a Reply