November 21, 2018

Architecture without Coaching leads to failure! (Part 3)

BY :     November 21, 2018

The Enterprise Architect as an Enterprise Coach

For the Enterprise Architect to stay relevant in the agile organization it is my view this is achieved by becoming a coach to all the persons and teams in the organization.

A coach in this context I define as someone that

  • provides positive support
  • provides positive Feedback
  • provides positive Advice on improving the effectiveness
  • Inspires
  • Guides
  • Enables contact with topic matter experts

And the enterprise architect should be coaching in the domains people, process and technology.

People, Process and technology are the same domains as we know from the Enterprise Architecture Models  TOGAF, IAF and DYA.

When an Enterprise Architect is not able to coach people, thus not able to help a person to make the step from “Unconscious incompetent” to “Conscious incompetent” and then bring them in contact with experts to evolve to “Conscious competence” then what is the added value of this E.A.? What is the value that an Enterprise delivers to an Enterprise?

A product that the Enterprise Architect in the non-agile did deliver where architecture principles, target architecture, domain decomposition overview etc. But when just a few people in the organization can read and understand these products, and 99% of the company does not read them, let alone does not implement it in a different way of working? What is then the added value? What is the net-result then?

For an Enterprise Architect to become a coach a balancing act is needed

The impact on the new activities of the Enterprise architect are the following;

Not over-thinking a target architecture in contrast to the old role of an E.A..

Find the balance between the knowledge and design that is needed to define the target solution while not overstepping the boundaries of the agile team autonomy.

This balance will be different per person, team and organization.

This implies that the EA should most of the time be coaching key stakeholders so that they can change the people (team) around them so that in an organization with high autonomy and high alignment, the teams move into a predictable direction.

Source:

This balance can only be found when the E.A. is a master in the topics and is able to communicate differently per situation per person. Just as Louis van Gaal.

In summary:

  1. When not focusing on continuous improvement but only focussing in producing a “thing” failure will come to you.
  2. When focusing on continuous improvement then an Enterprise Architect needs to be able to act as a coach of the type van Gaal & Sinek

And the reality is that most current Enterprise Architects will not fit this profile.

Edzo Botjes

About

Edzo Botjes is an Enterprise Engineer with more than 15+ years experience. His believe is that Enterprise Engineering covers not only Enterprise Architecture but also the skills needed to realistically implement innovation, governance and architecture. This implies that Group Psychology, IT Security Architecture, Technology Innovation and Ethics are a few topics that should be included into the developing strategy and architecture. Edzo is currently working on a Blockchain Reference Architecture and separately active as Principal Architect PKI.

More on Edzo Botjes.

Related Posts

Your email address will not be published. Required fields are marked *

6 + 1 =


    *Opinions expressed on this blog reflect the writer’s views and not the position of the Sogeti Group