The First 90 Days
The temptation in the first month is to announce a strategy. Resist it. A strategy announced before you understand where the risk and the readiness actually sit is a strategy you'll have to walk back.
Days 1–30: map before you move¶
Run stakeholder interviews with the same set of questions across every business unit: what outcome are you trying to reach, what's blocking you today, and are you ready to scale what's working. Use the answers to build a landscape map — the use cases already in flight, the foundational capabilities (data, platform, skills) each one can actually draw on, and where the risk exposure sits. You are not deciding anything yet. You are finding out what's true.
Days 31–60: publish the charter, stand up the forums¶
Put the mandate in writing: a charter that says what you decide, what you're consulted on, and what stays with business-unit leaders. Ambiguity here is what gets exploited later, when a project fails and everyone points at everyone else.
Then stand up the two forums from Setting the Operating Model: the portfolio council for funding decisions, and the responsible-AI review for risk sign-off. Set the minimum lifecycle gates every project must clear before it ships — a named business owner, a performance baseline, approved data access, a completed risk review, a monitoring plan, and an adoption approach (Umbrex, 2025). Projects that can't produce these six things aren't ready to fund, no matter how promising the demo looked.
Days 61–90: ship one thing for real¶
Pick two to four initiatives with strong sponsorship, real data access, and a benefit you can actually measure — not the most impressive idea, the most fundable one. Your day-90 target is concrete: at least one production deployment with monitoring and benefits tracking live (Umbrex, 2025). A pilot that never reaches production teaches you nothing about whether your operating model actually works.
Build a simple dashboard — value, adoption, risk — with clear escalation rules for when a metric moves the wrong way. This is the artifact you bring to the board. Not a strategy deck: a working system, with one real result in it.
Sources¶
- Umbrex — Chief AI Officer Playbook — The Chief AI Officer Mandate, 2025. named business owner, baseline, approved data access, risk review, monitoring plan, and adoption approach. View source · verified 2026-07-02 · primary
- Umbrex — Chief AI Officer Playbook — The Chief AI Officer Mandate, 2025. Deliver at least one production deployment with monitoring and benefits tracking. View source · verified 2026-07-02 · primary