← Back to Demand Signal Radar
PUBLIC VALIDATION BRIEF

Media constraints: correct the platform limits, then measure video server-side

Evidence observed in trypostit/trypost, a Marketing project.

2 comments0 positive reactions48 days openProject Radar 85
enhancement
Start the no-account validation tool4 guided steps · private browser notes · export anytime
DEMAND CONFIDENCE

REPEATED ACROSS 10 PROJECTS

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.
SOURCE EVIDENCE

Start with what users actually said

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.

Read original GitHub Issue ↗
MARKETING VALIDATION LENS

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.

01 · Product Capability workflows

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.
02 · EVIDENCE INTERVIEW

Interview five marketers or growth operators

  • 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?
At least three people independently describe the same painful workflow with recent examples.
03 · MINIMUM TEST

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.Measure completed workflow, time saved or a real distribution commitment; do not treat clicks or compliments as proof.
04 · DECISION GATE

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
Do not let GitHub engagement replace direct validation.

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.