Handle Stakeholder Disagreement During an Incident Tabletop

A tabletop can expose disagreement between security, technology, legal, and business teams. That tension is useful when it reveals an unclear decision right. An MDR consultant should not choose a winner or present a scenario answer as policy. Their role is to help the customer identify the question that requires ownership.

Ask which decision produced different expectations and who has authority to resolve it outside the exercise. Then ask what evidence or policy the stakeholders need before agreeing. This moves the group toward an accountable next action.

At a fictional online retailer, security may want to isolate a service quickly while operations worries about a peak sales period. The consultant can capture the trigger, decision owners, and communications path. The customer determines the final policy and any production action.

Do not diagnose an active incident or recommend actions beyond the information provided. A tabletop is a planning exercise. Keep confidential scenario detail with the customer and state when legal or executive approval is required.

Have two peers disagree about whether to notify leadership immediately. The consultant should summarize both concerns, ask who owns the decision, and propose a documented question for the responsible leader. They should not rush to resolve the scenario.

DealSpeak coaching can score neutral listening, clear recap, and ownership. A strong tabletop follow-up lists the disagreement, policy owner, expected evidence, and review date so the exercise produces an operational improvement. Customer teams can use this record to prepare the next review with shared facts.