Documentation process — Product defines exit criteria in Jira, Engineering delivers

Situation

Formalize documentation ownership: Product defines documentation requirements in Jira ticket exit criteria (e.g., docs suitable for blog post). Engineering delivers content meeting those criteria. Product or Marketing (Lindsay) refines technical content into user-friendly format.

Reasoning

Engineers were getting pulled into ad-hoc doc work outside the ticketed system, eroding the Jira-as-system-of-record discipline set 4/30. Product (Brady) was asking Engineering for docs without explicit acceptance criteria, creating ambiguity about done. The fix is structural: put doc requirements where work-in-flight already lives (Jira exit criteria) so engineers cant be ambushed and Product cant ask retroactively. Pairs with the QBR theme — formalizing the handoff before QBR makes the QBR about working systems, not negotiating new ones. Same externalize-friction shape as 4/30 Slack-only refusal.

Additional Context

Direct precedent: 2026-04-30 Jira-as-system-of-record enforcement, 2026-04-18 Quality initiatives must be ticketed visible work. Discussed with Chris Baek who is preparing the P+E QBR Miro board.

Observed Evidence

Peter <> Chris (5/1): explicit framework laid out — Product defines what, Engineering delivers how, Marketing refines for audience. Pairs with 4/30 Slack-only refusal as the ratchet pattern.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis