BRAC IT

Product Discovery Framework

Flow

Four logic layers turn the questionnaire into the final output.

1

Initiative Details

Metadata only. This section helps intake and traceability but does not score discovery type, risk, or route directly.

2

Discovery Type ID

Sixteen shared pattern questions plus one Project Type modifier choose the primary discovery type and the single qualifying secondary type.

3

Risk Engine

The 13 scored complexity questions create the 5-part risk profile. Risk floors can be raised by integration, compliance, executive, financial, external-user, or field-rollout signals.

4

Route And Fit

Time Available determines the main route, and the risk profile determines the minimum safe route and the fit warning.

Discovery Type ID

Primary and secondary types come only from this section.

Question Scoring

Selected answer adds the full question weight to exactly one discovery type.

The 16 Discovery Type ID questions use visible weights and neutral option patterns. No complexity score contributes to discovery type.

Project Type Modifier

Project Type is applied once after DT1-DT16.

B2C strongly boosts Mass Product, B2B boosts Platform/SaaS, Integration, and Enterprise, and Internal boosts Tactical, Workflow, and Program.

Primary Type Rule

Primary Discovery Type = highest final score.

Ties break by Anchor count, then by the earliest winning signal in DT1 through DT16, then by fixed discovery type order.

Secondary Type Rule

Secondary Discovery Type = single runner-up only if its score is at least 60% of the primary score.

If the runner-up stays below that threshold, the output becomes No strong secondary type.

Question Bank

Discovery Type ID questions and visible weights.

PT1: Project Type

The overall business model or engagement shape the initiative most closely fits.

Project Type is asked once and applied as a score modifier after the Discovery Type ID questions.

DT1: Who primarily experiences the value of this work?

Choose the group that most directly experiences the improvement or value created by the initiative.

Weight
8
Examples of option families
One requester or one small internal team, Several internal roles inside one operating flow, One program or department across branches or field teams, Multiple departments or enterprise functions...

DT2: How broadly must the same solution work?

Choose the operating breadth the solution must reliably support.

Weight
8
Examples of option families
One team or one narrowly scoped use case, One internal process across a limited set of roles, One program or department across many locations, Multiple enterprise functions with shared controls...

DT3: What is hardest to understand right now?

Choose the uncertainty that most needs discovery before the work can move responsibly.

Weight
8
Examples of option families
Exact requirement, rule, or edge case, Handoffs, approvals, or exception paths, Field reality versus head-office assumptions, Ownership, governance, or role hierarchy...

DT4: What kind of evidence would reduce uncertainty fastest?

Choose the evidence or activity most likely to unlock the next decision.

Weight
8
Examples of option families
Requirement walkthrough and acceptance-criteria review, Process observation and role mapping, Field validation and pilot feedback, Governance workshop and ownership alignment...

DT5: If this goes wrong, where would the damage show up first?

Choose the place where the first clear consequence would be felt.

Weight
5
Examples of option families
Rework on a small existing feature, Operational delay or confusion between roles, Program inconsistency across branches or teams, Control, reporting, or organizational coordination failure...

DT6: What operating shape must this solution support?

Choose the operating structure that best describes the solution’s natural shape.

Weight
5
Examples of option families
A bounded existing feature or report change, A role-based internal workflow, A program-wide operational model, A cross-functional governance structure...

DT7: What rollout pattern is most likely?

Choose the rollout or adoption pattern that best fits the initiative.

Weight
5
Examples of option families
Direct release to one small team or requester, Phased adoption within one internal workflow, Program rollout across branches or field teams, Cross-functional enterprise adoption and control rollout...

DT8: What dependency feels most central to success?

Choose the dependency or relationship that most strongly determines success.

Weight
5
Examples of option families
Clear business-rule alignment, Internal process alignment between roles, Field operations and adoption readiness, Governance and ownership alignment...

DT9: What will success depend on most?

Choose the factor without which the initiative would likely struggle.

Weight
5
Examples of option families
Getting the details right quickly, Making the workflow usable and consistent, Standardizing adoption across one operating unit, Clarifying governance and accountability...

DT10: Which change shape best describes this work?

Choose the description that best captures the shape of the initiative.

Weight
5
Examples of option families
Refining an existing feature or rule, Reshaping an internal workflow, Enabling one program at scale, Establishing an enterprise operating pattern...

DT11: How widely is ownership distributed?

Choose the ownership spread that best fits the work.

Weight
3
Examples of option families
Mostly one requester or one delivery pair, Shared within one operational flow, Shared across one program or department, Shared across many functions or governance groups...

DT12: How much repeatability or configuration is expected?

Choose how repeatable or configurable the solution needs to be.

Weight
3
Examples of option families
Very little; one specific change, Limited to one internal process shape, Repeated inside one program, Repeated across enterprise functions with controls...

DT13: Which failure mode matters most?

Choose the failure mode the team most wants to avoid.

Weight
3
Examples of option families
Missing a rule or edge case, Breaking handoffs or exception handling, Failing field or branch adoption, Creating governance gaps or unclear ownership...

DT14: What role does data or decision logic play?

