Write the problem hypothesis
For [specific user], completing [job] is difficult because [missing capability], causing [measurable consequence].
You can name one user, one situation and one measurable consequence without proposing a feature.[Feature] Strategy Discovery Phase 3 — description-driven adaptation
Evidence observed in HKUDS/Vibe-Trading, a Finance project.
4 comments0 positive reactions21 days openProject Radar 93
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: Split out of #969, which is closed now that Phase 1 (#978) and Phase 2 (#1007) have landed. That issue said from the start that Phase 3 was out of its scope, and the shape below is the two lines it reserved, expanded against what actually shipped. What exists now The Strategy Discovery facade answers what strategies…Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- When did you last need this?
- What outcome were you trying to reach?
- What did you use instead?
- How often does this occur?
- What commitment would prove it matters?
Run the smallest experiment
Deliver the outcome manually or with a narrow prototype before building a reusable feature.
A user completes the real workflow and commits time, data, distribution or budget to repeat it.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.