Culture is designed, not inherited

A few months after we closed an acquisition, I sat down with the engineering leaders we’d inherited to go through the roadmap, and the roadmap was a graveyard. Features we’d promised customers, features the deal had partly been sold on, sat quarter after quarter in the same column they’d started in. Nearly all of the team’s capacity was going into security work. Not a security incident. Security work: hardening, remediation, reviews, an endless conveyor of it, consuming almost everything.

So I started asking about priorities, which I thought was a neutral question, and I watched the room change. Voices tightened. People talked over each other. An engineer I barely knew was suddenly explaining, with real heat, that maybe some people didn’t understand what was at stake. Somebody else went silent in the way that’s louder than talking. I asked what I thought was a scheduling question and got back something closer to grief.

I walked into that meeting expecting a people problem, and I want to be honest about the specific shapes I expected, because the catalog is embarrassing. Acquired-company resentment. A leader protecting an empire. Engineers hiding from hard commitments inside righteous work nobody can criticize. I had the villain sketched before I sat down. All I had to do was find him.

I kept pulling the thread, meeting after meeting, and there was no villain anywhere. There was an absence.

No shared prioritization process existed. None. There was no agreed way to weigh a security investment against a customer commitment, no forum where that tradeoff even had a place to be argued, and underneath that, something more basic was missing: any common statement of where the organization was going. Not a bad strategy. No strategy, in the sense that nothing was written down that two people could stand in front of and point at while they disagreed.

And once you see that absence, the emotion in the room stops being mysterious. When there’s nothing external to point at, pointing is all that’s left, and people point at each other. Every tradeoff conversation becomes a referendum on the person making the argument. Question the security workload and you’re not weighing risk, you’re calling someone irresponsible. Push for the customer features and you’re not defending a commitment, you’re revealing you don’t care if the place burns. These engineers had inherited a pile of real risk and no framework for saying how much was enough, so they’d defaulted to the one workload that no one could ever fault them for. The most defensible work, infinitely. It wasn’t obstruction. It was shelter.

The turn for me, and it took longer than I’d like, was realizing the thing I’d been calling a people problem was a systems problem wearing people’s faces. Nobody in that room needed coaching. The organization needed load-bearing structure that simply wasn’t there, and every argument was the sound of humans compensating for its absence with adrenaline.

I’ve come to hold a stronger version of this than most leaders I compare notes with, so let me state it plainly. Culture is designed, or it’s decided by whoever is loudest. There’s no third state. Every organization has a culture; the only variable is whether anyone chose it. Leave it implicit and you haven’t kept it neutral, you’ve delegated it, to the most certain voice in the room, to the oldest habit, to whatever behavior survived the last reorg. Silence is a design decision too. It’s just one you made by default, and the loudest person thanks you for it.

The inherited-culture story leaders tell is comfortable because it makes culture weather. It came with the acquisition. It predates me. You hear it in the passive voice, culture as something that happened to the org chart. I don’t buy it, and that meeting is why. What we’d inherited wasn’t a culture of defensiveness. We’d inherited a vacuum, and defensiveness is what grows in a vacuum, reliably, like mold in a damp wall. You don’t argue with the mold. You fix the wall.

So that’s what we did, and the fix was almost offensively unglamorous. We wrote things down.

We built what I took to calling a leadership playbook: the expectations of every leader in the organization, in writing, specific enough to argue with. Where we were going, what got weighed against what, how a tradeoff got made and in what forum, who owed whom what. Then, and this is the part I’d defend in a fight, we embedded it where the org actually generates behavior. Into job descriptions. Into the structure itself, into how roles bordered each other and where responsibilities overlapped on purpose. Collaboration outside your formal role stopped being a virtue we hoped for at offsites and became a stated expectation of the job, written into the job, the way uptime is written into an SRE’s.

A word on how it got written, because the how turned out to be half the point. I didn’t draft the playbook and hand it down, though the version of me from a few years earlier absolutely would have, and it would have joined the long history of laminated values nobody reads. We built it with the same leaders who’d been shouting at each other, in sessions where the rule was that we were describing the system’s failures, not anybody’s. That framing wasn’t decoration. The whole premise was that the vacuum had done this, not the people, and the drafting process had to embody the premise or nobody would believe a word of the output. It also meant that when the document later absorbed a hard conversation, it could, because the people in the conversation had written it. You can’t point at a document that was pointed at you.

That last one matters more than it sounds. Every company says it wants collaboration, and almost none of them writes it into anybody’s actual role, which means acting on it is charity, and charity is the first budget cut when a quarter gets hard. The moment it’s in the job description, the conversation changes shape. You’re no longer accusing a colleague of being a bad partner, which is a fight. You’re reading a sentence you both agreed to, which is a meeting. The document absorbs the heat so the people don’t have to. That’s what the document is for. That’s what all the documents are for. An org chart, a job description, a prioritization forum: they’re heat sinks. The engineers weren’t angry because they cared too much. They were angry because caring had nowhere structural to go.

The underlying principle, and by now it governs almost everything I do in a new role, is: build systems before solving problems. Which sounds obvious and is the opposite of what ambitious leaders are trained to do. The trained move is to solve the visible problem, visibly. I could have walked out of that first meeting and mandated the roadmap. Sixty percent to features, effective Monday, thanks everyone. It would have felt like leadership. It would have photographed like leadership. And it would have solved that quarter’s standoff while guaranteeing the next one, because the vacuum, the actual problem, would still be there, now with a precedent on top: tradeoffs here get resolved by rank. I’d have become the loudest voice, which is to say, the culture.

Instead the security question got resolved almost as a side effect. Once a written strategy existed, once there was a forum where risk could be weighed against commitments in the open, the team sized the security investment against something instead of against nothing, and it settled into a defensible, bounded share of capacity. Nobody capitulated. Some of the promised features finally shipped. The engineer with all the heat in that first meeting turned out to be one of the best systems thinkers we had, once there was a system to think inside of, which I should sit with longer than I usually do, because I’d had him cast as the villain.

The change I actually watch for came later, though, and it’s the one I’d tell you to watch for. The tradeoff meetings got boring. People came in, pointed at the document, disagreed about the document, amended the document occasionally, and left with their relationships intact. All that adrenaline, gone, replaced by paper. I understand that boring meetings don’t make anyone’s leadership highlight reel.

I’ve never been prouder of anything that boring.