Skip to main content
How to Evolve Your Workplace Culture While Scaling Fast

How to Evolve Your Workplace Culture While Scaling Fast

Nobody tells you this when you're scaling fast: your culture is already changing, whether you manage it or not. The only question is who's steering it.

By · Published

Nobody tells you this when you're scaling fast: your culture is already changing, whether you manage it or not. The only question is who's steering it. I've watched founders treat culture as a slogan on the wall — something you write once at 15 people and defend forever. That's backwards. Culture isn't a document you protect. It's a set of decisions you keep making, out loud, under pressure, as the headcount doubles under you.

Most "how to preserve culture while scaling" advice is written for a company that isn't actually scaling — it assumes you have time to run values workshops and onboarding retreats. You don't. At 40% headcount growth per quarter, culture isn't preserved, it's re-founded, repeatedly, by whoever is in the room when the hard calls get made. My view, after years inside high-growth leadership teams: the companies that keep their culture intact aren't the ones with the best-written values. They're the ones whose leaders make the same call in week 40 that they made in week 4, and say why, in public, every time.

Why culture erodes at exactly the moment leaders stop noticing

Culture doesn't erode because people stop caring. It erodes because the feedback loop that used to catch drift disappears. At 15 people, you know if something's gone wrong within a day — someone tells you at lunch. At 150, the same problem sits for a quarter before it surfaces in an exit interview. Growth doesn't change what your people value. It changes how fast you find out when the organisation stops living those values, and by the time you find out, the new joiners who never knew the old way have already set the new norm.

This is the part scaling playbooks skip: culture change during hypergrowth is not gradual. It's a series of small, silent votes — a manager who lets a toxic top performer slide, a decision made in a Slack DM instead of the open channel it used to happen in, a promotion that rewards politics over the thing you claim to reward. Each vote is invisible on its own. By the time the pattern is visible in engagement scores, you're not fixing drift — you're doing culture repair on an organisation that's already forgotten what it used to be.

The four things I actually check before I tell a leadership team their culture is scaling well

  • Who gets promoted, not who gets praised: Praise is cheap and public. Promotion is the real values statement. If your stated value is collaboration but your last three promotions went to the loudest individual performer, the org already knows the truth and the values page is decoration.
  • What happens in the first bad decision after a new hire's start date: Every new joiner is watching how leadership handles the first visible mistake or conflict after they arrive. That single incident teaches them more about "how we really do things here" than the entire onboarding deck.
  • Whether disagreement travels upward without translation: In a small team, a junior person can tell the founder something's wrong directly. Track how many layers a piece of dissent has to pass through before it reaches a decision-maker — and whether it survives the journey intact or gets softened at each layer.
  • Whether your operating rhythm still forces the values, or just states them: Values that only live in a deck decay. Values that are structurally embedded in how OKRs get set, how post-mortems run, and how compensation decisions get made survive scale because the system enforces them even when no one's watching.
  • How fast a bad hire gets corrected, not whether one gets made: Every fast-scaling company makes hiring mistakes — that's not the signal. The signal is how many quarters it takes leadership to notice, name it, and act. Slow correction is the actual cultural tell, not the mistake itself.

The manager layer is where culture actually lives or dies

Founders obsess over their own behaviour as the culture signal, and it matters, but it's not where most employees experience the culture. Most people never sit in a room with the founder after month six. They experience the culture entirely through their direct manager — how that manager runs a one-to-one, whether that manager pushes back on unreasonable deadlines from above, whether that manager tells the truth about a missed target or quietly reframes it. Scaling fast means you're promoting managers faster than you can train them, and the newest, least-tested layer of management is the one carrying the entire cultural weight of the organisation to everyone below it.

This is why culture doesn't fail evenly across a fast-scaling company. It fails in pockets — one team where a manager was promoted for technical output and has never been taught how to hold a hard conversation, sitting right next to a team where the manager gets it completely. From the top, the aggregate engagement number looks fine. On the ground, half the company is having a completely different experience of "who we are" than the other half, and nobody at the top notices until the pocket that's failing starts losing its best people quietly, one resignation at a time, each one looking unrelated to the last.

My practical fix isn't more manager training decks. It's giving new managers a genuinely small number of explicit, non-negotiable behaviours — not a values list, a behaviours list — and checking those behaviours directly rather than trusting they'll be absorbed by osmosis. Things like: you tell your report the real reason for a decision, even an unpopular one. You don't let a deadline conversation happen only in writing. You escalate a resourcing conflict instead of quietly absorbing it into unpaid overtime. Three or four of these, held firmly, do more for culture at scale than a values workshop ever will, because they're checkable and specific rather than aspirational and vague.

