Hurry up⚠️ Only 50 tickets left in this pool WaysAwardsSubmit your WaysAwards project — enter the 2026 nominations

Career development

The Irreplaceable Designer: why and how to work with early-stage startups

September 5, 2023 12:45 PM

Long Lecture

🇵🇱 Polish

Bratysława 1

About

Going 0 -> 1 with founder, obsessed with his idea, is one of the Product Designer's most rewarding and challenging experiences. In a world without dozens of POs, corporate rat race, where your voice is heard — your skills thrive at the speed of light.The story about how to work with early-stage and why it is crucial for Product Designers' growth. What's essential for young and new founders, and how you can answer their needs and be a sparing partner from day one. And lastly, how one day you're working on branding to talk with developers about data sets the next day.

Talk by

Photo of Damian Redecki, Head of Design at tonik

Head of Design at tonik

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

A Polish-language reflection on becoming an irreplaceable startup designer by taking ownership beyond interface production. Early projects reveal how unclear domains, late stakeholder reversals, and technically ambitious ideas can defeat polished design. The response is not heroics: understand the business and implementation, test feasibility with developers, expose uncertainty, and make decisions traceable. Designers become valuable when they help the whole product move through ambiguity, while still building teams and systems that do not depend on one individual.

Key takeaways

01
Investigate domain complexity before promising
A problem that sounds simple can contain scientific, operational, or regulatory depth that changes the product approach.
Watch from 2:14
02
Surface late reversals and their consequences
When a stakeholder restores an old decision, document the reason, impact, and tradeoff instead of silently absorbing the change.
Watch from 7:28
03
Own the outcome beyond visual design
Design is one tool inside product work, so valuable designers follow feasibility, business logic, and delivery rather than stopping at approval.
Watch from 12:56
04
Prototype feasibility with engineering partners
A concentrated build can demonstrate whether an ambitious interaction is possible and reveal constraints earlier than polished mockups.
Watch from 18:42
05
Avoid making irreplaceability a bottleneck
Personal value should come from enabling better decisions and shared capability, not from keeping essential knowledge private.
Watch from 37:31

Video chapters

2:14A simple brief hides domain complexity
The first project shows how quickly confidence collapses when a team underestimates an unfamiliar field.
7:28When a finished brand decision reverses
A late request to restore the previous logo exposes missing alignment and the cost of weak ownership.
12:56Product ownership beyond the design files
The designer’s responsibility expands from artifacts to the complete area of product value and risk.
18:42A feasibility sprint with developers
Design and engineering collaborate intensively to prove that a technically difficult concept can work.
24:39The danger of the designer’s magic screen
Crisp visuals can conceal unresolved behavior, data, and implementation questions.
31:28Learning from work that ends after approval
A short engagement reveals why accepted design is not equivalent to a durable product outcome.
37:31Irreplaceable impact without personal dependency
The conclusion reframes value as shared understanding and momentum rather than individual control.

Read edited transcript highlights

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

Domain confidence should be earned early

A team of capable designers and researchers can still misjudge a problem that belongs to an unfamiliar scientific or operational domain. Early discovery should identify specialist knowledge, regulatory constraints, and the real-world process behind the interface. Admitting uncertainty protects the project more effectively than performing confidence until the first technical review.

Watch from 2:14

Late changes reveal an alignment problem

When a client reverses a central brand decision at the end, the immediate artifact is only part of the issue. The team should understand what changed, who now carries the decision, and how the reversal affects consistency, schedule, and trust. Making consequences explicit creates a chance to fix the decision process rather than arguing only about taste.

Watch from 7:28

Ownership follows the product past the mockup

Designers add more value when they stay engaged with business assumptions, data, implementation, and customer outcomes. This does not mean controlling every discipline. It means noticing dependencies, bringing the right people into the decision, and refusing to treat an approved screen as complete while the mechanism behind it remains uncertain.

Watch from 12:56

Engineering collaboration can replace speculative polish

A short joint build may answer feasibility questions that weeks of isolated interface refinement cannot. Designers can define the intended behavior while developers expose platform and performance constraints. The resulting prototype is not only a demonstration; it is shared evidence that improves scope, estimates, and the credibility of the proposed experience.

Watch from 18:42

The strongest designer leaves reusable capability

Being essential can feel like security, but a product that depends on one person’s memory is fragile. A valuable designer makes context visible, teaches collaborators, improves the system for decisions, and helps the team operate after the engagement. Their influence remains in the product and the organization without making absence a crisis.

Watch from 37:31

Explore WaysConf 2026

View the agenda

Get tickets