Facilitator Guide β Management (sessions 10β18)
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: Management. Other facilitator volumes: Technology usage Β· Strengthen the human. Pick a session in the menu β one is shown at a time.
Session 10 β Publish a One-Page AI Usage Doctrine
Management Β· β± 60 minutes Β· π― Artifact: AI Usage Doctrine
Learner outcome. Managers can write a clear doctrine that tells teams what AI uses are encouraged, restricted, forbidden, and reviewable.
Core idea. A doctrine reduces improvisation. It gives people permission to learn while protecting data, quality, accountability, and trust.
Facilitator intent. Guide learners to produce a usable AI Usage Doctrine while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about publish a one-page ai usage doctrine.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
An AI rule that stays in someone's head does not guide behavior. Publishing creates shared expectations and a basis for review.
π Try: Post the team AI rules where people actually work.Include examples of allowed and forbidden uses.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Different uses carry different risk. Drafting a low-risk email is not the same as recommending a benefit, diagnosis, loan, or disciplinary action.
π Try: List every AI use your team already performs.Separate drafting, recommendation, and decision uses.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
A doctrine is more practical than a long policy for daily behavior. It gives teams enough clarity to act while formal governance evolves.
π Try: Write four zones: encouraged, review required, forbidden, and escalate.Add a review date so the doctrine evolves with tools and rules.
π©βπ« 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 AI Usage Doctrine 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.
π 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.
π 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.
π 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.
π 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.
- Team or project
- Encouraged uses
- Allowed with review
- Forbidden uses
- Escalation triggers
- Data rule
- Verification rule
- Review date
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Fragile. People may have different risk tolerance and hidden assumptions.
Best choice. It gives permission and boundaries at the same time.
Sometimes necessary for high-risk contexts, but often blocks useful low-risk learning.
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 publish a one-page ai usage doctrine after building the AI Usage Doctrine?
- 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 AI Usage Doctrine 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
- Writing values without examples.
- Forgetting to define who owns each AI system.
- Treating AI assistance, recommendation, and decision as the same thing.
- Never revisiting the doctrine after tools change.
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 11 β Start Transformation From the Work Problem
Management Β· β± 55 minutes Β· π― Artifact: Work Problem Brief
Learner outcome. Managers can define the work problem, baseline measure, user group, and expected improvement before buying or deploying technology.
Core idea. Tool-first transformation creates theater. Problem-first transformation produces learning, measurement, and better decisions.
Facilitator intent. Guide learners to produce a usable Work Problem Brief while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about start transformation from the work problem.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
Real transformation changes roles, workflows, measures, skills, decisions, or customer experience.
π Try: Describe what would change for the user if a project succeeded.Name which workflow, role, or decision will be different after the change.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
A work problem should be observable and measurable. Vague goals like innovation or modernization are not enough.
π Try: Write the painful moment in the workflow before naming a tool.Measure the current baseline for delay, rework, or frustration.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Without a baseline, you cannot tell whether the change improved anything or only felt new.
π Try: Measure current turnaround time before piloting an AI assistant.Record current error types before changing a process.
π©βπ« 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 Work Problem Brief 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.
π 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.
π 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.
π 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.
Learner worksheet guidance
Tell learners to fill these fields during the session. Do not let the worksheet become decoration; pause and inspect it.
- Affected group
- Painful moment
- Current baseline
- Root cause hypothesis
- Desired improvement
- Constraints
- Possible solutions
- First test
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Tool-first change can create cost without solving the work problem.
Best choice. It turns transformation into measurable learning.
Too slow. A clear first problem statement is enough to start a limited test.
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 start transformation from the work problem after building the Work Problem Brief?
- 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 Work Problem Brief 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
- Starting with features instead of user pain.
- Using vague goals like 'modernize' or 'be efficient.'
- Forgetting to measure the current baseline.
- Ignoring simpler process fixes.
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 12 β Run a Limited Pilot With Balanced Metrics
Management Β· β± 70 minutes Β· π― Artifact: Pilot Board
Learner outcome. Managers can design a pilot with scope, guardrails, support, stop rules, and metrics for quality, speed, cost, risk, and experience.
Core idea. A pilot should not be a public relations demo. It is a disciplined learning device with permission to stop, adapt, or scale.
Facilitator intent. Guide learners to produce a usable Pilot Board while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about run a limited pilot with balanced metrics.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
The purpose of a pilot is learning. It should have scope, duration, users, data, metrics, support, and stop rules.
π Try: Test one request type with one team for two weeks.Exclude high-risk cases until the control method is proven.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
A tool can make work faster and worse at the same time. Balanced measures reveal tradeoffs.
π Try: Track time saved and customer callbacks together.Measure review effort and user stress during the pilot.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Stop rules prevent momentum from carrying a weak or harmful system into full deployment.
π Try: Stop if error severity exceeds the agreed threshold.Pause if users cannot verify outputs within the available time.
π©βπ« 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 Pilot Board 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.
π Insist on a real baseline. If learners cannot measure exactly, ask for a reasonable proxy and a date to improve it.
π 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.
π 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.
- Hypothesis
- Pilot users
- Included cases
- Excluded cases
- Baseline
- Metrics
- Support path
- Stop criteria
- Scale criteria
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
That is a rollout without the discipline of learning.
Best choice. You can learn without locking in a bad system.
Risky. Enthusiasts may hide usability, trust, or workload problems that others will face.
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 run a limited pilot with balanced metrics after building the Pilot Board?
- 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 Pilot Board 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
- Measuring speed but not quality.
- Ignoring the workload of review and correction.
- Not giving users a safe way to report problems.
- Scaling because the demo impressed people, not because the pilot proved value.
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 13 β Redesign Roles After Automation
Management Β· β± 65 minutes Β· π― Artifact: Role Redesign Map
Learner outcome. Managers can redesign a role so automation improves the job instead of leaving people only with stressful exceptions.
Core idea. Removing tasks is not the same as redesigning work. A good redesign preserves learning, ownership, relationship, and meaningful responsibility.
Facilitator intent. Guide learners to produce a usable Role Redesign Map while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about redesign roles after automation.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
Redesign is not simply removing tasks. It creates a healthier, more complete role around outcomes, learning, and decision rights.
π Try: Replace repetitive data entry with quality review and exception analysis.Add coaching duties when routine beginner tasks are automated.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
A role is more than a task list. It includes identity, learning, trust, workload, and contribution.
π Try: Map a role by outcomes, not just tasks.Name which decision rights must change if responsibility changes.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Automation changes what humans do next. If the role is not redesigned, people may inherit only difficult exceptions.
π Try: After automation, add improvement work instead of only monitoring.Check whether junior staff still have a path to learn the basics.
π©βπ« 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 Role Redesign 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.
π 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.
π 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.
π 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.
π 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.
- Role
- Current outcomes
- Tasks changing
- Learning moments at risk
- New responsibilities
- Decision rights
- Support needed
- Workload risk
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Incomplete. The role may become narrower, more stressful, and less developmental.
Best choice. Technology improves the work rather than hollowing it out.
May protect learning briefly but can waste capacity if not redesigned intentionally.
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 redesign roles after automation after building the Role Redesign 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 Role Redesign 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
- Treating people as task leftovers.
- Forgetting junior learning pathways.
- Giving responsibility without decision rights.
- Measuring only output while ignoring stress and development.
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 14 β Build the Human-in-the-Loop Control System
Management Β· β± 75 minutes Β· π― Artifact: Control Rule
Learner outcome. Managers can place human review where it actually detects errors, rather than using review as a symbolic final approval.
Core idea. Human control works only when the reviewer has criteria, time, evidence, authority, and a clear place in the workflow.
Facilitator intent. Guide learners to produce a usable Control Rule while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about build the human-in-the-loop control system.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
The human must have evidence, time, criteria, authority, and accountability. A symbolic final approval is not enough.
π Try: Require a specialist to review sensitive cases before response is sent.Let the reviewer see the source document, not only the AI summary.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Controls should catch errors while they are still reversible. They make responsibility operational.
π Try: Write a rule: if confidence is low, route to a human before action.Document every override and why it happened.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Escalation protects people when the case is sensitive, uncertain, high impact, or outside the tool's safe scope.
π Try: Escalate employee health, conflict, or legal questions to a trained person.Escalate customer complaints involving loss, harm, or distress.
π©βπ« 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 Control Rule 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.
π 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.
π 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.
- Workflow
- AI role
- Possible error
- Review point
- Reviewer
- Evidence available
- Review criteria
- Authority
- Escalation trigger
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Often symbolic. Late review may not catch hidden errors or may be too rushed.
Best choice. Review becomes real protection, not ceremony.
Too late for many high-impact uses.
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 the human-in-the-loop control system after building the Control Rule?
- 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 Control Rule 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 review equals responsibility.
- Reviewing only the AI answer without source material.
- Giving reviewers no time or power to stop the process.
- Failing to document why overrides happen.
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 15 β Govern Risk, Ethics, and Compliance
Management Β· β± 80 minutes Β· π― Artifact: AI Risk Register Row
Learner outcome. Managers can create a practical AI risk register and connect it to data classification, vendor review, bias testing, incident response, and legal review.
Core idea. AI is a sociotechnical system. Risk lives in the data, people, supplier, process, interface, incentives, and decision rights.
Facilitator intent. Guide learners to produce a usable AI Risk Register Row while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about govern risk, ethics, and compliance.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
Governance makes AI visible and accountable. It connects daily use to risk, ethics, compliance, and leadership decisions.
π Try: Assign an owner for each AI system.Review the AI register every quarter.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Risk has probability, severity, detectability, and reversibility. Not all risks are equal.
π Try: Rate one AI use by likelihood and severity of error.Write what would make a risk detectable early.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Ethics goes beyond legality. A use can be possible and still be unfair, opaque, or damaging.
π Try: Ask who benefits and who carries the risk.Ask whether you could explain the decision publicly.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Compliance depends on country, sector, data type, purpose, and level of impact. AI should not be used to bypass qualified review.
π Try: Route high-impact uses to legal, privacy, security, or compliance teams.Link each AI use in the register to the rule or policy it must follow.
π©βπ« 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 AI Risk Register Row 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.
π 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.
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
- Owner
- Users
- Data
- Supplier
- Autonomy level
- Impact
- Controls
- Incident signal
- Stop rule
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Incomplete. Informal tools can create real risk.
Best choice. You cannot govern what you cannot see.
Too passive. Start lightweight and improve it with risk, legal, security, and users.
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 govern risk, ethics, and compliance after building the AI Risk Register Row?
- 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 AI Risk Register Row 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 pilots as outside governance.
- Listing a risk without a control.
- Forgetting incident response.
- Keeping a register that nobody reviews.
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 16 β Lead Change Without Disengaging the Team
Management Β· β± 70 minutes Β· π― Artifact: Change Conversation Script
Learner outcome. Managers can communicate AI-era change honestly while creating participation, safety, and visible learning loops.
Core idea. People disengage when change feels done to them. They engage more when leaders tell the truth, invite local knowledge, and act on what they hear.
Facilitator intent. Guide learners to produce a usable Change Conversation Script while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about lead change without disengaging the team.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
Change leadership is not announcing decisions. It includes listening, explaining uncertainty, adjusting plans, and protecting people through transition.
π Try: State what is decided and what is still open.Hold a feedback review after a pilot and show what changed.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Disengagement often appears when people feel change is done to them, when risks are hidden, or when learning is demanded without support.
π Try: Ask what would make people hide AI errors.Watch for silence, resistance, cynicism, and reduced problem reporting.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
It is essential for AI adoption because hidden errors and silent fear make systems dangerous.
π Try: Thank someone publicly for reporting a tool mistake.Separate incident learning from blame.
π©βπ« 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 Change Conversation Script 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.
π 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.
π 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.
- Why now
- What is decided
- What is open
- Risks
- Protections
- Participation points
- Feedback channel
- Next update date
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
This creates fear and removes local knowledge from the design.
Best choice. Trust grows when people see both candor and action.
Unsafe promise. It may comfort briefly but damages credibility later.
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 lead change without disengaging the team after building the Change Conversation Script?
- 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 Change Conversation Script 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 hype instead of clarity.
- Pretending there is no risk.
- Asking for feedback without responding to it.
- Letting managers improvise different messages.
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 17 β Turn Productivity Gains Into Learning Capacity
Management Β· β± 60 minutes Β· π― Artifact: Productivity Reinvestment Plan
Learner outcome. Managers can reinvest time saved by technology into training, quality, safety, documentation, and better work design.
Core idea. If every minute saved becomes more throughput, people hide learning needs and treat AI as a threat. Shared gains create trust and capability.
Facilitator intent. Guide learners to produce a usable Productivity Reinvestment Plan while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about turn productivity gains into learning capacity.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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 gain is real only after setup, review, correction, coordination, and human impact are counted.
π Try: Measure net time saved after checking outputs.Compare faster production with rework and customer satisfaction.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
When productivity gains are reinvested into learning, the team becomes more capable instead of just more loaded.
π Try: Use part of saved time for peer review or documentation.Reserve weekly practice time after introducing a new tool.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Reinvestment prevents AI from becoming only a pressure multiplier.
π Try: Allocate 25 percent of saved time to training.Reward people who document lessons from failed tests.
π©βπ« 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 Productivity Reinvestment 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.
π 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.
π 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.
π 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.
- Tool or process
- Net gain measured
- Output reinvestment
- Learning reinvestment
- Quality reinvestment
- Recovery or focus time
- Recognition behavior
- Workload risk
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Short-term output may rise, but learning, quality, and trust can decline.
Best choice. Productivity becomes capability, not just pressure.
Understandable but unhealthy. Better to negotiate explicit reinvestment.
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 turn productivity gains into learning capacity after building the Productivity Reinvestment 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 Productivity Reinvestment 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
- Measuring only raw speed.
- Treating training as personal time.
- Rewarding enthusiasm but not careful risk reporting.
- Letting the workload expand invisibly.
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 18 β Execute a 90-Day Resilience Plan
Management Β· β± 90 minutes Β· π― Artifact: 90-Day Action Plan
Learner outcome. Managers and professionals can convert analysis into a 90-day cycle of baseline, pilot, learning, evidence, decision, and updated SWOT.
Core idea. Resilience is built by repeated action. A 90-day plan keeps the scope small enough to execute and concrete enough to prove progress.
Facilitator intent. Guide learners to produce a usable 90-Day Action Plan while applying the title concepts from the improved learner guide. The session should feel like coached practice, not a lecture about execute a 90-day resilience plan.
Watch for: Managers may speak in policy language. Push for examples, decision rights, stop rules, and visible feedback loops.
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.
Execution matters because AI-era anxiety often stays abstract. A 90-day cycle makes action small enough to complete.
π Try: Put two learning blocks on your calendar today.Choose a day-60 decision date before starting a pilot.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Ninety days gives time for baseline, practice, pilot, reflection, and a revised SWOT without pretending to predict the future.
π Try: Run a two-week pilot inside an eight-week learning plan.Refresh your SWOT at the end of the cycle.
π©βπ« Ask learners to give one example from their own context and explain why the concept matters for their artifact.
Resilience is built through repeated evidence-based action, not motivation alone.
π Try: Pair one threat with one opportunity and one measurable action.Add your pilot result to your portfolio or team documentation.
π©βπ« 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 90-Day Action 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.
π 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.
π 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.
π 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.
- Priority threat
- Priority opportunity
- Baseline
- Pilot task
- Two-week test
- Weekly learning block
- Responsibility partner
- Day-60 decision
- Day-90 SWOT update
Choice path facilitation
Ask learners which option they would naturally choose before revealing the consequence. This surfaces habits and risk tolerance.
Too broad. Learning without action may become avoidance.
Best choice. Small repeated action builds resilience.
Risky. Your options improve when you start before urgency forces action.
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 execute a 90-day resilience plan after building the 90-Day Action 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 90-Day Action 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
- Trying to solve every career risk at once.
- Skipping the baseline.
- Running a pilot with no decision date.
- Updating your story without evidence.
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.