# Runwise product improvement worksheet

Choose one customer task to improve. Use observations and product evidence before adding features.

## 1. Define the task and baseline

- Primary user and situation:
- Task they are trying to complete:
- Current completion or abandonment measure:
- Measurement period and source:
- Business result this task supports:

## 2. Inspect the journey

| Area | Evidence to review | Finding and source |
| --- | --- | --- |
| First value | Can a new customer complete the first useful task? | |
| Repeat use | What brings customers back, and where do they stop? | |
| Friction | Confusing steps, failed submissions, empty states, and recovery | |
| Accessibility | Keyboard access, readable labels, contrast, and phone layouts | |
| Reliability | Errors, response time, data integrity, and recovery | |
| Support | Repeated questions, workarounds, and unresolved requests | |
| Trust | Permissions, pricing expectations, privacy, and misleading copy | |

## 3. Prioritize a change

| Proposed change | Customer impact | Evidence and confidence | Effort / dependencies | Owner | Success check |
| --- | --- | --- | --- | --- | --- |
| | | | | | |
| | | | | | |
| | | | | | |

Avoid treating an unknown as a low score. Record the research or technical check needed to reduce the uncertainty.

## 4. Review the result

- Change and release date:
- Who reviewed the acceptance criteria:
- Before/after measure, with comparable users and time periods:
- What improved or became worse:
- Limitations or other changes that may explain the result:
- Next decision and owner:

Use sample information in public planning tools. Agree production access and handling before reviewing customer records.