Three Readers, One Surface, Three Different Jobs

What this means for you

Choco has three first-class audiences and they read the same page for different reasons. If a marketing page tries to satisfy all three at once, it satisfies none of them. The product register names each audience with a job-to-be-done; copy is written to one of them at a time.

The pitch

Authors arrive with an open IDE and a half-written PR; they want the changelog and the link to teammates. Readers arrive between a stack trace and a fix; they want the verified code sample and the provenance. Evaluators arrive from a Slack thread asking what to use for docs; they want a one-line answer in under three minutes.

Who it’s for

Anyone editing choco.tools copy or shaping a campaign asset. The audience is named on the page, not assumed.

Proof points

• Three audiences named verbatim in choco-design-system/PRODUCT.md § Users: doc authors, doc readers, evaluators / decision-makers
• Each audience carries a context line in the source: “27” monitor, open IDE, half-written PR” for authors, “between a stack trace and a deadline” for readers, “Slack thread asking what should we use for docs” for evaluators
• Evaluator success criterion is concrete: form a confident judgment in under three minutes, leave with a one-line summary they can paste into Slack
• Reader success criterion is concrete: find the answer in under fifteen seconds and trust it on first read because the verification chain is rendered, not claimed (per cho-co/web/PRODUCT.md)

quadrantChart
  title Three readers on one surface
  x-axis Casual visit --> Decision-grade visit
  y-axis Reading the prose --> Inspecting the proof
  quadrant-1 Evaluators
  quadrant-2 Doc readers
  quadrant-3 Curious passers-by
  quadrant-4 Doc authors
  Authors: [0.85, 0.25]
  Readers: [0.35, 0.80]
  Evaluators: [0.80, 0.55]