The Culture You’re Building Without Knowing It
How your daily behavior adds up to something larger than any individual practice
About a year into managing my own area at Amazon, I walked back from a shift managers’ meeting and noticed something I hadn’t seen before.
Two of my team leads were standing near the sort station, and one of them was coaching an associate through a process question. Not directing—actually coaching. Asking what the associate thought the issue was, letting him work through it, only stepping in to redirect when he stalled. It was, almost exactly, the way I’d been trying to run my own debrief conversations with her for months.
I stood there for a moment longer than I needed to. Because what I was watching wasn’t something I had assigned, or rolled out in a team meeting, or put in a development plan. She had just started doing it—and now she was doing it one level down from me, with her own people.
That was the first time I understood what culture actually is. Not a values statement on a wall. Not a set of norms you announce in an onboarding. It’s the accumulation of signals you’ve been sending—through what you’ve rewarded, what you’ve tolerated, and what you’ve modeled—until those signals become the way people behave when you’re not in the room.
The encouraging version of that realization is what I saw that day: good habits replicating downward, development becoming the way the floor operated rather than a thing I was personally trying to do.
But the same mechanism works in the other direction, too. And most managers encounter that version first.
The Culture That Was Already There
Every team you take over comes with a culture already running. It’s been shaped by everyone who managed that team before you: their habits, their tolerances, their shortcuts and their standards. Some of it is visible, such as the way people talk to each other, the pace they work at, the amount of noise around near-misses. Most of it isn’t. It lives in unspoken agreements about what gets addressed and what gets quietly ignored, about how problems get surfaced and by whom, about whether the people on this floor believe anyone is genuinely paying attention.
When you arrive, that culture doesn’t pause to let you get oriented. It evaluates you from the first shift. And what it’s watching—what your team is watching—has very little to do with what you say about your management philosophy or your expectations or the kind of leader you want to be.
They’re watching what you do when someone cuts a corner and you notice. Whether you follow through when you say you’ll look into something. Which problems get your energy and which ones quietly disappear. How you talk about the people above you when they make decisions you disagree with. Whether the standards you enforce on Tuesday still apply on Friday afternoon when the shift production is behind.
Culture is built from that material. The speeches don’t touch it.
Nobody Announced It
The thing you need to understand about culture is that it’s almost never deliberately designed. It accumulates.
The manager who lets the fastest associate skip safety documentation because the shift is behind hasn’t made a cultural decision in any conscious sense. But the team saw it. And next week, when someone else is behind, they have data about what actually matters when things get tight. That data compounds, and two months later the manager is confused about why safety compliance feels like a constant battle, not understanding that they resolved the question themselves weeks ago.
This is true in both directions. The manager who consistently takes ten minutes after a difficult situation to ask her team leads what they were thinking—not criticizing, just curious—isn’t usually thinking “I am building a culture of reflection.” She’s just doing what she does. But her team leads start doing the same thing. And eventually you end up with what I saw at the sort station that afternoon: a coaching behavior that nobody programmed, replicating naturally because it had become the floor’s normal.
Culture isn’t what you intend. It’s what you repeatedly do and, more importantly, what you repeatedly allow.
What You Reward Teaches More Than What You Say
Every time you give recognition, you’re teaching your team what matters. The question is whether you’re teaching them what you think you’re teaching.
Recognition that lands on the same two or three people—the ones who are loud, or fast, or who happen to be standing near you when something goes well—teaches a very specific lesson: visibility and proximity to the manager matter. Effort that happens quietly, in areas you don’t walk past as often, doesn’t register the same way. Over time, people adjust. Not cynically, just practically. They figure out how recognition works here and they act accordingly.
The same is true of assignments. Which team leads get the high-visibility problem to own? Who gets pulled into the planning conversation for the new process rollout? Who gets the stretch task when capacity allows? Every one of those choices is a signal about what kind of performance and what kind of person you value. Your team is reading those signals constantly, in more detail than you probably realize.
There’s an easy way to audit this honestly: look at who got your visible recognition and your development assignments over the last two months, and ask whether that list reflects your stated values. Or was it just whoever happened to be in front of you when something good happened? The gap between those two things is a culture gap.
What You Tolerate Is Also a Policy
The things you don’t address are just as powerful as the things you do.
I wrote in Creating Accountability Without Constant Oversight about how vague expectations become invisible ones; how “handle problems that come up” means different things to different people depending on what they’ve seen happen when they did or didn’t handle something. The same principle applies here, but at the level of culture rather than operations.
If a team lead is consistently slow to respond to quality issues and you’ve had a conversation about it but nothing has changed and you haven’t gone further, that’s now a data point about how seriously quality standards are held on your team. The team lead whose performance is slipping knows it. So does everyone who works alongside her.
If the loudest, most confident voice in every problem-solving conversation is always right regardless of whether the reasoning is sound, and you haven’t noticed or addressed it, you’re building a culture where volume matters more than analysis.
If the standard you enforce when things are calm gets quietly suspended when the shift is behind, the standard that’s actually in effect isn’t the one you wrote down. It’s the one people can observe being applied consistently.
None of these gaps require bad intentions. They mostly require a manager who’s too busy to address everything, which describes every manager. But the things that go unaddressed don’t disappear from the culture. They become its baseline.
What You Model Is the Loudest Signal of All
Your team watches how you operate, and what they see becomes a template.
Not because they’re trying to emulate you (though some of them are, especially your team leads). Because watching the person who runs the floor is the most reliable way to figure out how this place actually works. What does the manager do when something goes wrong? Does she stay calm and ask questions, or does she get loud and fix things herself? Does she follow through when she says she’s going to do something? Does she know who’s been struggling and act on it, or does she wait for problems to come to her?
I’ve seen this play out in very specific ways. In The Debrief That Builds Leaders, I wrote about the moment when a team lead starts asking her associates the same questions you’ve been asking her, the debrief habit replicating downward without anyone telling it to. That’s culture being built through modeling. But the same thing happens with cutting corners, with blaming other departments for problems, with responding to pressure by dropping standards. Whatever you do consistently is what your floor learns to do.
This is the part that many managers find uncomfortable: you’re modeling when you don’t intend to. How you handle the moment when your own manager overrules you in front of your team. How you talk about a struggling associate when you’re venting to a colleague and someone is within earshot. How present you actually are during a pre-shift versus going through the motions. Those moments teach at least as much as the intentional ones.
As I explored in Ethics in Leadership and Creating a Culture of Openness and Honesty, your team doesn’t just watch what you do with big decisions. They watch the small ones. That’s where character is actually visible—and character, compounded across hundreds of small decisions, is what culture is built from.
Reading the Culture You’ve Actually Built
The most useful thing you can do with the ideas in this post isn’t to start designing your culture. It’s to start reading the one you already have.
A few places to look:
How do problems surface? Do your team leads bring issues to you early, when they’re still manageable? Or do things tend to appear fully formed and already serious? Teams where problems surface late are usually teams where surfacing problems early has carried some cost in the past—frustration, dismissal, extra scrutiny. That’s a cultural signal.
What do people do when no one is obviously watching? The standard that holds during the middle of the shift when you’re occupied with something else is closer to the real standard than the one that holds when you’re standing right there. Walk past something you didn’t know you’d pass. See what you find.
What are the unspoken rules about bad news? Does your team know you want to hear about problems fast? More importantly—do they believe it? The stated preference for early escalation and the actual experience of having escalated early don’t always match, and your team knows which one is real.
Who gets the credit and who gets the blame? Watch what happens when something goes well versus when something goes sideways. Where does the credit flow? Where does the accountability land? Those patterns, applied consistently over months, define the culture your team is working inside.
You can’t see all of this clearly from inside it—which is one of the reasons I’ve written at length about self-awareness as a leader and why the one-on-one conversation is such a valuable diagnostic tool. Your team leads, asked directly and with genuine curiosity about what they observe, will tell you things about your culture that your own vantage point can’t show you.
Summary
The culture on your floor isn’t something that happens to you. It’s the sum of what you’ve been doing: the recognition you’ve given and withheld, the gaps you’ve addressed and the ones you’ve let slide, the behavior you’ve modeled under pressure and under calm. It’s been building since your first shift, whether or not you were thinking about it.
The good news is that the same mechanism that builds culture accidentally can build it intentionally. Not through announcements or value statements, but through the same small daily decisions made more consciously, with a clearer picture of what you’re actually communicating.
Start there. Read the culture you have. Then decide what you want to build.
From Theory to Action
Do the recognition audit. Pull up the last two months and list everyone you’ve visibly recognized—in team meetings, on the floor, in a conversation others could hear. Does that list reflect your stated priorities, or just the people who happened to be visible? The people who didn’t make the list aren’t invisible. They noticed too.
Name one thing you’ve been tolerating. Not to beat yourself up about it; just to be honest. One pattern of behavior or performance on your floor that you’ve addressed less than the situation probably warranted. Decide this week whether you’re going to address it properly or whether you’ve made a conscious choice to let it go for now. Either is a real answer. Drifting is the one that shapes culture without your input.
Ask your team leads what the unwritten rules are. Not in a formal culture conversation. Just slip it into a one-on-one: “What do you think people here believe about how problems get handled? What’s the actual expectation versus the stated one?” Listen without correcting. What they think the rules are is the culture, regardless of what you intended.
Watch how your team behaves when you’re distracted. Pick a shift this week and spend thirty minutes occupied with something real: paperwork, a call, a conversation at the dock. Then walk the floor without making a show of it. What changed while your direct attention was elsewhere? That delta is a culture reading.
Trace one behavior back to its origin. Choose something your team does consistently, whether good or bad. A habit, a norm, a default response to a certain kind of situation. Walk it back: where did it come from? If you look honestly, you can usually find the manager, the incident, or the repeated pattern that planted it. That exercise tells you more about how culture forms on your floor than most frameworks will.
Choose one behavior you want to build and commit to modeling it for thirty days. Not announcing it. Not putting it in a memo. Just doing it consistently enough that your team leads start to notice, and eventually start doing it themselves. The debrief habit is a good one if you’re working through this series. But it could be anything: the way you handle a near-miss, the questions you ask when something goes wrong, how you recognize effort that happened out of your line of sight. Choose deliberately, model consistently, and watch what replicates.
This post is the fourth in the current series, building on When to Step In and When to Step Back, The Debrief That Builds Leaders, and Creating Accountability Without Constant Oversight.
Next: How to Raise the Floor, Not Just the Ceiling—why developing your middle performers matters more than investing in your best ones.