Leave a system behind

Design that depends on me being in the room is fragile by definition. The work I’m proudest of is the work that kept going – kept growing, kept its logic – for years after I’d moved on. That almost never happens by accident. It happens because the design was built to be handed over.

A real system is three things, and most teams only fund the first. There are the components – the buttons and forms everyone pictures. There are the patterns – the agreed-upon ways those pieces get combined to solve recurring problems. And there is the written record of why: the reasons each choice was made, so the next person doesn’t relitigate a settled question or quietly undo it.

That third layer is the one that compounds. Components without rationale rot into a pile of options; the team forgets which variant means what and starts inventing new ones. Writing the reasons down is slow and unglamorous and it is the single highest-leverage thing a design lead can do for the people who come after them.

The test I hold myself to is simple: can the next person extend this without guessing, and without me? If the answer is no, I haven’t finished the work – I’ve just postponed it onto someone with less context than I have today.