Facilitator Guide β€” Technology usage (sessions 1–9)

Run these Lojik360 action sessions with a group β€” aligned to the three moves: delegate carefully, supervise rigorously, strengthen what stays human.

How to use this guide

This guide helps a facilitator, coach, trainer, or team lead run the 27 learner-action sessions. It is aligned to the improved learner guide and adds concept-teaching notes, guided action support, debrief questions, and learner artifact review criteria.

Facilitation principle. The facilitator should not lecture through the content. The facilitator's job is to help learners define concepts, act on real examples, protect sensitive information, review their artifacts, and leave with evidence of learning.
  • Start each session by naming the learner artifact to be produced.
  • Use the title concepts as a short warm-up before action begins.
  • Keep learners working with their own real but safe examples.
  • Use the guided action table to coach action, not to present slides.
  • Use the review rubric to inspect artifacts before learners leave the session.
  • Close each session with evidence, next action, and one open risk or question.

Learner version of these sessions: Technology usage. Other facilitator volumes: Management Β· Strengthen the human. Pick a session in the menu β€” one is shown at a time.

Session 1 β€” Map the Work Before Choosing the Tool

Technology usage · ⏱ 55 minutes · 🎯 Artifact: Workflow Map

Learner outcome. Learners can describe a real workflow in observable steps before deciding where AI or automation belongs.

Core idea. Technology selection should start with the work problem, not with the newest tool. A clear map reveals inputs, outputs, exceptions, owners, data sensitivity, and the points where human judgment must stay visible.

Facilitator intent. Guide learners to produce a usable Workflow Map while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about map the work before choosing the tool.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Map β€” To map is to make the invisible steps of work visible in a clear order.
A map helps you see what happens before you choose a tool. It shows the inputs, outputs, handoffs, decisions, exceptions, and risks that are usually hidden inside a routine.
πŸ‹ Try: Draw the five steps you follow before sending a weekly report.Mark the step where a mistake would be easiest to catch.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Work β€” Work means the actual tasks, decisions, conversations, files, approvals, and responsibilities that create a result.
Do not confuse work with a job title. Two people with the same title may do very different work, and AI affects tasks before it affects whole professions.
πŸ‹ Try: List the twenty tasks you performed this week and group them by routine, judgment, relationship, and verification.Choose one task and write the result it is supposed to create.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Tool β€” A tool is any system, software, AI assistant, automation, template, or method used to help produce work.
A tool should serve the work problem. A tool is not automatically a solution; it becomes useful only when it improves quality, speed, access, safety, or learning without creating unacceptable risk.
πŸ‹ Try: Name one tool you use daily and write what problem it actually solves.Identify one task where a checklist may be a better tool than AI.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Workflow Map that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Name one real process you repeat often. Write the exact start and end point. Avoid a vague process like 'communication'; choose something observable such as 'turn client notes into a follow-up email.'
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Break the process into small steps. Each step should take roughly 15 to 60 minutes and should produce a visible output.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Mark the data used at each step. Classify it as public, internal, confidential, personal, or highly sensitive.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Choose the technology role for each step: automate, augment, preserve, or redesign. Add one sentence explaining the choice.
πŸ‘‰ Make the choice visible. Ask learners what they rejected and why, not only what they selected.
πŸ”Ž Evidence: A selected option with one sentence explaining why it is the best safe next step.
Place human control at the point where a mistake can still be caught and corrected without serious harm.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Process name and trigger
  • Step-by-step map
  • Data used at each step
  • Risk if the step is wrong
  • Best role for technology
  • Human checkpoint
  • Manual fallback

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Ask AI to automate the whole process now
Too early. You may automate hidden confusion, expose data, or miss the true risk point.
βœ… Map the process first, then test one low-risk step
Best choice. You learn where the tool belongs before giving it too much control.
⚠️ Refuse all AI use because the process matters
Too broad. Important work can still include safe augmentation if control is designed well.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

I will describe a workflow. Help me break it into observable steps. For each step, ask what input, output, owner, data, exception, and risk I should record. Do not recommend tools yet.
Here is my workflow map: [paste]. Identify which steps are candidates for automation, augmentation, preservation, or redesign. Explain the risk behind each suggestion.
Act as a process quality reviewer. Challenge my workflow map. Where am I hiding judgment, sensitive data, or exceptions that a tool may mishandle?

Mini-case bridge

