Directed Nathan to surface eng-product communication gaps

February 12, 2026 at 6:08 PMpeoplemedium

Situation

After Department Heads meeting, spent 30 minutes coaching Nathan 1:1. Praised his handling of the meeting despite frustration. Directed Nathan and Justin to be proactively transparent with product, and specifically to surface instances where engineering communicates clearly but product claims ignorance.

Reasoning

The Department Heads meeting surfaced that product sometimes claims ignorance of things engineering has communicated. By directing Nathan to surface these gaps publicly, Peter creates accountability on both sides of the eng-product interface. This builds an evidence trail for cross-functional disputes. Coaching tone (praise first, then direction) invests in Nathan's growth while channeling frustration into productive action.

Additional Context

Immediately following Department Heads meeting where coordination mandate was set. Peter was in Riyadh in transit but invested 30 minutes coaching Nathan, indicating high priority. Told Max afterward he was 'pretty happy with the way Nathan handled that meeting.'

Observed Evidence

Slack DM to Nathan: 'Good job on this call being clear about what was already communicated with Prod. And the clarity around release planning and the board was great.' 'You are frustrated. This is the meeting for that stuff to come out.' 'I need you and Justin being super open and proactively clear with product. Where thats happening, and prod is then turning around and saying they dont know... I need that coming to light.' Slack DM to Max: 'Overall I was actually pretty happy with the way nathan handled that meeting. I know he was frustrated. Just spent a good 30 minutes with him.'

Matching Patterns

30%
Accountability Follow-Through(same category (people), setting expectations with consequences)

Confidence Breakdown

32/35
Evidence
18/30
Pattern
17/20
Source
11/15
Corroboration

Reasoning Depth Analysis

Org Signal:Signals that eng-product misalignment will be documented and visible, not swept under the rug
Who Affected:Bjorn's product org, Justin (also directed), broader eng-product dynamic
Precedent:Creates expectation that engineering leaders proactively document what they communicated to product
Consequences:If product claims we didn't know and engineering can show they communicated, accountability shifts
Timing:Immediately after Department Heads meeting where coordination mandate was set - reinforcing the standard 1:1

Source

reflection

AI Confidence

78%

Related Context

💬
DM with Nathan Blackham

slack

I need you and Justin being super open and proactively clear with product. Where thats happening, and prod is then turning around and saying they dont know... I need that coming to light.

💬
DM with Max Spevack

slack

Good feedback. Overall I was actually pretty happy with the way nathan handled that meeting. I know he was frustrated. Just spent a good 30 minutes with him.

Outcome

No outcome recorded yet.

Decision ID: 75590e11-c0e6-416b-8d13-0f11c6ecb815