The SPE focuses more on the product and less on the company in general. One of the most important differences is the much broader and fact-based vision. It is the basis for recognizing disruptive developments and discovering new opportunities.

Further significant differences result from the referential structure of the pyramid. It ensures that it is clear for each requirement which strategic goal it is contributing to. This enables a stronger focus on the most important goals.

Finally, SPE’s iterative approach allows it to be seamlessly integrated into agile product development. In contrast to the static strategy approaches, it thus remains permanently up to date.

The number of workshops required depends on the status of the product strategy and the complexity of the product, among other things. An initial assessment can be given after a preliminary discussion.

The pyramid is built top-down to consistently align the requirements with the vision, mission, strategies and goals of the roadmap.

Vision

The vision is generated from the forecast of the long-term development of the product environment. Trends and measurable developments of the past play an essential role here.

Mission

From the vision set up with SPE, there are several options for your mission. In one of the workshops, we select these and develop them comparatively quickly into a powerful mission statement.

Strategy

With a consistently open and honest discussion, the strengths, weaknesses, opportunities and risks for your product are brought to the table and prioritized. Subsequently, strategies are derived from this with the help of the PES system to fulfil the set mission.

Roadmap

Concrete, measurable goals are now derived from the strategies derived. Once qualified, they are placed on a roadmap. There are several methods to choose from. The best one for your company can be discussed in the preliminary discussion. It is fixed at the latest before the roadmap is drawn up.

Requirements

In the last step of the setup of the product vision pyramid, the existing and newly identified requirements are referenced to the goals of the roadmap and ranked in a order that reflects the order of the goals.

The number of workshops required depends on the status of the product strategy and the complexity of the product, among other things. An initial assessment can be given after a preliminary discussion.

The initial creation of the Product Vision Pyramid based on the SPE can be used directly for conventional projects and organizations. In addition, it is integrated with Agile product development with Ervolution. It is also easy to embed in larger agile organizations. At SAFe, there are already approaches with the portfolio vision, which are completed by the SPE.

A clear no! A consistent application of the SWOT analysis, especially the derivation of the strategies, is a very effective means of identifying the right strategies. Unfortunately, it is often only carried out superficially and usually ends with the identification of obvious strengths, weaknesses, opportunities and risks. At this point, it’s nothing more than a PowerPoint page. The real value lies in the – sometimes quite painful – examination of the identified points and the derivation of strategies from these findings.