Capture visions
The license package Strategic Portfolio Management is required to work with demands. The use case Strategy Validation must be activated.
A vision represents the long-term aspiration or desired future state of the organization. It is a broad and inspirational statement that guides the overall direction. An enterprise may have multiple visions that set the ultimate direction and inspiration for the organization. For example, a vision could be articulated as "Be the global sustainable energy provider."
Visions are the top items in the strategy network. Visions have goals that articulate the broad primary outcomes that the organization aims to achieve to fulfill its vision, which in turn have objectives that describe the specific measurable steps that need to be taken to achieve the goals. At the most granular level of the strategy network are strategic themes that describe the overarching areas of focus that align with the vision and goals. The affected IT architecture is captured on the level of the strategic theme and is then inherited by the vision that is its parent in the strategy hierarchy.
In the navigation panel, click Investment Architecture > Strategy Network > Visions. Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench or you can navigate to a vision's content area and define it in more detail there. Click to learn about how to use data workbenches.
Go to Investment Architecture > Strategy Network > Visions data workbench.
-
Add a new vision. Click
> Create Organization to open the edit panel and specify the basic data. -
Define the details of the vision.. Click the Navigate
button next to a vision to open its content area. Specify the vision's attributes as well as the relationships that it has to other assets in the repository.
Try to capture as much information as possible about the vision because complete data considerably improves the results of business questions and other analytics.
Once a vision is in the repository, you can define more details about it in the Visions data workbench . Or specify and analyze the vision in detail in its content area . In the data workbench, click the Navigate button for a vision to open its content area > Overview page. All mandatory fields must be defined to create the vision and save it.
Per default, the data workbench displays a limited set of basic attributes. You can add more columns via the Structure column to capture other attributes directly in the data workbench.
Define the vision's basic data. All mandatory fields must be defined to create the vision and save it.
- Name: (Mandatory) Enter a unique name for the vision. The name should help others easily understand the purpose of the vision.
- Object State: Specify whether the vision is in planning or active in the enterprise.
- Responsible Organization: Specify the organization that is responsible for the vision.
- Authorized Access tab: The user who creates the vision is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the vision. All users in the authorized user group can edit the vision.
A role represents a functional responsibility that a user or organization has for the vision. Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets?.
Responsibilities are based on preconfigured role types. Your company may also configure custom role types via the Portfolio Admin user profile. Depending on the role type, a specified user and/or a specified organization may fulfill the responsibility for the vision. A user assigned responsibility via a role has read-only permissions to the vision. To change data about the vision, they must also be specified as an authorized user or member of an authorized user group.
Roles can be assigned to a vision in the Visions data workbench or the vision content area via Overview > Responsibilities. A person can have one of the following roles or a custom role added by your company:
- Business Owner: A person or organization who owns the vision and is responsible for managing the functional requirements.
- Stakeholder: A person or organization who has an interest in the vision and therefore requires read-only access permissions.
To specify responsibilities for the vision:
- Click in the relevant role field to open the selector.
- Expand the ORGANIZATION or USER sections in the selector and select the person or organization fulfilling the role.
- Click OK to save the role definition and close the selector.
The first step in realizing a vision is to break the vision down to the goals that the organization aims to achieve to fulfill the vision. Goals are broad primary outcomes that are more specific than the vision but still high-level and long-term and translate the vision into broad achievable outcomes. For example, goal "Provide outstanding customer experience" may be specified in order to realize the vision "Be the global sustainable energy provider."
Go to the content area of the vision > Overview > Subordinate Value Nodes. Click and either create a new goal or add an existing goal to the vision. A vision can have multiple goals and a goal can be assigned to more than one vision.
The assets that are impacted by a vision make up the architectural scope of the vision. The affected architecture is inherited through the strategy network from the strategic themes that are at the granular level of the vision's strategic hierarchy.
To view all affected architecture elements, go to the vision's content area Architecture Scope > Affected Architecture. The impacted assets are displayed in a matrix according to the asset type.