Choose the statement that best describes the role of data, metrics, or decision logic in the initiative.

Weight
3
Examples of option families
Limited reference data for an existing change, Operational data inside a known workflow, Program tracking and reporting, Enterprise control, reporting, or governance data...

DT15: What user-contact model best fits the work?

Choose the user-contact model that best describes how the solution is experienced.

Weight
2
Examples of option families
Mostly indirect; handled by a small internal team, Internal staff use in a defined workflow, Program staff or field teams across locations, Cross-functional internal users with layered permissions...

DT16: How will success most likely be judged?

Choose the outcome pattern that will most likely define success for the initiative.

Weight
2
Examples of option families
Accuracy and completeness of requirements, Workflow clarity and reduced operational friction, Consistent adoption across the program, Governed adoption and clear ownership...

Risk Engine

The 13 complexity questions now generate risks, not type.

Ambiguity Risk

How unclear the problem, solution direction, maturity, or measurement model still is.

Questions used
Problem Clarity, Solution Clarity, Product Maturity or Newness, Measurement Readiness

Process and Coordination Risk

How difficult it will be to align people, workflow, coordination, and operating change.

Questions used
User Role Complexity, Stakeholder Complexity, Workflow Complexity, Change Management Need

Technical and Dependency Risk

How much delivery risk depends on systems, dependencies, technical feasibility, or failure handling.

Questions used
Risk of Wrong Build, Technical / Integration Complexity

Governance and Data Risk

How serious the governance, reporting, reputational, financial, or data consequences are.

Questions used
Business Impact, Data Sensitivity

Adoption and Rollout Risk

How challenging rollout, adoption, scale, and support are likely to be.

Questions used
User Scale, Change Management Need

Risk Signal Floors

These supporting questions can floor specific risks at High even when the numeric average is lower.

External Users Involved? (Can floor Adoption and Rollout Risk at High.) · Integration / API / Source Systems Involved? (Can floor Technical and Dependency Risk at High.) · Field Rollout Required? (Can floor Adoption and Rollout Risk at High.) · Financial Transaction or Money Involved? (Can floor Governance and Data Risk at High.) · Compliance, Sensitive Data, or Vulnerable Users? (Can floor Governance and Data Risk at High.) · Executive Reporting or Audit Impact? (Can floor Governance and Data Risk at High.)

Route Logic

Route comes from time, and fit comes from risk.

1 to 3 days

Flash Discovery

This is the main route output when this amount of discovery time is available.

1 week

Lean Discovery

This is the main route output when this amount of discovery time is available.

2 to 3 weeks

Standard Discovery

This is the main route output when this amount of discovery time is available.

4 to 6 weeks

Deep Discovery

This is the main route output when this amount of discovery time is available.

Ongoing

Deep Discovery

This is the main route output when this amount of discovery time is available.

Minimum Safe Route by Risk

Critical or 2+ High = Deep · 1 High or 3+ Moderate = Standard · 1-2 Moderate = Lean · all Low = Flash

Time vs Risk Fit

Available route meets risk route = acceptable · one level below = compressed · two+ levels below = severely under-scoped

Scorecard

The output page now exposes the full discovery-type ranking.

The Discovery Type Scorecard is shown as a ranked table with these exact columns:

Rank · Discovery Type · Final Score · Result

Output Map

Which logic layer feeds each final output.

Primary Discovery Type

Highest score after the 16 Discovery Type ID questions are scored and the Project Type modifier is applied.

Secondary Discovery Type

Only the single runner-up, and only when it reaches at least 60% of the primary score.

Discovery Type Scorecard

The ranked table of all 6 discovery types, showing the final ranked score and whether the type finished as Primary or Secondary.

Risk Profile

The 13 complexity scores grouped into 5 risks, with floor rules from the explicit risk-signal questions.

Time Route

The selected Time Available for Discovery answer only.

Minimum Safe Route by Risk

The final mix of Low, Moderate, High, and Critical risk bands.

Time vs Risk Fit

The comparison between the available time route and the minimum safe route by risk.

Required Reviews / Artifacts / Next Steps

Primary discovery type plus any High or Critical risks. Secondary type only adds one guidance extension to next steps.

Reference Rules

Compact rules used in both app and workbook.

Discovery Type ID

Sixteen shared pattern questions plus one Project Type modifier determine discovery type

Each selected answer maps to exactly one discovery type

Project Type is asked once and applied after the DT questions

Primary Type

Highest final type score across all 6 discovery types

Primary Discovery Type = top-ranked type

Tie-break by anchor count, earliest winning signal, then fixed type order

Secondary Type

Only the single runner-up discovery type appears, and only when it reaches at least 60% of the primary score

Otherwise the result is No strong secondary type

Secondary guidance is advisory only

Risk Engine

The 13 complexity scores produce 5 risks: ambiguity, process, technical, governance, and adoption

Risk floors apply from explicit risk signals such as integration or compliance

Risk no longer selects discovery type directly

Route Logic

Time Available for Discovery determines the main route output

Minimum Safe Route by Risk shows the minimum responsible route for the risk profile

Time vs Risk Fit shows whether available time is acceptable, compressed, or severely under-scoped