Tag Archives: digital governance

  • -

Digital governance & agility – getting it right this time!

Category:Uncategorized Tags : 

According to both Gartner & Mckinsey that statistics state more than 75% of the agility and digital transformation projects fail. Going through the details, it is also noticed that many still believe these transformation programs could be solved by applying EA tooling or BI tooling. However, these technologies are quite different in filosophy, and there are certain shortcomings and limitations of using using this type of tecnique to solver such programs:

  1. The BI “approach” is typically led by financial people and with a reporting perspective; nothing wrong with this, but it is just very different from the agenda of providing large change, interactions and planning. If you try to fry using a pot rather than a pan, it will take longer, and with a lower chance of success.
  2. However, what about the magic quadrant of EA Tools then? Quoting one of our customers, “EA Tools are like lemons, sour and very hard to eat on their own” … The magic quadrant seem populated with tools that have a very narrow view of enlightening the architect herself/himself that puts effort into modelling. How can that in any way help the corporate agility?

 

“Agility is the ability to change direction at higher pace, it is not about the speed!”

 

Agility is the ability to change direction at higher pace, it is not about the speed! For a company to be agile, it needs to provide a foundation where people share an understanding of change, and eventually, share the interest to change course when needed. This is partly culture, partly getting people to buy into to the strategy, often helped by a digital platform to help building a digital governance of managing the business processes, systems, and offerings.

As humans we encourage people to be proactive, thinking, questioning, – however – it also means if we don’t all buy into the strategy or direction, we will act differently as individuals. For a company to succeed to change course at a higher pace, we need to promote the idea and federate the updates –  and every day! Managing the agility is about carrying out many small steps where people can relate and buy into the updates of helping the bigger enterprise with transparency and regular feedback.

So almost paradoxically, what agility means at a corporate perspective is that we need the shared value of helping each other to federate updates and insight to make a company agile, by this, removing some of the individual freedom to avoid new ad-hoc ways of doing stuff. This is a very different perspective than to allow a few architects to analyse and build models on their own. Agility is about getting to the digital platform where decisions and changes can be made faster, with lower risk and based on federated input; otherwise the platform is just for architects, and then you can have a look in the magic quadrant: how to fail yet another time…

Now, as an example… an old one: “What is an application?”. As simple as the question is, who is interested in the answer? Why do we need the answer? How would we as a company ever get to the answer?

To answer it partially, we would advise you to take the enterprise perspective, that if users and people of the organisation cannot see the “calculation” and updates of what we believe is an application, you will never get to more than a point-tool perspective, so in an agile context, you will fail. If your approach is to model it for the architects, using a tool only the architects can handle, please look for the bin!

Back to the former question, applications can only be of relevance if they relate to the processes, the inner game or outer game of the business planning.

  1. If in context of the outer game, it is relevant to carve out what to shut down, what to procure to deliver the new business model – this is the sweet spot of corporate agility where the business model is transformed into a new form.
  2. If the inner game, then we talk efficiency or changes to way of working, then operational efficiency and processes are the sweet spot where business is being digitized.

If you ask in your organisation, the business leaders might say we have a few systems, if you ask the IT managers, they may say many processes, so many applications, and if you meet people from IT Operations, they have their own definition, and they say approximately 20 per device. To solve such a simple question with a modelling tool will not succeed. The entire wrapping of use-case, interaction and planning is required, and it is often motivated by having a label on that wrapping called “agility”, where the benefit of classic EA tools and BI technology seem limited.

The technology required to build the digital platform for improving the agility requires a flexible model, that can be changed again and again over time. It also requires people to use the outcome, daily, every day by loads of people to get the metadata correct. And it needs to look like the corporate web portal with colours, fonts, etc. to get the attractiveness that people buy into.

If you are in doubt on how to build a digital platform in order to succeed with the digital governance and agility, try to look at the organisational usage, then identity the interactions and flexibility. Try to avoid pre-built one-size-fits-all solutions, we mostly see that the can demonstrate value only on the first mile. With the right collaboration, each employee or team is accountable for their own part, they like to contribute to the bigger picture, and the management can avoid attachments and PowerPoints. This is what digital governance is all about.

In practice, this also means the digital platform will be a combination of human input, and online data like CMDB data (Cherwell, Service Now, etc.), PMO data (Project Server integration, or similar), people data (AD or HR data), finance data (SAP, etc.). A modern digital platform is where decisions and agility moves can be made from – it pulls the data into the single source of connected insight.

