Bill Walsh leadership lessons

Introduction

The standard of performance is not a slogan, it is a list. Where you park, how you answer the phone, what a meeting agenda looks like. None of it wins a game on its own and all of it decides what the team believes is normal.

Walsh took over a team that had won two games and spent his first year fixing things that had nothing to do with football. The record did not move. The behaviour did, and the record followed a season later.

The lesson translates cleanly to software teams. You cannot instruct people to care about quality, but you can decide what a normal pull request looks like, and then hold that line when the quarter gets tight.

The uncomfortable part is that the standard has to apply first to the person setting it. A leader who ships without review has already told the team what the rule really is, whatever the written policy says.

Keep it small enough to remember. Three or four behaviours, written where people can see them, revisited when they stop being true rather than quietly abandoned.

Software and tools

Tooling can enforce a standard but it cannot invent one. Linters, templates and checklists are useful precisely because someone has already decided what good looks like and encoded it.

Where teams go wrong is buying the tool first and hoping the agreement follows. It never does; you end up with a rule nobody chose and a warning everybody mutes.

Other resources

If you are setting a standard for the first time, three habits carry most of the weight:

1. Write down the behaviour, not the outcome you hope it produces.
2. Apply it to yourself in public before you apply it to anyone else.
3. Review it every quarter and delete anything the team has stopped believing.