Leadership-Team Accountability Conversation Guide

The problem to solve

Accountability conversations become personal when the group begins with who failed rather than what the work required. That pattern creates defensiveness and leaves the operating condition unchanged.

A better conversation examines the work, expected outcome, decision right, interfaces, and proof signals before discussing individual action.

The Work & Theory principle

Make the invisible explicit. Accountability is clearest when the organization has named the expected outcome, authority, dependency, and feedback loop around a piece of work.

Diagnostic questions

Bring one recent example to the meeting.

• What was supposed to happen?
• What actually happened, and what was the impact?
• Who owned the outcome and which decision?
• What authority or information was missing?
• Where did the interface fail?
• What agreement would make the next cycle clearer?

Practical next actions

Use a 30-minute format: five minutes to name the work and outcome, ten to reconstruct the interface, ten to agree the accountable owner and authority, and five to set the proof signal and review date.

End with a written agreement. Avoid assigning motives. If the same tension persists, revisit the role or workflow design rather than repeating the conversation.

Related artifact and pathway

Capture the agreement in the Organization Blueprint or a relevant Performance Contract. The guide is most useful when leaders are willing to test one operating change and review its effect.