EA tool adoption strategy

Driving User Adoption of Your Enterprise Architecture Tool

So, you have introduced an enterprise architecture tool into your organisation because you recognise its strategic value and understand that relying solely on Excel spreadsheets and one-off, manually created slide decks for decision-making insights is not conducive to collaboration. You have captured and imported the application data, previously stored in Excel files, into your tool. The data is now accessible through the diverse set of enterprise-related dashboards and reports.  At this juncture, how can you effectively discourage your organisation from reverting to their own versions of Excel files, which are often just transient copies of your application, technology, and process listings?

The successful implementation of any EA tool hinges on its adoption as the primary source of insights for your enterprise by your stakeholders. Achieving this requires a nuanced understanding of how a centralised tool, containing the verifiable truth, can facilitate more informed decision-making. However, it is acknowledged that altering established ways of working presents a significant challenge.

We’ve learnt a lot over the years implementing our EA tool, Essential.  Starting on the right footing is paramount. Here are some considerations to keep in mind when implementing your EA Tool and how you can improve and foster better user adoption.

Identify your Stakeholders and their Concerns

Through your engagement with your organisation, identify and compile a comprehensive list of critical questions or concerns they may be facing. These questions could encompass various aspects, such as cost optimisation, application support coverage of your business landscape, risk identification, technology risk and compliance requirements. It is essential to ensure that these concerns are directly linked to business outcomes and objectives that are clear and easy to understand.

Prioritise Delivery and Focus on High Value Cases

The stakeholder issues list should be prioritised. Several factors can be taken into consideration for this. For example:

  • Identify low-hanging fruit by assessing the data requirements for the issues and prioritising those where the required data is readily available
  • Identify issues that are important to potential EA Champions who will be allies to you or are already supportive of the need for EA. The EA Champions can be specific individuals or roles in the business.
  • Gaining C suite or leadership buy-in is also often crucial to success, in which case you should look at issues that will yield greater benefit for these stakeholder groups.

 

You may also consider using an existing prioritisation method such as the SAFE Weighted Shortest Job First (WSJF) to objectively prioritise the issues.

In some cases, you may need to lay the foundational building blocks first which can dictate the order in which you address the issues. For example, before focusing on implementing strategy management, you ought to have mapped out your landscape before you can start looking at what will need to change.

Views/Reports Identification

Minimise time to value by using the out-of-the-box dashboards and reports of the tool that address and provide insights in support of the priority issues identified in Step 2. Conduct a review of the available views and consider how the insights within the view will address these issues and how they will be utilised by the stakeholders associated with each issue.

Data Gathering, Capturing and Loading

Identify the data required for the views, reports, and dashboards prioritised in Step 3. For each of the prioritised issues, determine whether you have the necessary data and quality to meet the objective. Specify the source of the data, its location, and its formats. The data may originate from other systems or could be stored in files such as spreadsheets. Assess the data quality and perform any necessary data cleansing if required. Develop a project delivery plan and agree on delivery milestones with stakeholders. Import an initial, foundational data set either through system integrations or as a batch by utilising predefined spreadsheet loaders.

Curated Outputs

To avoid noise, establish the outputs that are relevant to specific stakeholder group. In Essential we use portals to group the dashboards and reports identified in step 3 to provide the key insights required to address specific stakeholders.  However, your tools may take a different approach such as setting up perspectives or workspaces that are specific to your stakeholders.

Change Management Process

When stakeholders understand how the views will address their concerns, adoption becomes purposeful rather than obligatory.

Training and Communications

The EA Champions identified in step 2 will play a crucial role in this phase. They can be the deliverer of the key messages and can collaborate with the EA Team to identify and promote the views containing the required EA insights.  This may be using various methods, we’ve seen short user training, short briefings, workshops, creation of targeted user guides and video guides that incorporate the views and their insights, all based on real organisational use cases. This approach reinforces the value of the tool among stakeholders. Adoption should be strengthened through continuous enablement rather than relying solely on one-time training sessions.

Measure and Communicate Value

It is imperative to create tangible impact to fully integrate an EA tool into the organisation and promote long-term adoption. This can be achieved by tracking and sharing the outcomes by examining the improvement in decision-making through the insights provided by the tool. For example, how the tool facilitated rationalisation, reduced costs, or identified risks within the landscape. Successful stories are essential to bolster and demonstrate value. User adoption is an ongoing process that should evolve by gathering feedback from the user community and revisiting the initial issues and objectives that were to be addressed.

In summary, to achieve success with your EA tool, we recommend adhering to the following three key principles:

  • Deliver Value Gradually: Instead of attempting to accomplish too much at once, focus on delivering value in small, incremental steps.
  • Maintain Data Integrity: Only capture data that is essential and that you can manage effectively. Avoid capturing data simply because it is available at a given point in time.
  • Clarify Roles and Responsibilities: Define clear roles and responsibilities for all stakeholders. This is not a one-time task but an ongoing process that requires continuous review and refinement.

 

Contact Us