Business wants to launch fast, IT wants a full architecture review, and compliance wants more controls. Stakeholders disagree. How do you move forward?

30-second answerSay your answer out loud first, then reveal.

Make each group's concerns explicit and legitimate, find the shared goal, and propose a plan that sequences risk: a limited, low-risk pilot (internal users, non-sensitive data, human review) that satisfies compliance's key controls and IT's minimum review, while giving the business early value. Get the executive sponsor to arbitrate trade-offs when needed. Document decisions, owners and timelines. Don't take sides or route around anyone.

Approach

Listen separately: what does each group need to say yes? What are their non-negotiables?
• Business: visible results this quarter.
• IT: integration standards, supportability, security.
• Compliance: data protection, audit trails, explainability.
Map requirements to phases:

Requirement	Pilot (week 4)	Production (week 12)
Users	20 internal staff	All 400 agents
Data	Non-sensitive categories	All categories, with PII controls
Controls	HITL on every output, audit log	Plus automated monitoring, DPIA completed
Architecture	Light review, sandbox	Full review, production standards

3. Joint working session: present the phased plan, and adjust it with each group's input.

4. Escalate deliberately: if trade-offs remain, frame them for the sponsor with options and consequences.

5. Communicate continuously: a weekly status note to all stakeholders.

Interview signal: treating stakeholders as partners, phasing risk, and using executive sponsorship appropriately.

PreviousYour demo worked perfectly, but in the customer's environment nothing works. Where do you look?

You understood something today that you didn't yesterday.

Business wants to launch fast, IT wants a full architecture review, and compliance wants more controls. Stakeholders disagree. How do you move forward?

Approach

Related