Stakeholders: who decides, who blocks, who uses
Map the people around a deployment by influence and stance, and give each one the evidence they need.
| Role | Cares about | What to bring them |
|---|---|---|
| Executive sponsor / economic buyer | Outcome, cost, risk, time to value | A business case with a measured pilot result |
| Champion (often a director or principal engineer) | Looking good; their team's workload | Material they can forward internally; early wins |
| Security and privacy | Data flows, retention, access, vendor risk | An architecture diagram with data classification, and answers before they ask |
| Platform / IT | Supportability, identity, cost to run | Deployment model, SSO, monitoring, runbooks |
| End users | Does it save time today? | A tool that fits their workflow, and a way to report problems |
| Procurement and legal | Terms, liability, data processing | Standard documents early; a clear owner on your side |
Anthropic's Applied AI Engineer post describes "long, multi-stakeholder procurement and adoption cycles, including technical evaluations, proofs of concept, security and architecture reviews" (official, Sources A6). Plan the reviews in parallel with the build, not after it.
Handling a blocker
- Understand the objection in their words, and what evidence would resolve it.
- Find the smallest change or proof that addresses it.
- Agree the decision criteria in writing before you produce the proof.
- Escalate only with a clear ask, after the direct route is exhausted.
Practice
Written for this site to drill the lesson. Not reported interview questions.
- The customer's CISO says no customer data may leave their tenancy. Map the stakeholders and the options.
- Write the message to your champion after a demo where the sponsor seemed unconvinced.
Check yourself
When should security review start?
In parallel with the build, from discovery onwards.
What do you agree before producing a proof for a blocker?
The decision criteria the proof must meet.
Saved in this browser.