Two presenters on stage at a TechKnowCon session: a woman speaks from a lectern with a laptop while a man in a Twitter T-shirt stands beside her.

Blog

If It Isn't in the Promotion Case, It Isn't in the Culture

Marko Gargenta

Founder & CEO, PlusPlus

· 4 min read

Share

Intro

At Twitter, we made a rule that sounds backwards to most engineers. The more senior you got, the less your job was to write code, and the more your job was to make other engineers 10x. This applied to individual contributors, not managers. We wrote it into the path to senior and staff.

Then an engineer would sit down to make their case for promotion and hit a wall. The path said: help others succeed. Fine. Prove it.

That wall is the whole story of company culture. A culture is not the values a company announces. It is the behavior a company can see, measure, and reward. If the work you say you value never shows up in a promotion case, it is not part of your culture, no matter what's painted on the wall.

Call it the promotion test.

Why does helping others disappear?

Code leaves a trail. Commits, pull requests, shipped features. Every line has a name on it.

Helping people leaves almost nothing. The workshop you ran. The new hire you sat with until the release process finally made sense. The doc you rewrote so the next person wouldn't get stuck where you did. None of it shows up anywhere.

How you design your rewards is how people behave. Not because engineers are cynical, but because they are rational. If the promotion committee can only see code, smart people produce code. The helping gets done by the few who would do it anyway, on their own time, and it quietly stops when they get tired or leave.

So the company says it values knowledge sharing, then runs a system that pays for knowledge hoarding. Every person on their own, guarding whatever they know that makes them hard to replace.

Isn't making people better the manager's job?

That's the obvious objection. At Twitter, we separated two roles that most companies blur together.

People managers handled hiring, firing, promotions, and all the machinery that comes with a reporting line. A leader is something else. A leader has no carrot and no stick. They earn influence on merit, by standing up and arguing for how we should build code here, how we should do design, and how we can improve the release process.

That distinction is exactly why the work has to be measured. A manager's influence is visible on the org chart. A leader's influence lives inside other people's work. If you don't go looking for it, you will never see it, and what you never see, you never promote.

What does measuring it actually look like?

We started counting. Workshops held. Mentorship sessions. Coaching arrangements. Documentation created from scratch or updated. All the activities that are about helping others, and that a typical organization never tracks.

None of those numbers is a perfect measure of impact. That's fine. The point is not precision. The point is that an engineer can walk into a promotion conversation with evidence instead of anecdotes, and a manager can say yes without it feeling like a favor.

At Twitter, roughly one in five engineers actively contributed to the shared body of knowledge. That is not what you get when teaching is something people squeeze in on their own time.

You can say, culturally, that you promote the people who help others succeed. But if you can't measure it, you can't act on it.

Say it, institutionalize it, operationalize it

Building a culture deliberately takes three steps.

Most companies do the first one well: they say what they want. Values decks, all-hands slides, the poster in the kitchen.

Fewer do the second: they institutionalize it. They write it into the career ladder, so it is officially part of how you get promoted.

Almost nobody does the third: they operationalize it. They build the system that makes the behavior visible, so the written rule is something a real person can use in a real promotion case.

Each step without the next one is theater. A value with no rule behind it is a slogan. A rule with no way to prove you followed it is a slogan with paperwork. Just saying it doesn't do the trick.

Why does this matter more now that AI writes the code?

For years, you could get away with a culture that rewarded output over sharing. Output was scarce, so paying for it made sense.

Output is no longer scarce. AI will write the code. What it can't supply is judgment, and judgment comes from experience that mostly was never written down. AI is trained on your documents. A new hire onboarded on your documents knows roughly the same things. The senior engineer is the one who knows what's missing from both.

That knowledge is now the edge, and it only moves out of a senior engineer's head into juniors, into the team, and into your AI if that person has a reason to move it. Generic AI plus generic knowledge gets you generic output. The knowledge that makes your company different lives in the people who have been there longest.

If your promotion system still rewards output over sharing, you are paying your most experienced people to keep their best knowledge to themselves, at exactly the moment it became the most valuable thing you have.

Your culture is whatever shows up in the promotion case. Everything else is a poster.