Reading books such as “The Process of Software Architecting” you will see statements such as “architecture focus on significant elements” a lot. Given my recent experience I can’t tell you more how important this is! Therefore I thought it’s worth posting a bit from my recent experience…
Of course, as architects we cannot focus on every tiny little detail – so we have to decide for ourselves, how deep we want to go in terms of influencing solutions for solving problems. Depending on the level of architecture (enterprise, solution/application, technical) you’re dealing with that might be very different. Also the goals you’re trying to achieve will influence what is significant for you in your specific project and/or organization, of course.
Generally speaking, some examples that are “significant” for me and where I try to be involved as an architect are the following ones (please note, these are examples from my recent experience and by no means a full list of things):
All of the above are just examples I had to deal with in the past year since I am in my new role, and of course they can differ with every project and organization. All of this helps me both, to be an effective architect (hopefully) and to save my energy for the really important things (instead of wasting it for discussions that are just not worth it). Also I know it is hard to find out, if something is really significant… but I think that’s one piece of our job that we HAVE TO do… and it makes it really interesting, by the way.