No bugs, only change requests — structural reframe for product/engineering interaction

May 19, 2026 at 2:55 PMoperationalhigh

Situation

Peter coached Brady (with Brian Dawson present) to eliminate the bug terminology in JPD/Jira entirely and replace it with change-request framing — borrowed from a CRM system Peter used at a smaller company earlier in his career, where the bug-tracking system had no bugs category type to eliminate the QA-vs-engineering-vs-product debate. Code works this way at this moment, I want to change it. Whether it's a bug or a new request — not material. Brady committed on the spot to roll out the change with Chris and Jamie and through Nathan's team. Brian aligned. Goal: remove the psychological/defensive trigger that makes prideful engineers slow to ship.

Reasoning

The bug label triggers a defensive response in engineers — Brian named it explicitly in the same meeting: a bug can signal to a prideful engineer that you screwed up. And their next step is to defend it. Peter has watched this drag down the speed-of-shipping conversations all year. The reframe removes the debate by reducing all change requests to one type and making priority the only conversation, not legitimacy. Connects to the broader observation Peter made in the same meeting: engineers here value perfect, not shipping. He values shipping — and the change-request framing aligns the terminology with that value.

Additional Context

Same meeting also covered the AI Forward Deployed Engineer discussion (Peter: write the JD first, then ask if Michelle can do it before adding a head), and the JPD-board granularity conversation (Peter protecting the board's soul from being prioritize-all-engineering-work-everywhere). This is the third Peter→Brady framework drop in 6 weeks: 5/5 strategy-first/tactics-second, 5/12 (5/13 reflection) Engineering QBR collaborative format, now 5/15 no-bugs-only-change-requests.

Observed Evidence

Direct quote of the full CRM-system story and the I-will-happily-make-that-shift-right-now commitment from Brady, plus Brian's aligned-as-well-yeah-I'm-aligned-as-well close. ~22-25 minute mark of 5/15 weekly sync transcript. Bug-triggers-defensiveness psychological framing came from Brian first; Peter extended with the change-request reframe.

Matching Patterns

50%
Protect Engineering Focus Through Process(process-level move, removes inter-team conflict, same category)
35%
Lead by Example with New Tools(Peter shares his own past usage, operational adoption)

Confidence Breakdown

33/35
Evidence
18/30
Pattern
20/20
Source
17/15
Corroboration

Reasoning Depth Analysis

Org Signal:Bigger than terminology — it's a teaching move about how prideful engineers ship faster when defensiveness is removed. Continues the meta-coaching arc with Brady that Peter has been running for weeks.
Who Affected:Every product-engineering interaction, not just Brady's tickets. Cascades through Nathan/Justin's teams. Brian Dawson (PM-ish role with Brady) was an aligned witness — now multiplies the rollout.
Precedent:First time Peter has framed THIS specific lever — joins strategy-first/tactics-second as part of the structural-process-coaching arc. Establishes that category vocabulary itself is a leverage point.
Consequences:Brady commits to rolling out with Chris and Jamie, then Nathan's team. Real test: does the language change actually land in Jira workflows over the next 4-6 weeks, or does it stay in conversation only?
Timing:Lands at the moment after copy-fail and dirty frag when engineers are exhausted and most likely to be defensive about quality — counterintuitive timing, but psychologically right. Peter is removing the defensiveness trigger right when defensiveness would otherwise spike.

Source

reflection

AI Confidence

88%

Related Context

🎥
Brian / Brady Peter Weekly Sync 5/15

fathom

Just don't call it a bug. ... Because who cares? You want the change made. Okay. What's your priority on that? Cool. That's where it lives. ... I lived it for almost a decade, and I thought it was absolute genius in terms of the conflicts that it got rid of.

Outcome

No outcome recorded yet.

Decision ID: f24ab94f-3b80-4846-be06-aa8db1b722b0