From AI Tourist to AI Leader: The 90-Day Transformation

Last year I ran a workshop for 30 directors and VPs at a Fortune 500 bank. I asked everyone to raise their hand if they had used AI in the last month. Every hand went up. Then I asked who had scored their AI use cases against a structured rubric. Two hands. Who had a documented cost model for any AI initiative? One hand. Who had presented an AI business case with projected ROI to their leadership? Zero.

Every person in that room was AI-aware. They had attended the conferences, read the analyst reports, experimented with ChatGPT. A few had even run pilots. But none of them had crossed the line from AI tourist to AI leader. That line is not about knowledge. It is about execution documents.

The Three Stages of AI Leadership

After working with over 200 executives on AI adoption, I have observed three distinct stages. Most people get stuck at stage one. The ones who reach stage three do it within 90 days, because the transformation is not about learning more. It is about building the right artifacts.

Stage 1: The AI Tourist. You have read the McKinsey report. You have tried the tools. You can hold a conversation about large language models at dinner. You might have even championed an AI pilot. But when the CFO asks for an ROI projection, you wing it. When a vendor pitches you, you have no structured evaluation framework. When your team asks which use case to pursue first, you go with gut feel. AI tourists consume AI information. They do not produce AI decisions.

Stage 2: The AI Practitioner. You use AI daily in your actual workflow. You have prompts that save you real time on real tasks. You can summarize documents, prepare for meetings, analyze data, and draft communications faster than anyone on your team. But your AI use is personal productivity. It does not scale beyond your own desk. You have not translated your personal efficiency into organizational capability.

Stage 3: The AI Leader. You have the strategic frameworks to decide which AI bets to make. You have the daily execution habits to use AI as a force multiplier. And critically, you have the business case documents to get AI initiatives funded, governed, and deployed. You can walk into any room with a scored use case, a three-scenario cost model, a one-page project brief, and a 90-day timeline. That is not enthusiasm. That is leadership.

Why Most Executives Stall at Stage 1

The gap between Stage 1 and Stage 3 is not expertise. It is not more AI courses or certifications. I have met executives with three AI certifications who cannot write a one-page project brief. The gap is having the right templates and knowing when to use them.

Consider what happens when an AI tourist tries to get an initiative funded. They write a 15-page proposal that takes three weeks. The proposal mixes strategy with technical details. The cost section is vague because they have never seen a proper AI cost model. The timeline is optimistic because they do not know about the data preparation phase that eats 40-60% of every AI project. The governance section is either missing or copied from a generic template that does not match their organization's risk profile.

Now consider what an AI leader does. They score 10 potential use cases in a 90-minute session using a 5-dimension rubric. They pick the top 2. For the winner, they fill in a one-page brief that takes 45 minutes. They build a three-scenario cost model using the 5-layer cost stack. They draft a 90-day timeline with phase gates and go/no-go criteria. Total time: one afternoon. Total documents: four pages. Approval: typically one meeting.

I watched this play out at a regional bank last year. Two directors in the same organization were both pursuing AI initiatives. Director A spent three weeks on a 47-page proposal for document classification. It went through four rounds of revision, got stuck in a committee, and died. Director B used the frameworks I am about to describe. She had a scored use case, a one-page brief, a cost model, and a timeline. She presented it in a 20-minute slot. Approved on the spot. Her pilot was running before Director A's second revision was complete.

The 90-Day Transformation: Week by Week

Here is the path I have seen work repeatedly. It is not theoretical. It is the sequence that Director B used, that a VP of Operations at a Top 20 bank used, and that I personally coach through when I do advisory work. Ninety days, three phases.

Phase 1: Foundation (Days 1-30). This is where you build your AI literacy beyond surface level and establish daily habits.

Week one: Learn the strategic frameworks. Not another AI overview course. Specifically: how to evaluate AI vendors without getting sold on demos, how to estimate real costs (not vendor quotes), how to assess organizational readiness, and how to identify which use cases are worth pursuing. This is a two-day investment, not a two-month certification.

Weeks two through four: Build daily AI execution habits. Start using AI for your actual job, every day. Meeting prep, document analysis, strategic thinking, communication drafting. The goal is not to become a prompt engineer. The goal is to develop an intuition for what AI does well and what it does not, based on your own experience rather than vendor claims. By day 30, you should be saving 3-5 hours per week through AI use, and you should have a clear sense of where AI adds real value in your domain.

Phase 2: Documentation (Days 31-60). This is where most people skip ahead or skip entirely. It is also where leadership is built.

Week five: Run a use case scoring session. Gather your team for 90 minutes. List every AI idea anyone has mentioned in the last six months. Score each one against five dimensions: strategic alignment, data readiness, technical feasibility, business impact, and organizational readiness. You will end up with 8-15 ideas scored and ranked. Pick the top 2-3.

Week six: Build the business case for your top pick. Fill in the one-page project brief, the three-scenario cost model, and the ROI calculator. If you have never built an AI cost model before, this is where the 5-layer cost stack matters. Vendor licensing is layer one. Data preparation, integration, change management, and ongoing operations are layers two through five. Most AI tourists only budget for layer one. That is why their projects go 2-3x over budget.

Weeks seven and eight: Build the 90-day timeline and governance documentation. Map the four phases: assessment, pilot, refinement, and production. Define go/no-go gates between each phase. Classify the project by risk tier and fill in the appropriate governance checklist. By day 60, you have a complete, presentation-ready package.

Phase 3: Execution (Days 61-90). This is where the documents become decisions.

Week nine: Present the business case. With the one-page brief, cost model, and timeline, this is a 20-minute presentation. You are not asking for permission to explore AI. You are presenting a specific initiative with specific costs, specific timelines, and specific success criteria. That is a fundamentally different conversation.

Weeks ten through twelve: Launch and manage the pilot. Your 90-day timeline gives you the structure. Your governance checklist keeps compliance on track. Your cost model prevents scope creep. You are not figuring it out as you go. You are executing a plan.

Week thirteen: Measure and report. Use the ROI calculator to compare projected versus actual results. Present findings to leadership. If the pilot succeeded, you have a proven case for scaling. If it failed, you have documented why, and you can make an informed decision about whether to iterate or kill it. Either way, you led. You did not just experiment.

The Three Tools That Make This Work

The transformation I described requires three distinct capabilities that most executives try to develop separately. This is a mistake, because they compound.

Strategic frameworks tell you which AI bets to make and which to avoid. Without them, you are reacting to vendor pitches and analyst reports instead of making proactive decisions grounded in your organization's reality. This is the thinking layer.

Daily execution prompts build the hands-on intuition that separates leaders from commentators. You cannot credibly lead an AI initiative if you do not use AI yourself. This is the doing layer.

Business case templates translate your strategy and experience into the documents that get initiatives funded, governed, and deployed. This is the building layer. Without documents, your AI strategy stays in your head. With documents, it becomes organizational capability.

Skip the strategic frameworks and you build the wrong thing. Skip the daily execution and you lack credibility. Skip the business case templates and you never get funded. The transformation requires all three.

Actionable Takeaway