Discovery Type
The lens used to decide what kind of uncertainty the initiative needs to reduce before build, pilot, rollout, or scale.
BRAC IT
Product DiscoveryThese terms are intentionally practical. They explain what the team needs to decide, prepare, or review.
The lens used to decide what kind of uncertainty the initiative needs to reduce before build, pilot, rollout, or scale.
The pace and depth of discovery work. Routes range from Flash to Continuous based on available time and risk exposure.
The lightest discovery route that still respects the highest risk signals. A compressed timeline should be accepted deliberately.
The discovery type that best matches the dominant uncertainty in the initiative.
A meaningful supporting discovery type that should influence the work even if it is not the main lens.
A concrete output that helps stakeholders decide whether to build, pilot, change scope, pause, or continue discovery.
The level of proof needed before the team can responsibly move forward. Higher risk requires stronger evidence.
The five-part view of ambiguity, coordination, technical dependency, governance/data, and adoption/rollout risk.
Ongoing product learning after launch or during long-lived initiatives, using live evidence to shape roadmap and improvement decisions.
The simpler non-model option that AI or ML must outperform before the team treats model work as justified.
The system, owner, or record treated as authoritative for a data item or business state.
Whether the team has enough ownership, time, evidence, artifacts, and review coverage to proceed responsibly.