Your first 30 days when the AI mandate lands on your desk

Two colleagues talking across a small table in an operations office, a notebook open between them, one listening intently
TL;DR

When you are handed an AI mandate, the highest-return thing you can do in the first thirty days is assess, not deploy. Run a two-week listening tour, read your current state across five readiness dimensions, map the AI your team already uses off the books, and tee up one or two quick wins without committing to them. At day thirty you give the board an honest current-state read and a plan to plan, not a tool you have already bought.

Key takeaways

- The pull to show early movement is the single biggest reason first AI mandates tip into the failure column. A month of honest groundwork beats a demo you said yes to in week one. - Weeks one and two are a listening tour. Talk to your own people about how work actually flows before you talk to a single vendor, because that is what tells you where AI would add value rather than automate a broken process. - Read your current state across five readiness dimensions, data maturity, team enablement, technology infrastructure, strategic alignment, and governance and risk. Data is one of the five, not the whole assessment. - Map the AI your people are already using off the books. The sanctioned picture understates the real footprint, and that shadow activity is both your true starting line and your first risk surface. - At day thirty, give the board an honest current-state read and a plan to plan, not a tool you have already committed to. Reframe the work internally as building AI readiness, not implementing AI.

Day one. You sit down and the inbox is already full. Vendor outreach, demo requests, “quick chats”, and somewhere in there a board member asking when they will see something. Everyone wants a meeting. The instinct is to start saying yes, to book the demos, to look like a person who is moving. The better first move is quieter and harder to hold to. Talk to your own people before you talk to a single supplier.

This is the second post in a six-part run on being handed the AI mandate. The first looked at why a problem-first stance beats a tool-first one. This one turns that stance into a day-by-day first month, because the first thirty days decide whether the rest of the mandate works.

Why does the first month decide the whole mandate?

The first thirty days set the trajectory because the choice you make in them is binary. You either spend the month assessing or you spend it deploying, and the version that assesses is the version that tends to work. Deploying early reads like progress to a board, but it commits you to tools before you understand the problems they are meant to solve.

The pull to show movement is strong, and it is exactly what tips initiatives into the failure column. MIT’s 2025 research found that the large majority of generative AI pilots produce no measurable impact on the P&L, and the failures sit upstream of the technology, in unclear problems and unready data. The pressure is sharper still if you were handed this because you make things happen, not because you know AI. Korn Ferry calls that the AI readiness paradox, strong operators given AI leadership without the AI-specific footing the task needs. A demo you said yes to in week one is a commitment made before you had the information to make it well. A month of honest groundwork costs you the appearance of speed and buys you the substance of it.

What does the listening tour in weeks one and two look like?

Weeks one and two are a listening tour. You sit with the people who do the work and you learn how it actually flows, where the friction is, what gets redone, what waits on someone else. You are not pitching AI. You are building the map that tells you where AI would add value rather than automate a process that is already broken.

There is a second reason to start with people rather than suppliers. Employee fear, about job loss, about being watched, about a tool that gets things wrong in their name, hardens into passive resistance the moment it is ignored. Open with listening and you defuse some of that before it sets. Carry one test into every conversation, the one Addepar puts to executives weighing an AI purchase. Would this initiative still matter if it did not use AI. If the honest answer is no, you have found a demo dressed as a problem, and you can let it go. The reframe that helps here is to describe the work as building AI readiness, not implementing AI, and to talk about freeing people from low-value work rather than replacing them. The language is not spin. It changes what you go looking for.

How do you read the current state across five readiness dimensions?

You read the current state across five dimensions, and you write each one down honestly. The five are data maturity, team enablement, technology infrastructure, strategic alignment, and governance and risk. Data is one of the five, not the whole job. The output is a single page that says, plainly, where the business stands on each, with no effort to make it look further along than it is.

Data tends to be the constraint that bites first. Poor data quality is named by 77 per cent of firms, on Gartner’s figures, as the biggest barrier to using AI responsibly, so a candid read of how clean and accessible your information is matters more than any tool comparison. Strategic alignment is the one delegates underweight. If you cannot say in a sentence how AI connects to what the business is actually trying to do over the next year, that gap will surface at the board table whether you name it now or not. Read all five. Resist the urge to start fixing any of them yet.

What is shadow AI and why map it first?

Shadow AI is the AI your people are already using off the books, the personal accounts and free tools they have brought in without anyone sanctioning it. You map it in the first month because it is both your real starting line and your first risk surface. The sanctioned picture understates the actual footprint. A meaningful share of employees are already using personal AI tools at work, often before any formal programme exists.

Read the map as diagnostic information rather than a hunt for wrongdoing. Where people have reached for AI on their own, they have told you where the friction is real enough to be worth solving, which is the most honest demand signal you will get. The risk side matters too, because client data pasted into an unsanctioned tool is an exposure you now know about and can manage. Read shadow AI as a free piece of research and a first governance task at the same time. Both readings are correct.

What do you commit to at day 30?

At day thirty you give the board an honest current-state read and a plan to plan, not a tool you have already bought. You show them where the business stands across the five dimensions, what AI your people are already using, and where the genuine value looks likely to sit. Then you commit to bringing them a ranked shortlist of opportunities in the next thirty days. You do not deploy anything yet.

