Culture is not the posters on the wall or the values on the website - it is how people actually behave when no one is watching. A strong engineering culture attracts talent, enables collaboration, and drives quality. A weak one drives attrition, breeds cynicism, and undermines execution. This guide helps you build culture intentionally rather than leaving it to chance.
Defining Meaningful Team Values
Effective team values are specific enough to guide behaviour and differentiate your team from others. 'We value quality' is too generic. 'We never ship without automated tests because we believe future developers should trust the code they inherit' is specific and actionable.
Involve the team in defining values rather than dictating them. Facilitate a workshop where team members share stories of when the team was at its best and at its worst. The values embedded in those stories - collaboration, craftsmanship, transparency, courage - are authentic expressions of what the team believes in.
Limit your values to three to five. More than that becomes impossible to remember and meaningless to apply. Each value should be a genuine guide for decision-making: when faced with a trade-off, the team should be able to reference a value to help make the call.
Building Rituals That Reinforce Culture
Rituals are repeated practices that embody your values. If you value learning, hold weekly tech talks. If you value transparency, write weekly team updates. If you value craftsmanship, hold regular architecture reviews. Rituals turn abstract values into concrete practices.
Some of the most effective rituals are informal. A tradition of celebrating deployments, a channel for sharing interesting articles, or a team lunch on Fridays builds connection and reinforces identity. These small traditions create the social fabric that makes a group of individuals feel like a team.
Evaluate your rituals regularly. Some will become stale and need refreshing; others will need to be retired as the team evolves. A ritual that the team resents attending is worse than no ritual at all. Check in periodically and adjust based on what is actually providing value.
Establishing and Enforcing Cultural Norms
Norms are the unwritten rules that govern daily behaviour: how the team communicates, how they handle disagreements, how they respond to mistakes, and how they treat each other. Making these norms explicit - writing them down as a team working agreement - prevents misunderstandings and makes onboarding smoother.
Enforce norms consistently. If the norm is 'we treat each other respectfully in code reviews' but you tolerate harsh feedback from a senior engineer, the actual norm becomes 'respect is optional for high performers.' What you tolerate defines your culture, not what you declare.
Update norms as the team evolves. What works for a five-person team may not work for a fifteen-person team. Review your working agreements when the team composition changes significantly and adjust for the new context.
Maintaining Culture Through Hiring
Every hire either strengthens or dilutes your culture. Include cultural assessment in your interview process - not 'culture fit,' which often becomes a proxy for homogeneity, but 'culture add,' which evaluates whether the candidate shares your values while bringing diverse perspectives and experiences.
Onboard new hires into the culture explicitly. Do not assume they will absorb it by osmosis. Share your team values, explain your rituals, and describe your norms during their first week. Assign an onboarding buddy who can help them navigate the cultural landscape.
Watch for cultural drift as the team grows. Each new hire shifts the culture slightly. If you hire several people in quick succession who do not share the team's core values, the culture can shift dramatically. Maintain intentionality about culture even when under pressure to hire quickly.
Sustaining Culture Through Change and Growth
Culture is fragile during times of change - reorganisations, leadership transitions, and rapid growth all threaten established cultural norms. During these periods, be more deliberate about reinforcing values, maintaining rituals, and modelling the behaviour you expect.
Scale culture through documentation, mentoring, and leadership development. As the team grows beyond a single manager's direct influence, the culture must be carried by multiple leaders at every level. Develop cultural ambassadors - team members who embody and advocate for the team's values.
Accept that culture evolves and guide the evolution rather than fighting it. The culture that works for a startup team may not work for a large engineering organisation, and that is fine. The core values can remain constant while the specific practices and norms adapt to the team's changing context.
Key Takeaways
- Define three to five specific, actionable values co-created with the team
- Build rituals that embody your values and create the social fabric of the team
- Make cultural norms explicit, enforce them consistently, and update them as the team evolves
- Maintain culture through hiring by evaluating 'culture add' and onboarding new hires into the culture explicitly
- Sustain culture through change by reinforcing values, developing cultural ambassadors, and guiding evolution intentionally
Frequently Asked Questions
- How do I change a toxic culture I inherited?
- Culture change is possible but requires sustained effort. Start by clearly articulating the culture you want to build. Model the new behaviour yourself - consistently and visibly. Reward team members who embody the new culture and address behaviour that contradicts it. Hire people who share the new values and, if necessary, manage out individuals who actively resist the change. Expect the process to take six to twelve months for visible improvement.
- How do I maintain culture across remote and distributed teams?
- Document your culture explicitly - remote teams cannot rely on osmosis. Create virtual rituals that build connection. Use written communication to reinforce values and norms. Make cultural expectations part of onboarding, and check in regularly on how remote team members are experiencing the culture. The principles are the same as for co-located teams, but the execution requires more deliberate effort.
- What is the difference between team culture and company culture?
- Company culture is the broad set of values and norms that define the organisation. Team culture is a local expression that operates within and extends the company culture. Your team may share the company's values of innovation and customer focus while also having team-specific norms around code quality, communication styles, and decision-making processes. Team culture should complement, not contradict, company culture.
Access Culture Building Toolkit
Use our interactive culture building toolkit to define team values, design rituals, and build working agreements that strengthen your engineering team's identity.
Learn More