Consulting and Executive Communication

Guide · Enterprise AI Solution EngineeringPage 16 of 18Overview → … → Consulting

Executive summary

Senior stakeholders need decision structure: what is happening, why it matters, options, recommendation, the ask and what happens next. Lead with SCRID (situation, complication, recommendation, impact, decision); keep architecture depth in the appendix until the decision is framed.

When to use this page

• Use for executive updates, investment asks and go/modify/stop recommendations.
• Use whenever a status update risks becoming a technology tour.
• Pair with Business case and VALUE gate.

Executive view

Demand an explicit ask, visible trade-offs and labelled uncertainty—not confidence theatre.

Decision required: What must you approve, defer or stop—and by when?

Technical view

Put architecture and model detail in the appendix; front page holds the decision narrative.

Name next steps and owners; label assumptions that still need validation.

Owners

Owner · Engagement / AI Solution lead presenting the ask

Contributors · Sponsor, finance, risk, delivery lead, SMEs for appendix depth

Communicate in decision structure

Senior stakeholders need:

• What is happening?
• Why does it matter?
• What are the options?
• What do you recommend?
• What decision is required?
• What happens next?

Executive update structure

Situation

Describe the current context.

Complication

Explain the problem, constraint or risk.

Recommendation

State the proposed action.

Impact

Explain value, cost, risk and timing.

Decision required

Make the ask explicit.

Example

Situation: Customer-service demand has increased while response times have deteriorated.

Complication: Agents spend significant time searching across fragmented knowledge sources, producing inconsistent responses.

Recommendation: Implement a retrieval-augmented AI assistant integrated with the existing service platform.

Impact: The proposed solution should reduce search time, improve consistency and provide auditable sources.

Decision required: Approve a six-week discovery and prototype phase.

Solution narrative

A strong solution narrative should cover:

1. Business problem
2. Current-state limitation
3. Target outcome
4. Proposed capability
5. Architecture
6. Security and governance
7. Delivery approach
8. Commercial model
9. Expected value
10. Decision required

Communicating trade-offs

Do not hide uncertainty. Use language such as:

• The main trade-off is…
• The preferred option is…
• This assumption requires validation…
• The risk can be reduced by…
• The decision is reversible if…
• The downside scenario is…

Decision required

Every executive update must end with an explicit ask, named owners for next steps, and labelled uncertainty—not a technology tour.

Case study: financial-services assistant

Executive ask is not “approve generative AI.” It is “approve a six-week discovery and prototype with defined evaluation gates, DPIA start, and a go/modify/stop decision.” Architecture and model details stay in the appendix until the decision is framed.

Output

SCRID memo or briefing, options and trade-offs, labelled uncertainty, next steps with owners, and appendix depth separated from the decision page.

Common failure modes

• Technology tours instead of decisions
• Hiding uncertainty to sound confident
• No explicit ask
• Mixing status updates with recommendations
• Overloading slides with architecture before the problem

Solution Engineer checklist

Solution Engineer checklist

• Update follows situation → complication → recommendation → impact → ask
• Options and trade-offs visible
• Uncertainty labelled
• Next steps and owners named
• Appendix holds depth; front page holds the decision

Practical exercise

Rewrite your last status email as a half-page SCRID memo. Delete every sentence that does not help the decision.

Key takeaways

• Decision structure beats technology tours.
• Make the ask explicit; name owners and next steps.
• Label uncertainty and trade-offs.
• Keep depth in the appendix until the decision is framed.

What to do next

1. Continue with the AI Solution Engineering toolkit.
2. Apply VALUE quality gate before sending.
3. Align the ask with Business case scenarios.