IDEAS home Printed from https://ideas.repec.org/h/spr/mgmchp/978-3-642-24223-6_9.html
   My bibliography  Save this book chapter

People, adoption and introduction of EAM

In: Strategic Enterprise Architecture Management

Author

Listed:
  • Frederik Ahlemann

    (EBS Universität für Wirtschaft und Recht)

  • Eric Stettiner

    (PricewaterhouseCoopers AG Wirtschaftsprüfungsgesellschaft)

  • Marcus Messerschmidt

    (PricewaterhouseCoopers AG Wirtschaftsprüfungsgesellschaft)

  • Christine Legner

    (Université de Lausanne)

  • Kunal Mohan
  • Daniel Schäfczuk

Abstract

Enterprise architecture management (EAM) has emerged from a fairly technical perspective on enterprises, and did not initially fully realise the importance of ‘soft’ human factors. Consequently, EAM practices were developed and implemented without significant attention to the needs and perspectives of EAM practitioners and the relevant stakeholders. Neglecting these individuals’ requirements sometimes leads to the implementation of EAM practices considered unsuitable, which are then rejected by their stakeholders. In short, because key users and important EAM stakeholders are the ones who eventually decide a new management approach’s success or failure, aligning EAM practices with stakeholders’ needs is a critical success factor. We find that, among other things, we need to ensure that EAM practices are perceived to be useful to and by the actual stakeholder. Furthermore, EAM practices should be recommended by influential colleagues and managers to generate positive word of mouth. We also find that the use of EAM practices can be increased through organisational support in the form of training and technical assistance. Such training and assistance will reduce people’s doubt that they are capable of using such practices properly. Providing incentives and making the techniques fun to use are further ways to encourage individuals to apply EAM practices. Based on these insights, organisations can develop specific change strategies to foster the organisational adoption of EAM and to integrate these strategies into a cyclic process of introducing EAM. Such an introduction process consists of ten steps from identifying the project sponsors to the final roll-out and continuous improvement of EAM practices. Each process cycle should not take longer than three to nine months, allowing for the quick realisation of benefits and an ongoing improvement of EAM practices. In order to avoid working in an ivory tower, management should adopt a pragmatic 80/20 approach, combined with a strong stakeholder orientation. This strategy also ensures a lasting impact.

Suggested Citation

  • Frederik Ahlemann & Eric Stettiner & Marcus Messerschmidt & Christine Legner & Kunal Mohan & Daniel Schäfczuk, 2012. "People, adoption and introduction of EAM," Management for Professionals, in: Frederik Ahlemann & Eric Stettiner & Marcus Messerschmidt & Christine Legner (ed.), Strategic Enterprise Architecture Management, edition 127, chapter 0, pages 229-263, Springer.
  • Handle: RePEc:spr:mgmchp:978-3-642-24223-6_9
    DOI: 10.1007/978-3-642-24223-6_9
    as

    Download full text from publisher

    To our knowledge, this item is not available for download. To find whether it is available, there are three options:
    1. Check below whether another version of this item is available online.
    2. Check on the provider's web page whether it is in fact available.
    3. Perform a search for a similarly titled item that would be available.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:spr:mgmchp:978-3-642-24223-6_9. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Sonal Shukla or Springer Nature Abstracting and Indexing (email available below). General contact details of provider: http://www.springer.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.