website logo
⌘K
πŸ“Introduction
πŸ“Essential Overview
Getting Started (What is Essential?)
The Essential Information Eco System
πŸ“How to be Successful with Essential
Identify Stakeholders and Concerns
Prioritise Delivery
Identify/Define the Views that will support Delivery
Identify any Meta Model extensions required and the impacts
Identify the data required, data sources, and population method
Plan Training/Consultancy
Extend Launchpad and build integrations and views as required
Complete Portal and Repository set-up
Capture data
πŸ“„Embed EA data management process to ensure data is maintained
Measure Value
πŸ“How To Use Essential
Using Essential Overview
πŸ“„Logging In and The Homepage
πŸ“„Capturing and Maintaining Data
πŸ“„Everyone's Essential Editors
πŸ”Hints & Tips
πŸ“„Bulk Data Imports
πŸ“„Essential Import Utility - To Bulk Load Data
πŸ“„Essential Viewer
πŸ“„Set Up Support Tools
πŸ“„Extending the Essential Meta Model
πŸ“„System Administration
πŸ“„Repository Administration
πŸ“„Managing User Security
πŸ“„Essential Product Releases and Updates
πŸ“EA Tutorials
πŸŽ“Business Architecture
πŸŽ“Application Architecture
πŸŽ“Technology Architecture
πŸŽ“Information Architecture
πŸ“„EA Support/Utilities
🌐Essential Meta Model Diagrams
Essential Meta Model (Overview)
Business Layer
Application Layer
Information/Data Layer
Technology Layer
EA Support
Meta Model Constructs
Essential Modelling Patterns/Definitions
πŸ“How to Populate Essential Views
Roadmap Enablement and Scoping Frameworks
Enterprise Views
Business Views
Information Views
Application Views
Technology Views
πŸ“Open Source
Open Source Overview
πŸ› οΈOpen Source Multi-User
βš’οΈOpen Source Installation
Accessing Essential OS
Essential OS Buttons
❓FAQs
Modelling in Essential
Data Capture, Maintenance and Releases
Viewer
User Management and Security
Launchpad and Import Utility
Open Source Configuration
Docs powered byΒ archbeeΒ 

Identify Stakeholders and Concerns

4min

A few key requirements for success:

  • Deliver value in small steps, don’t try to do too much in one go
  • Only capture data that is needed and that you can maintain, don’t capture data just because you have it
  • Clearly define roles and responsibilities going forward, this is not a one-off task but an ongoing exercise

To identify key objectives and value drops:

  • Engage with your key stakeholders to identify their areas of concern – a good way to do this is to identify the questions they have that can’t be answered, or take a long time to answer, such as:
    • What applications support a business capability/organisation?
    • What are the application/technology standards I should follow?
    • Where do we have risk?
    • Can we reduce costs?
    • And so on
  • Create a list of Stakeholders and their needs

ο»ΏThe Playbook can provide inspiration

ο»Ώ

Updated 03 Mar 2023
Did this page help you?
Yes
No
PREVIOUS
How to be Successful with Essential
NEXT
Prioritise Delivery
Docs powered byΒ archbeeΒ 
TABLE OF CONTENTS
A few key requirements for success:
To identify key objectives and value drops:
The Playbook can provide inspiration