Sometimes everything seems to be Architecture...

Recently, I am observing more and more issues in our company being attributed to architecture. It seems to me that every time when something pops up with significant effort or risk associated with it then people tend to attribute the issue to missing architecture.

Maybe they are right but I have strong doubts. Of course, there are such terms as architecture smells and the like. It is also right that a widely used definition of architecture says that it is an architectural issue if it is costly to change afterwards.

But consider a service being prepared for production that is suspected to drive production ressources to its limits. In my opinion this is an issue of capacity management and ressource planning in the context of the service's development project, respectively. If there are failures in these planning processes surfacing then it is illigitimate to call a missing or an incorrect architecture the root cause of the suspected problems.

Nevertheless, it might be that ressource usage or other details of the project have to be subject to an architectural review. But that is a whole different story...