The Owner-Not-Renter Veto
How a PM says 'not yet' to an executive chain that desperately wants to scale.
- Difficulty
- Advanced
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 90%
The hardest moment in product management is when the entire executive chain is excited, the launch was promised six months ago, and the line PM knows the product isn't ready to scale. Duggal's framework for that moment rests on the Nubank value 'we think and act like owners, not renters': as the owner of the product, delivering bad news early is not permitted dissent — it is your job. He pairs the ownership mindset with clarity, data, and a self-interest argument that makes the veto rational, not merely brave.
Origin
Derived from Nubank's five cultural values, particularly 'we think and act like owners not renters — we do what is right even when no one is telling us to do it.' Duggal frames the veto as the practical expression of that value under executive pressure.
Core principles
- 01As an owner, telling the leader the bad news early is expected of you — not tolerated in you.
- 02Don't tell me what I want to hear, even when there's a promotion at stake.
- 03Senior leaders who have killed or pivoted products respect clarity of thought and a high bar.
- 04Strong-willed executives with strong opinions are a feature of the job description, not an obstacle.
- 05The mess is yours either way — everyone will forget they told you to scale it.
- 06You practise this at mid-level; it does not arrive with a C-suite title.
How to run it
- 1
Claim ownership of the product, explicitly
Whether you're the PM, lead engineer, lead designer, or anyone on the team, adopt the owner-not-renter posture: this outcome is yours. That reframing is what makes early bad news an obligation rather than an act of insubordination.
Watch out The renter's move is to comply, scale it, and let the mess become someone else's. It won't be.
- 2
Deliver the bad news early, even against your own short-term interest
Say it early: I don't think it's going to work and here's why / it's not working and here's why / we should kill it and here's why. Do this even when it is inconvenient and even when a promotion is at stake — Duggal names those dynamics explicitly because they get very real very quickly.
Pro tip Pivoting early is cheaper and easier than pivoting late. Bite the bullet early and it works out better in the end.
Watch out Timing is the whole game. The same message delivered after scaling is an excuse; delivered before, it's leadership.
- 3
Bring clarity and data, not just conviction
Come with a clear read and the evidence behind it — for Nubank, that's typically the Sean Ellis score, the cohort analysis, and churn. The score brings science to what would otherwise be an art-based judgment call, which is what makes the veto arguable rather than emotional.
- 4
Argue the other side before you argue yours
Understand and articulate the tradeoffs and the case against your own position. Senior executives are strong-willed and bring strong opinions — that's the job description. Demonstrating you've genuinely engaged with their case is what earns the hearing.
Pro tip Someone who is not simply going with the flow and brings a high bar earns a lot of respect from leaders who have killed products themselves.
- 5
Name the self-interest: the mess will be yours regardless
The final, unsentimental argument. If you scale a product that isn't working, the mess is a thing you will still own — and everyone will forget that they told you to scale it, and will still blame you. So you might as well bite the bullet earlier and pivot when it's easier to do.
In the wild
Nubank's entire executive team was excited about the bill-payments assistant; the product review six months prior had concluded it would be amazing; the whole management chain had been counting on it. The pressure on the line PM to scale was, in Duggal's words, immense — and the PM's job in that moment was to say no, because the Sean Ellis score was borderline and the value was not yet found.
→ The team held the line, mined the bullseye cohort instead, rebuilt the product around cross-rail consolidation, and only then scaled — reaching over 10 million monthly actives rather than scaling a broken product to a big mess.
Nubank launched its rewards credit card on 4 July 2021 with executive appetite to scale, but the product only resonated with the fee-waiver cohort. Rather than scaling into that ambiguity, the team stayed in the lab for two to two and a half years figuring out where the product-market fit actually was and iterating there.
→ Aggressive scaling only started once the fit was understood — a two-year veto held against organisational impatience, avoiding a large credit-product mess.
Common mistakes
Telling the leader what they want to hear
The renter's compliance. It preserves the promotion for one review cycle and hands you a much larger, much more public failure later.
Pushing back with conviction but no data
Senior executives bring strong opinions by design. An opinion-versus-opinion fight is one a line PM loses. Bring the score, the cohorts, and the churn.
Assuming pushback capability arrives with the title
If you think you're practising for a senior job, you have to practise now — the ability to hold a hard line with clarity does not appear miraculously when you get a C-suite title.
Believing the blame will be shared
Everyone who pushed to scale will forget they pushed. The mess and the blame land on the product's owner regardless of who ordered the scaling.
Is it for you?
Best for
Line product managers and product leaders under organisational pressure to scale a product that has not yet demonstrated product-market fit.
Not ideal for
Reversible, low-stakes decisions where the cost of being wrong is trivial, or organisations without a culture that rewards candour — where the veto carries real career risk.
From the transcript
“you're an owner of that product as the product manager or the lead engineer or the lead designer or in fact anyone on the team…”
“it's expected of you as an owner to tell me the bad news and tell it to me early even when it's convenient even when…”
“and there's a lot of respect for someone who has a real Clarity of thought”
“we're all going to forget that we told you to scale the thing we're all going to still blame you at the end of the…”
“the job of the product manager in many instances is to say no”
From the episode
Be fundamentally different, not incrementally better
Jag Duggal (Nubank, Facebook, Google, Quantcast)