YAS / IMPLEMENTATION CAPABILITY
Build the smallest product loopthat can prove useful work.
A product is the right intervention when a repeatable user job needs a durable interface, data model, and release path beyond scattered tools.
← Build
When this capability is useful
- MVP scope grows faster than evidence.
- The product has screens but no core operating loop.
- A no-code stack blocks reliability or required integration.
What must be designed
- A bounded core workflow and acceptance criteria.
- Product state, data ownership, and learning signals.
- A release plan that keeps scope and exception risk visible.
Decision artifacts
Choose the surface after the operating model.
- 01
MVP scope canvas.
- 02
Core-loop diagram.
- 03
Release and learning plan.
When not to use it
- Do not promise market validation through coding.
- Do not build a feature catalogue before the core loop.
- Do not use ‘from idea to scale’ as a generic promise.
Related decision path
Customer and product systems
Open related path →What are you trying to make work?
Bring the workflow, the bottleneck or the product idea. We can start with what exists and define the next useful version.