# Routine Product Canvas

Use this canvas to design a recurring service around continuity rather than repeated transactions.

## 1. Promise

- What should continue without the customer reconstructing it?
- What is the customer committing to?
- What is the business committing to protect?
- What would break that promise?

## 2. Place

- Which entitlement, time, person, capacity, or access should persist?
- What is recurring?
- What is specific to one date?
- When is a place held or released?

## 3. State

- Which words describe the relationship, routine, and occurrence?
- What does the customer see?
- What does staff see?
- Where could the two disagree?

## 4. Exception

- Which ordinary changes need deliberate paths?
- Is the change one time or ongoing?
- Who can make it?
- What else does it affect?

## 5. Recovery

- How does the product preserve continuity when something fails?
- What remains safe?
- What is the next action?
- When does a person take over?

## 6. Learning

- Which evidence reveals friction in the relationship, not just activity?
- Where does support repeat work?
- Which states cause confusion?
- What should the next release improve?

## Review

For each answer, record:

- the person accountable for the decision;
- the product state or rule that represents it;
- what the customer sees;
- what staff sees;
- the exception and recovery path;
- the evidence that will show whether it works.

Created by Peter Schroeder. Read the full framework at https://peterschroeder.com/insights/design-membership-products-around-routine