Onboarding is a culture decision, not a logistics task

Most companies scaling fast treat onboarding as an HR logistics problem: laptop, badge, benefits form, a welcome deck with the values on slide four. That deck is not what teaches a new hire the culture. What teaches them is the first ambiguous situation they encounter and how it gets resolved around them — a missed deadline nobody addresses, a colleague who cuts corners without consequence, a manager who says one thing in the all-hands and does another in the team meeting. New hires are pattern-matching machines in their first ninety days. They will believe what they observe over what they were told in the deck, every single time.

The companies that protect culture through fast growth treat the first ninety days as the highest-leverage cultural intervention they have — not because of the content of onboarding, but because it's the one window where a person is actively comparing what they were promised against what they're seeing. Waste that window on logistics and you've lost your best chance to set the norm deliberately, before the new hire starts setting it for themselves based on whatever they happen to observe first.

How to build an accountability culture in an organisation

Accountability culture means people take genuine ownership of outcomes, not just activities. I don't think this is built through better performance reviews. It's built through four unglamorous mechanisms, and if any one of them is missing the other three won't save you.

  1. Clarity of ownership — Everyone must know exactly what they're accountable for and how it connects to a business outcome, not a task list. Ambiguous ownership is the single biggest killer of accountability — you cannot hold someone to a standard they were never told was theirs to hit.
  2. Consequence that's actually felt — Accountability without meaningful consequence is just expectation. Organisations that celebrate results but quietly absorb failures — no conversation, no course correction, no changed incentive — teach everyone that accountability is theatre. People calibrate to what happens, not to what's said.
  3. Leadership modelling it first, visibly — Accountability culture flows downward from how the executive team treats its own misses. If the leadership team's failures get explained away in the all-hands while a junior team's failures get a stern memo, the org has learned the real rule in one meeting.
  4. Systems that make it visible, not optional — Performance management, OKR cycles, and operating rhythms have to surface accountability as a routine, structural fact — not an occasional intervention. If the only time accountability gets discussed is during a crisis, it isn't culture, it's damage control.

How to build psychological safety in a C-suite team

Psychological safety at the top table means an executive can raise a concern, challenge a peer, disagree with the CEO, or admit a mistake without that costing them politically. This is harder to build in a C-suite than anywhere else in the company, because the stakes of being wrong in front of peers are highest exactly where the room is smallest and most exposed.

  • The CEO has to model vulnerability first — visibly admitting uncertainty or a wrong call signals that this room is different from the rest of the org, where hedging is often safer
  • How the CEO responds to the first act of dissent in a meeting sets the norm for every challenge that follows — react defensively once, and you've told the room the invitation was never real
  • Meeting structure has to be engineered for safety, not left to goodwill — rotating who speaks first, running pre-mortems, and collecting written input before open discussion stop the most senior or loudest voice from setting the answer before the room has spoken

None of this is soft. A C-suite that can't disagree in the room will disagree in private, in coalitions, after the decision is made — which is far more expensive to the business than an uncomfortable ten minutes in the meeting itself.

The distinction I actually stand behind

If you take one thing from this, take this: culture isn't something you scale, it's something you keep re-deciding under worse conditions than the last time. Every founder I've worked with who scaled well made peace with that early. Every one who scaled badly kept waiting for the culture work to be "done" so they could move on to the next priority. It's never done. That's not a failure of the plan — it's the nature of the thing.

The companies that get this right don't have better values statements than the companies that get it wrong. I've read both sets of values decks, and honestly, they're often indistinguishable — collaboration, ownership, customer obsession, the same eight words in a different order. What separates them is whether the values are load-bearing. A load-bearing value shows up in a promotion decision that costs the business a good salesperson because they hit the number the wrong way. A decorative value shows up only in the onboarding deck.

So when a leadership team asks me how to protect culture through a scaling phase, I don't hand them a workshop. I ask them to show me the last three hard calls — a firing, a promotion, a resourcing decision made under pressure — and I read the culture off those, not off the wall. That's the only audit that tells you the truth, because it's the only one your organisation has already been quietly running on you, decision by decision, since the day you stopped being able to know everyone's name.

My honest advice to any leader scaling fast: stop trying to protect the culture you had. It's already gone, and grieving it wastes time you don't have. Instead, decide — explicitly, in public, in the next hard call you make — what the culture becomes next. That's the job. Not preservation. Authorship.