Case 01
Difficult Conversation
A management decision simulation
Monday · 09:00
- Today is Monday, 09:00. You manage a six-person team working on Project Atlas. Final delivery is this Thursday at 16:00.
- Sara has missed two agreed dates. Her work is usually good.
- The Product team is waiting for Sara's work before it can continue its part of the project.
- Your manager wants an update before 17:00.
- You also have a hiring meeting at 10:30, a budget decision at 13:00, and a leadership meeting at 16:00.
- You do not yet know why the first date slipped. This simulation covers Monday only: today's decisions shape the plan for Thursday, but you will not play through final delivery.
Your objective
Talk about the two delays, understand the cause, and reach a practical agreement with Sara. Your scenario score is out of 10: clarify the problem (2), understand the cause (3), agree the work (3), and plan follow-up (2). Other meetings affect the day but do not earn conversation points.
About this simulation
This is a fictional practice scenario. Its 10-point rubric is a design rule for this exercise, not a validated assessment of management ability. One action can satisfy several explicitly listed criteria; there is no personality score. It sits beside the essay on why difficult conversations get delayed: the cause is not assumed before the person gives an account. The ICF stance and the HBR essays are context, not proof of a result. Choice details are not sent or saved; only general usage events are recorded. Times and the project name are there so the day can be played.
Why We Delay Difficult ConversationsDesign context and sources
Management simulations inform time costs, delayed consequences and path-dependent decisions. These sources do not validate this game's outcomes or effectiveness.
DCS-v5.1