Frame
Phase Goal
Establish whether a microproduct is worth building and feasible to deliver before you enter execution.
What Must Be True Before You Build
- A repeated workflow pain exists for a specific user segment.
- You can access enough data to create clear utility.
- The value proposition is concrete enough to test quickly.
- A baseline architecture is feasible within team and budget constraints.
Required Outputs
- Problem brief with target user, problem, data inputs, output utility, and success metric.
- Go/no-go criteria for moving into implementation.
- Architecture decision brief with pipeline, storage, and cost assumptions.
Module Map
- Ideation: define demand, data availability, and minimum useful outcome.
- Design: translate requirements into concrete specifications and product shape.
- Architecture: pick a modern data pipeline and justify key system decisions.
- Data Stack & Analytics Engineering: choose orchestration, transformation, and storage for reliable data workflows.