EA

Enabling Transformation of your Business Platform: Enterprise Architecture for Hybrid Cloud World

Alistair Russell · May 12, 2021 · Leave a Comment

Back in 2016, we wrote an insight piece discussing the role of the Enterprise Architecture (EA) capability of an organisation in designing and delivering the architectures for future cloud environments, the pitfalls and some of the phony thinking that was touted at the time. The original article entitled “Cloudy Day” is available on request from Laing Russell. Prompted by listening to Peter Weil from CISR (Centre for Information Systems Research) at Massachusetts Institute of Technology (MIT) talk about their recent research on most effective strategies for “re-platforming” enterprises, we went back to the original “Cloudy Day” piece. Reviewing that five year old piece, it was interesting to note what’s changed and what’s endured. Especially as our work on strategy and enterprise architecture is increasingly focused on enabling the development of a digital platform for organisations. Digital platforms that make the most effective use of cloud capabilities.

The cloud industry is slated to grow from $371.4 Billion in 2021 to $832.1 Billion by 2025 according to the latest analyst’s figures. Back in 2016, we were predicting 36% pa growth from a $13.3 Billion starting point. By our calculations that 36% pa growth rate would have put us at about the $62 Billion mark in 2021, so we have comfortably outstripped that growth metric. AWS, Azure and Google Cloud Platform are now the market leaders and there other players in train as well. However, the majority of organisations are embracing hybrid architectures, adopting some cloud-based services across the landscape from IaaS to SaaS. Five years on, it is still the minority that are entirely cloud resident.

One significant shift in the narrative from 2016, is the move away from a cost-based benefit case for adopting the cloud to a benefit case based on business agility, flexibility and elasticity. The cost reduction argument was always a false narrative. Many organisations, to their peril, have fallen prey to the salesmen’s patter and ended up with higher running costs in the “cloud”. We have been involved in several turnaround initiatives where unpicking a simplistic rush to a ‘cloud nirvana’, has proved expensive, complex and time consuming. Today, we are all more acutely aware than ever that the hybrid architecture needs to designed with a clear-eyed view of how different aspects of the cloud environment enable value, reduce risk and at what cost. Once strategy, design and implementation path are set out they need to be governed tightly. An outcome of this shift is that quality vendors now offer multi-year payback schedules to justify the investment in the transition.

As more organisations look to transform to deliver value as a platform, their operating models are evolving such that value is delivered by an eco-system that extends beyond the traditional organisational boundaries. These operating models require a new level of engagement by organisational leaders in setting and governing digital strategy and architectures. For example, flexible integration and API management strategies are transformational utilities in their own right. However, if poorly architected they can become contributors to technical and organisational debt through design ‘cul-de-sacs’ and in-efficient processes. We are finding that EA needs to support the organisational leadership in being aware of the benefit opportunities and risks. EA are using new collaborative processes to produce design artifacts, with the associated commitment based on understanding, that will deliver for the organisation and its stakeholders.

Back in 2016 there was a greater scarcity of expertise in cloud technologies than there is today. The increased understanding of the “cloud” has helped ensure we have better technical architectures in this constantly developing environment. But organisations are still dependent on the strategic perspective that the EA brings. EA is as necessary as ever. EA helps make explicit that vital link between your hybrid cloud services and your organisation’s business strategy.

Micro-standards Enabling Pace and Agility

Alistair Russell · September 17, 2020 · Leave a Comment

An enduring dilemma for organisations is setting and holding their position on standards. Standards good vs. standards bad can and often does become an unhelpful debate. The focus can be on the narrative of the standard itself rather than the outcomes that they promote. This dilemma has many specific challenges in our work with clients as it impacts their ability to get the best value from digital technologies.

Current, critical complications are evident in many areas. These areas include: what the specific technology is able to do; the range and flexibility of business models for how that technology can be provided; what customers need and the ways that organisations deliver on those needs; notwithstanding the implications of the current disruption to where and how work is delivered prompted by the Covid 19 pandemic.

