Process charter
Turns the sponsor’s request into the initiative’s contract: goal, scope, KPIs, roles and risks.
Command: /ef:process-charter · Methodology: Is2Be Process · Phase: Phase 1 · Identification
When to use it
Section titled “When to use it”At the start of any process initiative, before gathering evidence or designing anything.
It’s working if
Section titled “It’s working if”- Goals are SMART and every KPI has a baseline or a way to measure it.
- Whatever the brief doesn’t say shows up as an assumption [SUP-nn], not as a fact.
- It ends with concrete questions for the sponsor, resolved at the phase gate.
Where it fits
Section titled “Where it fits”- Before: It’s the first step.
- After: SIPOC
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/ef:setup. -
The team’s inputs: what this step transforms.
What if I barely have a brief?
Ask it to interview you. It asks one question at a time, each with a recommended answer, until the essentials are covered; anything left unanswered becomes an assumption.
What if the sponsor gives no figures?
The charter doesn’t invent them: it lays out the goal’s structure and marks values as assumptions [SUP-nn], which become questions for the phase gate.
Can I change the scope later?
Yes, but not quietly: update the charter and record the change in a PDR.