E1 — Shashi Mandate Session — Meeting Prep

Meeting date: 2026-07-07 · Prep started: 2026-07-04

PrAxis workshop. Exploratory by design — this is not the Executive Brief. Stage progression: Understand → Architecture → Pressure Test → Brief → Debrief Framework.

Stage 1 — Understand the Meeting

True purpose. Not information-gathering. Two things are happening at once: (1) extracting Shashi's actual, stress-tested definition of a winning year, replacing the provisional framing from a brief prior conversation; (2) resetting the relationship's footing now that Shashi is boss, not peer. The second is arguably higher-risk than the first — a peer-to-boss transition that isn't consciously handled tends to leak into how directly Shashi will give feedback, and how much Amir defers versus pushes back.

What success looks like. Leaving with year-end criteria specific enough to act on — not "programmes and a roadmap" as a phrase, but what counts as a programme, how many, and what "tracked and executed diligently" means operationally. Plus: convening authority and data access confirmed (ideally in writing), a steer on Renaka sequencing, and a working read on whether Shashi is treating this as a real strategic conversation or a formality.

What can only come from Shashi, specifically. - Whether the volume-not-primary-driver framing is his settled conviction or a placeholder he hasn't pressure-tested himself. - The political weight behind this appointment — is APAC Differentiated under its own pressure (from CEO or board) to show fast wins, which could quietly reintroduce volume pressure regardless of the stated framing? - What "genuinely useful to your APAC Differentiated agenda" means in his own words, not Amir's inference. - Whether the license to convene functions is real delegated authority or something Amir will have to re-litigate function by function.

What should not be discussed yet. - No finished programme plan — nothing has been tested against real accounts yet. - No precise KPI numbers. Asking Shashi to commit to hard metrics before the team/data download risks locking in an arbitrary number that's expensive to unwind later. - Nothing about Amir's own career trajectory or scope ambitions — too early, wrong register for a first working session as direct report.

What a first-class executive does differently here. An average manager runs the nine prepared questions as an interview and leaves with answers. A first-class executive also uses the session to read Shashi — does he engage with the real tension in "programmes over volume" (which cuts against short-term revenue optics), or does he retreat to safe generalities when pressed? That tonal signal — building freely vs. delivering a pre-defined thing — matters more than the literal wording of any answer. A first-class executive also does not treat "sharpen the mandate" as purely a definitional exercise; the unstated job in a first meeting as new direct report is to demonstrate, within the hour, that the appointment was the right call — competence signalling and information-gathering happen simultaneously, not sequentially.

Fact / assumption / hypothesis / political-signal split

Stage 2a — Question Triage (before full architecture)

Nine original questions from the Weekly Loop, reduced to six headline questions for this sitting, one folded in as a natural follow-on, and one deferred entirely to E2 (team one-to-ones), where it's better answered anyway.

Combined. Original Q1 ("what does a strong year-end look like — customer count, what counts as a 'programme,' what 'tracked and executed diligently' means") and Q3 ("confirm performance = programmes/execution/leading indicators, over volume") are one question, not two — Q3 is really the closing confirmation of Q1's answer. Merging removes a redundant second pass at the same topic.

Deferred to E2, not this session. Original Q9 ("who owns the contract library and real commercial deal data — allocation splits, settlement terms, tolerance bands, rate benchmarks") is a who-has-the-data question. Shashi is very unlikely to hold this at field level — the team does. Asking it here spends Shashi's time on something the team download answers better, and crowds out the questions only he can answer.

Folded in, not standalone. Original Q2 (key-account list size, MNC vs. regional treatment, current criteria) rides naturally on the back of the year-end definition — if time allows, ask it as a direct follow-on to Q1's answer rather than as its own agenda line. If the conversation runs long, it's the first thing to drop; it can be picked up with the team or in a fast follow-up note to Shashi.

The six headline questions, in sequence:

Deferred to E2: who owns the contract library and commercial deal data (orig. Q9). Fold in opportunistically: key-account list size / MNC vs. regional criteria (orig. Q2) — attach to Q2 above if the conversation supports it; otherwise pick up separately.

Stage 2 — Conversation Architecture

Not a script. The six questions are the spine; this is how the conversation actually moves, and what to do when it doesn't go as planned.

Major themes

Flow

