Hand the Dawson document-noise complaint back to Justin with an instruction - be done with subtle

September 11, 2026 at 10:34 PMpeoplelow

Situation

Justin DMed Peter that Brian Dawson AI-generated document output is an increasing source of wasted time for more people than just him, attached the RLC Pro HPC specification document and a related Jira bug, and closed with no direct ask for you, just awareness. Peter declined that framing, asked whether working it from my side meant being very clear with Brian, got Justin admission that it meant being polite and probably too subtle, and answered - be done with subtle.

Reasoning

Justin was routing a peer problem upward while describing himself as already handling it, which usually means the handling is not working. Peter diagnosed the failure as delivery rather than substance - he took no position on whether the documents are actually poor, going straight to whether Justin had said so plainly. The informal polite channel has a track record of failing here, so the answer is a different instrument rather than more of the same. Peter also declined to intervene himself, which is the substantive half of the decision.

Additional Context

Landed roughly fifty minutes after Peter spent half an hour disagreeing with Dawson directly in the Brian and Brady sync and closed that conversation by checking it had not felt combative. He is asking Justin to have the conversation he had just modelled having. Runs alongside the earlier choice to route the RLC-AI driver override through Bjorn rather than overrule Dawson publicly - same person, same instinct to keep corrections out of venues that humiliate.

Observed Evidence

Direct quotes from the Slack DM exchange, four messages over four minutes.

Matching Patterns

45%
Switch Instrument, Not Intensity(treats the track record of the informal channel failing as the trigger, diagnoses delivery rather than substance)
25%
Demonstrate the Standard, Then Collect It(partial - Peter had modelled the direct conversation an hour earlier)

Confidence Breakdown

30/35
Evidence
20/30
Pattern
18/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:No direct ask, just awareness is not an accepted way to hand a peer conflict to the CTO. It gets handed back with an instruction rather than absorbed.
Who Affected:Brian Dawson, the subject, who does not know the exchange happened; Damen Knight, on the linked Jira bug; the other unnamed people Justin says are losing time.
Precedent:If you are going to raise a peer to Peter, you are expected to have raised it to the peer first and plainly. Escalation follows a clear direct attempt, not a subtle one.
Consequences:Real - Peter declined to intervene in a conflict he could have taken on himself, and put the burden of a difficult conversation back on Justin.
Timing:Immediately, in the DM, with no meeting scheduled around it - which itself signals the conversation is Justin to have rather than something to work up to.

Source

reflection

AI Confidence

74%

Related Context

💬
DM with Justin Haynes

slack

Justin: I am working on this from my side of things, but Brian AI slop is becoming an increasing source of wasted time and annoyance for not just me. No direct ask for you, just awareness. Peter: by working it you mean being VERY clear with Brian? Justin: I mean being polite and probably too subtle. Point taken. Peter: yeah - be done with subtle

Outcome

No outcome recorded yet.

Decision ID: 90a673f1-89c1-4a04-9b9f-a21df351cb02