COIN Model: Context, Observation, Impact, Next Steps
The COIN Model helps you give feedback as Context, Observation, Impact, and Next Steps, so the other person hears why you are talking, what you saw, what it did, and what you will do next together.
Framework Card
- Name:
- COIN Model
- Goal:
- Structure a feedback conversation as Context, Observation, Impact, and Next Steps so the talk stays factual and ends on a joint next move.
- Flow:
- Context → Observation → Impact → Next Steps
- Best For:
- Giving developmental feedback without a character verdict; Review comments that need an observable event and a next action; Team check-ins about a specific behavior or process
Why it matters
Feedback often fails in the same two ways. It sounds like a verdict ("you are careless") or it never becomes a next action ("please do better"). The listener then argues the label, or nods and nothing changes.
That matters in a 1:1, a review, or a peer conversation after a client meeting. The other person cannot work with a mood. They can work with a scene, a checkable event, a work consequence, and a question about what happens after this talk.
COIN is a way to put those four pieces in order. It is not a promise that the conversation will feel easy.
What it is
COIN is a four-beat structure for giving feedback:
| Beat | Job |
|---|---|
| Context | Why this conversation is happening, and when |
| Observation | What you saw or heard, without reading motive |
| Impact | What that did to the work, the team, the client, or the goal |
| Next Steps | A joint ask or plan for what happens next |
The letters are teaching shorthand. The method is the order: reason to talk, fact, consequence, next move. COIN does not start with a feeling (that is FFC). It does not stop at impact (that is SBI). It does not sort criticism you just received (that is FIRE).
Next Steps is collaborative on purpose. A command that the other person did not help shape is still a next action, but it is not using the last beat as designed.
How it works
A useful COIN pass is a conversation in four beats, not a poster of four letters.
1. Context
Say why you are talking, and point to a real scene: yesterday's client meeting, this week's standup, the last three report due dates. Two sentences is often enough. If the other person still does not know why this is a conversation, add the reason. If they already know, stop.
2. Observation
State what can be checked. "Three reports landed after the date we had agreed." Not "you do not care about quality." If you did not see it, say you heard it from a named source, or do not use COIN yet.
3. Impact
Connect the observation to work: delay, rework, a client who stopped talking, a teammate who waited. Impact is a consequence, not a personality theory.
4. Next Steps
Ask what would make the next instance different, and whether support is needed. Offer a specific option if you have one, then leave room for theirs. Do not skip this beat, and do not fill it with a lecture.
Review the four beats by weight. If Context is a speech and Next Steps is a slogan, cut the scene and write a real ask.
How it compares
When another lens fits better, or when you need a complementary view, these methods do different jobs. They are not interchangeable labels for "feedback."
Related communication lenses
| Framework | What it helps you see | How it differs from COIN |
|---|---|---|
| SBI Model | Situation, Behavior, Impact | Three-part fact message. No required Next Steps conversation. |
| FFC Technique | Feeling, Fact, Comparison | Starts with a feeling and a standard. COIN starts with context and ends on a next move. |
| FIRE Model | Facts, Interpretations, Reactions, Ends | For processing criticism you received. COIN is for delivering a message. |
COIN is the lens for a feedback talk that must include a joint next step. Other methods help when the job is a three-part fact message, a feeling-plus-bar comment, or sorting incoming criticism.
When to Use This Framework
- Developmental feedback. A missed handoff, a repeated interruption, or a strong piece of work that should be named with the same four beats.
- Performance-review comments. You need one incident that is specific enough to act on, not a year of adjectives.
- Team check-ins. A process or behavior is affecting the group, and the talk should end on a change, not a vent.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: Reports that keep arriving late
Context. I want to talk about the last sprint's reporting dates, because they affect the client send.
Observation. Three of the four weekly reports landed two or more days after the date we had on the board.
Impact. Engineering waited to start the next slice. The client got a compressed review window.
Next Steps. What would make the next three reports hit the date? Do you need a different cut-off from design, or a shorter template?
Implication: COIN made the event and the next move visible. It did not prove the person is "unreliable." It showed one pattern and asked for a plan.
Example: Interruptions in a client meeting
Context. After yesterday's client walkthrough.
Observation. You spoke over the client three times while they were still finishing a question.
Impact. They shortened their answers. We left without the constraint they had started to name.
Next Steps. Next time, can we let them finish, then you take the technical follow-up? If you need a signal from me, we can agree on one.
Implication: Same four beats. Observation is countable. Next Steps is a working agreement, not a character fix.
Takeaway
What COIN can help with
- Making one feedback conversation evaluable in order
- Separating the reason to talk, the fact, the work effect, and the next move
- Catching comments that skip to a verdict or never ask what happens next
What COIN cannot replace
- Situation, Behavior, Impact. SBI names a scene, an action, and an effect. It does not require a joint next-step beat. Use SBI when the job is a three-part fact message.
- Feeling, Fact, Comparison. FFC starts with a speaker-owned feeling and a bar. COIN starts with context and ends on next steps.
- Receiving criticism. FIRE separates facts, interpretations, reactions, and ends when you are the one who was evaluated. COIN is for giving the message.
- A care-and-challenge stance. Radical Candor is about whether you care and whether you challenge. It is not a four-beat script.
- Mediation or a formal performance plan. COIN structures one talk. It does not replace HR process or a third-party facilitator.
Honest scope: COIN structures giving feedback so facts and a next move are visible. It does not replace the methods above, and it should not be sold as guaranteed constructive outcomes.
Frequently asked questions
No. SBI is Situation, Behavior, and Impact. COIN adds an explicit Context beat and an explicit Next Steps beat. The method difference is the next-step conversation, not a ranking of which acronym is fuller.
Yes. The same four beats work when the observation is something you want repeated. Next Steps can be "keep this pattern on the next launch" rather than a fix.
Ask. Next Steps can be a genuine question about support, sequencing, or a smaller checkpoint. Inventing a plan the other person cannot own is not the last beat.
FIRE is for the person receiving evaluation: separate what happened from the story, the feeling, and the goal that feeling is pulling toward. COIN is for the person giving the message.
The teaching order is Context, Observation, Impact, Next Steps. If you skip Context, the other person may not know why they are in the room. If you skip Next Steps, you have something closer to SBI.