The Product Leader's Approach to Culture Building

What separates good products from great ones when it comes to culture building isn’t the perks or the mission statements. It’s whether the culture actually enables people to do their best work.

Imagine beautiful culture decks that nobody follows and organisations with no formal culture documentation where everyone understand exactly how things work. The former has culture marketing. The latter has actual culture.

Traditional approaches to culture building often fall short because they treat culture as something you define rather than something you cultivate. Let me share what I think actually works.

Building Early Foundations

What to Prioritise

Early-stage culture building isn’t about values posters. It’s about establishing patterns that will compound over time.

Decision-making norms come first. How do decisions get made here? Who’s involved? How much consensus is required? These patterns form quickly and become surprisingly sticky. Get them right early.

Communication defaults matter enormously. Are we a meeting culture or an async culture? Do we default to transparency or need-to-know? These choices shape everything.

Conflict handling needs explicit attention. When people disagree (and they will), what happens? Is disagreement welcomed or suppressed? How do tensions get resolved? Healthy conflict patterns are learned, not innate.

Learning orientation sets the tone for growth. Is failure punished or treated as education? Are experiments encouraged or seen as risky? Culture either enables learning or inhibits it.

Quick Wins

Some tactics deliver immediate cultural impact:

Hire for culture contribution, not just fit. Don’t just ask “will this person work within our culture?” Ask “what will this person add to our culture?” Diversity of perspective strengthens teams.

Model the behaviour you want. Culture flows from leadership. If you want transparency, be transparent. If you want people to take risks, take risks visibly. Actions speak louder than values statements.

Create rituals that reinforce what matters. Weekly demos that celebrate learning, not just shipping. Retrospectives that surface problems openly. Team moments that build connection.

“Culture is what people do when nobody’s watching. It’s the thousand small decisions that compound over time.”

The Startup Reality

Resource Constraints

Building culture with limited resources requires prioritisation. You cannot invest in everything simultaneously.

The good news: culture building doesn’t require budget. The best cultural investments are time and attention, not money.

The challenge: time and attention are your scarcest resources. Every hour spent on culture is an hour not spent on product or customers.

My approach: integrate culture building into existing activities rather than treating it as separate. Retrospectives can reinforce learning culture. One-on-ones can model communication norms. Code reviews can demonstrate how you handle quality and feedback.

When culture building becomes embedded in how you work rather than separate from it, the resource constraint largely disappears.

Speed vs. Quality Tradeoffs

Culture shapes how your team navigates speed/quality tensions.

Some cultures optimise for speed at the expense of sustainability. “Move fast and break things” sounds exciting until the things you break include your team’s wellbeing.

Other cultures optimise for quality at the expense of velocity. Perfectionism masquerading as craft leads to endless polishing and nothing shipped.

Healthy cultures find dynamic balance. They understand that speed and quality aren’t always in tension—sometimes moving fast produces better outcomes. They make trade-off decisions explicitly rather than defaulting to one extreme.

Build cultural norms that support this balance:

Distinguish between reversible and irreversible decisions
Create permission to ship imperfect work when learning is the goal
Celebrate both velocity and craftsmanship, depending on context
Surface trade-offs for explicit discussion rather than implicit assumption

Scaling for Growth

When to Formalise

The cultural practices that work for ten people break down at fifty. The question is recognising when to add structure.

Warning signs that formalisation is needed:

New hires take a long time to “get” how things work
Different teams interpret the same cultural norms in incompatible ways
You personally have to resolve cultural conflicts because there’s no other mechanism
People cite the same cultural values to justify opposite behaviours

When these appear, it’s time to document. Not to create bureaucracy, but to scale shared understanding.

Start with principles that inform decisions. These shouldn’t be rules but guidelines that help people make consistent choices. “We prioritise user impact over technical elegance” tells people how to navigate trade-offs without prescribing specific outcomes.

Add examples that illustrate what principles look like in practice. Abstract values are interpreted differently by different people. Concrete examples create shared reference points.

Team Evolution

Culture evolves as teams grow, and that’s healthy. The goal isn’t to preserve early culture forever—it’s to evolve culture intentionally.

Some cultural elements should persist:

Core values that define who you are
Decision-making principles that keep things coherent
Behavioural norms that enable collaboration

Other elements should evolve:

Communication practices that need to scale
Rituals that made sense for smaller teams
Informal processes that need formalisation

The trap is trying to preserve everything. Founders often romanticise early culture, treating any evolution as dilution. But culture that cannot evolve becomes a constraint rather than an enabler.

Guide evolution intentionally. Name what you want to preserve and what you’re willing to change. Make cultural evolution a conscious choice rather than accidental drift.

Key Takeaways

Culture is what people do when nobody’s watching, not what’s written on posters—focus on patterns, not declarations
Early foundations matter most: decision-making norms, communication defaults, conflict handling, and learning orientation
Integrate culture building into existing activities rather than treating it as separate work requiring separate resources
Formalise when informal practices break down at scale, starting with principles that guide decisions
Allow culture to evolve intentionally; trying to preserve early-stage culture forever becomes a constraint

Next Steps for This Week

Here’s a practical exercise: ask three people on your team to describe your culture in their own words.

Don’t give them prompts. Don’t reference values documents. Just ask: “How would you describe how we work here?”

Compare the answers. Where they align, that’s your actual culture. Where they diverge, that’s where cultural work is needed.

The gap between espoused culture and actual culture is where improvement opportunities hide. This week, find that gap.

Have questions or thoughts? Get in touch - I’d love to hear from you!