# Connected MVP Canvas

Turn a product promise into one useful tool and a testable release decision.

## Whose job are you improving?

Name the person, trigger and result they can inspect.

[Your notes]

## What have you observed?

Record a recent example, its source and date. Separate assumptions from observations.

[Your notes]

## What single action will the tool perform?

Use a precise verb and name. Include the actions it will not perform.

[Your notes]

## What inputs are required?

List each field, allowed values and what happens when it is missing.

[Your notes]

## Which source and rules govern the answer?

Name the source owner, permitted collection, current-version rule and missing-data behavior.

[Your notes]

## What will a useful result contain?

Specify inspectable fields and the empty state.

[Your notes]

## Which cases must pass?

Include the ordinary path, absent data, invalid inputs, access boundaries and an out-of-scope request.

[Your notes]

## What would justify a limited pilot?

Choose conditions before the demonstration, plus an owner and review date.

[Your notes]

Companion article: https://waymaker.cx/blog/mcp-connected-mvp-canvas
