Some years ago, an old friend of mine – a fellow software developer – said something that stuck with me: “The most useless person on a team is an architect.” He believed that architecture¹ is just done, not a specialized skill.

At first, I agreed. After all, we’ve been building software for decades. We have established patterns, best practices, and a good understanding of how things work. Most of the time, choosing an architecture for a web application, for example, feels like following a flowchart².

Lately, I’ve realized that the problem isn’t architecture but how we approach it. We often jump into technical details without asking the crucial question: Why?

We get so caught up in how to build something that we forget why we’re building it in the first place. This is where “architecture”(2) fails. It becomes a box-checking exercise, a choreographed dance of applying the “correct” patterns and diagrams.

But here’s the thing: architecture is more than just boxes and arrows. It’s about more than just documenting the system’s structure or creating intricate schematics to meet esoteric compliance standards a gatekeeper sets. At its best, architecture is not a tool for communication but a catalyst for collaboration.

Think of it as a toolbox for creating a shared understanding. An excellent architectural work facilitates discussion, clarifies goals, and helps everyone involved move in the same direction. It bridges the gap between technical details and business objectives, ensuring that the “how” aligns with the “why.”

We lose sight of its true potential when we reduce architecture to mere compliance. Instead, it can be a platform for innovation, a bridge that connects ideas and solutions. Let’s not create barriers but bridges, and let’s not stifle innovation but foster it.

To fix this, we need to change the conversation. We must move beyond the technical intricacies and focus on the bigger picture. We need to ask: What value are we trying to create? How does working on the architecture support our business goals? Who are the stakeholders, and how can we involve them in the architectural process? How can we use the architecture process to foster a shared understanding and drive better decisions?

When done right, architecture is a powerful tool for alignment, communication, and, ultimately, success. It’s not just a tool, it’s a mission. It’s high time to reclaim its true purpose, to unlock its full potential, and to make a difference in our projects and our industry.