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.
- 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.
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.
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.
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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Too early. You may automate hidden confusion, expose data, or miss the true risk point.
Best choice. You learn where the tool belongs before giving it too much control.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The Workflow Map names a real context, user, task, decision, or situation. | The artifact uses vague language such as 'improve work' or 'use AI better.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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.
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 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 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.
π 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.
π 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.
π 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.
π 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.
π 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.
Length alone is not quality. Add the right information, not every possible detail.
Best choice. Good prompting is structured delegation plus supervision.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The Prompt Pack names a real context, user, task, decision, or situation. | The artifact uses vague language such as 'improve work' or 'use AI better.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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.
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 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.
π 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 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.
π 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.
π 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 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.
Risky. Polished language can hide errors, exaggeration, or a voice that weakens trust.
Best choice. You gain speed while keeping responsibility.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The 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.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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.
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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Not enough. Citations can be wrong, irrelevant, invented, or misread.
Best choice. Match verification effort to risk and impact.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The Verification Plan names a real context, user, task, decision, or situation. | The artifact uses vague language such as 'improve work' or 'use AI better.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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 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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Unsafe. Convenience is not a data governance rule.
Best choice. You create space to learn without creating unnecessary exposure.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The Sandbox Charter names a real context, user, task, decision, or situation. | The artifact uses vague language such as 'improve work' or 'use AI better.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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 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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Maybe, but annoyance does not prove stability or safety.
Best choice. You learn from a contained pilot.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The 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.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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 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.
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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Weak choice. Availability is not validity.
Best choice. You protect decisions from false precision.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The 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.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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 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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Not enough. Impressive input handling does not prove reliable output.
Best choice. You learn which mode actually supports the work.
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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The 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.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.
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.
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 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.
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.
π 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.
π 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.
π 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.
π 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.
π 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.
Dangerous. Urgency does not erase privacy, security, or contractual duties.
Best choice. It protects trust while still allowing useful 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.
Mini-case bridge
π©βπ« 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
| Criterion | What good looks like | Red flag |
|---|---|---|
| Specificity | The 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.' |
| Actionability | The next step is small, dated, and possible within seven days. | The learner ends with an aspiration but no action. |
| Human responsibility | The learner names who decides, reviews, verifies, or carries responsibility. | The tool, policy, or system appears to be responsible by itself. |
| Evidence | The learner saves proof: a baseline, example, draft, rule, message, map, or review note. | The learner leaves with only an opinion or intention. |
| Safety | Sensitive 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.