Four Readers, Four Reasons to Care

What this means for you

Chronicle has four named reader segments, each with their own trigger phrase pulled from real frustrations. When copy has to choose, the hierarchy is set: developers and product managers are fast self-serve, technical writers and compliance teams are slower team-buyer paths. Lead with the fast paths. Build assets that the slow paths can socialise.

The pitch

Product managers want visibility. Technical writers want accuracy across releases. Developers want craft equivalent to their code tools. Compliance teams want a defensible audit trail. The same timeline answers all four questions, but the framing changes by segment.

Who it’s for

Anyone briefing a Chronicle campaign asset who needs to pick the primary reader before writing the first line.

Proof points

• Four segments are named and quoted in docs/marketing/chronicle-campaign-intelligence.md with their actual frustration language, not marketing speak
• Product manager trigger: “I asked the team three times who changed the pricing section. Nobody remembered.”
• Technical writer trigger: “Every release cycle I spend 2 hours figuring out what changed in the spec since last quarter.”
• Developer trigger: “I have Git blame for code but nothing equivalent for my RFCs and ADRs.”
• Compliance trigger: “Our current audit trail is ‘export to PDF and hope nobody asks questions.’”
• Self-serve segments (developers, individual PMs) convert fast. Team-buyer segments (compliance, writing teams) need a “share with your team” CTA.

quadrantChart
  title Chronicle reader segments, by velocity and depth
  x-axis "Skim" --> "Deep evaluate"
  y-axis "Self-serve" --> "Team buyer"
  quadrant-1 "Compliance and legal"
  quadrant-2 "Technical writers"
  quadrant-3 "Individual product managers"
  quadrant-4 "Developers and OSS maintainers"
  "Product managers": [0.4, 0.35]
  "Developers": [0.85, 0.2]
  "Technical writers": [0.7, 0.75]
  "Compliance teams": [0.8, 0.9]