AI is getting remarkably good at the HOW. It can generate code, propose architectures, compare design patterns, and automate implementation.That’s exactly why architects need to become even better at the WHY.
If I could rename the role, I’d jokingly call it Problem Architect instead of Solution Architect. ๐
Not because solutions aren’t important, but because architecture begins long before the first solution is designed. It begins with understanding the problem, the business context, and the trade-offs that define success. A Solution Architect focuses on how to solve a problem. Great architects first ensure everyone understands why that problem is worth solving. The best architects do both – but the order matters.
This isn’t a new idea. Some of the best-known software architects have been saying this for years:
๐ Mark Richards & Neal Ford (Fundamentals of Software Architecture) captured it in their Second Law of Software Architecture: “Why is more important than how.” Their point is that anyone can eventually understand how an architecture works. The real challenge is understanding why architectural decisions were made, because every trade-off is driven by business goals, constraints, and context
๐Michael Keeling (Design It!) takes this a step further by showing how architects should approach design itself. Before evaluating technologies or architectural styles, architects need to understand stakeholders, business goals, constraints, and quality attributes. In other words, architecture starts in the problem space before it moves into the solution space
๐Gregor Hohpe (The Software Architect Elevator) describes architects as constantly riding the elevator between the penthouse (business strategy) and the engine room (technology). Architects create value by translating business intent into technical decisions and technical realities back into business language
๐Vlad Khononov (Learning Domain-Driven Design) argues that effective software design starts with understanding the business domain. Without understanding the problem space, it’s impossible to design the right solution
The more capable AI becomes at the HOW, the more valuable architects become through the WHY.
โข Why this problem?
โข Why now?
โข Why this approach?
โข What outcome actually creates value?
Those questions require curiosity, empathy, context, and judgment. They are what turn technical expertise into architecture.
So before jumping into diagrams or technology choices, ask one question first:
๐ช๐ต๐ฎ๐ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ ๐ฎ๐ฟ๐ฒ ๐๐ฒ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐๐ฟ๐๐ถ๐ป๐ด ๐๐ผ ๐๐ผ๐น๐๐ฒ?
Perhaps great architects have always been Problem Architects first – understanding the WHY before designing the HOW.
โDo you think architects spend enough time on the WHY, or are we still too focused on the HOW?
Originally published on:ย Post | LinkedIn