"When Code Becomes Real"
What does accountability look like? Sometimes, it’s just a small pause. Back when we had a carefully managed release process, code changes would pile up over the week. On release day, the release manager took charge, while the authors of those changes were almost invisible in the process. Their code shipped, but they felt none of the weight. So we tried something simple: before release, each author had to give their own change a green tick. Just a quick “yes, I’m happy for this to go live.” It wasn’t about compliance. It was about creating a moment of reflection: Would I put my name to this? Do I stand behind it? That tiny gesture shifted the mindset. Responsibility wasn’t somewhere “out there” in the process anymore, it lived with the person who wrote the code. Sometimes change starts with a big system redesign. But other times, it begins with a single tick. Until next time, ✉️ Enjoying The Messy Middle? If someone sent this email your way and you’d like to get it direct, you can sign up here. |