Learn by Doing vs Courses
This bonus episode explores why courses can start the journey, but real confidence comes from building, shipping, reflecting and using AI as a practical partner in the work.
What this bonus episode is about
This bonus episode of Zero to AI is about the difference between learning about AI and learning through AI. It starts with a personal realisation: Steve had spent years strengthening the strategist part of himself, the part that plans, analyses, maps and prepares, but the performer part had become weaker.
The episode was shaped by a video about the strategist versus performer problem. The strategist works in safety through research, learning and planning. The performer works in uncertainty through doing, failing and learning in motion. For anyone rebuilding work with AI, that distinction matters.
This episode does not dismiss courses. It recognises their value. Courses provide language, maps, examples and confidence. But they cannot replace the kind of proof that only comes from building something small, testing it, reflecting and shipping again.
Courses gave me belief. The loop gave me proof.
Why learning by doing matters
The core problem in this episode is not intelligence. It is transfer. You can understand the buzzwords, complete courses and collect certificates, but still freeze when asked to build something useful. That gap between knowing and using is where many people get stuck.
Steve describes reaching a point where learning still felt productive, but the work was not moving forward. More research, more strategy documents and more planning did not create momentum. What changed things was the decision to stop optimising for certificates and start optimising for outcomes.
This is also why the wider Zero to AI starting point is built around practical progress. The goal is not to sound fluent in AI. The goal is to use AI to create something real in your own work.
The strategist and the performer
The strategist is useful. It creates systems, frameworks, checklists and plans. In larger organisations, this role can be supported by implementation teams. But when you are building your own work, launching a brand or creating new services, the strategist cannot do everything alone.
The performer is the part that acts in uncertainty. It writes the first draft, builds the rough workflow, records the first demo, tests the broken automation and learns from what happens next. The performer may feel nervous, but it moves.
This bonus episode is really about rebuilding that performer muscle. Steve started with quick wins, small tasks and tiny projects that could be finished in 10 or 15 minutes. Mistakes stopped being treated as failures and became data.
Key ideas from the episode
1. Courses are the spark, not the destination
Courses can give you vocabulary, structure, examples and confidence. They are especially useful at the beginning. But if you keep stacking certificates, you can accidentally build an identity around learning instead of building.
2. Just-in-time learning keeps momentum alive
When you get stuck, the answer is not always another full course. Sometimes it is one focused question, one short explanation, one fix and then a return to building. Learning becomes useful when it unlocks the next action.
3. AI can become a co-performer
Used well, AI is not just a search tool. It can be a teacher, mentor, critic, troubleshooter and planning partner. The value comes from using it inside the task, not only beside the task.
When learning becomes a tool, not a hiding place
A major turning point in the episode is the shift from learning as avoidance to learning as empowerment. Steve describes how the strategist wanted to return to more study whenever a task felt hard. But instead of falling into another course, he began using just-in-time learning.
The rule was simple: only learn what is needed right now to complete the next task. Not a full curriculum. Not ten more tutorials. Just the missing piece that unlocks movement.
This is where tools like ChatGPT became useful in a different way. Instead of asking broad questions, Steve began asking for exact next steps, troubleshooting help, clearer prompts and practical feedback. The learning happened inside the doing.
From certificates to shipped work
The second half of the episode turns the idea into a practical philosophy. Steve reflects on how courses helped him understand AI vocabulary and context, but they did not automatically create the ability to ship workflows, automate processes or fix real problems.
The missing piece was not more knowledge. It was transfer. He needed to move from knowing about AI to using AI in his own world. That meant flipping the learning plan from course-first to build-first.
This does not mean courses are bad. It means they need a finish line. Take one or two useful courses, build language and confidence, then move into practice. The next level of skill comes from touch: fingers on keys, real problems, imperfect outputs and reflection.
The 14-day starter plan
This bonus episode includes a simple 14-day plan for testing the learning-by-doing approach. It begins with one tiny project that matters to your day, such as email, calendar, notes or a small workflow. The aim is not to create something impressive. The aim is to create something real.
The plan asks you to define success in one sentence, build for 90 minutes, use short just-in-time learning when blocked, add one feature, record a rough demo, tidy one edge, rest or read one useful document and write a short reflection. Then you repeat or extend the loop.
Choose something connected to your real work, such as notes, email, calendar, reporting or a recurring admin task.
Aim for ugly and working rather than polished and theoretical. Use AI to guide the next practical step.
Write what worked, what did not, what you learned and what the next single action should be.
Over two weeks, aim for several small shipped improvements instead of one perfect unfinished project.
Two examples from the episode
The first example is the creation of the Zero to AI brand itself. It did not begin as a complete website, polished offer or full content system. It began with one story post that explained what Zero to AI meant and why it existed.
From there, Steve used small slices of work: drafting the story, shaping the tone with AI, creating an early brand direction, recording a short walkthrough, sending it to a trusted person and writing down what worked. The lesson was that lowering the bar made it possible to start.
The second example came from consulting work with a manufacturing business. The goal was to create a simple spreadsheet that forecast production requirements, component usage and cash flow from past data. It began as a basic table, then became a useful decision-making tool through iteration, automation and weekly summaries.
The reflection loop
One of the most important parts of the episode is the reflection loop. Doing alone is not enough. Reflection turns doing into progress. Without it, you can ship things but miss the lesson.
The reflection prompts are simple: what worked, what did not, what did I learn, did I keep my commitment and what is next? One action, one owner and one date. This kind of short log helps progress compound because each build informs the next.
This is also why AI can become more useful after you start shipping. You stop asking vague questions like “what should I learn next?” and start asking specific questions such as “this broke, show me the fix” or “critique my prompt and make it more resilient.”
Practical reflection
This bonus episode asks you to notice where learning has become a hiding place and where action needs to become the teacher. The goal is not to abandon strategy. It is to reconnect strategy with performance.
What is one tiny AI-assisted thing you could build, test or ship this week that would give you proof instead of just more knowledge?
Where to go next
This page is designed to stand alone as a bonus foundation episode. You can listen, read, reflect and take one small action without needing to move into a more advanced learning experience. If the episode resonates, return to the Season 1 archive and keep exploring the wider foundation journey.
You can also visit the Zero to AI blog for related reflections, or use the Who Zero to AI is for page to understand whether this practical, mid-career AI learning approach fits where you are now.
This bonus episode is a foundation piece.
Season 1 is built to help you make sense of AI learning without pretending the answer is simply more content, more courses or more planning. This bonus episode gives you the core shift: learn enough to act, then let action teach you what matters next.
To understand the wider purpose behind the project, visit the About Zero to AI page or return to the Season 1 archive.
Build one small thing.
You do not need another perfect plan before you start. Pick one small problem, give yourself a focused block of time and let the first shipped slice become your teacher.