← Back to Demand Signal Radar
PUBLIC VALIDATION BRIEF

Widget: make the chat window fit on small phones

Evidence observed in answerLoops/answerLoops, a Research project.

2 comments0 positive reactions11 days openProject Radar 77
enhancementgood first issuehelp wanted
Start the no-account validation tool4 guided steps · private browser notes · export anytime
DEMAND CONFIDENCE

REPEATED ACROSS 8 PROJECTS

Related friction appears in 8 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: The problem today The chat window on a customer's website is a fixed width (about 380 pixels). On phones narrower than that, part of the window hangs off the edge of the screen and visitors can't reach the send button or close button. What to change On small screens (phone width), the chat window should fill the…Excerpted from the public Issue. Read the complete thread before interpreting it.

Read original GitHub Issue ↗
RESEARCH VALIDATION LENS

Recruit: Recruit people who can bring a recent literature, evidence-review or source-tracing task.

Guardrail: Measure citation accuracy, coverage and review time; never reward speed at the expense of source fidelity.

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 researchers, analysts or librarians

  • 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 citation accuracy, coverage and review time; never reward speed at the expense of source fidelity.
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.