A training coordinator wants to use AI to create workshop agendas. The mapping exercise shows that drafting the agenda is easy to augment, but confirming participants, adapting to local constraints, and handling sensitive feedback require human control.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of map the work before choosing the tool after building the Workflow Map?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Workflow Map names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Choosing a tool before defining the work problem.
  • Treating a job title as one process instead of mapping actual tasks.
  • Putting human review only at the end, when the error is already hard to reverse.
  • Ignoring data sensitivity because the task feels routine.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 2 β€” Prompt With Context, Constraints, and Checks

Technology usage · ⏱ 50 minutes · 🎯 Artifact: Prompt Pack

Learner outcome. Learners can write prompts that define the task, audience, source material, limits, and verification method.

Core idea. Prompting is not magic wording. It is the discipline of giving a system the situation, the goal, the boundaries, and the quality criteria it must satisfy.

Facilitator intent. Guide learners to produce a usable Prompt Pack while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about prompt with context, constraints, and checks.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Prompt β€” A prompt is the instruction, context, material, and success criteria you give to an AI system.
A good prompt is structured delegation. It tells the tool what to do, for whom, with what limits, in what format, and how the answer should be checked.
πŸ‹ Try: Rewrite 'summarize this' as a prompt that names audience, purpose, length, and key risks.Ask AI to list its assumptions after answering your prompt.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Context β€” Context is the situation surrounding the task: audience, purpose, background, constraints, available information, and decision use.
Without context, AI fills gaps with generic patterns. Context helps the output fit the real reader, organization, risk level, and action needed.
πŸ‹ Try: Before asking for a draft, write who will read it and what decision they must make.Add two constraints from your real setting, such as low bandwidth, legal review, or limited time.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Constraints β€” Constraints are limits the answer must respect, such as length, tone, data rules, budget, audience, source boundaries, or format.
Constraints turn a broad request into useful work. They also stop the tool from inventing scope, tone, or authority it should not have.
πŸ‹ Try: Tell AI to use only the facts you provide and to flag missing information instead of inventing it.Ask for a 150-word version, a bullet version, and a version for a beginner.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Checks β€” Checks are the verification steps used to inspect an AI output before trusting or using it.
Checks convert AI from a confident generator into a supervised assistant. They may include source review, recalculation, expert review, field validation, or stakeholder feedback.
πŸ‹ Try: After an AI summary, compare three claims against the original document.Ask a colleague to review the output for missing context before sending it.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Prompt Pack that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Choose one real task. Write the weak prompt you would normally use in a hurry.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Add the missing context: audience, purpose, source material, constraints, tone, length, and decision use.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Tell the tool what not to do. Name forbidden sources, confidential details, claims it must avoid, and assumptions it should flag.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Ask for a checkable format. Request headings, bullets, a table, or a decision note only if that format helps you inspect the answer.
πŸ‘‰ Treat review as action. Ask who checks, what evidence they use, and what power they have to pause or change the result.
πŸ”Ž Evidence: A verification note showing source, reviewer, criteria, or correction.
Add a verification instruction: sources to open, numbers to recalculate, risks to flag, or expert review needed.
πŸ‘‰ Treat review as action. Ask who checks, what evidence they use, and what power they have to pause or change the result.
πŸ”Ž Evidence: A verification note showing source, reviewer, criteria, or correction.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Task
  • Audience
  • Context
  • Source material
  • Constraints
  • Output format
  • Verification method
  • What the tool must not do

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Make the prompt longer until the result improves
Length alone is not quality. Add the right information, not every possible detail.
βœ… Use a prompt frame and define checks before trusting the output
Best choice. Good prompting is structured delegation plus supervision.
⚠️ Copy a famous prompt from the internet
Sometimes useful, but it may not match your data, risk, audience, or work standards.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Use this frame to help me write a better prompt: role, task, audience, context, constraints, output format, risks, and verification. Ask me one question at a time until the prompt is clear.
Rewrite this prompt so the output is easier to verify: [paste weak prompt]. Keep the task realistic and include a section for assumptions and limits.
After answering my prompt, create a verification checklist for the answer. Separate facts to check, assumptions to test, and judgment calls I must make.

Mini-case bridge

A manager asks an AI assistant to 'write a policy.' The result sounds polished but misses local rules. After adding audience, scope, approved sources, exclusions, and a review checklist, the output becomes a draft that legal and HR can actually evaluate.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of prompt with context, constraints, and checks after building the Prompt Pack?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Prompt Pack names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Asking for a final answer when you need a draft.
  • Forgetting to state the audience and decision context.
  • Letting the tool invent sources or policies.
  • Not asking for limits, assumptions, and verification steps.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 3 β€” Delegate Drafting Without Losing Your Voice

