Before the class: select participants and target tasks
Distinguish executive, manager, and operational needs. Ask each group to select a task, such as summarizing public material or drafting an agenda. Agree the exercise output and assessment criteria with the team owner. Ensure participants can access company-approved tools. Developers who need implementation skills require a separate learning path appropriate to that goal rather than the same general office-work syllabus.
Module 1: capabilities, limits, and data
Discuss the difference between search, drafting, and automated actions. Practice recognizing confident answers that lack support. Use public or synthetic examples to distinguish material allowed in a tool from material needing permission. The module output is a practical usage boundary and a route for questions about uncertain data or tool use. Align this with the organization’s actual rules rather than a generic promise of safety.
Module 2: write instructions that can be evaluated
Participants practice specifying the objective, audience, context, boundaries, format, and an example of the desired output. Use several instructions for the same task and compare the results. Encourage participants to add missing context and request clarity about uncertainty. The output is a task-specific instruction template with notes on when it is insufficient. Good-looking wording alone is not the assessment criterion.
Module 3: review outputs before use
Teach fact-checking against sources, checking numbers with calculation tools, and assessing completeness against the brief. Include an exercise with deliberately incomplete information so participants practice rejecting unsupported conclusions. The output is a simple review sheet identifying the reviewer and whether an output can be used, needs correction, or requires a more qualified person. Assess the review process as well as the draft.
Module 4: practice by role
Sales teams might prepare research summaries from public sources, operations teams might draft reports from synthetic data, and managers might assess options against a brief. These are sample exercises, not productivity promises. Each group compares its output with agreed criteria. Record remaining manual steps and process changes needed before applying the exercise at work. Do not assume that completing one exercise establishes readiness for every use case.
After the class: assign follow-through
Select a limited use case for follow-up, assign an owner, and schedule review appropriate to the team. Assess quality, work time including review, and reported problems. Microsoft’s introductory learning materials can provide additional reading. This is KODE’s sample syllabus and does not claim Microsoft affiliation or certification. Discuss the audience and target capabilities with KODE to shape a relevant training program.