Product democracy doesn't work - Blagoja Golubovski (VP Product, Usercentrics)

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.