Through the lens
From phone tap to frontier: the nine phases of personal AI adoption
A lot of people I speak to feel like they have missed the AI moment.
They haven’t. They have just never seen the map.
There is a natural learning progression to AI adoption – nine recognisable phases, from opening a chat interface for the first time to building systems where multiple AI agents coordinate automatically. Each phase teaches you something specific. Each one lays the groundwork for the next. The sequence is not invented — it reflects how people genuinely acquire new technical capabilities, a pattern consistent with decades of skill acquisition research.
The reason so many people feel stuck or overwhelmed is not that AI is too complex. It is that they are either starting at the wrong phase, or trying to jump ahead without the foundations in place. Both feel the same from the inside: like AI just doesn’t work for you.
It does. You just need the map.
Phase 1 – The phone tap
You open Gemini, ChatGPT, or Copilot on your phone and ask it something. An answer comes back. At first, it feels like a smarter search engine. For many people, the first encounter is not text at all – it is a voice conversation with Gemini Live or ChatGPT voice mode, or generating an image with Copilot Designer. The medium varies. The learning is the same.
Then at some point, it gets something confidently wrong. Yet that moment is more valuable than it seems. You have just encountered your first hallucination – and you have started building the most important skill in AI literacy: critical evaluation. Not blind trust. Not blanket scepticism. The beginning of a calibrated instinct that everything after this depends on.
Over 800 million people use ChatGPT every week. You are not behind. You are at the start.
What you learn: Conversational AI works – and it also fails. Both are important to experience.
Phase 2 – Context and memory
You discover that AI quality scales directly with the context you give it. You start using persistent workspaces – Perplexity Spaces, ChatGPT Projects, Claude Projects – where you can pre-load documents, set custom instructions, and carry knowledge across conversations.
What you learn here is fundamental: the AI is not magic. It works with what you give it. In practice, the people who get remarkable results from AI are not using a different tool. They are giving it better context.
This phase also teaches you what context windows are – the limits on how much an AI can hold at once. Understanding those limits is what separates someone who uses AI well from someone who is constantly frustrated by it.
What you learn: Garbage in, garbage out. Better context, better output. This is also where prompt engineering begins – the practice of writing precise, well-structured instructions to get consistently useful results. It is a learnable skill, not an innate talent, and naming it matters.
Phase 3 – Model literacy
Over time, you start to realise that different AI models are genuinely different tools. Claude reasons differently from GPT. Gemini integrates differently with Google Workspace. DeepSeek approaches problems differently again.
As a result, you stop treating AI as one monolithic thing and start treating it as a set of different instruments. You develop opinions about which model handles which type of work best. That sounds like a small shift – but it changes everything about how you approach AI-assisted work.
What you learn: Match the model to the task. Not all AI is the same.
Phase 4 – Going pro
You make a deliberate financial commitment to a paid tier. Claude Pro, Gemini Advanced, Perplexity Pro – each roughly twenty pounds a month. In doing so, you make a decision: this is a tool worth taking seriously.
Inside those tools, you encounter something important: system prompts. Persistent instructions that shape how an AI behaves across an entire session. You start designing workflows rather than firing off single questions. You think in sequences – first the AI does this, then I review that, then the AI takes my feedback and goes again.
This is where AI shifts from “answering questions” to “working with you.” It is also where most people quietly stop – not because it is too difficult, but because no one ever told them this was the stage to push through.
What you learn: Workflow design. AI as a repeatable process, not a one-off query.
Phase 5 – Into the code
You start using AI to help you write code, scripts, or formulas. Maybe that is Python. Maybe it is Power Automate expressions, Excel formulas, or SQL. The specific language does not matter.
What matters is what this phase teaches: AI-generated output requires verification. You cannot evaluate what you cannot at least partially read. This is the phase that builds genuine confidence in AI as a collaborator – because you learn where its edges are.
A 2025 study found experienced developers were 19% slower when using AI tools – but 90% faster on boilerplate tasks. The gap comes down to one thing: whether you can review what the AI produces. Those who can, capture the upside. Those who cannot end up slower, not faster. GitHub’s 2026 enterprise data puts a number on the upside: PR review time dropping from 9.6 days to 2.4. Building that reviewing muscle is the real work of phase 5.
What you learn: AI output is a draft, not a deliverable. Verification is the skill.
Phase 6 – The terminal
You start directing AI from the command line – via tools like Claude Code, Aider, or Gemini CLI. No longer working through someone else’s interface. The work happens through API keys, scripts, and shell commands.
From there, you learn how AI APIs work. You also start scripting AI workflows. You discover that AI can be a component in a larger automated process, not just a conversation partner. This is the phase that separates people who use AI tools from people who build with AI.
What you learn: AI is programmable. It is a component, not just a chat interface.
Phase 7 – Multi-agent orchestration
You build systems where multiple AI agents coordinate with each other. One agent researches. Another drafts. A third reviews and flags issues. You have moved from AI as assistant to AI as a team.
For example, a delivery team I worked with built an agent that took a process normally requiring four to five hours down to under an hour. That was phase 7 in practice – an orchestrated system that understood context, followed instructions, and handed outputs between agents reliably. It only worked because the team had genuinely moved through phases 2 to 6. You do not build reliable agents on a foundation of phase 1 experience.
This is also the phase where RAG – Retrieval-Augmented Generation – becomes essential. Rather than relying solely on what a model was trained to know, RAG connects agents to live documents, data sources, and knowledge bases. It is what separates agents that are genuinely useful from agents that confidently make things up.
What you learn: Orchestration patterns. How to design systems that operate with minimal human intervention at each step. And how to ground those systems in real, current information.
Phase 8 – Customise and fine-tune
You move beyond using AI models as they come out of the box. You start adapting them. Custom GPTs, fine-tuning a base model on your own data via API, building a Claude Project with a specific character and persona – this is the phase where you stop configuring AI and start shaping it.
Here, the distinction matters. Phases 1 through 7 teach you to work with AI as it arrives. Phase 8 teaches you that the model itself is malleable. You can train it on your writing style, your domain knowledge, your organisation’s specific terminology. A fine-tuned model does not just follow instructions – it has absorbed a context you built for it.
This phase also teaches something equally important: fine-tuning is not always the answer. Better prompting resolves most problems. RAG resolves most knowledge problems. Fine-tuning is the right tool for a narrower set of cases – style, accent, deep domain specialisation – and understanding when to reach for it, and when not to, is part of what this phase develops.
What you learn: The difference between instructing AI and training it. When fine-tuning is the right tool – and when it is not.
Phase 9 – Sovereign AI
You run AI entirely on your own hardware. No data leaves your environment. Models like Llama, Mistral, or Qwen run locally via tools like Ollama.
For most individuals, this phase is optional – more curiosity than necessity. For organisations in regulated sectors, healthcare, financial services, public sector – it is increasingly the destination. Even for personal use, running a local model teaches something valuable: AI is infrastructure, not just a service.
What you learn: Data sovereignty in practice. Cost, control, and capability trade-offs.
The transitions that define the journey
The shift between phases is not just a tool change. It is a cognitive one:
- Phase 1 to 2: “AI answers questions” to “AI needs context to be useful”
- Phase 2 to 3: “My AI tool” to “different models for different jobs”
- Phase 3 to 4: “I use AI” to “I design AI workflows”
- Phase 4 to 5: “AI writes prose” to “AI writes executable logic”
- Phase 5 to 6: “AI assists me” to “I direct AI programmatically”
- Phase 6 to 7: “One AI pipeline” to “multiple AI agents coordinating”
- Phase 7 to 8: “I orchestrate AI” to “I shape the AI itself”
- Phase 8 to 9: “Cloud AI I control” to “infrastructure I own and govern”
Each shift changes the central question – from “what can AI do?” to “how do I build AI systems that do this reliably?”
Why this matters beyond personal use
Here is where the personal journey connects to something larger.
The teams delivering real results with AI in enterprise programmes are not the ones with the biggest budgets or the most advanced platforms. They are the ones where the people involved have genuinely moved through these phases themselves. They understand what AI can and cannot do because they have encountered both, at every level of the stack.
The data backs this up. Organisations that pair AI investment with structured capability building are nearly twice as likely to report strong ROI – 42% report significant returns when upskilling is structured, versus 21% without, according to a 2026 DataCamp/YouGov survey of over 500 enterprise leaders.
You cannot shortcut this with a workshop or a certification. The literacy is experiential.
If you are feeling behind on AI right now, the answer is not to read more reports about it. Instead, open the app, start at phase 1, stay curious, and let the progression do its work.
Which phase are you at right now? Drop it in the comments.
About the author
I’m a Microsoft FastTrack Recognised Solution Architect. I design AI-augmented delivery systems and help enterprise teams move through the phases – not around them.
Connect on LinkedIn: linkedin.com/in/mike-richard