Opening (Theme A + Q1) → anchor (Theme B, Q2, fold in list-size/criteria if it's flowing) → pivot to harder ground (Theme C, Q3 then Q4) → grounding (Theme D, Q5) → close (Theme D, Q6 + forward logistics).

The pivot from B to C is the moment to watch. Theme B is comfortable — Shashi gets to talk about vision. Theme C asks him to commit resources and boundaries. Don't rush that transition; let the definition-of-success answer settle before asking what it will take to convene the functions that make it real.

Follow-ups by question

• Q1 (agenda usefulness): "Is there something specific that isn't working today that you'd want this role to visibly fix within six months?" — converts an abstract answer into a concrete early target.
• Q2 (year-end definition): "What would make you say at year-end 'that was a strong year' versus 'okay, but not what I wanted'?" and "Is there a number in your head — even rough — for what real key-account coverage looks like?"
• Q3 (convening authority): "If I need R&D or trading's time and don't get it, what's my recourse?" and "Would an intro note from you to those functions help before I arrive?"
• Q4 (pricing boundary): "Concretely — if I want to offer a differentiated commercial term to a key account, whose sign-off do I actually need?" This is the question that turns a conceptual boundary into a real decision-rights answer.
• Q5 (baseline): "If the honest current baseline is close to zero, is that the fair comparison point, or will there be pressure for immediate movement regardless?"
• Q6 (Renaka): "Anything I should prepare before that conversation happens?"

Difficult questions (uncomfortable but worth asking)

• The load-bearing one: "If six months from now the volume numbers are soft but the programme pipeline is strong, will that genuinely read as success — or will pressure shift back to volume?" This tests whether the stated framing survives contact with real performance pressure. Everything else in the mandate depends on the honest answer here.
• Triangulation risk: "Are you and Renaka fully aligned on this framing, or is part of my job to align the two of you?" Sensitive, but the alternative is discovering a gap between them later, after commitments have already been made to each separately.
• Sponsorship strength (soften before asking): rather than "did you push for this or was it handed to you," ask "how much of this mandate is your own design versus something set above you?" — same information, less confrontational framing.

Political considerations

• The "programmes over volume" framing may be Shashi's genuine conviction, or useful positioning language for his own agenda upward (APAC Differentiated as forward-looking) — or both. That's not a problem; if it's both, Amir's success is Shashi's success, which is real alignment, not just a directive to satisfy. Worth noting which it seems to be, but not worth asking directly.
• Renaka is a triangulation risk, not just a sequencing question — if Shashi and Renaka hold different unstated expectations, Amir is exposed the moment he commits language to one before checking the other.
• Watch energy, not just words: does Shashi engage animatedly with the tension in "programmes over volume" (real conviction) or answer it the way one answers a question already decided elsewhere (surface compliance)?
• Throughout: the objective is not just extracting five answers — it's demonstrating synthesis in real time (reflecting Shashi's own words back sharper than he gave them) so this meeting also does the competence-signalling work flagged in Stage 1, rather than treating information-gathering and impression-management as sequential.

Next: Stage 3 — pressure test this architecture (missing questions, sequencing problems, premature topics, risks, missed opportunities).

Stage 3 — Pressure Test

Missing questions

• Why now / why this shape. Nothing asks why this role exists at this moment, or what precipitated it. "Near-zero base" implies no real predecessor, but it's worth confirming — was there a prior attempt at this space that fell short, and is Shashi reacting to that? This shapes what "success" implicitly needs to avoid repeating.
• The negative space of success. Q2 defines what a strong year looks like. Nothing asks the inverse: what would cause Shashi to lose confidence early — a specific failure mode he's watching for. Symmetry matters; the downside signal is often more concrete than the upside one.
• What Shashi needs from Amir directly. Nothing probes whether there's a way to be useful to Shashi's own agenda beyond the customer portfolio itself. This is a missed sponsorship-deepening opportunity, not just a nice-to-have.
• Live fires. Nothing asks if there's a customer situation already active that Amir should know about before day one, to avoid being blindsided in week one.

Sequencing problem — Theme A has no actual move

Stage 2 named "the relationship reset" as the first theme but gave it no explicit question or action — it was left as ambient tone rather than something addressed directly. Opening straight into Q1 ("what would make this useful to your agenda") is still content-first. A genuine first move for Theme A would be naming the shift plainly — something like "this is a different dynamic than when we were peers — how do you want this to work day to day?" — before moving into the six-question spine. Worth deciding whether to add this as an explicit opener rather than leaving the reset implicit.

Assumptions worth challenging

