Almost every beginner has had this experience: a promising new tool, a few productive sessions, then gradual abandonment. The notebook app you loved for two weeks. The productivity system you set up in February. The course you were halfway through.
AI tools are not immune to this. The enthusiasm of the first few sessions doesn't automatically convert to a lasting habit. Without a specific structure, most people revert to their default workflows within a month.
This module gives you that structure. A 90-day plan that's designed around one principle: sustainable momentum. Not the maximum possible usage. The minimum necessary to build the skill genuinely.
The goal at the end of 90 days is not "I tried AI." It's "I can point to three things I do differently and better because of these tools, and I have one piece of work I'm genuinely proud of."
Days 1 to 30: Replace three repetitive tasks
The biggest mistake beginners make in the first month is trying to use AI for everything. You end up in a dozen different use cases simultaneously, none of them well, and you don't get good at any of it.
The better approach: pick three repetitive tasks in your working or studying life and commit to replacing them with AI-assisted workflows. Just three. Do those every time, until the process feels natural.
Good candidates for the first 30 days:
Research summarising. If your work or study involves reading a lot of reports, articles, meeting notes, or job listings, this is the highest-impact starting point. Every time you have something to read, try summarising it with AI first to get the shape of it, then read the parts that matter. This alone can cut reading time significantly for long documents.
Drafting first passes. Before you write any work communication from scratch, an email, a report section, a response to a brief, ask AI for a first draft, even a rough one. Then edit it. Don't start from a blank page if you don't need to.
Preparing for conversations. Before a job interview, a difficult meeting, a presentation, or a negotiation, spend 10 minutes prompting AI to help you think through the key questions, likely objections, or important points. It's a thinking partner, not a script.
What "replacing" actually looks like:
You don't have to use AI every single time if the task is quick and your current method is faster. But you do need to use it enough times that the habit forms. Set a simple rule for yourself: "For the next 30 days, every time I need to summarise something over 500 words, I run it through AI first."
Tracking progress (simply):
Don't build a complicated tracking system. A note in your phone or a sticky note on your monitor with three checkboxes is enough:
- Did I use AI for a research summary this week?
- Did I use AI for a first draft this week?
- Did I use AI to prepare for a conversation this week?
If all three are checked, you're building the habit.
Days 31 to 60: Study with AI as your tutor
If you're shifting careers, you're probably learning a new field. Module 3 covered the risks of relying on AI for information quality. This phase is about using AI for the specific task it handles very well: helping you understand and retain concepts you're actively studying.
The technique that works is called study-explain-critique-revise. Here's how it runs:
Ask. Find a concept in whatever you're studying that you don't fully understand. Ask AI to explain it. Use the "explain this to me like I just arrived" prompt from Module 7.
Explain back. Once you think you've understood it, close the AI tab (or scroll up so you can't read the explanation), and type out your own explanation in plain language. Don't look. Just explain it as if you're describing it to a friend.
Get critiqued. Paste your explanation back to the AI. Ask: "Here's my attempt to explain [concept]. What have I got right, what have I got wrong or incomplete, and what's the most important thing I missed?"
Revise. Update your explanation based on the feedback. Write the corrected version somewhere you'll keep it (notes app, physical notebook, Google Doc).
This four-step process is more effective than passive reading for the same reason that writing an essay is more effective than reading a textbook. You're retrieving and constructing knowledge, not just absorbing it.
How much time this takes:
One concept, done properly, takes 20 to 30 minutes. If you have two hours a week for study, that's three to four concepts per week done solidly, not dozens of concepts done superficially.
Be patient with the scope. Deep understanding of a small number of concepts will serve you better in an interview or in practice than a surface-level overview of many concepts. The study-explain-critique-revise loop makes sure you're actually learning something, not just scrolling past explanations.
What AI is bad at here (so you know):
It's bad at checking your understanding through testing if you haven't asked it to. It defaults to explaining, not quizzing. If you want to be tested, ask to be tested: "Ask me five questions about [concept] without giving me the answers first. Wait for my responses before telling me what I got right or wrong."
Days 61 to 90: Build one portfolio artefact
The third phase is about producing something external. Something you could share. Something that demonstrates, to a potential employer, a collaborator, or your own future self, that you can work productively with AI.
This is different from the things you've produced for your own use. A cover letter you improved, a summary you generated, a study plan you made, those are valuable, but they're internal. A portfolio artefact is public-facing: a piece of work that someone else can see and evaluate.
Three options, depending on where you're at:
Option 1: A written project. Choose a topic in your target field that you could write about substantively, based on what you've learnt over the past 60 days. Write a 600 to 800 word piece, an essay, an analysis, a professional opinion piece, using AI as a research and drafting assistant, but making every editorial decision yourself. Publish it somewhere: LinkedIn, a personal blog, a Medium account. The act of publishing forces a level of care that private drafts don't.
Option 2: A curated LinkedIn post series. Commit to three to five posts over the 30-day period, each about something you've learnt or observed in your new field. Use AI to help you draft, structure, and refine each post, but let your actual experience and perspective drive the content. This builds an observable track record of engaging with the field publicly.
Option 3: A documented case study. If you've done a project at work, a volunteer engagement, a course assignment, or any piece of work in the field you're targeting, document it as a case study: the problem, what you did, what you used AI for (be specific and honest), what the result was, and what you'd do differently. This kind of honest documentation, including the AI-assisted parts, is increasingly valued by employers who want people who can actually use these tools.
The key discipline for any of these options:
AI is a collaborator, not the author. Your perspective, your editorial judgement, and your actual experience have to be the backbone of the piece. AI helps you write faster and clearer. It doesn't tell you what to think.
Be honest in the work itself about where AI helped. Not a disclaimer for its own sake, just the same kind of attribution you'd give to any resource you used. "I used Claude to help structure the research for this" is perfectly fine and increasingly unremarkable. Pretending you didn't when you did is the problem.
The honest scope close: what's next
At the end of 90 days, you'll have:
- Three AI workflows embedded in your daily practice
- A deeper understanding of your target field, built with AI as a study partner
- One piece of public work that demonstrates you can use these tools meaningfully
That's a real foundation.
But this course is called the foundation for a reason. There is more. Here's where to go next, honestly:
If you want AI-verified credentials and roles in the AI space: HirerAI is being built as a two-sided platform for exactly this, verifying that you can use AI well, and connecting that to employers who care about it. It launches soon. If the course has given you momentum and you want that momentum tied to a career outcome, that's where it's heading.
If you're a business owner or professional who wants AI embedded in your operations: Request the AI Opportunity Report at innmotion.com.au/find-your-motion. We audit the work your team actually does and come back with a written report mapping where AI can save time, lift revenue, and the order to ship it in. Tailored to your industry, grounded in what's real right now.
If you want the deeper playbooks: The advanced operator-level workflows, how to build AI-powered processes, how to use AI across a business, how to get consistent, reliable outputs at scale, are not in this free course. That's by design. The foundation matters, and it matters to do it before the advanced work. When you're ready, ask about what's next.
Our genuine view: "uses AI well" is now a real, observable, differentiated skill. Not "uses AI", that's everyone. Uses it well: with good judgement about when to trust the output, when to push back on it, how to frame questions that get useful answers, and how to make the outputs actually yours. That's the skill. That's what 90 days builds.
You came into this course somewhere on the spectrum of curious-to-nervous. That's fine. Every skilled person started uncertain. The difference between people who develop the skill and people who don't is not talent or technical aptitude. It's whether they produced something real on day one instead of waiting to feel ready.
You did that in Module 1.
The rest is practice.
What this course does NOT teach (final statement)
This is stated clearly at the start and worth repeating at the end, with full respect to anyone who came looking for more:
- Building AI agents, APIs, or automated pipelines
- The coding skills required to work as an AI engineer or ML practitioner
- innmotion's internal product-building methodologies
- Specific job-application strategies for AI engineering roles (HirerAI is being built to cover that territory, launching soon)
- Career coaching or personal development counselling (different product, different relationship)
- The advanced operator-grade workflows used by people who build products with AI for a living
Those things exist. They're real. Some of them are genuinely powerful. This course is not where they live. Giving you a taste of advanced technique without the foundation to use it well wouldn't serve you.
What this course does give you is the foundation. Real. Tested. Honest about where the tools work and where they don't. Built for people who haven't started yet and need to start well.
That's what "Take the Leap" means. Not leap into the deep end without knowing how to swim. Leap with enough knowledge to make it worth it.