…or is being a Solution Architect akin to being in the diplomatic core? I find myself wondering sometimes what is the greater challenge – negotiating world peace or achieving consensus across differing technical disciplines?
I have been fortunate to work with a range of very knowledgeable technical specialists and subject matter experts and my conclusion is that with deep knowledge comes deep convictions. Navigating the choppy waters of what is the technically superior solution vs. what is the best solution for the business can lead to some very impassioned debates.
Before the time of Docker (makes me really old) my early views of solution architects were they just drew boxes in Visio, were unable to have a meeting less than 4 hours and had acres of time on their hands as they produced endless documentation.
From the other side of the fence I have come to realise that I have a mild addiction to write on walls and that there is power in those boxes and documents. Once something is written down people can talk around it, those boxes drive discussion and aid comprehension. The design documents provide context and a place to explain why a decision was made at that point in time.
As DevOps adds fuel to the Agile fire I find myself relieved that the amount of required documentation has been slashed, yet those scrums need direction, the business needs to understand what it is splashing its cash on – so the Visio boxes and decision logs live on with a lot less fluff around the outside.
In the fast moving world of DevOps those diplomatic skills that I started this post with become ever more important. You need to take time to understand your stakeholders: What are their concerns? What motivates them? How do they view their colleagues? You also need to keep laser focused on the Business drivers and the outcomes that deliver those drivers. Balancing the needs of the Business against the needs and wants of your stakeholders whilst still delivering outcomes – that’s the trick, perhaps World Peace would be more realistic.
Please note this post was originally posted on LinkedIn
No Comments