Situational Judgment Scenarios — Practice Set (10 Short Cases with Coaching Notes)

Scenario 1 — Delegation vs. Ownership

One of your direct reports, Maya, is capable but new to a recurring monthly report that requires cross-team coordination. She asks you to 'just handle the tough parts' because she is worried about deadlines. Your team is stretched but the organization expects leaders to develop successors.

1. Take over the difficult parts yourself to ensure the report is delivered on time.
2. Walk Maya through the tough parts step-by-step and let her do the work while you review before submission.
3. Assign the whole report to another experienced team member to keep things moving.
4. Postpone the report and inform stakeholders you'll reschedule until Maya feels ready.

Model answer: B

Why: Option B balances delivery responsibility and development. It supports Maya to stretch while keeping a safety net (review). Taking over creates dependency; reassigning prevents growth; postponing undermines stakeholder trust.

Coaching/reflection questions:

• What specific step is Maya most unsure about, and how could you make a short micro-teaching moment?
• How will you maintain quality without doing the work for her?
• What success criteria and timeline will you agree on now?

Scenario 2 — Performance Correction

Jordan has missed two deadlines and the quality of his deliverables has declined. When you raise it in a one-on-one, Jordan blames unclear priorities and asks for more time. Other teammates are affected by rework.

1. Document the performance issues and start a formal performance improvement plan (PIP).
2. Clarify priorities together, set a short-term improvement plan with check-ins, and remove or adjust nonessential tasks.
3. Publicly call out Jordan in the next team meeting to underscore expectations.
4. Ignore it for now; hope his performance rebounds once deadlines pass.

Model answer: B

Why: Option B addresses root causes (priorities, workload) and creates a short, supportive structure for improvement. A PIP may be appropriate later if there is no progress, but starting with coaching preserves trust and is proportional.

Coaching/reflection questions:

• How do you diagnose whether the issue is skills, motivation, or workload?
• What measurable, time-bound indicators will show improvement?
• How will you involve Jordan in designing the improvement steps so he owns them?

Scenario 3 — Conflict Between Peers

Two senior engineers are in repeated heated exchanges about an architectural choice. The tension is visible in email threads and slows delivery. Both are highly competent and hold different strong opinions.

1. Pick one architecture and direct them to implement it to end arguments.
2. Ask them each to present pros and cons in a short aligned decision meeting and decide using clear criteria and a timeline.
3. Let them keep arguing — their debate may eventually reveal the best solution.
4. Move both engineers to different projects to avoid further conflict.

Model answer: B

Why: Option B creates a structured forum to surface trade-offs, clarifies decision criteria, and produces a timely decision. Directing without buy-in risks passive resistance; avoidance wastes valuable perspectives; moving them undermines talent allocation.

Coaching/reflection questions:

• What decision criteria (cost, maintainability, time-to-market) matter most here?
• Who should be involved in the final decision and why?
• How will you document the decision so the team can move forward confidently?

Scenario 4 — Change Fatigue

Your organization is implementing multiple changes: a new tool, a reorg, and updated performance metrics. Team morale is low and several team members say they are overwhelmed.

1. Push harder — change takes energy and leaders must maintain momentum.
2. Pause new initiatives from your team and focus on communicating priorities and providing support for adoption.
3. Tell the team to accept change as part of work and keep expectations high.
4. Remove yourself from detailed change work and wait for senior leaders to resolve it.

Model answer: B

Why: Pausing nonessential initiatives and focusing on clear priorities reduces overload and builds trust. Momentum is important, but unchecked pace can erode capacity and performance.

Coaching/reflection questions:

• Which changes are critical and which can be delayed or simplified?
• What practical supports (training, protected time, temporary staffing) could lower friction?
• How will you surface team concerns without making them feel punished for speaking up?

Scenario 5 — Delegation Mismatch

You assigned a high-visibility task to a mid-level team member confident they could handle it. Midway through you discover they misinterpreted the scope and delivered an incomplete product to stakeholders.

1. Take back the task entirely and deliver it yourself to protect the relationship with stakeholders.
2. Hold a candid conversation with the team member about expectations, then coach them through revising and resubmitting quickly.
3. Blame the team member to make clear consequences for future mistakes.
4. Ignore it and hope stakeholders won't notice the gaps.

Model answer: B

Why: Option B preserves stakeholder trust while preserving the individual's development. Taking over undermines future growth; blame damages psychological safety; ignoring risks harm to relationships.

Coaching/reflection questions:

• At delegation time, what checks (milestones, acceptance criteria) should you have agreed on?
• How would you repair stakeholder trust while reinforcing learning for the team member?
• How might you redesign future delegations to balance autonomy and risk?

Scenario 6 — Bias in Promotion Decisions

An informal shortlist for promotion favors people who attended the same external networking events as the manager. A high-performing candidate from a different background is being overlooked.