Technology usage · ⏱ 60 minutes · 🎯 Artifact: Draft Revision Log

Learner outcome. Learners can use AI for first drafts while preserving accuracy, tone, responsibility, and originality.

Core idea. A draft is not a decision. AI can help produce a starting point, but the human remains responsible for the message, evidence, audience fit, and final judgment.

Facilitator intent. Guide learners to produce a usable Draft Revision Log while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about delegate drafting without losing your voice.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Delegate β€” To delegate is to give a task to another person or tool while keeping responsibility for the result.
Delegation to AI is not abandonment. You decide the task, define boundaries, review the output, correct errors, and remain accountable.
πŸ‹ Try: Delegate only the first draft of a message, then revise facts and tone yourself.Ask AI to create three structure options, not the final decision.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Drafting β€” Drafting is creating a first version that will be reviewed, corrected, and improved.
A draft is raw material. AI is often useful at this stage because a rough structure can reduce blank-page friction, but the draft still needs human judgment.
πŸ‹ Try: Ask AI for a first draft, then mark every sentence that needs verification.Create a before-after revision log showing what you changed.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Voice β€” Voice is the recognizable style, tone, values, and level of care in your communication.
Voice protects trust. A generic AI tone may sound smooth but fail to match the relationship, culture, emotion, or responsibility of the moment.
πŸ‹ Try: Replace three generic phrases in an AI draft with words you would actually say.Add one real example from your context to make the message yours.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Draft Revision Log that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Select a low-risk communication. Write the purpose in one sentence and name the reader's real concern.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Ask AI for a first draft only after you provide audience, tone, facts, length, and what must be avoided.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Highlight every claim that needs verification: names, numbers, dates, promises, policy statements, and cause-effect claims.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Rewrite the draft in your voice. Add one specific example, one honest limit, and one clear next step.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Compare the raw AI draft with your final version. Write down what you changed and why.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Reader
  • Reader concern
  • Message purpose
  • Facts that must be accurate
  • Tone words
  • Sentences I changed
  • My added example
  • Final next step

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Send the polished AI draft because it sounds professional
Risky. Polished language can hide errors, exaggeration, or a voice that weakens trust.
βœ… Use the draft as raw material and revise the facts, tone, and examples
Best choice. You gain speed while keeping responsibility.
⚠️ Avoid AI because writing must be fully human
Not necessary. You can delegate first drafts while preserving judgment and voice.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Draft a [message type] for [audience]. Purpose: [purpose]. Use these facts only: [facts]. Tone: [tone]. Avoid exaggeration, invented details, and promises I did not make.
Review this draft for voice, clarity, and trust. Mark sentences that sound generic, inflated, unclear, or risky. Do not rewrite yet.
Help me create a revision log. Compare my raw draft and final draft, then list what changed in facts, tone, structure, specificity, and responsibility.

Mini-case bridge

A nonprofit director uses AI to draft a donor update. The first version is generic. She adds the actual field story, removes inflated claims, and includes measurable progress. The final message is faster to prepare but still recognizably hers.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of delegate drafting without losing your voice after building the Draft Revision Log?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Draft Revision Log names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Letting AI decide the message's moral weight.
  • Keeping generic phrases because they sound smooth.
  • Failing to add lived context, examples, or constraints.
  • Editing only grammar while leaving weak thinking intact.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 4 β€” Verify AI Outputs and Sources

Technology usage · ⏱ 60 minutes · 🎯 Artifact: Verification Plan

Learner outcome. Learners can separate plausible answers from trustworthy answers by checking sources, logic, calculations, and missing context.

Core idea. Fluent language is not evidence. Verification must match the risk of the use: quick checks for low-risk drafts, stronger checks for decisions that affect money, rights, safety, reputation, or health.