If you bring your old tool, we can help you with the bin and the new approach.

We power your digital MooD!


  • -

Start your digital service integration – introducing SIAM

Category:EA,UK Blog Tags : 

As we force ourselves into even higher gears of technological innovation, the trend in the market is to move closer to multi-sourcing and high-end services from best-of-breed suppliers; e.g. one supplier might be good at delivering People Performance Management, while another provider is excellent at providing Information Management. So instead of outsourcing all infrastructure and databases to one supplier, it may be attractive to partner with that vendor, who is e.g. leading in cutting edge solutions to People Performance Management and Information Management –  including all operations, maintenance and development.

For the organisation procuring such services from still more high-end providers there is a challenge of how to succeed with the management and administration of services, which doesn’t necessarily fit with each other. How to manage the multi-sourcing setup providing insight and accurateness of the information management of the different service providers.

The term to manage the multiple vendors to provide consistent services to the end-users is denoted Service Integration and Management (SIAM). The objective is to provide a single business-facing IT organisation, however, as these vendors deliver different types of services, the term services often gets blurred in discussions – and can often be quite different things! Hence, there is a pitfall in trying to establish a huge services framework as a theoretically based exercise. To succeed, we recommend building the services step-by-step as the digital governance is established in the  living architecture.

According to the research paper by Goldberg et al, SIAM is the discipline to procure and blend services from multiple external and internal providers. As the SIAM management eventually will have a cost, and the best-of-breed providers may be hard to compare with more traditional outsourcing providers, there may be a challenge on cost.

Many clients face different issues implementing and getting the SIAM layer to perform satisfactory. Simply to succeed with SIAM, the organisation needs to understand the architectural structure of the IT landscape, and how it is managed by delegating accountabilities of a digital governance. However, the main pitfall is still that most stakeholders are reluctant to buy ‘services’, e.g. if they have a preference for certain vendors, certain products, certain solution patterns. There is this paradox, as to succeed with service integration, you might have to go around services as a term. To establish an end-to-end SIAM solution you need to work on the digitalisation of the metadata and information management of the different vendors. To succeed with SIAM, you need to manage your sourcing assets with all the relevant dependencies as part of managing the digital governance. This is almost a prerequisite to manage SIAM as an ongoing digital process.

Before moving into SIAM, an organisation should consider many factors. We have listed 7 pieces of advice to succeed with digital services integration:

  1. Map out your Business Capability Map so you have a consistent view of ‘what does the business do’, and what is done where in the business

 

  1. Then map the business applications and business projects and other sourcing deliverables. This allows a direct coupling from IT to Business, and allows in parallel the business services construction. Try to avoid layers of academia and ‘noun services’, start building the typical orderings and offerings requested from stakeholders and end-users.

 

  1. Enable a digital solution of the management of the service integrator; managing the information exchange between own organisation and external providers. What is the live information you get from the providers to secure your information is up to date.

 

  1. Enable a digital solution of the management of the service integration, managing the information between the different providers. What is the alive information you need to manage the vendor?

 

  1. As the SIAM solution evolves there will be a living representation of how infrastructure relates to business applications, and development, and further into the business. Make sure this end-to-end model is clear, alive and governed using terms common for end-users (not the academics).

 

  1. Align the vendor management with the information management to align scope and expectations across the provider contracts. The information management should be an online living architecture which at heart supports the SIAM solution. Ensure silo-services and non-silo services are experimentally approached, validated, and approved.

 

  1. Get yourself an advisor who can help you to build the SIAM portal with an agile mindset. Most of the services and groupings of a SIAM solution must mature, the fastest route is to experiment, validate and grow. It is like a restaurant, where the services menu card is not ready day 1, but testing a menu card, you will see which services are asked for, in what type or spiciness, and what other meals could be composed from some of the same ingredients.

 

The integration of interdependent multi-sourcing services is difficult for many clients, but for those clients who manage the information management as a  living architecture with digital governance, it is a minor step. The challenges of assuming this is done by IT Service Management is often a too simplified picture, and the challenges to solve the services enabling before building the SIAM portal seems often academic with limited success and low impact. We advise to bring alive the digital platform using interaction in the planning and definition of the SIAM solution. This is the safest way to enable your digital services transformation.

We power your digital MooD.