Product democracy doesn't work - Blagoja Golubovski (VP Product, Usercentrics)
Episode
42 min
Read time
2 min
Topics
Career Growth, Relationships, Startups
AI-Generated Summary
Key Takeaways
- ✓Decision Input vs Ownership: Separate input collection from decision-making authority. Input should come from customers, data, research, stakeholders, engineering constraints, and sales insights, but one accountable owner makes the final call. When groups providing inputs also control decisions, you create committees that optimize for safety rather than outcomes. If you cannot identify who made the call, no real decision exists.
- ✓Three-Level Decision Framework: Structure decisions at distinct altitudes with different owners and frequencies. Level one covers strategic bets (where to play, how to win) owned by CEO and executive team, made rarely with high consequences. Level two handles product priorities and trade-offs, owned by product leadership, made regularly with reversible costs. Level three manages execution details, owned by teams, made daily with low reversal costs.
- ✓Real Prioritization Requires Trade-offs: Effective prioritization means explicitly stating what you will not do and what gets delayed. Articulate specific trade-offs like choosing growth over retention or delaying feature Z by two quarters. If you cannot articulate the downside of a decision or all options look equally good, you have not made a real decision. Leaders who avoid naming trade-offs protect relationships, not the business.
- ✓Hiring Product Leaders: CEOs claim they want bold leaders who challenge the executive team, but actually screen for low-friction communicators who absorb pressure without creating conflict. The critical missing skill in interviews is assessing whether candidates can adjust communication style across altitudes, from board level to individual contributors. Most hiring teams only evaluate communication within their own sphere, missing this essential capability for success.
- ✓Scaling Judgment Over Roles: Product teams fail because organizations scale roles faster than they scale judgment. Promoting individual contributors to people managers without redefining what good work looks like causes breakdown. Leaders continue solving problems directly and reviewing artifacts instead of enabling teams to make better decisions consistently. Product management is fundamentally a judgment game requiring contextual coaching, not just frameworks and best practices from the internet.
What It Covers
Blagoja Golubovski, VP Product at Usercentrics, challenges the notion that product organizations should operate as democracies. He explains why singular accountability beats consensus-driven decisions, how to structure decision-making at three distinct levels, and what CEOs get wrong when hiring product leaders who can actually drive change rather than just manage stakeholders.
Key Questions Answered
- •Decision Input vs Ownership: Separate input collection from decision-making authority. Input should come from customers, data, research, stakeholders, engineering constraints, and sales insights, but one accountable owner makes the final call. When groups providing inputs also control decisions, you create committees that optimize for safety rather than outcomes. If you cannot identify who made the call, no real decision exists.
- •Three-Level Decision Framework: Structure decisions at distinct altitudes with different owners and frequencies. Level one covers strategic bets (where to play, how to win) owned by CEO and executive team, made rarely with high consequences. Level two handles product priorities and trade-offs, owned by product leadership, made regularly with reversible costs. Level three manages execution details, owned by teams, made daily with low reversal costs.
- •Real Prioritization Requires Trade-offs: Effective prioritization means explicitly stating what you will not do and what gets delayed. Articulate specific trade-offs like choosing growth over retention or delaying feature Z by two quarters. If you cannot articulate the downside of a decision or all options look equally good, you have not made a real decision. Leaders who avoid naming trade-offs protect relationships, not the business.
- •Hiring Product Leaders: CEOs claim they want bold leaders who challenge the executive team, but actually screen for low-friction communicators who absorb pressure without creating conflict. The critical missing skill in interviews is assessing whether candidates can adjust communication style across altitudes, from board level to individual contributors. Most hiring teams only evaluate communication within their own sphere, missing this essential capability for success.
- •Scaling Judgment Over Roles: Product teams fail because organizations scale roles faster than they scale judgment. Promoting individual contributors to people managers without redefining what good work looks like causes breakdown. Leaders continue solving problems directly and reviewing artifacts instead of enabling teams to make better decisions consistently. Product management is fundamentally a judgment game requiring contextual coaching, not just frameworks and best practices from the internet.
Notable Moment
Golubovski argues that when executives keep relitigating execution-level decisions, the real problem is that strategic direction was never clear in the first place. The three decision levels are highly coupled, and micromanagement at the bottom signals confusion at the top. Environment almost always beats individual skills, so even highly skilled product people will fail in organizations without clear decision-making mechanics.
Episode Transcript
If your version of alignment means everybody has to agree, you have a committee. That's my point. I started as an engineer, and I quickly realized that the hardest problems were not technical. They were deciding what to build, why to build it, and what not to build. Real product leadership really is about creating clarity, where to play, how to win, and then making sure that there are explicit trade offs. Democracies are great for value, but they're terrible for decisions. Leadership sets a very clear strategy, where to play and how to win. Product leaders, they translate that into an explicit priorities and trade offs. And then the teams execute with full autonomy inside those constraints. One is, you separate the the input from the decision itself. Input should be really broad, but accountability must be singular. We need to frame decisions at at three different levels. Level one, you have your strategic bets. Level two, this is where you have your product bets. Level three, the execution decisions. If your product leader is not one of the the kind of bold product leaders, how can you as a up and coming product person try and grow into one of those great product leaders? Well, Goya, happy New Year. Welcome to the podcast. How are you doing? Great. Great. Hi, Randy. How are you? Happy New Year to you as well. Thank you very much. Yeah. Always good year. So we're gonna talk about some of the things you've learned in your career as a product leader today, and we're really happy to have you here. But for people who don't already know who you are, can you just give us a a brief introduction? What are you up to these days, and how did you first get into product in the first place? Great. So, Brandy, currently, right now, I'm in a in a transition, a very kind of intentional one. I'm wrapping up my time at Usercentrics. I'm currently there as a VP of product. And at the end of this month, leading a product through a big scale phase, and I've helped more than double our revenue over the last eighteen months or so, passing a 110,000,000 ARR and so on, building a platform operating across a 195 countries, millions of sites and apps, and billions of consent signals collected on a monthly basis. So I'm intentionally back on the market right now. That doesn't happen really very often, especially not publicly like this, which means I'm actually looking for CEOs and and, you know, and, founders that are scaling at the moment that real that need real product leadership with lots of clarity, pace, and execution. How did I get in product? Very simple. I started as an engineer, and I quickly realized that the hardest problems were not technical. They were deciding what to build, why to build it, and what not to build. So that's kinda what pulled me into into product, …
Get the full transcript (6,683 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 39-minute episode.
Get The Product Experience summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from The Product Experience
What I learned from building, and shutting down, a startup — Kirsten Mann (Strategic Advisor)
Sep 9 · 51 min
Eye on AI
#327 Baris Gultekin: The Next Phase of AI - Agents That Understand Your Company's Data
Mar 19
More from The Product Experience
How to position your product for a future nobody can predict - April Dunford (Author of Obviously Awesome)
Sep 2 · 37 min
The Daily (NYT)
An Expert on Conflict Says Your Relationships Are Doomed Without It
Aug 22
More from The Product Experience
We summarize every new episode. Want them in your inbox?
What I learned from building, and shutting down, a startup — Kirsten Mann (Strategic Advisor)
How to position your product for a future nobody can predict - April Dunford (Author of Obviously Awesome)
Four mistakes scaling teams make - Julia Barham (Coach & Mentor)
How to lead a product team through AI adoption - Tiama Hanson-Drury (CPTO, Opus 2)
How OpenAI moves fast and decides what to build — Blaine Billingsley (Member of Technical Design Staff, OpenAI)
Similar Episodes
Related episodes from other podcasts
Eye on AI
Mar 19
#327 Baris Gultekin: The Next Phase of AI - Agents That Understand Your Company's Data
The Daily (NYT)
Aug 22
An Expert on Conflict Says Your Relationships Are Doomed Without It
The Rich Roll Podcast
Jul 27
Michelle Khare Is The Tom Cruise Of YouTube: How Anxiety Became Her Superpower
Odd Lots
Jul 23
Why Apple Is Heading Into a Pivotal Moment
Lenny's Podcast
Jul 19
Netflix CPTO on AI and the future of product and tech roles | Elizabeth Stone
Explore Related Topics
This podcast is featured in Best Product Management Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Product Experience.
Every Monday, we deliver AI summaries of the latest episodes from The Product Experience and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime