Google Meeting Communication Coaching for Brady/Nathan

April 9, 2026 at 3:10 PMstrategyhigh

Situation

Directed Brady and Nathan on exactly how to communicate during the Google GDC follow-up call — present CIQ as calm, capable, and dedicated; don't volunteer unnecessary details; distinguish technical infeasibility from resource constraints. Personally bookended the engineering meeting with success criteria. Chose to keep GDC post-mortem attribution under Peter's name rather than crediting others.

Reasoning

The Google relationship is strained (two phone calls expressing unhappiness in one week). Uncontrolled, overly-transparent messaging was actively weakening CIQ's position. Brady and Nathan needed explicit coaching because Google was conflating 'can't do technically' with 'need more people', which undermined confidence in CIQ's capabilities. Presenting a unified CTO voice rather than diffusing responsibility across multiple people strengthens CIQ's negotiating position.

Additional Context

Extends the GDC communication centralization established April 7. Tissa changed the meeting agenda that morning to focus on 6.18 FIPS plan, timelines, and development model — making this a high-stakes technical meeting that required disciplined messaging.

Observed Evidence

Direct Slack messages coaching Brady/Nathan before the Google call. Fathom recording of pre-GDC strategy session where Peter decided to bookend meeting with success criteria. Email to Max explaining why attribution under Peter's name was deliberate.

Matching Patterns

30%
Executive Sponsorship for Strategic Partnerships(CTO-level control of partner messaging, same category (strategy))
30%
Small Circle for Sensitive Operations(controlling information flow to strained partner, same category (strategy))

Confidence Breakdown

34/35
Evidence
20/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:Centralizing communication signals CIQ takes this relationship seriously at the executive level
Who Affected:Kelly (relationship manager), Tissa (Google champion depending on CIQ credibility), Google engineering team forming impressions of CIQ
Precedent:Establishes that strained partner communications get CTO-level messaging discipline
Consequences:If Brady/Nathan say the wrong thing, Google could escalate or reduce engagement; correct messaging preserves Tissa's internal champion position
Timing:Day-of coaching because Tissa changed the agenda that morning — no time for formal prep

Source

reflection

AI Confidence

85%

Related Context

💬
Brady/Nathan Group DM - Meeting Coaching

slack

This is a VERY careful call today. We are not talking to friends. We are talking to a company that has literally gotten on the telephone with us twice in the last week to tell us the are unhappy.

💬
Brady/Nathan Group DM - Messaging Precision

slack

'would take months of work' is a meaningless statement that brings up tons of other questions.

🎥
Pre-GDC update from Tissa Call

fathom

Peter will bookend the meeting by defining success criteria upfront and reviewing them at the end.

📧
Email to Max re: GDC post mortem attribution

email

I generally really want to make sure people are publicly accredited for their stuff… But in this case it sounding like it came from me was critical.

Outcome

No outcome recorded yet.

Decision ID: 049b556f-8a23-4d2d-8615-8c80abb6f2e5