Your Culture Is Either Designed or Deferring to Whoever's Loudest in the Room
BLUF/Summary
Culture isn't optional. Every organization has one. The only question is whether yours was designed deliberately by leadership or assembled accidentally by whoever happened to be most influential as the company grew. Accidental culture is dangerous because it's invisible — it shapes how decisions get made, how conflicts get resolved, how people are evaluated and incentivized, and how the organization responds to pressure, all without anyone consciously choosing those patterns. By the time leadership notices the culture isn't what they wanted, it's deeply embedded in how the organization operates. Designing culture on purpose isn't a soft initiative. It's a hard, deliberate act of choosing what your organization will value, articulating it explicitly, and reinforcing it through systems until it becomes the default pattern of behavior.
What Accidental Culture Actually Looks Like
When leaders don't deliberately design culture, the organization defaults to whatever culture the most influential people happen to bring with them. If the founder is a hard-driving perfectionist, the culture becomes hard-driving and perfectionist — even if the founder never articulated those values or considered whether they were the right ones for the organization. If the senior engineer is conflict-averse, the engineering team becomes conflict-averse. If the most influential sales leader treats relationships transactionally, the sales organization becomes transactional.
None of this happens consciously. Nobody decides "we will be a hard-driving perfectionist organization." It just happens — through hiring choices, through how decisions get praised or criticized, through which behaviors get tolerated and which don't, through which conflicts get addressed and which get avoided.
The result is a culture that nobody designed, that may not match the values leadership thinks the organization has, and that will be very hard to change once it's embedded. Accidental culture is the cumulative residue of every micro-decision the organization made when it wasn't paying attention to what it was becoming.
The danger is that accidental culture eventually conflicts with what the organization needs. The hard-driving perfectionism that worked at 20 people becomes burnout at 200. The conflict-aversion that kept early teams comfortable becomes inability to address performance issues at scale. The transactional sales culture that won early deals becomes a churn problem when client retention starts mattering. By the time leadership notices the mismatch, the patterns are deeply entrenched in how the organization operates.
Why Culture Has to Be Designed at Scale
In small organizations, culture can be transmitted through proximity. Everyone watches the founder. Everyone hears how decisions get discussed in the same room. The culture is whatever the leadership team models, and new hires learn it by being close enough to observe it.
This breaks at scale. Once an organization passes 50 people, most employees no longer have direct, regular contact with the leadership team. They learn the culture from their immediate manager, their peer group, and the patterns they see around them. If the culture hasn't been articulated and systematically reinforced, what new hires absorb is whatever local culture happens to exist in their team — which may bear no resemblance to what leadership thinks the company culture is.
Past 200 people, the problem compounds. Now there are multiple layers of management between leadership and most employees. Each layer transmits culture imperfectly, with their own additions and omissions. Without deliberate design and reinforcement, culture fragments into local cultures that vary widely across the organization. The same company can have a high-trust collaborative culture in one department and a blame-driven low-trust culture in another, with leadership unaware of the difference.
The only way to prevent this fragmentation is to design culture deliberately and reinforce it through systems that operate at every level of the organization, regardless of which manager or peer group a person happens to work in.
What Designing Culture Actually Means
Designing culture isn't writing a values poster and putting it in the lobby. It's the deliberate, systematic work of choosing what the organization will value, articulating those values in behavioral terms, and building systems that reinforce them so consistently that they become the default pattern.
Choose a small number of cultural principles. Five to seven principles is a workable range. Fewer than five and you can't capture enough of what makes the culture distinctive. More than seven and people can't remember them, which means they can't apply them. The principles should be specific enough to be actionable. "Excellence" is not a cultural principle — it's a vague aspiration. "We default to publishing knowledge so others can build on it" is a cultural principle, because it tells people what to actually do.
Articulate each principle in behavioral terms. What does this principle look like in practice? What behaviors does it require? What behaviors does it discourage? A cultural principle that can't be translated into specific behavioral expectations is just a feeling — it can't shape how people actually act.
Tie principles to operational systems and financial incentives. A cultural principle about ownership ("Be an Owner, Not a Victim") needs to be reinforced through systems that reward ownership behavior — clear roles and authority, weekly priority commitments that surface accountability, performance reviews that explicitly assess ownership behaviors. Without operational reinforcement, cultural principles become decorative rather than directive. Tough decisions regarding high performers with weak cultural alignment (e.g., the person in sales who is a jerk or disengaged, but closing huge deals) show what your principles really are, and not just what you say they are.
Hire for cultural alignment. Interview questions should explicitly assess whether candidates align with the cultural principles. Not in a vague "culture fit" sense, but in specific behavioral terms. If the principle is "Publish Knowledge and Processes," interview for whether the candidate has actually documented their work and shared it. If the principle is "Quality and Speed," interview for how they've balanced those tensions in past roles. Cultural alignment in hiring is the most powerful long-term reinforcement mechanism, because it shapes who joins and stays.
Onboard explicitly to the culture. Every new hire should be introduced to the cultural principles in their first week, with examples of what the principles look like in practice. Culture transmitted through osmosis is culture that fragments. Culture taught explicitly is culture that scales.
Coach to the principles continuously. When someone exhibits a behavior that aligns with a principle, name it. When someone exhibits a behavior that violates a principle, address it. Coaching — done deliberately and consistently — is what turns articulated principles into lived practice. Without continuous coaching, principles become aspirations that nobody enforces.
Audit culture periodically. Once or twice a year, leadership should assess whether the culture in practice matches the culture as designed. Are the principles being applied? Are there gaps between what's stated and what's tolerated? Are some teams operating in ways that violate the principles without consequence? The audit is what surfaces drift before it becomes entrenched.
What a Designed Culture Looks Like
Cultural principles, when designed well, look something like these (drawn from organizations I've worked in or advised):
Be an Owner, Not a Victim. When something goes wrong, your first response is to figure out what you can do about it, not to look for who to blame. When you see a problem, you take responsibility for raising it and contributing to the solution, even if it's not "your" problem.
Publish Knowledge and Processes. When you figure out how to do something well, you document it where others can find it. When you make a decision that future people will need to understand, you record the rationale. You default to sharing rather than hoarding.
Invest Time in Planning. You spend time thinking about how to do work before doing it. You bring agendas to meetings. You define what "done" looks like before starting. You recognize that time spent planning is not time wasted — it's time that prevents larger time loss later.
Quality and Speed. You don't accept the false tradeoff between quality and speed. You build systems that produce both. When you have to make a tradeoff in a specific instance, you think carefully about which dimension matters more for that decision rather than defaulting to one or the other.
Make Decisions and Adjust. You make decisions with available information rather than waiting for certainty. You're explicit about the assumptions behind decisions so they can be revisited if those assumptions change. You don't treat reversible decisions as if they were permanent.
These are examples, not prescriptions. The right cultural principles for any organization depend on what that organization is trying to be. The point is that the principles are specific enough to guide behavior, behavioral enough to be coachable, and reinforced enough to actually shape what the organization becomes.
What Changes When Culture Is Designed
Organizations with deliberately designed cultures experience differences that compound over time.
Decisions become more consistent. When everyone understands what the organization values, they make decisions that align with those values without needing to ask. The cultural principles become a decision-making framework that scales.
Conflicts become more productive. When the principles include explicit guidance on how to disagree (publishing your reasoning, addressing issues directly, separating the person from the position), conflicts get resolved through the principles rather than through politics.
Performance becomes easier to evaluate. When the principles include behavioral expectations, performance reviews can assess whether someone is exhibiting the behaviors the organization values, not just whether they hit their numbers. The "what" and the "how" both matter, and both can be assessed.
Hiring becomes more effective. When interviews explicitly assess cultural alignment in behavioral terms, the people who join are more likely to thrive — and the people who would have been a poor fit self-select out.
And — most importantly — the organization develops the ability to adapt without losing what makes it distinctive. Strategy can change. Markets can shift. Leaders can transition. But the cultural principles, if designed well and reinforced systematically, persist across those changes and provide continuity. The organization stays itself through transitions that would otherwise fragment its identity.
The Keel Connection
In the Keel Framework, culture is one of the heaviest components of Element 1 — The Boat, your people. The principles you design and reinforce shape who joins your organization, how they work together, how they make decisions, and what they expect from each other. When culture is designed deliberately, the boat sails in a coordinated way even when the leader isn't watching. When culture is accidental, the boat drifts in whatever direction the strongest local current happens to push it.
Designing culture is one of the most uncomfortable forms of work a leader does, because it requires articulating things that have usually been left implicit, and enforcing them in ways that can feel uncomfortable when they conflict with how influential people prefer to operate. But the alternative — accidental culture that drifts away from leadership's intent — is far more uncomfortable in the long run, because by the time you notice the drift, undoing it is enormously expensive.
Where to Start
If your organization doesn't have explicit cultural principles, the work begins with a leadership conversation. What do you actually value? What behaviors do you want to be characteristic of your organization? What patterns do you want to encourage and discourage? Write down a draft of five to seven principles, articulated in behavioral terms.
Then test them against reality. Are these the principles your organization actually operates by today? If yes, you're articulating what already exists, which is easier. If no, you're committing to changing the culture toward what you've articulated, which is harder but more important.
Introduce the principles deliberately. Discuss them in town halls. Add them to onboarding. Reference them in coaching conversations. Tie them to performance reviews. Use them in hiring interviews. Reinforce them through every system that touches how people work.
Over time, the principles stop being a list on a page and become the way the organization actually operates. That's the goal — not the articulation, but the embodiment. Articulated culture is the start. Designed culture is what happens when articulation is reinforced consistently enough that it becomes the default behavior of the organization, regardless of who's in the room.
The leaders who do this work build organizations that scale without losing their identity. The ones who don't build organizations that wonder, eventually, how they ended up so different from what they intended to be.
This is part of an ongoing series on building enterprise operating systems. Read more about the full approach in the Keel Framework, or explore related posts on the ambiguity tax of unclear roles, your operating cadence as strategy's immune system, the Friday 3pm accountability rule, and high agency as a systems problem.
