1.2"I Found Something" vs "You Broke Something"

The single most important shift in bug reporting is moving from blame-oriented language to observation-oriented language. This is not about being soft or avoiding truth. It is about framing the conversation so the developer's energy goes toward fixing the problem rather than defending themselves.

Language Comparison

Blame-Oriented (Avoid)	Observation-Oriented (Use)
"You forgot to validate the email field"	"The email field accepts invalid formats like 'abc@'"
"This is broken again"	"This behavior differs from the acceptance criteria in SHOP-123"
"Whoever wrote this didn't test it"	"This scenario may not have been covered during development"
"Why wasn't this caught in code review?"	"This edge case might be worth adding to the unit test suite"
"The developer didn't follow the spec"	"The implementation differs from the spec in this area -- should we update the spec or the code?"

Why Framing Matters

• Blame triggers defensiveness. A developer who feels attacked will spend energy justifying their code instead of evaluating the bug.
• Observation invites collaboration. When you describe what you see without assigning fault, the developer naturally moves to "let me look at this."
• Bug reports are permanent records. Managers, new team members, and auditors may read them months later. Tone persists.