Facilitator intent. Guide learners to produce a usable Verification Plan while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about verify ai outputs and sources.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Verify β€” To verify is to check whether something is accurate, supported, current, relevant, and safe enough to use.
Verification is proportional to risk. A low-risk brainstorm may need a light check; a decision affecting money, rights, safety, or reputation needs stronger evidence.
πŸ‹ Try: Open the original source behind one AI citation and confirm it supports the claim.Recalculate a number from an AI output using a spreadsheet or calculator.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
AI Outputs β€” AI outputs are the text, summaries, recommendations, classifications, images, code, tables, or actions produced by an AI system.
Outputs may be useful without being reliable. They can contain errors, bias, missing context, outdated information, or invented details.
πŸ‹ Try: Break one AI answer into facts, assumptions, recommendations, and uncertainties.Highlight which parts of the output you can verify and which parts require expert judgment.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Sources β€” Sources are the original documents, data, people, observations, or records that support a claim.
A source is not just a link. It must be relevant, credible, current, and actually connected to the claim being made.
πŸ‹ Try: Compare an AI summary with the original policy text.Check author, date, scope, and quoted passage before using a source.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Verification Plan that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Classify the use as low, medium, or high impact. The higher the impact, the stronger the verification must be.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Separate the output into claims, calculations, recommendations, and assumptions.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Choose the verification lane for each part: primary source, calculation tool, expert review, field check, or user testing.
πŸ‘‰ Make the choice visible. Ask learners what they rejected and why, not only what they selected.
πŸ”Ž Evidence: A selected option with one sentence explaining why it is the best safe next step.
Open original sources instead of trusting citations or summaries. Check author, date, scope, and whether the source actually supports the claim.
πŸ‘‰ Treat review as action. Ask who checks, what evidence they use, and what power they have to pause or change the result.
πŸ”Ž Evidence: A verification note showing source, reviewer, criteria, or correction.
Write a decision note that says what you verified, what remains uncertain, and who accepts responsibility.
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • AI output
  • Impact level
  • Claims to verify
  • Numbers to recalculate
  • Assumptions to test
  • Missing context
  • Responsible reviewer
  • Decision after verification

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Trust the answer because it includes citations
Not enough. Citations can be wrong, irrelevant, invented, or misread.
βœ… Verify only the parts that affect the decision
Best choice. Match verification effort to risk and impact.
⚠️ Reject all AI answers unless a human expert wrote them
Too rigid. AI can support work if verification is proportional and explicit.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Break this answer into factual claims, calculations, recommendations, and assumptions. For each item, suggest the most appropriate verification method.
Act as a skeptical reviewer. What would make this answer false, misleading, incomplete, outdated, or unsafe?
Create a verification log for this output. Columns: item checked, method, evidence, result, remaining uncertainty, reviewer.

Mini-case bridge

An analyst receives a market quote with a convincing citation. She opens the original source and discovers it does not support the claim. The team changes its rule from 'ask for citations' to 'open the primary source.'
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of verify ai outputs and sources after building the Verification Plan?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Verification Plan names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Confusing fluent writing with evidence.
  • Checking only the final answer instead of the underlying assumptions.
  • Using the same AI tool to verify its own unsupported claim.
  • Skipping verification because the answer matches what you hoped was true.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 5 β€” Build a Safe Learning Sandbox

Technology usage · ⏱ 45 minutes · 🎯 Artifact: Sandbox Charter

Learner outcome. Learners can design a low-risk space for experimenting with AI tools without exposing confidential data or disrupting operations.

Core idea. Experimentation becomes useful when it is bounded. A sandbox protects the organization while giving people enough freedom to learn by doing.

Facilitator intent. Guide learners to produce a usable Sandbox Charter while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about build a safe learning sandbox.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Safe β€” Safe means the activity limits harm to people, data, operations, reputation, and legal or ethical obligations.
Safety does not mean zero risk. It means risks are known, bounded, monitored, and acceptable for the learning purpose.
πŸ‹ Try: Use fictional customer profiles instead of real customer data.Set a stop rule before starting an experiment.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Learning β€” Learning is the process of turning experience into better skill, judgment, and future action.
Learning is stronger when it produces evidence. A sandbox should answer a specific question, not simply create impressions.
πŸ‹ Try: Write one question your experiment must answer.After the test, record what worked, what failed, and what you would change.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Sandbox β€” A sandbox is a controlled space for testing ideas, tools, and workflows without exposing real systems to unnecessary risk.
The sandbox gives freedom inside boundaries. It protects sensitive data and operations while allowing hands-on practice.
πŸ‹ Try: Test a tool with ten fictional cases before using real approved cases.Limit access, budget, and time for a two-week experiment.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Sandbox Charter that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Write one learning question. Make it narrow, such as 'Can AI summarize public meeting notes accurately enough for a draft?'
πŸ‘‰ Ask for a short written output, then have learners underline the parts that are specific, checkable, and owned.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Select safe data: fictional, public, anonymized, or explicitly approved.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Limit the sandbox. Define time, budget, users, permissions, and tools.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Choose success criteria and stop criteria before the test starts.
πŸ‘‰ Make the choice visible. Ask learners what they rejected and why, not only what they selected.
πŸ”Ž Evidence: A selected option with one sentence explaining why it is the best safe next step.
Capture lessons in a simple log so learning becomes transferable, not just personal curiosity.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Learning question
  • Allowed data
  • Forbidden data
  • Approved tools
  • Permissions
  • Success criteria
  • Stop criteria
  • Lesson log

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Experiment freely with whatever files are easiest to access
Unsafe. Convenience is not a data governance rule.
βœ… Use bounded tests with safe data and clear stop points
Best choice. You create space to learn without creating unnecessary exposure.
⚠️ Wait until every policy is perfect before learning anything
Too slow. A careful sandbox can produce learning while formal rules evolve.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Help me design a two-week AI sandbox for this learning question: [question]. Include allowed data, forbidden data, permissions, success criteria, stop criteria, and lesson capture.
Review my sandbox charter for privacy, security, quality, and scope risks. Suggest tighter boundaries without killing useful learning.
Create five fictional test cases that resemble my real work without using confidential or personal data. My context is: [context].

