Anand Padia

Here's something I don't say often. The best thing I ever built came out of a mistake.

Early in my career, I shipped something I thought was done. It wasn't. Users hit a wall I hadn't seen coming, and for weeks, my team was firefighting instead of building. It was uncomfortable in a way that stuck with me, not because it was catastrophic, but because I realized I'd been so focused on finishing that I stopped watching.

That's the thing about design leadership nobody puts in a job description. Most of it is noticing. Noticing when a team is quietly stuck. Noticing when a "fix" is really just moving the problem somewhere else. Noticing when you're the only person in the room who can see the whole picture, and deciding to say something about it.

Every system I build now, the ones that check themselves before anything ships, the ones that don't need me in the room to keep working, exist because of that one uncomfortable week. I didn't design my way out of that mistake. I just decided never to make that particular one again.