Where you point them matters as much as what you show. The instinct is to promise a customer-facing showpiece, because that is what looks impressive. The evidence points the other way. MIT found that back-office automation produces the highest returns while sales and marketing pilots show the lowest, despite attracting the most funding. So aim the early attention at the unglamorous work, document processing, internal admin, the repetitive tasks that eat hours without anyone counting them. The sixtieth-day post in this series turns that shortlist into a ranked plan, and the board update post handles the harder conversation about resetting expectations on timelines. For now, the move is to assess well, say so honestly, and resist the demo. If you want a second pair of eyes on your first thirty days, book a conversation.

Sources

- MIT NANDA (2025). State of AI in Business 2025. Cited for the finding that the large majority of generative AI pilots show no measurable P&L impact, and that back-office automation produces the highest returns while sales and marketing pilots show the lowest despite the most funding. https://sranalytics.io/blog/why-95-of-ai-projects-fail/ - Schellman (2025). AI Implementation Failures in Real-World Deployments. Cited for poor data quality being named by 77 per cent of firms (Gartner) as the biggest barrier to responsible AI use, the rationale for putting a data-maturity read in the first month. https://www.schellman.com/blog/ai-services/ai-implementation-failures-in-real-world-deployments - Broadcom Security (formerly Symantec) (2024). Your Guide to Data Governance in an AI-Driven World. Cited for the link between data governance maturity and responsible AI adoption, supporting the governance and risk readiness dimension. https://www.security.com/expert-perspectives/your-guide-data-governance-ai-driven-world - BridgeView (2025). AI Readiness, the five pillars. Cited as the source of the five readiness dimensions used in the current-state read, data maturity, team enablement, technology infrastructure, strategic alignment, governance and risk. https://www.bridgeviewit.com/ai-readiness/ - Addepar (2025). Questions Executives Should Ask Before Adopting AI. Cited for the problem-first test, would this initiative still matter if it did not use AI, and the warning against flashy demos with no measurable outcome. https://addepar.com/blog/questions-executives-should-ask-before-adopting-ai - LogixGuru (2025). The Board Wants an AI Strategy by Tuesday, a CIO's Survival Guide. Cited for the gap between sanctioned AI initiatives and the real footprint created by employees using personal AI tools, and for the single-page current-state assessment as the month-one output. https://www.logixguru.com/post/the-board-wants-an-ai-strategy-by-tuesday-a-cios-survival-guide - Korn Ferry (2025). Six Signs Leaders Lack AI Readiness and How to Fix It. Cited for the AI readiness paradox, where operators are handed AI leadership without the AI-specific competencies, and the finding that leaders who focus on efficiency over capability building see lower adoption. https://www.kornferry.com/insights/featured-topics/gen-ai-in-the-workplace-articles/6-signs-leaders-lack-ai-readiness-and-how-to-fix-it - Ataccama (2025). AI Readiness. Cited for the three pillars of readiness, business-strategy alignment, governance frameworks, and AI-ready data, supporting the strategic alignment dimension of the current-state read. https://www.ataccama.com/blog/ai-readiness - HR Executive (2025). How to Keep Employee Distrust from Limiting Your Company's AI Strategy. Cited for employee fears hardening into passive resistance, the rationale for opening with a listening tour rather than a tool roll-out. https://hrexecutive.com/how-to-keep-employee-distrust-from-limiting-your-companys-ai-strategy/ - ESG Dive (2025). Execs Fear Job Loss Due to AI. Cited for the executive anxiety around being held responsible for AI adoption, the pressure that pushes delegates to deploy too early. https://www.esgdive.com/news/execs-fear-job-loss-due-to-AI/818075/

Frequently asked questions

Should I really spend a whole month before deploying anything?

Yes. The first thirty days are for assessment, and the discipline to hold that line is what separates mandates that work from mandates that stall. Deploying a tool in week one to show the board movement is the most common way these initiatives fail, because it automates problems you have not understood yet. A month of groundwork is the highest-return thing you can do, and it earns you the right to move fast later.

What do I tell the board at the end of the first month?

An honest current-state read and a plan to plan, not a tool you have already bought. Show them where the business actually stands across the five readiness dimensions, what AI your people are already using off the books, and where the genuine value sits. Then commit to bringing them ranked opportunities in the next thirty days. Resetting the expectation of immediate results is part of the job.

Where should I look first for AI that genuinely pays back?

Unglamorous back-office work, usually. MIT's research found back-office automation produces the highest returns while sales and marketing pilots show the lowest, despite attracting the most funding. So resist the instinct to start with the customer-facing showpiece. Document processing, internal admin, and repetitive operational tasks are where the value tends to sit, and they carry far less reputational risk if a first attempt underperforms.

This post is general information and education only, not legal, regulatory, financial, or other professional advice. Regulations evolve, fee benchmarks shift, and every situation is different, so please take qualified professional advice before acting on anything you read here. See the Terms of Use for the full position.

Ready to talk it through?

Book a free 30 minute conversation. No pitch, no pressure, just a useful chat about where AI fits in your business.

Book a conversation

Related reading

If any of this sounds familiar, let's talk.

The next step is a conversation. No pitch, no pressure. Just an honest discussion about where you are and whether I can help.

Book a conversation