How It Works
Every problem moves through the same disciplined lifecycle, whether it is reported by a user, a builder, or an organization.
Express the Problem
Your journey, by role
Problem Contributor
Describe→Clarify→Publish→Find Others→Add Evidence→Join Research→Evaluate Solutions→Follow Outcomes
Builder
Discover→Evaluate→Save→Research→Propose→Validate→Prelaunch→Beta→Launch→Learn
Research Participant
Create Profile→Find Study→Review Consent→Participate→Contribute Evidence→Receive Incentive→Track Impact
Product Team
Define Question→Recruit→Study→Analyze→Decide→Measure
Organization
Capture Problems→Prioritize→Research→Test Solutions→Pilot→Measure→Learn
A concrete example
A support lead describes a recurring onboarding failure. Three other users confirm the same friction and add their workarounds. The problem is structured, evidence accumulates, and an opportunity view surfaces the affected segment and existing-solution gap. A builder proposes a fix, tests the riskiest assumption with five interviews, and opens a waitlist before writing production code. Only once evidence holds up does the build begin.