Module 1.1 established how the current generation of AI tools came to exist. Module 1.2 developed what those tools actually are as systems. Module 1.3 surveyed where they show up in professional work across the domains this programme covers. Each of those modules built conceptual understanding. This module converts understanding into applied capability.
The central question this module answers is how to make AI tools useful in a practitioner's own work. The answer has several parts. A practitioner needs to see their own work as a set of tasks rather than as a role description, because tasks are what can be accelerated or supported by AI while roles are too broad to work with. They need to know how to give an AI tool a well-constructed instruction, because the quality of the output depends substantially on the quality of the instruction. They need to understand how to build up from simple prompts to more sophisticated patterns, so that their capability grows as their confidence grows. They need working frameworks for common situations, so that they are not starting from scratch every time. They need to know how to iterate when the first output is not quite right, because first outputs are rarely final. They need to know how AI systems fail and how to catch those failures before they damage the work. And they need a practical path for turning these skills into a sustainable practice, because capability develops through deliberate use rather than through single-session study.
This module treats each of these components in turn. The treatment is practical. A practitioner who has worked through the module can sit down at their desk, identify a task in their own work that AI can support, construct an effective instruction for that task, evaluate what the AI produces, refine it through iteration, and take responsibility for the final output. That is the applied capability Stage 1 is meant to produce. Stage 2 then builds on this capability with the collaboration disciplines that integrate AI tools into structured professional practice.
One note before the sections begin. The skills in this module are not technical skills in the sense that programming or data analysis are technical skills. They are communication skills. The practitioner is learning to communicate clearly with a system that processes language, produces language, and responds to the specific way requests are framed. The better the communication, the better the output. This is why the module works for practitioners across all the domains surveyed in Module 1.3, and why the skills transfer across tasks even though the specific applications differ. The underlying discipline is the same.