Home / Summaries / Strategic Enterprise Architecture Management Challenges, Best Practices, and Future Developments / ea-tool-eam

EA frameworks, modelling and tools - Management implications

4 important questions on EA frameworks, modelling and tools - Management implications

What is the relevance of frameworks for EAM?

An EA framework is not crucial for EAM success. In some cases, developing your own model, procedures and artefacts may be the optimal solution.

What is the best practice for EA modelling?

It's best when there is a focus on value added documentation and when a pragmatic 80/20 approach is chosen.

What are typical pitfalls of EA tool selection and
implementation?

The selection process begins before the EA approach, methodology
and EAM processes have been agreed upon.
EA tool objectives are not clearly defined.
The assumption that the marketleading EA tool will fit any organisation is a false one, and can lead to EA tools being selected that do not match (e.g., oversized or wrong priorities) the organisation’s EAM activities.
Users must be trained.
Tool selection activities, as well as tool implementation projects often lack resources. Such activities cannot be done parallel to day-to-day operations. Where this does happen, one of the two suffers

What success criteria should be considered when selecting and implementing an EA tool?

The EA tools’ objectives should be thoroughly defined.
Objectives should be translated into measurable requirements, including exclusion criteria for EA tool selection.
Helpful to use an existing tool evaluation as an input or starting point.
Pilot a tool before purchasing: representatives of all stakeholders should be introduced to the shortlisted EA tools for demos, test usage, and so on.

The EA tool’s integration into the existing system landscape should be considered.
A business case should be written that documents the objectives, costs and benefits.