1. Proceed with the informal shortlist to avoid disrupting the manager's plans.
2. Pause the process, review objective performance data and criteria, and ensure diverse perspectives are included in the decision panel.
3. Invite the overlooked candidate to a different role to keep them engaged but not promoted.
4. Ignore the pattern — politics happen in every organization.

Model answer: B

Why: Option B reduces bias by making criteria explicit and broadening decision inputs. This preserves fairness, talent retention, and organizational credibility.

Coaching/reflection questions:

• What objective criteria should promotion decisions use here?
• Who else should weigh in to reduce groupthink or affinity bias?
• How will you communicate decisions so people understand the rationale?

Scenario 7 — Urgent Crisis, Limited Info

A critical production incident threatens customer delivery. You have incomplete information and must choose a response quickly. Team members propose different fixes, each with uncertain downstream effects.

1. Pick one proposed fix immediately and direct the team to implement it.
2. Form a short, focused incident team to gather key facts in 15–30 minutes, decide on the safest reversible action, and communicate the plan.
3. Delay action until you have full certainty to avoid mistakes.
4. Escalate to senior leaders and wait for them to decide.

Model answer: B

Why: Option B balances speed and prudence: gather essential facts quickly, choose a reversible or low-risk action, and communicate. Immediate unilateral action risks avoidable harm; waiting for full certainty is impractical in crises.

Coaching/reflection questions:

• What are the minimum facts needed to decide within the time window?
• Which actions are reversible or contain risk most effectively?
• How will you capture lessons after the incident to improve future responses?

Scenario 8 — Micromanagement Tendency

Team members report you often check their work in detail and redo small parts without explaining the changes. Some are reluctant to make decisions independently.

1. Keep doing it — you care about quality and the team should meet your standards.
2. Discuss the feedback with the team, identify where standards are unclear, and agree on acceptance criteria and delegated decision boundaries.
3. Stop intervening entirely to prove trust, even if quality dips temporarily.
4. Tell the team they can do what they want but you will still review after the fact.

Model answer: B

Why: Option B addresses both the manager's quality concerns and the team's need for autonomy by clarifying standards and decision boundaries. Abruptly stopping or maintaining the same behavior won't solve the underlying misalignment.

Coaching/reflection questions:

• Where can you safely loosen control to develop capability?
• What acceptance criteria will give you confidence without constant oversight?
• How will you give feedback when standards aren't met while preserving psychological safety?

Scenario 9 — Rewarding the Right Behavior

A team member consistently hits individual targets by prioritizing short-term wins that create manual rework for others. Another teammate collaborates to create a reusable solution but misses a target this quarter.

1. Reward the high-performer who hit targets — numbers matter.
2. Recognize and reward the collaborator who built a reusable solution and adjust recognition criteria to value sustainable outcomes.
3. Give equal recognition to both to avoid conflict.
4. Avoid changing recognition — people know how to succeed around targets.

Model answer: B

Why: Option B aligns rewards with long-term team effectiveness. Incentives shape behavior; recognizing sustainable, collaborative work reduces harmful short-termism.

Coaching/reflection questions:

• How do current incentives create unintended behaviors?
• What recognition or goal adjustments would encourage durable solutions?
• How will you communicate changes so people see the logic and fairness?

Scenario 10 — When to Escalate

Your team is facing a contractual issue that could affect delivery and client relationships. You can attempt to resolve it directly, but the contract terms may require legal involvement.

1. Handle it yourself to keep the client relationship smooth and avoid creating red tape.
2. Consult legal or appropriate stakeholders early, while preparing a proposed client-facing solution to speed agreement.
3. Ignore the legal detail and focus on technical fixes first.
4. Escalate immediately to senior leadership without proposing options.

Model answer: B

Why: Option B balances speed with appropriate expertise. Early consultation avoids surprises and supports a client-friendly solution. Handling it alone risks contract violation; immediate escalation without options may slow resolution.

Coaching/reflection questions:

• What is the minimum consultation needed to avoid risk while keeping momentum?
• How will you present trade-offs to stakeholders clearly and quickly?
• What follow-up actions will prevent similar issues later?

Facilitation tips and variations

To deepen learning, try these facilitation moves:

• Ask participants to explain the trade-offs that led them to alternative answers.
• Run the same scenario after a month and compare answers to see growth in judgment.
• Encourage participants to convert coaching questions into short action commitments (e.g., 'I will add acceptance criteria to delegated tasks this week').
• Where appropriate, adapt scenarios to your organization's language, role levels, or sector-specific risks.

Next steps

Use these scenarios regularly to develop proportional responses, build coaching muscle, and reduce defaulting to a single leadership style. Consider pairing this practice set with real incident debriefs or one-on-one development plans to convert reflection into behavior change.