canvas
Capability Value Proposition Canvas
A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an implementation style.
Outcomes
- Clear reusable capability value proposition
- Consumer tasks, gains, and pains captured without assuming a technology
- Candidate reusable capabilities identified for architecture evaluation
How it works
- List the consumer tasks and outcomes the capability should support.
- Identify gain-enabling capability features.
- Identify pain-relieving capability features.
- Group the features into candidate reusable capabilities.
Work with this canvas
Use the purpose, outcomes, and instructions above as your static reference while capturing evidence in the interactive workspace.
Local canvas workspace
Capability Value Proposition Canvas
Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style? Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.
Active section: Consumer tasks and outcomes. Select a section with a pointer, or focus it and press Enter or Space.
Consumer tasks and outcomes
What are consumers, partners, users, systems, or teams trying to achieve?
Gain-enabling capability features
What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?
Pain-relieving capability features
What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?
Reusable capabilities
What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?
APIOps Cycles · CC-BY-SA 4.0 · Osaango Ltd