Mini-case bridge

A marketing team wants to test campaign generation but cannot use real customer files. It creates fictional customer profiles, tests ten scenarios, and evaluates quality, bias, and editing effort before touching approved systems.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of build a safe learning sandbox after building the Sandbox Charter?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Sandbox Charter names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Using real sensitive data because the test is informal.
  • Testing many questions at once and learning nothing clearly.
  • Forgetting to define when the experiment should stop.
  • Keeping lessons private instead of turning them into shared practice.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 6 β€” Automate One Simple Workflow

Technology usage · ⏱ 70 minutes · 🎯 Artifact: Automation Pilot Card

Learner outcome. Learners can select a stable, low-risk task and design a small automation with a manual fallback.

Core idea. Automating a confused process usually multiplies confusion. Start with a frequent, stable, low-risk task and measure the full cycle, including review and correction.

Facilitator intent. Guide learners to produce a usable Automation Pilot Card while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about automate one simple workflow.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Automate β€” To automate is to let a system perform a task or part of a task with reduced manual effort.
Automation is best for stable, repeated, rule-based work. It becomes risky when the task contains hidden judgment, unclear inputs, or high-impact exceptions.
πŸ‹ Try: Automate file naming for standard documents but keep human review for unusual cases.Measure the time spent correcting automation errors before calling it a success.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Simple β€” Simple means the task is narrow, understood, repeated, measurable, and low enough risk to test safely.
Simple does not mean unimportant. It means the first pilot is small enough to learn from without creating major disruption.
πŸ‹ Try: Choose a weekly status summary before automating a complex approval process.Test ten cases instead of changing the workflow for everyone.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Workflow β€” A workflow is a sequence of steps, roles, inputs, outputs, decisions, and handoffs that produces a result.
Automation changes workflows, not isolated buttons. To improve a workflow, you must understand what happens before, during, and after the automated step.
πŸ‹ Try: Write the current workflow before changing it.Name the manual fallback if the automated step fails.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Automation Pilot Card that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

List five repetitive tasks and score each one for frequency, stability, risk, data readiness, and review effort.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Pick the safest high-value candidate, not the most exciting one.
πŸ‘‰ Make the choice visible. Ask learners what they rejected and why, not only what they selected.
πŸ”Ž Evidence: A selected option with one sentence explaining why it is the best safe next step.
Measure the current baseline: time, errors, rework, stress, and handoffs.
πŸ‘‰ Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
πŸ”Ž Evidence: A number, proxy, or observation that can be compared after the test.
Design a small test with real but approved examples and a manual fallback.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Measure net gain after setup, correction, approval, and communication.
πŸ‘‰ Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
πŸ”Ž Evidence: A number, proxy, or observation that can be compared after the test.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Candidate tasks
  • Frequency score
  • Stability score
  • Risk score
  • Data readiness
  • Baseline time
  • Fallback method
  • Net result

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Automate the most annoying task immediately
Maybe, but annoyance does not prove stability or safety.
βœ… Automate one stable, low-risk task and measure the full cycle
Best choice. You learn from a contained pilot.
⚠️ Automate only after the entire process is redesigned
Sometimes needed, but it can delay safe learning on a simple subtask.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Here are five tasks: [list]. Score them for automation suitability using frequency, stability, risk, data readiness, and review effort. Explain the safest first pilot.
Help me create a baseline measurement plan for this task: [task]. Include time, errors, rework, handoffs, and user experience.
Design a manual fallback for this automation pilot. What should happen if the tool fails, produces uncertainty, or creates a suspicious result?

Mini-case bridge

