AI curriculum

Course outline for Human–AI Workflow Design

A convincing recommendation can be wrong, and an approval button does not ensure meaningful review. Design a draft-and-review workflow that assigns decision authority using consequences, reversibility, and reviewer capacity. Test how people detect errors and retain the skills needed to challenge outputs.

About Human–AI Workflow Design

A convincing recommendation can be wrong, and an approval button does not ensure meaningful review. Design a draft-and-review workflow that assigns decision authority using consequences, reversibility, and reviewer capacity. Test how people detect errors and retain the skills needed to challenge outputs.

Human–AI Workflow Design Course Objectives

  • Allocate drafting, recommending, approving, and executing to named roles.
  • Choose pre-action approval or monitoring based on consequence and reversibility.
  • Define evidence-based review and escalation criteria.
  • Identify persuasive errors without relying on stated model confidence.
  • Revise a review policy using disagreements and observed workload.

Pre-requisites

  • Familiarity with a team or operational workflow and its decision owners.
  • Basic awareness of AI limitations and workflow modeling; coding is not required.

Before this course

Complete the required courses or bring equivalent experience. Recommended courses add useful depth; they are not enrolment gates.

Required preparation

Recommended preparation

Understands AI limitations and workflow roles before allocating work and authority; coding is not required.

Find your place in the learning map

Lab Setup

  • Text or diagram editor and a timer or spreadsheet.
  • Supplied synthetic decisions, evidence packets, convincing output fixtures, and a simulated action-permission table.
  • No model subscription, real messages, or external actions are needed.

Detailed Course Outline

Module 1: Allocate work and authority

  • Human-agent collaboration: Assign drafting, recommending, approving, and executing to named roles with explicit evidence requirements and decision responsibilities.
  • Division of work: Allocate tasks according to consequence, reversibility, and judgment needs rather than assigning everything a model can generate.
  • Human approval: Choose pre-action review for consequential decisions and require evidence checks rather than treating an approval button as sufficient.
  • Human escalation: Define who receives missing, contradictory, or unsupported recommendations and what evidence enables a responsible next decision.

Practical outcome: Create a draft/recommend/approve/execute matrix and escalation rules based on consequences and reversibility.

Module 2: Make review an active control

  • Authority boundaries: Separate recommendation privileges from execution rights and deny simulated sends that lack the required human authorization.
  • Uncertainty: Identify missing support and contradictory evidence without substituting persuasive wording or stated model confidence for justification.
  • Review: Apply independent evidence checks and acceptance criteria while measuring reviewer time, disagreements, and available review capacity.
  • Skill retention: Design practice tasks that preserve the domain judgment reviewers need to recognize errors and challenge automated recommendations.

Practical outcome: Define independent evidence checks, reviewer-capacity limits, and practice tasks that preserve judgment.

Module 3: Test and revise collaboration

  • Simulator-based practice: Use supplied correct and persuasive incorrect outputs to rehearse accept, reject, and escalate decisions without real consequences.
  • Automation bias: Detect unjustified acceptance of convincing recommendations and compare reviewer decisions with independently checked supporting evidence.
  • Ironies of automation: Examine how reduced routine practice and concentrated exception handling can weaken oversight, then revise one bounded collaboration control.

Practical outcome: Run persuasive correct and incorrect cases, record reviewer disagreements, and propose a bounded policy correction.

Practical exercise

  • Produce an authority matrix, review checklist, and escalation record for a fictional draft-and-approve process.
  • Review six supplied outputs, including correct, unsupported, and contradictory recommendations; justify accept, reject, or escalate decisions with evidence.
  • Verify that simulated unapproved sends are denied and unsupported recommendations cannot pass the acceptance checklist.
  • Measure reviewer time and disagreement, then revise one control and specify a skill-retention exercise.

What you will produce

Specify and test human review and delegated authority for an AI-assisted decision workflow.

How the work is checked

  • Every action has a named owner and explicit authority.
  • Unsupported recommendations and unapproved sends fail acceptance.
  • Six case decisions cite independent evidence rather than model confidence.
  • The revised policy addresses measured review effort and disagreement.

Six-hour noncoding simulation; human approval can fail, and these cases do not establish calibrated risk estimates or a complete human-factors program.

When another approach is better

  • Do not add approval to every harmless reversible action if it creates an unmanageable review queue.
  • Do not delegate consequential decisions when reviewers lack evidence or the ability to challenge the result.

How we train

Contact us for full course details, including duration, delivery options and lab requirements.

Ask about exercises, instructor feedback and the prior knowledge you need. Tool-specific courses marked provisional may become modules in a broader course.

Discuss your learning goals