Why I call it architecture

I didn’t set out to call myself an architect. It sounded too grand for what I do. But I kept noticing the same thing about how I work: I reach for the whole thing, not one piece of it. I want to know how everything fits before I care about any single part.

For a long time I didn’t have a word for that. Architect turned out to be the most accurate one, so I stopped arguing with it.

Builder, designer, engineer. Those are the crafts that make a thing real. Architect isn’t a rank above them. It’s the responsibility for how they fit together, and for whether the result is any good to be inside of.

That’s the part I keep gravitating to. The way the pieces add up, not any one of them on its own.

What changed is the material. Architecture meant buildings because a building was the biggest thing one person could shape. Now a lot of what people use every day is software, and AI has pulled back together the work that specialization once split apart. More and more I’m the builder, the designer, and the engineer, and still the one holding the whole.

Most of what I build is invisible. A banking app, a trust profile, a service someone moves through without thinking about it. Those shape how people decide and who they trust, which is why they’re worth building carefully. That’s the shift that made me take the word seriously.

Calling any of this architecture can still sound like reaching. Product architect is already a title, and it means different things everywhere. I’m not trying to standardize a job. I’m trying to name how I actually work, and to keep working that way as the tools change.

Architect is the part that lasts. Product is just where I’m applying it now. If the work outgrows product, the way of working comes with it.