Product & Management Stage

Chaos – wzrost – struktura czyli o zarządzaniu produktem w trzech aktach

September 17, 2025 3:25 PM

Power Talk

🇵🇱 Polish

Bratysława 1

About

Jak wygląda zarządzanie produktem, gdy firma liczy 10 osób? A jak, gdy zatrudnia 100... albo 1000? Bazując na własnym doświadczeniu, chcę powielić się tym, jak zmienia się rola Product Ownera w różnych typach organizacji oraz z jakimi wyzwaniami mierzy się zespół produktowy w firmie, która dynamicznie się rozwija – przechodząc drogę od startupu, przez fazę scaleupu, aż po dojrzałą korporację.

‍

Talk by

Photo of Piotrek Birski, Chief Product Officer at PayPo

Chief Product Officer at PayPo

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

Explore the 2026 agenda More WaysConf recordings

From the recording

Talk in brief

In this WaysConf presentation, Piotrek Birski, Chief Product Officer at PayPo, outlines how product management paradigms must adapt across three distinct stages of company growth: startups, scaleups, and corporations. He explains that there is no single "correct" product management model; instead, organizations must align their structures, processes, and decision-making styles with their current evolutionary phase. Startups focus on rapid validation and flat structures, scaleups transition from founder intuition to systematic data, and corporations manage complex compliance and risk. Birski warns against over-processing, comparing processes to spices that can ruin a dish if overused, and introduces the musical concept of "groove" as a metaphor for maintaining a healthy, rhythmic, and collaborative product development pace that avoids constant firefighting.

Key takeaways

01
Match Product Management to Growth Stage
Product management practices cannot be copy-pasted from one organizational size to another. Leaders must adapt their style to the company's current phase—startup, scaleup, or corporation—rather than forcing rigid corporate frameworks onto early-stage teams.
Watch from 21:00
02
Transition from Intuition to Systems
While startups rely heavily on founder intuition and HiPPO (Highest Paid Person's Opinion) decision-making, scaleups must transition to systematic data collection. This shift ensures that product decisions are backed by scalable customer insights rather than individual opinions.
Watch from 13:49
03
Balance Processes Like Spices
Processes are essential for scaling, but over-processing can paralyze an organization. Product leaders should implement just enough structure to maintain alignment without suffocating innovation and speed.
Watch from 22:24
04
Empower Product Owners to Challenge C-Level Ideas
In corporate environments, Product Owners often default to executing top-down requests without evaluating their actual business value. POs must use data to push back against low-impact executive ideas and propose higher-value alternatives.
Watch from 19:28
05
Establish a Product Groove
Successful product organizations operate with a "groove," which balances structured rhythm (KPIs and roadmaps) with improvisation (data-driven pivots). This harmony prevents constant firefighting and keeps the team energized and aligned.
Watch from 25:48

Video chapters

0:00Introduction to Product Paradigms
Piotrek Birski introduces the three acts of product management—chaos, growth, and structure—and explains how the role of a Product Owner changes across different company sizes.
2:41Defining Startups, Scaleups, and Corporations
The speaker breaks down the distinct characteristics of startups, scaleups, and corporations based on their business models, funding, speed, and organizational structures.
7:12Product Management Models in Startups
An analysis of three startup product models—Product Co-founder, All-in-One, and Mini Squads—using real-world examples like Notion and Figma.
12:34Navigating the Scaleup Phase
Exploring the challenges of transitioning from a startup to a scaleup, including shifting from founder intuition to systematic data and managing multiple backlogs.
16:09Corporate Product Management and Risk
A look at the complexities of product management in large corporations, where compliance, risk management, and cross-departmental roadmaps often slow down execution.
21:00Adapting Processes and Scaling Wisely
Birski discusses the importance of tailoring product management to the company's lifecycle and warns against the dangers of excessive bureaucracy.
24:09Finding the Product Groove
Using a musical metaphor from AC/DC's Brian Johnson, the speaker explains how establishing a "groove" helps product teams maintain rhythm, harmony, and energy.

Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

The Evolution of Company Stages

Companies generally progress through three main stages if they survive: startup, scaleup, and corporation. In a startup, the focus is entirely on validating the business model through rapid MVP testing and flat structures of just a few people. As a scaleup, the business model is verified, and the goal shifts to market expansion, which introduces specialized departments and safer experimentation. Finally, a corporation focuses on maintaining its market position through highly complex, regulated structures and diversified revenue streams, where conservative innovation dominates.

Watch from 2:41

Startup Product Management Models

Startups typically manage products through one of three models: Product Co-founder, All-in-One, or Mini Squads. In the Co-founder model, exemplified by Notion's early days in Kyoto, founders handle everything, sometimes rewriting the entire codebase themselves to find product-market fit. The All-in-One model, seen in Figma's early history, features highly blended roles where even the CEO directly gathers customer feedback. Mini Squads introduce autonomous, goal-oriented teams with dedicated Product Owners, though this model carries risks of architectural and user experience fragmentation.

Watch from 7:12

The Scaleup Transition and the Danger of HiPPO

Transitioning to a scaleup requires shifting focus from pure speed to sustainable scale, usually when a company grows to between 50 and 150 people. During this phase, organizations must move away from relying on founder intuition or the "HiPPO" (Highest Paid Person's Opinion) and instead build systematic information loops. Without structured roadmaps and clear prioritization, scaleups risk falling into a trap where teams simply execute whatever a director demands without understanding the actual business value of their initiatives.

Watch from 12:34

Corporate Bureaucracy and Top-Down Decisions

In large corporations, product management is heavily constrained by risk management, compliance, and legal departments. Roadmapping becomes a multi-month compromise between various business units, often leaving Product Managers frustrated by endless status updates. A common pitfall is when executive teams spend valuable time micro-managing minor features—such as a process change that yields negligible revenue—instead of allowing Product Owners to leverage data to identify and prioritize high-impact opportunities.

Watch from 16:09

Finding the Right Process Balance

Product leaders must adapt their management style to the company's current reality rather than blindly importing corporate frameworks into startups. Processes should be treated like spices: too few make the organization chaotic and bland, while too many paralyze decision-making. While some corporations successfully maintain agility—such as Allegro's rapid Amazon-style document reviews and weekend deployments—the ultimate goal is to scale consciously without letting bureaucracy stifle the team's core capabilities.

Watch from 21:00

Operating in a Product Groove

Drawing inspiration from AC/DC vocalist Brian Johnson, product teams should strive to find their "groove." In product development, groove represents a healthy operational rhythm that combines structure (KPIs and roadmaps) with the ability to improvise based on incoming data. When a product organization achieves this harmony, it moves away from reactive firefighting and gains the collective energy and alignment needed to seize market opportunities effectively.

Watch from 24:09

Explore WaysConf 2026

View the agenda

Get tickets