Build Team Culture — Engineering Leadership, Part 8
Culture isn't posters on the wall. It's how you handle the first time someone misses a deadline. How you respond to a 3am page. What you reward; what you tolerate.
Step 1: Culture Is What You Do (10 min)
Stated values: "We value quality."
Actual culture: "We ship features even with known bugs."
Mismatch = cynicism.
Your behavior — under stress — is the culture. Engineers watch. They calibrate to what you actually do.
Step 2: Decide Your Defaults (15 min)
Defaults define culture:
Async vs. sync — meetings or docs?
Sharing vs. ownership — knowledge in docs or in heads?
Iteration vs. perfection — ship fast or polish?
Process vs. judgment — rules or trust?
Pick deliberately. Document. Reinforce.
For most engineering teams in 2026: async-default, documented, iterative, judgment-trusting. Adjust to context.
Step 3: Rituals (15 min)
Weekly:
Monday: priorities sync
Friday: demo / show & tell
1:1s with each engineer
Quarterly:
Planning
Retro
Off-site or focused team day
Daily:
Standups (or async)
Lunch together (occasional)
Rituals create rhythm. People know what to expect.
Skipping a ritual once = fine. Skipping repeatedly = signal the ritual is dead.
Step 4: Standups That Help (10 min)
Bad: 30 minutes; everyone reads a status report.
Good:
10 minutes
"Blockers? Anything the team should know?"
Skip if nobody has anything
Async standups (Slack thread) work better for many teams.
The ritual: surface blockers; align on priorities. Not: track who's working.
Step 5: Demos and Show & Tell (10 min)
Friday: each engineer shows 2 minutes of what they shipped or learned.
Effects:
Forces shipping (otherwise: nothing to show)
Spreads knowledge
Celebrates progress
Builds trust
Don't make it formal. Casual; show off; ask questions.
Step 6: Make Praise Public (5 min)
Slack channel for the team:
"Sarah's incident response was 🔥"
"Bob shipped X; gnarly migration done well"
"Alice's PR comment saved us a bug"
Specific. Public. Regular.
People stay where they're seen. Praise costs nothing.
Step 7: Handle Mistakes Well (15 min)
Engineer pushes a bug to production.
Bad culture:
Blame in public
Cold treatment
Permanent reputation hit
Good culture:
Acknowledge in retro (blameless)
Focus on the system gap that allowed it
Move on
Maybe they fix it; learn
How you handle the first mistake teaches the whole team.
Step 8: Set the Tone in Meetings (10 min)
What you do:
Listen?
Interrupt?
Defer to seniors?
Invite quiet voices?
Disagree well?
Your meeting behavior models the team's. People copy you.
Push for:
Brief, focused meetings
Decisions documented
Voices balanced
Disagreement encouraged
Step 9: Glue Work Is Valued (10 min)
"Glue work" — docs, reviews, mentoring, onboarding, incident response.
Often invisible. Often done by underrepresented engineers.
Your job: see it; reward it. Promote it in writing. Mention in reviews.
If only feature work counts, glue work dies. Then nothing holds together.
Step 10: Tolerance Defines Culture (10 min)
What you tolerate becomes culture:
Tolerate a brilliant jerk → toxic team
Tolerate undocumented decisions → tribal knowledge
Tolerate skipped 1:1s → low engagement
Tolerate flaky tests → broken CI culture
Tolerate poor PR descriptions → low-quality reviews
The hardest part: addressing tolerance. The brilliant-jerk conversation. The "we need to talk about your tone" conversation.
Avoid these and the culture you wanted dies.
What You Just Did
Building culture: what you do > what you say, defaults, rituals, standups, demos, praise, mistakes, meeting tone, glue work, tolerance. Culture you can name and shape.
Common Failure Modes
Stated values vs. actual behavior. Cynicism.
Standups that drag. Drains hours per week.
Praise only at reviews. Recognition is rare.
Public blame. People hide bugs.
Tolerate a jerk. Whole team adjusts toward toxic.
