- Comfort with earlier modules in this track
- Ability to explain trade-offs and risks without jargon
- Explain target state in your own words and apply it to a realistic scenario.
- A target state is a shared picture of how the system should work, not a vendor shopping list.
- Check the assumption "Target is testable" and explain what changes if it is false.
- Check the assumption "Ownership is clear" and explain what changes if it is false.
- Solve a complex scenario with explicit assumptions and constraints
- Write one mitigation plan and one fallback plan
- A concise design or governance brief that can be reviewed by a team
- Vendor-first target state. If the target state is vendor-first, it will not survive constraint changes.
- No migration plan. Without a migration plan, the target state remains aspirational.