The Four Lists You Never Wrote Down

Every team I have joined had a values page, and not one of them described the team I actually walked into. That is not hypocrisy. Nobody writes a values page dishonestly. It is that the real one was never written at all. It assembled itself out of a hundred small moments where somebody said the awkward thing and it went fine, or said it and it did not go fine, and everybody watching quietly updated their model of what this place is.

So I stopped reading the page and started asking four questions instead. They are not a philosophy. They are a diagnostic, and they take about twenty minutes to run honestly on a team you already know.

// in one breath
  • Four questions that reveal a team's real culture faster than any values exercise, because they ask about behaviour rather than intent.
  • Three of them are pleasant to answer. The fourth is the one that actually holds the structure up.
  • And the uncomfortable hierarchy underneath all of it, which took me a long time to accept.
the instrument

Four Questions, Asked About Behaviour

Here are the four, with the answers I want to be true of a team I am responsible for. Yours will differ, and that is the point: the exercise is worthless if you copy someone else's answers. What matters is that you can state yours, and that somebody who has watched your team for a month would recognise them.

What we do
Stay pragmatic. Spend effort where the value is. Make the trade-offs explicit rather than burying them in an implementation. Say the uncomfortable thing while it is still cheap to say.
What we tolerate
Being wrong out loud. Not knowing. Disagreement that stays about the work. Note that all three are things people are usually punished for, quietly, and that the punishment is rarely deliberate.
What we celebrate
The best idea, whoever it came from. And the person who made their own job unnecessary, which is the hardest kind of contribution to reward because it looks, on paper, like someone doing less.
What we refuse
Blame. Ego. Silence when somebody knew. Selective facts, which is the most respectable-looking of the four and does the most damage.

Read those four rows again and notice the shape. The first three describe what a team reaches toward. Only the last one describes what it will spend something to stop.

the load-bearing one

Refusal Is the Only One That Costs

Doing, tolerating and celebrating are cheap to declare. Nobody argues against pragmatism. Nobody objects to celebrating good ideas. You can put all three on a wall and change nothing about how Tuesday actually goes.

Refusal is different, because refusing something means that at some point a real person does that thing and there is a consequence. The list is not tested when you write it. It is tested the first time the person doing the refused thing is senior, or well liked, or shipping something the quarter depends on. Whatever happens in that moment becomes the actual list, and everybody learns it within a day.

Which is why I pay most attention to the refusals, and why I write them as behaviours rather than qualities. Ego is a word people argue about. Presenting the facts that support your position and omitting the ones that do not is a thing somebody either did or did not do in a meeting on Thursday, and it can be named without putting anyone on trial for their character.

// the part worth keeping

Every team already has these four lists. Unwritten, they get filled in by whoever pushes hardest.

why bother

The Reason Underneath the Instrument

All four lists exist to protect one thing: that bad news travels fast and costs nothing. Not comfort, not niceness. Speed of bad news. A team where problems arrive early and cheaply will out-deliver a stronger team where problems arrive late, every time, because late problems are the expensive ones.

I did not learn this from a book. I learned it running a team that delivered on time and told me nothing, until the things they had not told me stopped being survivable. They were not difficult people. I had made silence the safer option, without ever intending to, and it took me a long time to understand that I had done it. That story is told properly elsewhere and I will not retell it here. The lists are what I built afterwards, so I would never again have to rely on noticing.

The argument for why safety comes first at all is its own essay, and if you have a team of very experienced people who nonetheless tell each other nothing, that has its own failure mode. What I am offering here is narrower and more practical: the four lists are how you find out where you currently stand, before you decide what to change.

the hierarchy

Skillset, Mindset, Alignment

Running this exercise honestly for a few years taught me something I resisted, because it is inconvenient for anyone who likes solving problems by hiring.

Skillset
Teachable. Genuinely. Give a capable person the time and the material and they will get there, and this is the part managers worry about most and should worry about least.
Mindset
Much harder. It moves, but slowly, and mostly by what the person sees rewarded around them rather than by anything you tell them. This is where the four lists do their real work.
Alignment
Hardest of all. Getting a group of people genuinely pointed at the same outcome is harder than any technical problem I have worked on, and I have worked on some difficult ones.

That ordering is why the lists are worth writing down. You cannot instruct a mindset into existence and you certainly cannot instruct alignment. What you can do is be extremely consistent about which behaviours are welcome and which are not, and let people draw the obvious conclusion. Culture is a slow instrument. The four lists are just a way of making sure you are playing it deliberately rather than by accident.

One caution, and it applies to me as much as anyone. The lists will flatter you if you let them. Writing down what you refuse is not the same as refusing it, and the gap between the two is invisible from the inside, which is a specific case of the more general problem that your own judgment is the thing you can least easily audit. So test them the only way they can be tested: ask somebody who joined in the last six months what this team actually tolerates. They still have the eyes for it. In another six months they will not.

Write the four lists. Then watch what happens the first time somebody important breaks the fourth one. That moment, not the document, is your culture, and you will get exactly one chance to decide what it says.

// continue exploring