A logistics coordinator automates a weekly shipment summary. The first pilot saves drafting time but reveals that exceptions still need human review. The final workflow auto-prepares the report and flags uncertain rows.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of automate one simple workflow after building the Automation Pilot Card?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Automation Pilot Card names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Automating an unstable process.
  • Ignoring setup, review, and correction time.
  • Failing to test exceptions.
  • Removing the manual fallback too early.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 7 β€” Use Data Without Fooling Yourself

Technology usage · ⏱ 65 minutes · 🎯 Artifact: Metric Interrogation Sheet

Learner outcome. Learners can ask practical questions about data quality, bias, sample size, correlation, causality, and misleading visualizations.

Core idea. AI depends on data, and data always has a story. Good users ask where the data came from, who is missing, what changed, and what the numbers cannot explain.

Facilitator intent. Guide learners to produce a usable Metric Interrogation Sheet while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about use data without fooling yourself.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Data β€” Data is recorded information, such as numbers, text, categories, dates, images, audio, transactions, or observations.
Data is shaped by how it is collected, labeled, cleaned, excluded, and interpreted. It is never neutral simply because it is numerical.
πŸ‹ Try: Ask who is missing from a dataset before using it.Define a metric in plain language and check if others define it the same way.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Fooling Yourself β€” Fooling yourself means drawing a confident conclusion from weak, incomplete, biased, or misunderstood evidence.
AI and dashboards can make weak reasoning look precise. You avoid self-deception by checking definitions, samples, missing context, correlation, and incentives.
πŸ‹ Try: Write three alternative explanations for a trend before deciding what caused it.Add one qualitative signal to explain a dashboard number.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Metric β€” A metric is a measurement used to describe performance, behavior, quality, cost, risk, or progress.
A metric should improve a decision. If nobody knows what decision the metric supports, it may create noise rather than clarity.
πŸ‹ Try: Connect one metric to one decision it should improve.Add a second metric that could reveal harm hidden by the first.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Metric Interrogation Sheet that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Choose one metric you often see or use. Write the decision it influences.
πŸ‘‰ Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
πŸ”Ž Evidence: A usable written sentence, rule, script, prompt, or brief.
Define the metric in plain language. If two people define it differently, stop and resolve that first.
πŸ‘‰ Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Ask who or what is missing from the data. Look for silent exclusions.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Check whether the chart implies a cause when it only shows a pattern.
πŸ‘‰ Treat review as action. Ask who checks, what evidence they use, and what power they have to pause or change the result.
πŸ”Ž Evidence: A verification note showing source, reviewer, criteria, or correction.
Add a second signal that would confirm, challenge, or explain the metric.
πŸ‘‰ Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Metric
  • Decision influenced
  • Definition
  • Data source
  • Who is missing
  • Possible bias
  • Second signal
  • Decision rule

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Use the metric because it is already on the dashboard
Weak choice. Availability is not validity.
βœ… Question the metric before connecting it to action
Best choice. You protect decisions from false precision.
⚠️ Reject metrics because they can be biased
Too far. Metrics are useful when interpreted with context and humility.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Interrogate this metric: [metric]. Ask questions about definition, source, sample, missing data, bias, correlation, causality, and decision relevance.
This chart seems to show [interpretation]. Give me three alternative explanations and one additional data point that would help decide between them.
Help me rewrite this dashboard insight so it separates observation, interpretation, uncertainty, and recommended action.

Mini-case bridge

A support team celebrates shorter handling time after adding AI summaries. A second metric shows customer callbacks increased. The team learns that speed alone hid unresolved issues.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of use data without fooling yourself after building the Metric Interrogation Sheet?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Metric Interrogation Sheet names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Treating a precise number as a true number.
  • Ignoring who is missing from the sample.
  • Confusing correlation with causation.
  • Using a metric without naming the decision it should improve.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 8 β€” Work With Multimodal AI

Technology usage · ⏱ 60 minutes · 🎯 Artifact: Multimodal Test Card

Learner outcome. Learners can compare text, image, audio, video, and document-based AI uses and choose controls appropriate to each mode.

Core idea. Different input types create different opportunities and risks. A voice note, photo, spreadsheet, PDF, and video do not require the same privacy rules or quality checks.

