Joint Team Intro Meeting — Meeting Prep

Meeting date: 2026-07-06 (Day 1, provisional) · Prep started: 2026-07-04 Context: small team (2–5), roles not yet known to Amir. Amir leading. Precedes the individual one-to-ones (E2, 7/8).

PrAxis workshop. Exploratory by design — not the Executive Brief yet.

Stage 1 — Understand the Meeting

True purpose. This is not an information-gathering session — that's what the 1:1s are for. This is the team's first live data point on what kind of manager they're getting. They continue their existing work under a new manager; this is explicitly not a departing-staff handover, which means there may be no clean "fresh start" framing available — some may be comparing Amir, consciously or not, to whoever led this space before, or to no one at all if the role itself is new.

What success looks like. The team leaves with three things settled: who Amir is (briefly), what week one actually looks like for them (nothing dramatic, individual conversations coming), and that their voice will be heard individually, not just managed as a group. Depth of content is not the measure here — the 1:1s carry that.

What can only happen in this room, not in the 1:1s. The group dynamic itself — who speaks first, who defers to whom, who fills silence, who watches others before answering. This is the first live input to the people-map you want to build across the week (who creates energy, who creates clarity, who people naturally follow) — and it shows differently in a group than it will one-on-one. Worth treating this meeting as observation, not just delivery.

What should not be discussed yet. - No account-specific content, no numbers, no performance language. - No promises about org changes, headcount, or structure — even reassurance can turn into an accidental commitment if phrased loosely. - No implicit comparison to a predecessor, even a flattering one.

What a first-class executive does differently. An average manager treats this as "introduce myself, state expectations, take questions." A first-class executive reads and addresses the unstated anxiety directly — this is a leadership change the team likely didn't ask for, even if nothing is wrong — and does it without over-promising. They also resist the pull to fill the room with their own vision; day-one talking too much is the single most common failure mode here, not too little.

Fact / assumption / hypothesis / political-signal split

Scenario locked: Shashi present, co-leading. Default scenario for this prep. A solo variant can be drafted as a diff later if the format changes.

Stage 2 — Conversation Architecture

Themes

Flow

Shashi opens (frames why, expresses confidence, hands over) → Amir's personal intro + entry posture → practical logistics → open floor with explicit permission to hold things back for the 1:1s → Shashi closes if he wants to.

A sequencing wrinkle worth naming

This meeting (provisionally Monday) happens before the mandate-sharpening session with Shashi (Tuesday). Nothing about the role's direction is actually settled yet — only the provisional framing exists. Keep language in front of the team deliberately general ("early days, still shaping this together") rather than presenting anything as decided. Saying something here that turns out to contradict what emerges Tuesday costs credibility with both audiences.

Branches

• If Shashi's framing leans hard into performance/urgency language: don't contradict him in the room, but pivot your own section back to "in week one, my job is to listen" rather than layering on more pressure.
• If the team is unusually quiet/formal in front of Shashi: treat that as data about the culture, not a verdict on the team — expect the 1:1s to reveal more than the group setting will.
• If someone asks a politically loaded question (job security, why this role exists) in the room: let Shashi field the organisational/political half; take the personal/working-style half yourself, unless he visibly hands it to you.

Worth doing before the meeting, not in it

A short pre-sync with Shashi on core messaging — so neither of you says something in the room the other has to walk back (e.g. any language implying restructuring, headcount change, or a fixed timeline for results).

Stage 3 — Pressure Test

• Missing: the pre-sync with Shashi on messaging isn't in the loop anywhere as an action — worth adding to the E1 prep or handling separately before Monday.
• Sequencing risk: flagged above — team intro before the mandate is actually settled with Shashi. Real risk of over-committing language too early.
• Assumption to challenge: that the team will be neutral-to-receptive. Unknown whether this consolidation reduces anyone's autonomy or replaces an arrangement they were attached to — worth entering without assuming warmth.
• New risk specific to the co-presented format: the audience is now double — team and boss watching how you handle the room. Guard against performing for Shashi rather than actually speaking to the team.
• Missed opportunity: the debrief right after — comparing notes with Shashi on his read of the room — is itself a political-economy data point (Q10, informal influence) and shouldn't be skipped just because the formal meeting is over.

Stage 4 — Executive Brief

Meeting Objective Land as a considered, credible addition to the team — not an imposed change — while giving away as little settled content as possible, since the mandate itself isn't locked until Tuesday.

Conversation Openers 1. (Let Shashi frame first.) Personal intro: who you are, briefly, and why you're glad to be doing this. - Calibration note (personal working note, not a script): the gated/oversharing worry is the same root cause either way — treating your own airtime as something to manage for perception rather than as a means to an end. Fix: cap it structurally, don't judge content mid-sentence. ~30–40 seconds: one sentence on relevant background, one sentence on why this move genuinely drew you, optionally one light personal line (how you like to work, not your life outside it — skippable), then pivot straight into the entry posture ("what I want from week one is..."). The pivot is the actual safety valve — it moves the floor off you by design. Shashi's opening carries the legitimacy work, so your content doesn't have to; erring slightly toward brief and over-delivering on curiosity about them in the open floor is directionally correct, not a compromise, given the meeting's own objective is listening-first. - Finalized script (~35 sec, drafted 2026-07-06): "Quick background on me: my path's run through Strategy, then Non-food as a P&L, most recently Project Garuda — our largest greenfield capital build, from investment case through to handover. What genuinely drew me to Strategic Customer Partnership is that it's a brand-new pillar — this hasn't existed as a dedicated function before, so we get to design how we win with key customers from the ground up, together. I tend to work by getting close to the data and the people closest to the customer before I propose anything. So my posture for the next few weeks is to listen and learn first — understanding the customer universe and what's already working — before we shape together how we'll measure success." - Revision note: earlier draft used "there's nothing built yet" and "baselining" — both read as an implicit critique of whoever handled customer relationships before this pillar existed. Reframed as a deliberate new investment (brand-new pillar) rather than a gap someone left, and softened the entry-posture language to "listen and learn first" / "shape together" throughout. 2. "I'm not here to audit anyone in week one — I want to understand where things work well and where they don't, from you." 3. Practical: individual conversations happening this week (name the day if set), and what those are for. 4. Open floor: "What would be useful for me to know before we go deeper individually?" — with explicit permission to say nothing yet and save it for the 1:1.

Things to Listen For - Whether the room's response to Shashi is warm/energised or flat/deferential — a data point on his standing with this team. - Who speaks first, who defers, who watches others before answering — the first read for the people-map. - Any question that's really about job security or continuity, dressed as something else.

Political Signals - How much conviction Shashi puts into introducing the role — perfunctory vs. genuinely invested — is itself a signal for the Political Economy workbook. - Whether Shashi's framing and your own stay aligned live, or whether you find yourself quietly softening something he said.

Watch Outs - Don't present anything as settled — nothing is, until Tuesday. - Don't compete for airtime or over-explain to manage your own nerves about the room. - Don't let this become the venue for hard content — that's what the 1:1s are for.

Definition of Success The team leaves knowing who you are, that nothing dramatic happens this week, and that their individual voice is coming — plus you leave with a first read on the room's dynamics and on Shashi's standing with this team.

Not done yet, by choice: Stage 5 (debrief framework) — parked for now, same as E1, to be handled live at debrief time.