Your goal: take a troubled program from alarm to a decision: check the numbers,
stabilize, diagnose, bring options with numbers, and reset.
How this works (about 30 minutes)
- One main question with layered follow-ups, then a shorter second question.
- Ask Marcus for any facts you need; he answers in a line.
- A notepad sits beside the call for your numbers or plan. Tell Marcus when to look.
- No hints and no scores during the call. Your report comes after.
What scores well
- Checking what "25%" and "85%" really measure before reacting
- A forecast with numbers and what it assumes
- A root cause backed by evidence, not blame
- Options with costs, one recommendation, and the owner deciding
- A reset that would catch the next drift early
Tips
- Read the module reading first: Planning and Execution.
- Ask questions; strong candidates gather facts before solving.