Structure Is How Culture Keeps Its Promises
“We have to evolve past playing six-year-old soccer,” one operations leader told me.
“When everybody sees the ball, they run to the ball. Then the ball moves, and everybody runs to the ball. We’ve got to have roles, division of duty, and understand that somebody else is doing what they’re supposed to do.”
As a soccer mom who spent plenty of weekends watching six-year-old games, I appreciated the metaphor immediately. At that age, soccer is less a formation than a cheerful hot mess of shin guards, enthusiasm, and nearly everyone chasing the same ball—unless, of course, someone has decided to sit down and pick dandelions. It is adorable when the players are six. It is a much less dependable operating model for a growing organization.
Nine years ago, my daughter and her teammates gave me a front-row seat to the classic six-year-old soccer strategy: follow the ball, improvise the rest, and leave room for the occasional dandelion break.
I was interviewing the operations leader as part of an employer brand foundation project I’ve been working on. From the outside, employer brand work can sound like an exercise in finding the right words: clarify the message, sharpen the careers-page language, and explain why someone would want to work there.
The words do matter, but a credible employer brand can’t only describe what leaders hope the culture feels like. It also has to reflect what employees are actually asked to navigate and what candidates can reasonably expect after they join the team.
During the interviews, I was listening for both sides of that story: what made the organization distinctive, what employees valued, and what kind of person would feel energized there. I was also listening for places where the lived experience required more context, support, or clarity than the polished, aspirational version of the story might suggest.
This company had real cultural strengths. People had autonomy, flexibility, access to leadership, and opportunities to influence what the organization was becoming. Decisions moved quickly, and employees who enjoyed building rather than inheriting a finished playbook could have a meaningful impact.
My interviews also surfaced the realities that often accompany growth: evolving roles, informal onboarding, communication norms still being defined, and important work that depended heavily on initiative, proximity, and people knowing whom to ask.
None of that made the culture inauthentic. It did show where the culture would need more support if a growing number of employees were going to experience it consistently.
When cultural strengths begin carrying too much weight
The leader who shared the soccer metaphor with me also described the organization as intentionally “process light.” He preferred it that way, but he could see the benefit of adding enough process to create greater consistency across the company as they expanded. He wasn’t asking for layers of approvals or a complicated operating system. Rather, he was talking about clearer roles, practical onboarding, and enough coordination that people could trust others to handle the work they owned.
That distinction resonated with me.
The organization didn’t need more structure because its culture had failed. It needed thoughtful structure because the culture was valuable—and rapid growth was making it harder to rely on personality, proximity, and unwritten understanding to sustain it.
This is where many leaders feel a genuine tension.
They worry that clearer roles will limit collaboration and innovation. That established processes will slow people down, or that communication protocols will replace accessibility with layers. They fear that formalizing the way work happens will make the organization feel more corporate and less human.
Those concerns aren’t imaginary. Process can become cumbersome at times. After all, a meeting can always lead to another meeting if left unsupervised.
But structure and culture are not natural opponents. At its best, structure is how culture keeps its promises.
For autonomy to feel empowering, people need enough context and clarity to make decisions confidently. For flexibility to feel fair, employees need shared expectations that do not change from one manager to the next. And for ideas to truly come from anywhere, people need to understand how those ideas will be heard, evaluated, and acted on.
Without that support, cultural strengths can gradually become sources of friction. Autonomy can feel like abandonment. Flexibility can turn into inconsistency. Accessibility can depend on who already has a relationship with leadership.
“We all pitch in” can turn into a situation where everyone runs toward the same problem while another important responsibility sits unattended.
The gap between a cultural value and a lived experience
Employer brand work makes this gap difficult to ignore.
You can’t responsibly describe an employee promise without considering what helps the organization keep it. Messaging may attract someone to the company, but onboarding, management practices, communication norms, and everyday workflows determine whether the promise feels true once that person arrives. It’s that shared meaning across the employee experience that helps make that promise credible.
A company may say it values candor, for example. But what does candor look like in practice?
Where are disagreements expected to happen?
How do leaders respond when someone challenges an idea?
What separates directness from unnecessary bluntness?
What happens when candid feedback points upward rather than downward?
The same is true for flexibility. A flexible culture sounds appealing, but employees still need to know what they can count on.
How should availability be communicated?
What decisions can managers make independently?
Are expectations reasonably consistent across teams, or does flexibility depend on informal relationships and individual interpretation?
Even autonomy needs infrastructure. “Use your judgment” works well for someone who has been at the organization for six years and helped shape its norms. It can feel much less empowering to a new employee who is still trying to understand what good judgment looks like in this particular workplace.
In my coaching class earlier this week, someone raised two questions that stayed with me: Do leaders’ actions match the organization’s stated values? And what does the organization reinforce through the behavior it allows?
Those questions get at something important: culture is shaped not only by what an organization names, but by what its systems reinforce, clarify, reward, tolerate, or leave open to interpretation.
If collaboration is a value, the workflow should not require people to discover important information by accident.
If accountability is a value, ownership and expectations should not remain vague.
If respect is a value, leaders cannot ignore patterns of behavior that quietly make it harder for others to contribute.
If learning is a value, people need room to ask questions before they are expected to perform as though they already know the unwritten rules.
A value becomes meaningful when employees can see it reflected in how work actually happens.
Just enough structure
The answer is not to replace a nimble organization with a miniature version of a large corporation.
A 40-person organization doesn’t need infrastructure designed for 4,000 people. A growing nonprofit doesn’t need a policy for every hypothetical situation. A consulting firm doesn’t need three approval layers for decisions that one informed person can make responsibly.
The more useful question is: Where would a little more clarity help people experience the culture more consistently?
If autonomy matters, that may mean clarifying decision rights and escalation points.
If flexibility matters, it may mean establishing shared expectations for availability, communication, and outcomes.
If leadership accessibility matters, it may mean creating regular updates, office hours, or dependable ways for employees to ask questions and surface ideas as the organization grows.
If respectful candor matters, it may mean giving managers and teams clearer norms for feedback and disagreement.
If speed matters, it may mean naming priorities, owners, and decision points so energy does not scatter across too many competing efforts.
These aren’t necessarily heavy systems. In many organizations, the most helpful structure is quite ordinary: a more thoughtful onboarding plan, a clearer handoff, a simple decision log, an agreed communication rhythm, or a conversation about what a role owns and what it does not.
The goal is not to eliminate ambiguity. Some uncertainty is unavoidable, especially in organizations that are growing, experimenting, or building something new. The goal is to stop asking people to navigate ambiguity that could reasonably be reduced.
What are you really trying to preserve?
As I reviewed the interviews, I noticed that the qualities people most wanted to preserve were often the same ones creating the clearest need for structure. Flexibility needed shared expectations. Autonomy needed context. Access to leadership needed a way to remain accessible as more people joined. Entrepreneurial energy needed enough coordination that people could move quickly without repeatedly running into one another.
The leadership team was trying to become more repeatable without losing what made the company distinctive. That’s an important nuance.
Not every informal habit is a cultural value. Some habits simply developed because the organization was smaller, fewer people needed to coordinate, and early employees carried a great deal of institutional knowledge in their heads.
As the organization changes, leaders may need to separate what is truly worth protecting from what has merely become familiar and/or comfortable.
The casual conversation that once kept everyone informed may need to become a more intentional communication rhythm. The founder’s open door may need additional channels (e.g., set office hours) so access does not depend on timing or proximity. The expectation that everyone jumps in may need clearer ownership so collaboration remains generous rather than chaotic.
That is not necessarily culture loss. I think it represents culture becoming more durable.
Three questions for growing organizations
Leaders don’t have to formalize everything at once. A more practical starting point is to ask:
What part of our culture are we most afraid of losing?
What behaviors allow people to experience that part of the culture?
What small amount of structure would make those behaviors easier, clearer, and more consistent?
The answers may reveal that what feels like a choice between culture and structure is not really a choice at all.
The organization may not need more rules. It may need clearer promises…and systems that help it keep them.
And occasionally, it may need a few people to hold their positions instead of the whole team chasing the ball (or sitting down to pick dandelions).
Help your culture keep its promises
If growth is making it harder for employees to experience your culture consistently, Mosaic BizOps can help connect the employer promise with the onboarding, communication, and people systems that make it real. Learn more about my approach to employer brand and people systems work.
