Skip to content

IL 101 · Module 1

From Use Case to Project Charter

Walk through every field of the Industry AI Project Charter, and the boundary between IL 101 and AD 101-103.

Start Section 1
0 / 1 completed

Learning objectives

  • Explain the boundary between IL 101 and AD 101-103: IL 101 never repeats use-case discovery, process/pain-point understanding, or portfolio prioritization.
  • List the required fields of an Industry AI Project Charter and who is responsible for each.
  • Distinguish workflow redesign from the AI capability itself, and define the AI and human responsibilities.

Where IL 101 fits

60 min

Turning a prioritized Use Case into an investable project

AD 101 finds candidate use cases, AD 102 understands the process and pain points, and AD 103 prioritizes them in a portfolio. IL 101 starts from one already-selected use case and turns it into a project charter, a value hypothesis, measurable success criteria, a pilot scope, and a decision-ready proposal: it never redoes the work of the previous three courses.

The Industry AI Project Charter is IL 101's required artifact. IL 201 (Proof of Value) and Gate 1 (the Value Gate) both start from this charter. It must be confirmed jointly by the executive sponsor and the business/process owner, not filled in unilaterally by the learner.

Required Industry AI Project Charter fields
FieldWhat it covers
Problem statement / current workflow / baselineWhat the current state is and where the gap is: observable and checkable
Target outcome / success metricsMeasurable goals and success criteria, not the activity itself
AI role / human roleWhat AI recommends or executes, and what a human decides and verifies
Data/context, systems/integration, constraints, risksData, system integration, constraints, and risks
Pilot scope / estimated effort / Go-No-Go criteriaPilot scope, estimated effort, and the criteria for moving to the next stage

Info

Human, AI, Human: the sponsor and process owner confirm the problem and target; AI assists with analysis and recommendations during execution; the Go/No-Go decision and accountability stay with people.
  1. Pull together your AD 102/103 outputs
    Gather the already-prioritized use case, process map, and pain-point analysis: this is the charter's input, not something to redo.
  2. Fill in each required field
    Using the seven fields above, translate the AD 101-103 outputs into charter language: current state and gap, measurable targets, AI/human role split, data and constraints, pilot scope, and Go-No-Go criteria.
  3. Mark which fields need sponsor confirmation
    The charter is never filled in unilaterally; mark which fields must be confirmed jointly with the executive sponsor or process owner before they are final.
Check yourself

A learner in IL 101 Module 1 re-runs AD 103's use-case portfolio prioritization to double-check the ranking before writing the Project Charter. Which judgment is most correct?

A learner in IL 101 Module 1 re-runs AD 103's use-case portfolio prioritization to double-check the ranking before writing the Project Charter. Which judgment is most correct?

Key takeaway: A good project charter lets a sponsor decide whether the next stage is worth investing in, without needing to understand the technical details.

What next?