Practically, software architecture is about making certain you have as few tools as possible, to do a job, with the flexibility to accommodate other tools, when necessary. Documenting standards, exceptions, rationales and the alignment of the parties that hold an interest in the decisions is also a benefit of architecture.

What that looks like, practically speaking, varies from company to company. However, you do have to achieve a significant level of size and complexity for this function to make sense. If you're saying that architecture, in some form, doesn't make sense in an organization, I'd challenge whether the size or complexity of that organization has reached the threshold.