AI Playbooks

Practical decision frameworks for moving from interest to implementation.

This page is not a placeholder library. It is a structured view of the playbooks teams actually need when they are trying to decide what to prioritise, what to fix first, and how to move without creating avoidable risk.

Each playbook below points to a real next step in the site: readiness assessment, strategy work, delivery services, articles, and deeper research.

What These Playbooks Cover

Three recurring decisions shape most AI programmes.

Are we actually ready?

Readiness, governance, data quality, sponsorship, and operating constraints before commitment.

What should we do first?

Use-case selection based on value, feasibility, adoption fit, and control requirements.

How do we deliver without chaos?

Sequencing, integration planning, governance gates, accountability, and rollout discipline.

How To Use This Page

Use the playbooks to sharpen a decision, then move to the right next destination.

This section is designed as a routing layer, not just a summary. If your team needs a readiness view, use the scorecard. If the question is strategic, go to advisory. If delivery is already underway, move toward implementation and platform work.

01

Diagnose

Understand maturity, constraints, and where the main readiness gaps are before promising outcomes.

Open the AI readiness scorecard

02

Prioritise

Choose the few opportunities worth backing and sequence them around feasibility, controls, and value.

Explore AI strategy work

03

Deliver

Structure delivery, platform work, integration, governance, and rollout so implementation holds in practice.

View implementation support

Playbook Library

Three playbooks for the decisions that matter most.

Each playbook below includes the central question, what it helps clarify, and where to go next depending on what your team is trying to solve.

Readiness Playbook

Work out what must be true before scaling AI activity.

This playbook is for teams that have ideas and pressure to move, but need a defensible view of maturity across governance, data, leadership alignment, systems, and delivery capability.

What It Clarifies

  • Whether strategy, data, governance, and operating ownership are mature enough for real delivery.
  • Which readiness gaps will slow adoption or create unnecessary delivery risk.
  • What foundations need strengthening before broader investment or rollout.

Use-Case Playbook

Prioritise the opportunities worth serious attention.

This playbook is for leadership or delivery teams trying to avoid scattered pilots, vague ambition, and overcommitment. It forces the right conversations around business value, feasibility, data access, controls, and change readiness.

Typical Outputs

  • A clearer shortlist of use cases ranked by operational value and practical feasibility.
  • A sharper view of dependencies such as data, platform work, policy, or stakeholder sponsorship.
  • A more disciplined roadmap for what to pilot, what to defer, and what to stop pursuing.

Deployment Playbook

Structure delivery so implementation works in the real estate you already have.

This playbook is for teams already moving into build or rollout and needing clarity on sequencing, platform dependencies, controls, testing, integration, and accountability for live service performance.

What It Forces You To Address

  • How platform integration, data quality, governance gates, and operating ownership affect rollout sequencing.
  • What testing, monitoring, and escalation design are needed before a service goes live.
  • How adoption, training, and workflow redesign get handled instead of assumed.

Why This Matters

Most programmes do not fail from lack of ideas. They fail from weak sequencing and vague ownership.

The point of a playbook is to reduce ambiguity. It creates a shared frame for decisions that otherwise stay fuzzy: readiness, prioritisation, control design, and delivery sequencing.

01

Decision Clarity

Turn broad ambition into a clearer decision about what is viable now, later, or not at all.

02

Control Discipline

Make governance, accountability, and operating constraints part of the design instead of an afterthought.

03

Delivery Momentum

Give teams a path from strategy into practical execution with fewer false starts and less wasted effort.

Move Forward

If one of these playbooks matches your current problem, use the closest next step now.

Start with the scorecard for a maturity signal, move into strategy if prioritisation is the issue, or speak with Usalama if the challenge is already in delivery.