Facilitator intent. Guide learners to produce a usable Multimodal Test Card while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about work with multimodal ai.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Multimodal β€” Multimodal means using more than one type of input or output, such as text, image, audio, video, tables, or documents.
Different modes reveal different information and create different risks. A photo, voice note, and spreadsheet do not need the same checks.
πŸ‹ Try: Compare an AI summary from a voice note with one from written notes.Check whether an image-based answer missed details visible to a human.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
AI β€” AI refers to systems that perform tasks associated with prediction, generation, classification, pattern recognition, or decision support.
AI can assist with perception and language, but it does not automatically understand responsibility, context, or consequences.
πŸ‹ Try: Use AI to organize observations, then decide yourself what action is responsible.Ask the tool to state uncertainty and what original material a human should inspect.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Mode β€” A mode is the form in which information enters or leaves a system, such as speech, image, text, or structured data.
Choosing the right mode affects accessibility, accuracy, privacy, and review effort.
πŸ‹ Try: Test whether a text form or voice note gives clearer information for field reports.Use a checklist to decide whether a photo contains personal or sensitive information.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Multimodal Test Card that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

Choose one problem that appears in more than one format, such as support requests, maintenance notes, interview feedback, or training questions.
πŸ‘‰ Make the choice visible. Ask learners what they rejected and why, not only what they selected.
πŸ”Ž Evidence: A selected option with one sentence explaining why it is the best safe next step.
Select two input modes to compare. Use approved or fictional data.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Define what a good output must include and what would make it unsafe.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Run the same task in both modes and compare accuracy, missing context, privacy, and review time.
πŸ‘‰ Treat review as action. Ask who checks, what evidence they use, and what power they have to pause or change the result.
πŸ”Ž Evidence: A verification note showing source, reviewer, criteria, or correction.
Decide which mode is useful, which needs control, and which should not be used for this task.
πŸ‘‰ Turn this into a real conversation. Ask learners to prepare the exact question or message they will use.
πŸ”Ž Evidence: A prepared question, message, interview note, or feedback pattern.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Problem
  • Mode 1
  • Mode 2
  • Expected output
  • Accuracy result
  • Privacy concern
  • Review effort
  • Best use

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Use the mode that feels most impressive
Not enough. Impressive input handling does not prove reliable output.
βœ… Compare modes using the same task and clear criteria
Best choice. You learn which mode actually supports the work.
⚠️ Avoid non-text AI because it is too risky
Too broad. Some multimodal uses are safe when data and review are controlled.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Help me design a comparison test for this problem: [problem]. I want to compare [mode 1] and [mode 2]. Include criteria for accuracy, privacy, accessibility, and review effort.
Create a review checklist for AI output based on [photos/audio/documents/video]. Include what original material a human must inspect before acting.
Generate fictional sample inputs for a multimodal AI test in this context: [context]. Avoid personal or confidential data.

Mini-case bridge

A maintenance technician receives photos, voice notes, and old reports. A multimodal tool prepares a draft intervention sheet, but safety decisions remain with a qualified technician after reviewing the original materials.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of work with multimodal ai after building the Multimodal Test Card?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Multimodal Test Card names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Forgetting that images, voices, and documents can contain sensitive data.
  • Judging output quality without checking the original input.
  • Using the same review criteria for every mode.
  • Letting accessibility benefits hide privacy or accuracy problems.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.

Session 9 β€” Protect Data, Privacy, and Cybersecurity

Technology usage · ⏱ 75 minutes · 🎯 Artifact: Data Boundary Card

Learner outcome. Learners can identify data risk before using AI and apply practical safeguards for access, sharing, storage, and incident response.

Core idea. The fastest tool is not useful if it leaks confidential information, violates trust, or gives an attacker a new path into the organization.

Facilitator intent. Guide learners to produce a usable Data Boundary Card while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about protect data, privacy, and cybersecurity.

🧭 Domain note. Keep learners close to real work: tasks, data, verification, tool limits, and human responsibility.
Watch for: Learners may jump too quickly to tool choice. Slow them down and ask what the tool is being trusted to do.

Title concepts to teach

Use this section to make the improved learner-guide title concepts practical before learners begin the worksheet. Keep this short and example-driven.

Data Protection β€” Data protection means controlling how information is collected, used, shared, stored, retained, and deleted.
Protection starts before the prompt. You must know what kind of data you have and which systems are approved to process it.
πŸ‹ Try: Classify data before pasting any example into an AI tool.Remove names, account numbers, and identifying details from test cases.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Privacy β€” Privacy is the right and expectation that personal information is handled with care, purpose, limits, and respect.
Privacy is not only secrecy. It also includes consent, relevance, minimization, access control, and fair use.
πŸ‹ Try: Ask whether a person's information is necessary for the AI task.Replace real profiles with fictional profiles for experimentation.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Cybersecurity β€” Cybersecurity is the practice of protecting systems, accounts, data, and operations from unauthorized access, misuse, disruption, or attack.
AI can expand the attack surface through connected tools, files, prompts, plugins, accounts, and hidden instructions.
πŸ‹ Try: Limit an AI assistant's access to only the files needed for the task.Treat external documents as untrusted inputs until checked.
πŸ‘©β€πŸ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.

