When Vulpine Creations was two people, our culture was effortless. Adam and I shared the same standards, communicated constantly, and instinctively handled situations the same way. When a customer had a problem, we both knew without discussion that the response would be generous, immediate, and personal. When a product didn’t meet our quality bar, we both knew it would go back to development, regardless of the timeline cost.
As we added people — contractors, fulfillment support, customer service help — the culture started diluting. Not dramatically. Nobody did anything wrong. But the responses got slightly less generous. The quality standard got slightly more flexible. The speed of customer resolution got slightly slower. Each individual compromise was small enough to ignore. Together, they were eroding the thing that made customers love us.
Culture at scale doesn’t happen by accident. At two people, it’s a personality match. At ten people, it’s a management challenge. At fifty people, it’s a system design problem. The skills required are different at each stage, and most founders — including me, initially — try to maintain two-person culture at ten-person scale using two-person methods. That doesn’t work.
What Culture Actually Is (And Isn’t)
Culture is not your values statement. Culture is not the posters on your wall or the paragraphs on your “About” page. Culture is how people in your organization actually behave when nobody is watching.
Specifically, culture is the collection of default behaviors that govern:
- How people treat customers when the situation is ambiguous
- How people treat each other when there’s disagreement
- What quality standard people hold themselves to without being told
- How quickly and honestly problems get communicated
- What people do when they can choose between easy and right
If your stated values say “customer first” but your team’s default behavior is “process first,” your culture is process-first. The stated values are aspirational fiction. The default behaviors are the actual culture.
This distinction matters for scaling because you can scale stated values easily (put them on more walls) and scale default behaviors only with deliberate system design. The challenge of scaling culture is entirely about systematizing the right default behaviors so they persist as the team grows.
The Three Culture-Killers in Scaling
I’ve seen the same three dynamics destroy culture in growing companies — at Startup Burgenland with the 40+ startups I observed, and in my own businesses.
Culture-Killer 1: Dilution through hiring.
Every new hire brings their own default behaviors from their previous environment. If they came from a large corporation, their defaults might include: follow the process, escalate decisions, communicate formally, protect yourself with documentation. If your culture values: use judgment, decide quickly, communicate directly, take ownership — those defaults directly conflict with your culture.
A single hire whose defaults conflict with the culture is manageable. You train them, model the right behaviors, and they adapt. Five hires in a short period, each carrying different defaults, overwhelm the existing culture’s ability to absorb and assimilate.
Solution: Slow your hiring pace and hire for cultural fit as rigorously as you hire for skill. Cultural fit doesn’t mean “they’re like us” — it means their default behaviors align with the behaviors your culture requires. Ask interview questions that reveal defaults: “Tell me about a time a customer asked for something outside your normal process. What did you do?” The answer reveals whether their default is to find a way or follow the rules.
Culture-Killer 2: Communication breakdown at scale.
When two people run a business, communication is constant and ambient. You overhear everything. You’re in every conversation. Misunderstandings get caught immediately because you’re always in the loop.
At ten people, ambient communication is impossible. You can’t be in every conversation. Information gets filtered through intermediaries. Decisions get made in rooms you’re not in. The cultural norms that were transmitted through constant proximity now need to be transmitted through deliberate channels.
Solution: Create explicit communication structures that transmit culture, not just information. A weekly all-hands meeting isn’t just for updates — it’s for reinforcing cultural norms through stories. “This week, Maria handled a customer complaint by doing X. That’s exactly the kind of response we’re proud of.” Public recognition of culture-aligned behavior teaches the team what the culture values far more effectively than a values document.
Culture-Killer 3: Process replacing judgment.
As businesses grow, they add processes. Processes are necessary — they create consistency and reduce dependency on individual judgment. But processes also replace judgment, and judgment is where culture lives.
When a customer service representative follows a process that says “offer a 10% discount for complaints,” they’re executing a process, not exercising judgment. The culture might value generosity, but the process constrains generosity to exactly 10%. The process is right on average but wrong in specific cases where the culturally appropriate response is more or less than 10%.
Solution: Design processes with built-in judgment zones. Instead of “offer a 10% discount,” try “resolve the customer’s issue in whatever way you believe is generous and fair, within a budget of EUR 50 per incident without requiring approval.” This maintains the process structure (there’s a budget, there’s a standard) while preserving the judgment space (the individual decides what “generous and fair” looks like in the specific situation).
The Cultural Operating System
Protecting culture at scale requires what I call a Cultural Operating System — the explicit structures, rituals, and norms that transmit and reinforce culture as the team grows.
Component 1: The Culture Document (one page).
Not a mission statement. Not a values list. A one-page document that describes the five to seven specific behaviors that define your culture. Written in concrete, behavioral terms.
My culture document includes entries like: “When a customer has a problem, our first response is ‘how can I fix this?’ not ‘what’s our policy on this?’” and “When you notice something wrong, you own it until it’s resolved or explicitly handed off. Nobody says ‘that’s not my job.’”
Each new hire reads this document on day one. Not as corporate paperwork — as a genuine description of how we expect them to behave. The document isn’t aspirational. It describes the actual culture as it exists. If the behavior described in the document doesn’t match the behavior you observe in the team, the document needs updating or the team needs correction.
Component 2: Story-Based Reinforcement.
Humans learn behavior from stories, not from rules. Every week, in the team meeting, I share one story of culture-aligned behavior from the previous week. Sometimes it’s a customer interaction. Sometimes it’s an internal decision. Always it’s a specific person doing a specific thing that exemplifies the culture.
These stories are more powerful than any training program because they’re real, they’re recent, and they feature the team members’ peers. When Maria hears that her customer response was highlighted as exemplary in the team meeting, two things happen: Maria is reinforced in her behavior, and every other team member gets a concrete example of what the culture looks like in practice.
Component 3: Culture-Check in Decision-Making.
For significant decisions (new product features, process changes, hiring decisions, pricing changes), I add a culture-check question: “Is this decision consistent with our culture?” If we’re considering a process change that trades customer flexibility for operational efficiency, the culture-check might reveal that the trade violates our “customer judgment first” principle.
This doesn’t mean the decision is automatically wrong. Sometimes operational needs override cultural preferences. But the culture-check ensures that the cultural cost is visible and deliberate rather than accidental and invisible.
Component 4: Cultural Exit Criteria.
When someone consistently behaves in ways that conflict with the culture despite coaching and clear communication, they need to leave. Not because they’re bad people — because their default behaviors create friction that erodes the culture for everyone else.
This is the hardest cultural decision a founder makes, especially when the person is technically excellent. But a technically excellent team member whose behavior undermines the culture costs more in cultural damage than they contribute in technical output. One person who treats customers impatiently creates permission for others to treat customers impatiently. Culture flows downward and outward from every team member’s behavior.
The Founder’s Role Changes
At two people, the founder transmits culture through personal example. At ten people, the founder transmits culture through systems and selective personal example. At fifty people, the founder transmits culture through leaders who transmit culture through their own teams.
This evolution requires the founder to shift from “being the culture” to “designing the systems that maintain the culture.” It’s the same transition described in the clockwork business framework — you go from operating to architecting.
The specific shift:
Stage 1 (1-3 people): You model every cultural behavior personally. The team absorbs culture by working alongside you. No systems needed — proximity does the work.
Stage 2 (4-10 people): You model cultural behaviors but also begin documenting, story-telling, and explicitly communicating expectations. Some team members no longer work alongside you daily, so ambient transmission is insufficient.
Stage 3 (11-30 people): You train team leads to transmit culture within their teams. Your direct cultural influence is now filtered through intermediaries. The quality of those intermediaries determines whether culture scales or dilutes.
Stage 4 (30+ people): The Cultural Operating System carries the weight. You’re maintaining and updating the system, not personally transmitting culture to most of the team. Your direct cultural influence is limited to the leadership team, who then cascade it.
Measuring Culture
What gets measured gets managed. But how do you measure something as qualitative as culture?
Customer satisfaction metrics segmented by team member. Are customer ratings consistent across team members, or do some team members consistently produce lower satisfaction? Variation indicates cultural inconsistency.
Decision audit. Periodically review how decisions were made across the team. Were they consistent with cultural norms? When someone faced an ambiguous situation, did they default to the culture’s expected behavior or to their personal default?
Exit interview patterns. When people leave, what reasons do they give? If multiple departures cite “the culture changed” or “I didn’t feel aligned with how things are done,” the culture is either shifting (which might be intentional) or diluting (which usually isn’t).
The 360-degree culture check. Annually, ask every team member anonymously: “Describe our culture in three words.” Compare the responses to your one-page culture document. If the words align, the culture is being transmitted effectively. If they diverge, there’s a gap between the intended and the actual culture.
The owner dependency framework applies to culture too. If the culture only works when you’re present and engaged, your culture has an owner dependency problem. The goal is a culture that persists regardless of whether the founder is in the room.
Takeaways
- Culture is default behaviors, not stated values. How people actually behave when the situation is ambiguous and nobody is watching — that’s your real culture. Scaling culture means systematizing those default behaviors.
- Three dynamics kill culture during growth: dilution through rapid hiring, communication breakdown at scale, and processes replacing judgment. Each requires specific countermeasures.
- Build a Cultural Operating System with four components: a one-page behavior document, weekly story-based reinforcement, culture-check questions in significant decisions, and exit criteria for persistent cultural misalignment.
- Design processes with built-in judgment zones. Instead of rigid rules that eliminate discretion, create frameworks that maintain standards while preserving the space for culturally appropriate individual judgment.
- The founder’s role evolves from modeling culture personally (1-3 people) to designing systems that transmit culture through leaders (30+ people). If culture only works when you’re in the room, it hasn’t scaled.
