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.Evidence observed in trypostit/trypost, a Marketing project.
Related friction appears in 10 independent repositories. This is stronger than one backlog item, but still requires direct user validation.
Project strength and demand confidence are measured separately.Reporter context: Design and implementation plan for the media-constraint work, ready to execute. Supersedes the approach in #287 and covers all three goals of #200. Full design doc and the Phase 1 task-by-task plan are attached as comments below, so this issue is self-contained. Why #287 can't be merged as-is PR #287 extended from…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit people running a current campaign, channel or content workflow—not people reacting to an idea pitch.
Guardrail: Measure completed workflow, time saved or a real distribution commitment; do not treat clicks or compliments as proof.
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.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.Measure completed workflow, time saved or a real distribution commitment; do not treat clicks or compliments as proof.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.