Before the session

  • Review the matching learner-facing session before facilitating.
  • Prepare a simple example of a completed Data Boundary Card that is safe to discuss.
  • Remind learners not to paste confidential, personal, regulated, or sensitive information into public tools.
  • Decide whether learners will work individually, in pairs, or in role-based groups.
  • Prepare a visible timer so action time does not disappear into discussion.

Opening move

  • Ask learners where this session topic already appears in their real work or life.
  • Invite them to name one mistake that would be costly if they handled the topic casually.
  • State that the goal is a concrete artifact, not agreement with the facilitator.

Guided action support

Use the learner actions from the improved guide. Your job is to keep each action concrete, safe, and evidenced.

List the data types involved in one AI use case.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Classify each data type: public, internal, confidential, personal, or highly sensitive.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.
Name which tools are approved for each class. If you do not know, mark it as unknown instead of guessing.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Apply least privilege: decide the minimum access, retention, and sharing needed.
πŸ‘‰ Keep the learner working on a real case. Ask for a concrete sentence, example, or decision before moving on.
πŸ”Ž Evidence: A visible entry in the learner worksheet that another person can understand.
Write the incident path: what to do if data is pasted into the wrong tool, exposed, or used in an unsafe output.
πŸ‘‰ Pause for data safety. Ask learners what information must not be shared and what can be safely fictionalized.
πŸ”Ž Evidence: A completed data note with allowed, forbidden, and unknown information clearly separated.

Learner worksheet guidance

Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.

  • Use case
  • Data type
  • Data class
  • Approved tool
  • Allowed action
  • Forbidden action
  • Access limit
  • Incident contact

Choice path facilitation

Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.

⚠️ Paste the data because the task is urgent
Dangerous. Urgency does not erase privacy, security, or contractual duties.
βœ… Classify the data first and use only approved paths
Best choice. It protects trust while still allowing useful work.
⚠️ Never use AI for any internal work
Too broad. Many internal uses are safe when data boundaries are clear.

Prompt safety and use

These learner prompts can be useful, but remind learners to use only information they are allowed to share.

Help me classify the data in this AI use case: [describe]. Ask me about public, internal, confidential, personal, and highly sensitive information. Do not ask me to paste real sensitive data.
Create a data boundary card for this use case. Include allowed tools, forbidden data, access limits, retention concerns, and incident steps.
Act as a cybersecurity reviewer. What could go wrong if an AI assistant is connected to these files or tools: [describe connection]?

Mini-case bridge

A team connects an assistant to shared files. A malicious instruction hidden in an uploaded document attempts to reveal internal information. The team limits permissions, reviews logs, and changes the workflow so external documents are treated as untrusted.
πŸ‘©β€πŸ« Ask learners what the person or team in the mini-case did well, what risk remained, and what they would copy or change in their own context.

Debrief questions

  • What changed in your understanding of protect data, privacy, and cybersecurity after building the Data Boundary Card?
  • Where did you notice a temptation to skip a check, avoid a hard choice, or stay vague?
  • What part of your work can you apply this to within the next seven days?
  • What evidence would convince you that this session changed behavior, not only awareness?

Artifact review criteria

CriterionWhat good looks likeRed flag
SpecificityThe Data Boundary Card names a real context, user, task, decision, or situation.The artifact uses vague language such as 'improve work' or 'use AI better.'
ActionabilityThe next step is small, dated, and possible within seven days.The learner ends with an aspiration but no action.
Human responsibilityThe learner names who decides, reviews, verifies, or carries responsibility.The tool, policy, or system appears to be responsible by itself.
EvidenceThe learner saves proof: a baseline, example, draft, rule, message, map, or review note.The learner leaves with only an opinion or intention.
SafetySensitive information is removed, fictionalized, or kept inside approved systems.The learner exposes real data unnecessarily or cannot name the data boundary.

Common mistakes to watch for

  • Assuming a tool is safe because it is popular.
  • Using real personal or confidential data in informal tests.
  • Giving a connected assistant more access than the task requires.
  • Not knowing who to contact when something goes wrong.

Close the session

  • Ask each learner to state the artifact they created and the next action they will take.
  • Collect one unresolved question or risk from each learner or group.
  • End by connecting the session back to Lojik360's three moves: delegate carefully, supervise rigorously, and strengthen what remains human.