Performance Conversation Framework
Use it when...
Use when: a leader sees a performance pattern and wants a conversation that builds the person's ability to self-correct.
What this is
A six-step conversation structure the book calls "a comprehensive approach for coaching without micromanaging." It treats a performance discussion as a developmental partnership: observation, impact, context, capability, system, partnership. The book contrasts it with a fix-it approach: identify the problem, tell them what to do differently, follow up to ensure compliance.
Use when / Do not use when
Use when: a leader sees a performance pattern and wants a conversation that builds the person's ability to self-correct. Natural companion to the Capability-System Diagnostic (a Coaching OS tool), which supplies the content for steps 3-5. Do not use when (addition): the leader has not yet identified a specific pattern and situation to put into step 1.
| # | Step | Script or prompt (verbatim) | Book's note |
|---|---|---|---|
| 1 | Observation Without Judgment | "I've noticed [specific pattern] when [specific situation]." | Descriptive rather than evaluative; creates shared understanding without triggering defensive responses. |
| 2 | Impact Reflection | "This appears to be creating [specific impacts] for [specific stakeholders]." | Focuses on effects rather than intentions; connects patterns to consequences without assuming motives. |
| 3 | Context Exploration | "What factors seem to be influencing this pattern? What makes it easier or harder to be effective?" | Treats context as relevant rather than an excuse; performance emerges from the interaction between individual and environment. |
| 4 | Capability Clarification | "What skills, knowledge, or mindsets seem most relevant to this situation? Where do you feel most confident or most challenged?" | Treats capability as developmental rather than fixed; growth-oriented rather than judgment-oriented. |
| 5 | System Consideration | "How do our current systems support or hinder effectiveness? What small adjustments might make a significant difference?" | Treats systems as malleable; shared responsibility for enabling conditions rather than all on the individual. |
| 6 | Development Partnership | "How might we work together to strengthen these patterns? What support would be most valuable?" | Collaborative rather than directive; the person is an active architect of their own development. |
Book's quote from a leader who adopted it: "I used to approach performance issues with a fix-it mentality - identify the problem, tell them what to do differently, follow up to ensure compliance. Now I approach these conversations as a partnership to understand patterns, impacts, context, capabilities, and systems. We develop solutions together rather than me imposing them. The result isn't just better performance - it's stronger capability to self-correct and continuously improve."
Book's stated goal: "The goal isn't controlling behavior through surveillance and direction. It's building the insight and capability that enable people to manage their own performance effectively."
How to run it (Performance Lab suggested practice)
- Before the conversation, fill step 1 and step 2 with real content: the pattern, the situation, the impact, the stakeholders. Check that step 1 is a description, not a judgment.
- Run steps 3-6 as questions. Write down what the person says; do not supply the answers.
- If steps 3-5 show a system factor, use the Capability-System Diagnostic to separate capability from system before agreeing actions.
- End with one agreed support action and one named follow-up.
Record sheet (Performance Lab suggested practice)
- Pattern / situation:
- Impact / stakeholders:
- Context factors (their words):
- Capability: confident / challenged:
- System adjustments proposed:
- Support agreed / follow-up:
From Performance Is Personal by Chad T. Dyar, Ch.8.