BRAC IT

Product Discovery Framework

Can this product create value, trust, and repeated usage for a very large number of external users with minimal handholding?

Mass Product Discovery is for products whose users are mostly outside the client or product owner organization and where adoption, activation, retention, trust, analytics, support, and controlled rollout all matter.

External usersLarge scale potentialSelf-service usageAdoption mattersActivation mattersRetention mattersTrust mattersSupport load mattersAnalytics matterControlled rollout matters

New mass product

Use this lens when the product is not live yet and the team needs to understand audience, journey, trust, measurement, and rollout decisions before scale.

New mass product

For a new mass product, pay closest attention to audience definition, priority segments, market-gap evidence, journey shape, and analytics. These activities explain whether the opportunity is real before the product reaches scale.

Clarify Mass User ContextIdentify User Segments and Priority UsersBenchmark Similar Mass ProductsMap the End-to-End User JourneyDefine Data Analytics and Event Tracking

Banglalink-style mass-product situations

Mass-product discovery is often continuous. The useful evidence mix changes depending on whether the team is improving a live feature, redesigning a major journey, or exploring a new market gap.

Management perception is not enough at mass scale.

Treat internal belief as an assumption. Stronger discovery foundations come from industry research, behavioral analytics, support evidence, and direct user observation.

Live feature optimization

Use this pattern when an existing feature is being improved through continuous feedback, analytics, support signals, and targeted usability checks.

Current BehaviorAnalyticsSuccess MetricsPrototype and UsabilityTrust, Risk, and Support
Evidence to compare
  • Feedback triaged by frequency, severity, source quality, and business alignment
  • Feature adoption, funnel drop-off, retention, session, support, and complaint data
  • Observed understanding from live or prototype interactions
Watch out

Do not treat every feedback item as equal. Loud feedback needs to be weighed against behavioral data, severity, and strategic value.

Major UI overhaul

Use this pattern when a mass product needs a redesign, information architecture change, or high-visibility journey update.

User SegmentsBenchmarkingJourneyPrototype and UsabilityAnalytics
Evidence to compare
  • Large-scale A/B tests or controlled rollout evidence
  • Surveys and usability testing for comprehension, confidence, and feature visibility
  • Device-specific reviews for screen size, aspect ratio, reach, and physical holding patterns
Watch out

A redesign can look better while making critical actions harder to notice or reach on common devices.

New product and market gap discovery

Use this pattern when the team is evaluating a new mass product, new form factor, or unserved segment opportunity.

Mass User ContextUser SegmentsBenchmarkingResearch PlanFinal Recommendation
Evidence to compare
  • Industry and competitor research before internal assumptions harden
  • Evidence of underserved segments, unmet jobs, or weak existing alternatives
  • App versus web suitability, accessibility trade-offs, and segment-specific UX preferences
Watch out

At mass-product scale, management perception of user need is a weak signal unless it is backed by market data, observed behavior, or direct user evidence.

Lifecycle stages

Use the stages to understand how the activities connect without reading the full framework in one pass.

Explore the framework one activity at a time.

Choose the path that best matches your situation. The activity guide will update to show which activities are Core, Useful, Later, or Advanced for that path.

Understand People

Clarify who the external users are, what they do today, and which groups matter most.

Clarify Mass User Context

Clarify who the external users are, expected scale, and the diversity factors that change design, rollout, and support.

Output: Mass User Context Summary

CoreRead activity

Identify User Segments and Priority Users

Break the large user base into meaningful segments so discovery is not biased toward one narrow audience.

Output: User Segment Map

CoreRead activity

Understand Current Behavior and Alternatives

Understand what users actually do today, not only what stakeholders hope they will do.

Output: Current Behavior and Alternative Journey Map

AdvancedRead activity

Shape the Experience

Use benchmarks and research planning to define the journey and first value moment.

Benchmark Similar Mass Products

Study similar products, market gaps, and industry patterns so the team understands user expectations, trust signals, support patterns, and opportunity size.

Output: Mass Product Benchmark Matrix

CoreRead activity

Design the Discovery Research Plan

Choose the right research methods based on scale, risk, timeline, and user accessibility.

Output: Mass Product Research Plan

UsefulRead activity

Map the End-to-End User Journey

Map the journey from awareness to repeated usage so the team can see first value, friction, trust, and support needs.

Output: Mass User Journey Map

CoreRead activity

Measure and Test

Define analytics, success metrics, and flow testing before the product reaches scale.

Define Data Analytics and Event Tracking

Define what should be tracked, how success will be observed, and how analytics quality will be maintained.

Output: Lifecycle Measurement Map, Funnel Analysis Plan, Event Tracking Plan

CoreRead activity

Define Activation, Retention, and Success Metrics

Define how the team will know whether the product is working for users and for the business.

Output: Success Metric Framework

UsefulRead activity

Prototype and Usability Test Key Flows

Test whether users can understand and complete the most important flows before development or large-scale rollout.

Output: Usability Test Findings and Flow Improvement List

UsefulRead activity

Launch Responsibly

Review trust, support, rollout, and final recommendation decisions together.

Define Trust, Risk, and Support Model

Identify what could damage user trust and how support will respond when things go wrong.

Output: Trust, Risk, and Support Model

UsefulRead activity

Plan Rollout and Continuous Discovery

Plan how the product will launch, be monitored, improved, and scaled.

Output: Rollout and Continuous Discovery Plan

UsefulRead activity

Final Recommendation

Package the evidence and choose the recommendation that best fits the current discovery confidence and risk picture.

Output: Mass Product Discovery Brief and Final Recommendation

UsefulRead activity