Skip to content
Skip to content
Products

Spekir Atlas

Product documentation

Initiatives

Connect a planned business change to the systems and capabilities it affects.

PilotUpdated
On this page

Use an initiative to describe an effort such as replacing CRM, including its objective, owner, status and dates when those are known. Use a change request to describe the specific edits someone will make in the architecture model.

Read the scope

In the pilot navigation, open Initiatives and select an initiative. The list shows a schedule bar, counted status filters and sortable plan documentation coverage. The fact sheet shows Scope tabs for Applications, Business Capabilities and other affected types with recorded rows, plus linked Change requests and Objectives. Application scope records Add, Modify or Remove. Other recorded relations and the investment, staffing and value-case details remain accessible. Confirm missing scope with the initiative owner before using it in a portfolio decision.

Change focus (for example Migration or Consolidation) describes the work. It is separate from Initiative type (Idea, Program, Project or Epic). Existing Must-Win Battle records read as Program, and Strategic Project and Initiative records read as Project. The list, fact sheet, roadmap and exports use these labels; an unclassified value stays Unknown.

Read plan documentation coverage

An application in scope is documented when a linked change request contains an item targeting that application. Drafts count; Rejected and Cancelled requests do not. Each application counts once, even when several items or requests mention it. No scope shows No scope yet, rather than a percentage.

Documentation is not approval, implementation or realised value. Read the request's status and its changes before drawing those conclusions. An overdue banner means the end date has passed while the initiative is Planning or Active; it does not move the initiative to Done.

Move from intent to implementation

Record which applications will change and which capabilities need to keep working during the transition. Use a change request to group concrete changes such as updating a lifecycle stage or redirecting an integration. Check the request for the approval and implementation status of each relevant change. An initiative's status and dates describe the effort. The current landscape reflects the model edits that have been applied.

Contents

Need a hand?

Contact Spekir

Atlas · Search this product’s guides