Four Lessons From a Week on a New Platform

I spent last week deep in a new agentic AI platform. The lessons that stuck had almost nothing to do with the technology. I’ve been leading engineering teams for a few decades now, so I should have expected that. Every time I take on something new, I tell myself this one will be different, that the hard part will be the code. It never is. Map the people before the architecture Most of my week went to a question that sounds trivial and isn’t: who actually owns what? It came up in an incident review. It came up again in a release quality discussion, and again at the kickoff for a new product. Same question, three different rooms. So I traced ownership across teams and time zones, sat in on org structure conversations, read an architecture decision doc, and spent real time on recruiting. Almost none of it involved reading code. It’s tempting to open the codebase first. Don’t. A platform is a people-and-systems problem wearing a technology costume. If you can’t name the owner of each…