Product as a Service
The Process

1. Identifying the Need

The process begins with a business need or idea. Before moving forward, the organization checks whether a functional governance structure is already established.

• If governance exists: Proceed to validate whether the need is well-defined and actionable.
• If not: Conduct a governance workshop and assemble the governance board.

2. Clarifying and Defining the Need

The next step is ensuring that the need, potential solutions, and KPIs are clearly defined.

• If the need is not well-defined: Assemble an ideation team (internal + external) to refine it.
• A workshop is held to define the problem, possible solution paths, and measurable KPIs.
• The definition is checked again for clarity and actionability.

3. MVP Team Assembly & Kickoff

Once the need is fully defined, an MVP team (internal + external contributors) is assembled. The MVP team reports directly to the governance board. A kickoff workshop introduces the two parties to each other and initiates the MVP development cycle.

4. Development & Validation

Development follows a rapid iterative Build – Measure – Learn loop.

• After each iteration, the governance board assesses whether to proceed.
• If “No”: Depending on the situation, the MVP team may iterate again or stop the effort.
• If “Yes” but a pivot is needed: The process backs up to an earlier stage to decide which new direction to go forwards.

5. KPI Achievement & Next Steps

When development cycles demonstrate that KPIs have been met:

• A governance + management decision determines how to transition from the MVP or prototype.
• Options include integrating into an existing unit, creating a new internal unit, or spinning it out using internal or external teams.
• Respective parties are assembled for hand-off when needed.

6. Closure & Learning

The final step is a post-mortem workshop to capture lessons learned. The process concludes with documentation and handover to operational owners.