The mistake of starting with technology
Every week, in some company, someone opens a technical meeting with the wrong question.
It is not about the problem. It is not about the customer. It is not about the expected outcome.
It is about the stack.
"Should we use Kubernetes?", "Should we migrate to microservices?", "Which framework should we adopt?". The discussion starts with the tool before there is any clarity about the problem. At that point, the destination is already set.
The tool is not the starting point
When an initiative starts with technology, it is already contaminated.
The team optimizes for the tool, not for the outcome. Decisions get made based on previous experience, personal preference, and market hype, not on real need.
The final product is technically coherent. But it solves the wrong problem. Or it solves well a problem that should never have been solved that way.
That is not a technical failure. It is a sequencing failure. Starting with the tool means skipping steps that cannot be skipped.
Three questions that should open any technical initiative
Before any technological decision, three questions need clear answers:
Why does this need to exist? Who does this matter to? Which business metric is supposed to change?
If there is no objective answer to all three, the initiative is not ready to start. That is not bureaucratic blockage. It is protection against waste.
The right technology for the wrong problem is still a mistake. And usually an expensive one.
The real role of the architect
An architect who does not ask these questions is not doing architecture. They are executing complexity.
Architecture does not start with the diagram. It starts with understanding the context: how the company operates, where it loses efficiency, which outcome needs to be achieved, and why it matters now.
When that understanding exists, the technology choice stops being a bet and becomes an informed decision.
The tool comes after. Always. No exception.
What changes when the order is right
Teams that start with the problem arrive at simpler, cheaper, and more effective solutions.
Not because they avoid sophisticated technology. But because they only adopt sophistication when it solves something that cannot be solved in a simpler way.
The question that should open every initiative is not "which technology should we use?". It is "which problem do we need to solve, and how do we know we solved it?".
Whoever answers that question first gets to the right place faster. And spends much less along the way.