Initiatives

You begin by defining an initiative with a summary (1), followed by an optional explanation of the current situation and background knowledge (2). This initial overview sets the foundation for understanding the goal's purpose and context.

In the next section, you'll document key metadata, including the initiative in Jira, contact persons and links to additional documents (3). As your project evolves, this section becomes a central hub where you can link all product goals that this initiative contribute to, creating a clear chain of accountability and progress.

To ensure your initiative can be effectively evaluated, you'll add the necessary success factors (4). Each success factor is structured with a concise title and precise description, made concrete and measurable through specific sub-goals. This measurement framework enables you to track progress and demonstrate success systematically.

An Initiative can both create and mitigate risks. But it is important to know the risks. Enter the risks (5) in this table and evaluate them. The evaluation can be done with the status macro, which you activate with /status.

Next comes the Business Opportunities (6). Similar to the risks you need to know these. Enter the Business Opportunities in this table and evaluate them. The evaluation can be done with the status macro, which you activate with /status.

If you have defined many initiatives you’ll need to prioritize them, because you cannot work on everything at once. For this purpose, there is the prioritization macro (7) that is documented separately. You can edit the values by clicking on the macro and then on the icon with the pencil. On the right side, a panel opens with the possible settings. The priority value is automatically calculated and filled at the top of the page.

Sometimes it is the case that other services are needed to achieve the goal of the initiative or there are other dependencies (8). Enter this kind of dependencies in the table. You can indicate the type again with the status macro (enter /status).

This is where the underlying Customer Journeys are blended in (9). The Customer Journeys have their own template and are created as subpages to the associated Initiative. You need to click on the button Create new Customer Journey to create a new one.

The template concludes with a simple question and answer block (10). If any content-related questions arise during filling, you have a central place here where you can deposit them. This way, others who have similar questions can share them.