Jira confidence-as-contract doctrine codified across engineering directs

Situation

Codified explicitly in Justin 1:1 5/21 and same-day endorsed via Chris W DM: Jiras confidence number is a communication contract between engineering and GTM. Rules: (1) drop confidence immediately when a date is at risk (e.g., 80%→50%), (2) slide the date by a calculated intentional amount, (3) once confidence is high (95%), the date is a firm commit and must be hit even at extra cost, (4) treat ALL work as change-requests (no bug-vs-scope debate), (5) any change in understanding triggers immediate date/confidence updates. Engineering Order of Operations vs JPD prioritization formally separated: engineering owns operational/health priority (e.g., image build pipeline rework), JPD = product-value priority. Significant misalignment triggers a conversation. Same doctrine to be rolled out to Nathan and Max next.

Reasoning

Multi-layer structural completion of the bug-vs-scope reframe started 5/19. The 5/19 Brady reframe (no bugs, only change requests) was the language piece — it removed the bug category but did not create enforcement surface. The 5/21 doctrine is the mechanism piece — confidence numbers give the language real-world teeth: dates that do not move must be backed by confidence updates as risk emerges, and 95% must be hit. Together they are the structural fix to the date-changes-happening-AFTER-deadlines pattern (4/14 → 5/12 → continued post-5/19 with multiple directs pushing dates after missing them). The accountability shifts from did you hit the date to did you flag the risk in time. Chris W applying the doctrine the same day (V4 +7d slip at 98% confidence) is the smoking gun the doctrine lands. Rolling it to Nathan and Max completes the cascade — when all four directs use the same language and mechanism, GTM finally has one source of truth and the Chris-Baek micromanagement ask (engineer-level tickets) becomes unnecessary.

Additional Context

Same week as the Brian Dawson 5/21 8am GTM-side reframe: consolidate/rename product priority tickets, ~130 items → ~50-55 value-driven initiatives over next 3-4 months. Engineering doctrine + product board cleanup landed in the same week intentionally — the two sides of one reframe. Mid-year review timing also relevant: directs are in reflective-receptive mode when the doctrine gets taught.

Observed Evidence

Justin 1:1 transcript-level coaching of the protocol. Chris W same-day application + Peter explicit endorsement in DM. Action item for Peter to schedule walkthrough with Nathan/Max. Engineering Order of Operations formalized as separate from JPD.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis