Engineering owns all QA — Nathan accountable; tests required for Done; Ryans team builds tooling not rescue

Situation

Non-negotiable directive issued to Ryan: engineering is responsible for its own QA, Nathan is named accountable for quality, and a ticket is not Done until it has documented executed tests. Ryans role is re-shaped: build QA automation tooling (Gauntlet CLI, Outfitter, CIQCTL) that empowers engineers, NOT take over QA responsibility from engineering. Documentation also clarified: engineering provides all technical content; the customer-ready presentation layer is a Ryan-and-Lindsay conversation. Ryan to define a Definition-of-Done lifecycle visual for H2 to standardize across the org. Peter committed to email Nathan and Justin directly to reassert.

Reasoning

Same family as the 5/21 Jira confidence doctrine (D3). D3 makes dates engineerings responsibility; D4 makes quality engineerings responsibility. Both close the Ryan-team-fills-the-gap and QA-blames-Eng-Eng-blames-QA cycles by re-attaching ownership to the source. Ryans team was structurally drifting into permanent-rescue mode — Ryan named it (we are manually filling engineering gaps which is unsustainable) and Peter answered not by growing Ryans team to absorb more rescue, but by pushing it back. Naming Nathan as accountable rather than engineering generically is the give-away: diffuse ownership = nobody owns it; concrete name = real conversation when a ticket lands Done without tests. Ryans new role mirrors the Justin paved-paths pattern from 5/6 — internal tooling that empowers the line org without substituting for its responsibility. The Definition-of-Done visual is the structural closure: future Done debates collapse to did this meet the visual.

Additional Context

Same week as Jira confidence doctrine (D3) and the GTM-side board cleanup (Brian Dawson consolidating ~130 product priority tickets to ~50-55). Three reframes — dates, quality, product priority — landing in the same week. The reframes reinforce each other: if quality and dates both have clear owners and product priority is consolidated, the misalignment-blame loops collapse.

Observed Evidence

Direct Fathom summary of Peters directive language. Peter-assigned action item: Email Nathan/Justin: reassert engineering QA ownership; require tests for Done. Ryan-assigned action items reshape Ryans team toward tooling (Gauntlet/Outfitter/CIQCTL) and Definition-of-Done visual.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis