Class 11 · Movement 02
Professional
Communication
Session 11 · Consulting
Session 11 · Communication is a role

Every deployment has a builder — and a translator.

Deltaowns the build — the code, the data, the demo
Echoowns the mission — stakeholders, expectations, the org’s map

Palantir staffs both on every deployment — the radio-alphabet role names are theirs: “technical build and organizational navigation are separate, equally hard skills.”

How seriously? This seriously.

Palantir sent new hires Keith Johnstone’s Impro — an improv textbook — to learn status mechanistically: how to read a room, when to lower yourself, when to hold ground. Communication trained like engineering. Not soft filler.

Your team runs the same pair: before the first visit, name your Delta(build owner) and your Echo (stakeholder owner). Same person some weeks — never zero people.
Compendium Part II — FDE History & Practice (Echo/Delta · the Impro onboarding)
Session 11 · Structure

Answer first. Then the reasons.

Recommendation
Key arguments
Evidence & detail

The Minto pyramid — “executives don’t want to follow your journey.” Owners don’t either.

The journey version

“So first we tried the CSV export, but the encoding was broken, so then we looked at the API, which needed a key, and after that we…”(the owner stopped listening at ‘CSV’)

Answer-first

“Quotes now generate in one day, not three. Two reasons: inventory syncs nightly, and pricing pulls live. One risk to flag: Dana’s spreadsheet still feeds one field — here’s the plan for it.”

The weekly recap email — your template, every week:
1 · The answer: “Quotes now generate same-day.”2 · Why / what changed: “Inventory syncs nightly; pricing pulls live.”3 · What’s next + what we need: “Next: Dana’s field. We need 20 min with her Tuesday.”
Three sentences, answer first — and the week-14 final presentation is the same pyramid, one hour long.
Minto Pyramid / BLUF (sources in research/notes/movement-m3.md, captured Aug 2026)
Session 11 · Translation

The same sentence, twice.

engineerWe’ll add RLS policies on the customers table.
partnerEach of your staff will see only their own customers — nobody else’s.
engineerThe webhook failed silently over the weekend.
partnerOrders stopped syncing Tuesday. Here’s how we caught it, and what we changed so it can’t happen quietly again.
engineerIt’s basically done — just needs tests.
partnerIt works in our checks. Before your team relies on it, we’ll verify it against a week of real orders.
The rule: translate mechanism into outcome — what changes for whom, by when. When you don’t know yet, that’s still answer-first: “I don’t know — we’ll have an answer by Friday.” And two words never leave your mouth on-site: “basically done.”
Session 11 · Representing

The trust you walk in with is borrowed.

How owners decide who to let in

Trust doesn’t come from pitches — it flows through intermediarieswho’ve earned it for years: 31% of owners name their accountant their single most-trusted advisor. Whoever the trusted advisor vouches for gets in.

The referral you’ll carry

Your five partners come through CTSBDC advisors — the same pattern. The owner is trusting the advisor’s judgment, not your résumé. That credit is spendable and burnable, and it isn’t yours.

Representing

On every visit you are UConn, Connect.AI, and the CTSBDC’s judgment — all three. So your Echo keeps the advisor one-pager: one page — problem found, what we’re building, status, next step — updated after every visit, ready for the advisor to forward any morning.

Compendium Part II — “Distribution Through Trusted Intermediaries”
Connect.AI logoConnect.AI
Class 11 · Professional Communication01 / 05
1 / 5
Checking access…