These complications and many others mean that there is not, and probably will never be, an axiomatic truth. Whilst recognising that the right place on standards for you and your organisation is and should be contingent, we do recommend moving to having a set of what we would call micro-standards. In our work on digital strategy and the development of Enterprise Architecture capability, we are concluding that rather than universally mandating a specific software solution or platform we recommend setting standards at a lower, micro, level in the hierarchy. Micro-standards that should ideally fit within an overarching architectural and operating framework.

We see this as a more effective and productive approach than taking time deciding for example, whether or not strategic business units are able to choose the “best” software for their needs or if a standard ERP should be introduced across the whole enterprise or having a programme of work to ensure that there is single, trusted view of the organisation and its performance for the Board.

We recommend that micro-standards should be developed within each of the five key architectural domains of busines, data, solution, technology and security based upon sound guiding principles. For example, in a ‘cloud first’ world, if your organisation has a principle dictating single-cloud as opposed to multi-cloud, then your business units can work within this standardised environment provided to rapidly implement change, whilst you can be comforted by the knowledge that they will not be building anything that fails to interoperate with the existing infrastructure. Noting that governance behaviour and process need to ensure the right standards are set and complied with.

The business benefits of standardisation are well rehearsed. Technology provision costs are lower with standardisation, standard software allows digital technology teams to focus and spend less money and time on integration; standard processes enable resources inside and outside your organisation to be more flexible. With the addition of micro-standards organisations can meet the needs of customers at pace. Rather than restricting innovation, micro standards enable the flexibility required to assemble and disassemble building blocks efficiently. You know they’ll fit together, you know the way that the process will be coded, tested and put into operation.

Build it and they (probably) won’t come

Alistair Russell · August 28, 2020 · Leave a Comment

With apologies to the scriptwriter of the Field of Dreams. Whilst the film is an enjoyable watch, that well-known quote from the film is just not true. No matter how great ‘it’ is, people will probably not ‘come’. Just because it’s there. Just because you built ‘it’.

Designing and building the best solution is necessary, but it is not sufficient. Designing and building the right things will never be enough. In whatever context, we need to build the right solution and engage with others. We need to market and sell, too.

Working with clients and indeed in getting started with Laing Russell, we’ve been reminded of how important it is to market and sell. How important it is to work with clients to work through the design and development of the right strategy, business case, operating model and structure. enterprise architecture, governance model or implementation plan. And how critical it is to build support to make it happen at the same time.

We notice and have to remind ourselves of the need to invest time and resources in engaging with and communicating with others. Maybe it’s because we tend to have design focused, solution development brains that are motivated by and are arguably skilled at getting to the best answer to a particular set of complicated challenges. Maybe it’s because our preferences are to work things out or make sense of the world. For whatever reason, we know that if we are going to deliver the right outcome we have to sell our great solutions to relevant stakeholders. We have to identify and connect with them. We need build their confidence in our capability to deliver value. Or, in terms we first picked up on service quality study tours to Disney years ago, we have to ‘manage the show’.

In our experience, the first step is to give yourself and your teams the time and the tools to manage the show. Value engagement with stakeholders as highly as getting the right answer. Clearly, provide direction, provide resources, coach and manage in a traditional sense to ensure everyone can deliver. Additionally, we recommend concentrating on three key areas:

get clear on the outcomes, in terms of what you want key stakeholders to think and feel alongside the classic sales analysis ideas of understanding their ‘needs’ and ‘wants’ and their relative significance in delivering the optimum solution for your organisation;
work super hard at simplicity, simplicity of message and method of communication and engagement;
keep learning, reflect on the outcomes from what you and your teams do, ask for the gift of feedback, keep developing your practice, keep testing yourself, keep trying new approaches.

We would value hearing what you have learnt in managing the show. What do you find works well? What tools do you use? How much time is enough?