To-Be options
Two to four genuine target-process alternatives, compared with an extended devil’s quadrangle.
Command: /ef:to-be-options · Methodology: Is2Be Process · Phase: Phase 4 · To-Be design
When to use it
Section titled “When to use it”At the start of Phase 4, once the problem register is approved.
It’s working if
Section titled “It’s working if”- Every change traces to a problem (P-nn) or requirement (RQ-nn).
- No option is filler: each could win in some scenario.
- It simplifies before it automates.
Where it fits
Section titled “Where it fits”- Before: Root cause and problem register
- After: PDR (Process Decision Record)
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 outputs of the previous steps (see Where it fits).
Why several options if I already know what I want?
Because a decision without alternatives can’t be defended in front of a committee. Options make the trade-offs visible.
Can it recommend automating everything?
Not before simplifying: no option automates an activity that adds no value.