6 years, 9 months ago

Are you an Architect or an Engineer or a Technician?

A few days ago I had posted some thoughts about relationship between an Architect role and an Engineer role. I had referred to the Zachman Framework to explain the trade-off and dependencies in these two important role profiles. The beauty of Zachman Framework is that it does not stop at explaining only dynamics at the Architecture level but it seamlessly connects both the Business Consumer and the Technology Implementer perspectives in a simple single framework. 

Please see the simple illustration from Zachman Framework below. At the heart of below picture is the dual-relationship of an Architect role profile and the Engineer role profile as I had outlined in my previous blogpost. The Technician perspective is an interesting one and an important one. I state this because it is at the Technical perspective that the Business and Operating Models chalked up by an Architect are realised. I think that a good mature CIO or IT department has to consider the architecture in totality and offer capabilities across this spectrum. 
Architect Engineer & Technician Perspectives from Zachman Framework
All Copyrights with Zachman International
The key question of this post is, who do you think you are? Are you an Architect or an Engineer or a Technician? I suppose the answer depends on a number of factors; your organisation design, it’s operating model, your own skills and capabilities. Just to give an interesting example, I used to work for a CTO who used to say, “Give me a programmer over a process engineer anyday”. What he meant was, he would rather deliver better results faster working at the Technician level rather than working at the Architect or an Engineer level. 

I am not stating that his perspective is right or wrong but the point I am trying to make is having awareness of these different perspectives is important. An organisation and individuals who identify and respect these perspectives will be progressive and will make a positive difference to their business by dynamic delivery capability. What probably my CTO meant then was, he would rather work with an architect who was not shy to roll up the sleeves and perform the role of an Engineer or a Technician. Do such architects exist? This is a rare breed in my experience. 

The first, second, third and now fourth generation outsourcing models add an interesting dynamics in this discussion. For example, if a large Retailer or a large Bank outsources it’s Data Centre Infrastructure and Operations to a Technology outsourcing supplier, would you call them as your Technicians? Probably yes, if you also give away your key Technician resources. Probably no, if you keep them in-house keeping an oversight on your supplier. 

As an individual an Architect or an Engineer needs to think about his / her role and capabilities within the organisation. The CIO, CTO or the IT leadership needs to think about range of capabilities they need to invest to make a positive difference to their business consumers. You can have many labels and titles if you like but what matters is understanding and delivery of Architect, Engineer and Technician perspectives. As an operating model an organisation may choose to keep these capabilities in-house or outsource them but as long as it recognises and manages their delivery, they will meet their objectives successfully. 


References used in this blogpost for further reading and credits