• That Shashi has sharpened answers ready. He may still be forming his own view of APAC Differentiated's agenda. Worth preparing for "figure it out and come back to me" as a live outcome, and deciding in advance whether Amir pushes for at least directional guardrails in that case, or accepts open licence at face value.
• Meeting length. Nothing in the Weekly Loop or First-Week Plan states how long this session actually is. The six-question spine assumes something like 60–90 minutes. If it's shorter, the architecture doesn't fit and needs a fallback (Q2 and Q3 only, everything else by follow-up note).
• "In writing," live. Asking for a convening mandate in writing during the conversation itself may be too transactional for a first sitting. Softer version: ask for it as a follow-up ("could we put that in a short note afterwards"), not as something to walk out of the room holding.

Premature / risk to flag

• The Renaka triangulation question ("are you and Renaka aligned, or is aligning you two part of my job") is bold for a first 1:1 as new direct report. Asked with zero evidence of divergence, it risks reading as suspicion of your new boss on day one — working against the trust-building goal in Theme A. Recommend holding this one back unless something in the conversation actually signals a gap; don't lead with it.
• Interview-format risk. Six prepared questions from Amir risks the session feeling like Amir is running his own agenda on the boss on day one. Mitigate by naming it explicitly and inviting Shashi to redirect — e.g., "I've got a few things I'd like to understand from you, happy to start wherever's most useful to you."

Missed opportunity

• No question invites Shashi to set the agenda at all, given this is nominally framed as his first working session with a new direct report, not Amir's interview of him.

Reminder (not for this session): no Knowledge Hub CRM profile exists yet for Shashi. Per the workstation's routing, this should get created/updated after the debrief — flagging now so it isn't lost.

Stage 3.5 — Resolutions

• Renaka triangulation question: held back. Not asked unless the conversation itself signals a gap between Shashi and Renaka.
• Actual session length unknown — architecture rebuilt as modular tiers below so it survives a shorter slot.
• Theme A opener, negative-space question, and live-fire question: added into the modular structure.

Modular question tiers (drop from the bottom if time is short)

Tier 1 — non-negotiable, fits ~20–30 min: 1. Name the shift explicitly: "This is a different dynamic than when we were peers — how do you want this to work day to day?" 2. Year-end definition, both directions: what does strong look like, and what would make you say early on this isn't working? 3. Convening authority + data access — ask for it, follow up in writing rather than expecting it live.

Tier 2 — add if the session runs ~45–60 min: 4. Pricing/trading boundary — propose vs. approve vs. set. 5. What baseline is fair from a near-zero start? 6. Anything already live with a customer that I should know about before day one?

Tier 3 — only with 75–90+ min, otherwise pick up by follow-up note: 7. What would make Key Accounts genuinely useful to your own agenda? (can also be inferred from how he answers #2) 8. Key-account list size / MNC vs. regional criteria. 9. Renaka sequencing — logistics, resolvable by a short follow-up message if dropped.

Stage 4 — Executive Brief

Readable in under two minutes, immediately before walking in.

Meeting Objective Leave with a stress-tested (not provisional) year-end definition, confirmed convening authority and data access, and a working read on how Shashi wants the reporting relationship to run day to day.

Critical Questions 1. This is a different dynamic than when we were peers — how do you want this to work day to day? 2. What does a strong year actually look like — and what would make you say early on this isn't working? 3. What authority do I have to convene R&D, supply, trading, and finance — can we get data access and the convening mandate confirmed in writing afterward? 4. Where does central pricing/trading authority end and local/commercial influence begin — propose, approve, or set? 5. Is there anything already live with a customer I should know about before day one?

Things to Listen For - Whether he engages with the real tension in "programmes over volume," or defaults to safe generalities when pressed. - Energy versus surface compliance when discussing the mandate — real conviction reads differently from a position already decided elsewhere. - Whether authority is offered as something real and specific, or as goodwill to be re-earned function by function.

Political Signals - "Yours to build" language vs. "deliver this pre-defined thing" language. - Any unprompted mention of Renaka, the CEO, or board expectations — surfaces pressure on Shashi that could quietly reintroduce volume regardless of today's framing.

Watch Outs - Don't present a finished plan or commit to hard KPI numbers before the data/team download. - Don't lead with the Renaka triangulation question — held back this session. - Don't let this become an interview format — name the six-ish questions as things you'd like to understand, and invite him to redirect.

Definition of Success Walk out with a specific, falsifiable year-end bar (not a phrase), a real answer on convening authority, and a genuine read on whether this is a partnership being built with you or a role being filled.

Next: Stage 5 — debrief framework — once you're ready, and separately: the E2 team one-to-ones prep.