I have been thinking about the role of an architect in any project. Most
architects are a very smart bunch. They have many concepts that they hold in
their head. They usually have several options for any problem they encounter. This does not
mean that they have to explain that to everyone. I believe that if you have to take more than
2 minutes to explain, conceptually, how the architecture is expected to work,
they have failed to do right by the stakeholders.
I imagine there are several stakeholders to what architects communicate.
- Development team
- Development managers
- Product team
Each of them are looking for assurences that the solution would a) solve and
b) within budget. They usually dont care about the gyrations we went through to come to that place.
The fact that we have explored many options and came up with
an optimal solution, while interesting to other architects, is more often than
not, confusing to pretty much every other constituency.
I also believe that if we are not able to communicate clearly, the onus is on us, as architects, to clean up communication rather than blaming the listener.
Of course, there are applications that might not fit this mold. But such applications likely have stakeholders of similar cadre.
This stream of consciousness is written with Vimpress