5 signs of loss of focus

5 Signs Your Enterprise Architecture Team Is Losing Focus

Enterprise Architecture Success Starts with Focus

Enterprise Architecture teams rarely fail because of poor modelling skills, rather they fail because they lose focus.

Successful Enterprise Architecture teams spend their time helping organisations make better decisions and don’t become consumed by documentation and modelling activities that deliver little business value.


Having worked with hundreds of Enterprise Architecture teams over the years, there is a clear pattern we can see to those teams that are successful: they focus.  Whilst this may seem obvious, it is surprising how often EA teams have no real focus, or how they start getting distracted, so lose focus.

As architects, we’re here to add value and help the organisation make better decisions, not to sit in a corner and do ‘stuff’.  We’ve blogged before on defining success, on stakeholder buy-in, on how business outcomes can still be IT focused, and on how distraction can be your downfall, so here we’re homing in on the signs that you are losing focus. If you see these signs, then you really should reassess your priorities, because if you are not focused, you can be sure that people in your organisation will notice, and at that point your credibility is at stake.

Sign 1: You’re Churning Out Diagrams and Documents instead of Business Value

You are primarily creating models, diagrams or documents.  Conversations with the stakeholders are minimal but you have lots of diagrams.

In one organisation we consulted with, we arrived to find that the enterprise architects had spent three years creating an elaborate model of the business.  When we asked why they had spent so long, the answer was, ‘We need something to anchor our conversations on, and it has to be right’. Unsurprisingly, that model was already out of date when they finally presented it. What the team hadn’t realised was that the wider perception in the organisation was that they were an expensive irrelevance.  We soon persuaded them to abandon the model, to check with the CIO what really mattered, and to re-focus their efforts on outputs which helped him to make better decisions.

Any work will almost certainly involve creating artefacts, but if most of your time is spent creating these, then your balance is wrong.  Talk to your stakeholders to work out what their needs are and focus on these.

Sign 2: You’re Trying to Model Everything in the Enterprise Architecture

Closely linked to the above issue and more related to people who use repositories, you are trying to capture and model every process, application, technology, etc, and documenting them in exhaustive detail, regardless of their importance.  You spend most of your time updating the data rather than focusing on real business problems.

Ideally, everything would be captured to create a holistic view of the enterprise, but the reality is that time is limited.  The key is to focus on the information needed to answer today’s strategic questions and to support current change initiatives.  Everything outside of that is just noise and can wait.

Sign 3: You’re Working In Isolation

Look at your workload and who you are engaging with.  Is there little engagement from business leaders, delivery teams or operations teams?  What is your work supporting that would really interest these stakeholders?  If there is little engagement, then your Enterprise Architecture has become an internal function not delivering visible value.

Enterprise Architecture delivers its best value when you are out there collaborating with the stakeholders that matter and influencing decisions.  Start with the CIO, ask them which decisions they need help with. You must also try to embed architecture into planning, investment and transformation decisions. Note, this is not a short-term fix, but should be the target for EA.

Sign 4: EA is Recognised as Valuable, but You are Spinning too many Plates

You have lots of requests coming in and try to service as many as you can; you are trying to keep everyone happy but feel that the key work is suffering; you don’t have time to dedicate enough effort to the work you feel matters the most.  For EA teams that have started to gain traction, this is one of the biggest challenges.  The organisation begins to see value and wants to engage with EA, but you end up getting spread quite thinly.

The skill here is to learn to say no.  Capacity is limited, so you can’t do everything.  The danger is that when you try to service everybody, you end up compromising on the quality of the output.  Our preferred approach is always to push the priority decisions to the CIO, ’We can’t do it all, so what do you want done first, and what should we stop’.  This pushes the onus onto the CIO and ensures that they provide the necessary focus for the EA team.

Sign 5: You’re Focused on the Current State Architecture

We see this quite often. We were once told, ‘We need to understand our current state before we can work out the target state’.  This means that most effort is spent documenting the current state with little attention paid to helping future strategy, investment choices or transformation planning.

You do need the current state, but only where it is appropriate, so rather than spending weeks and months working out what you already have in place to an unnecessary level of detail, you should concentrate on the areas where the information is required. If, for example, a Finance Initiative is planned, then focus on that area’s current state.  You may wish to anchor on business capability models that you can rapidly create up front with some high-level data but leave the detail until you need it.  A contrarian approach, which we quite like, is to create the target state then work backwards to the current state.  You may argue that your target state needs to be guided by your current state, but unconstrained thinking often leads to different perspectives and more innovate solutions, and common sense will often tell you if you are way off something that is achievable.

So, Just Focus

In summary, if your team spends more time documenting than influencing decisions, is not constantly engaging with the change teams or business stakeholders or is spread so thinly that you’re not sure what to prioritise on next, you’re probably losing focus.

  • Enterprise Architecture should enable decisions not just create documentation
  • Spend more time with stakeholders and less time documenting
  • Let the business priorities drive the architecture priorities
  • Lean towards capturing what is needed to solve the immediate problems
  • Success should be measured by value delivered, not volume of documentation

 

Keep in mind that the best Enterprise Architecture teams are not recognised for the breadth and quality of their models, but for the quality of the decisions they enable.

Related Links

What is EA?

 

Quick Reference

Warning Sign What It Usually Means What To Do
Producing diagrams Focusing on outputs instead of outcomes Work from business priorities
Modelling everything Trying to build the perfect repository Capture only what’s needed
Working in isolation Weak stakeholder engagement Spend time with business leaders
Too many requests No prioritisation Let leadership set priorities
Only documenting current state Looking backwards, not forwards Spend more time shaping the future

 

Lead Author: John Mayall – LinkedIn

Contact Us