Situation-Behavior-Impact

Full Markdown demo

# SBI: Review-Meeting Feedback

## Input Summary
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Classic Case Context
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Skill Used
- Situation-Behavior-Impact
- Give feedback with concrete context, observed behavior, and impact.
- Best for: Manager feedback, peer conversations, leadership, and tense moments.
- Can generate: Feedback script, observable facts, impact statement, and follow-up ask.

## Situation Judgment
A senior engineer repeatedly interrupts PMs; junior PMs are now quiet, but his technical judgment remains important.

## Executive Summary
The feedback should not evaluate personality. It should name the meeting situation, describe observable behavior, explain impact on discussion quality, and make a testable ask for the next review.

## Framework Analysis
| SBI block | Speakable script |
| --- | --- |
| Situation | In the last three PRD reviews, especially Tuesday's permissions discussion |
| Behavior | You said 'this requirement is pointless' before the PM finished the context |
| Impact | Junior PMs spoke less, and we lost the full user background |
| Ask | Next time, ask two clarifying questions before giving the technical judgment |

## Reusable Diagram
This is a Markdown-only output. Switch to diagram or PDF-ready output to generate Mermaid.

## Recommendation
Have a private 15-minute conversation. Acknowledge the value of his technical judgment, then set a clear meeting behavior boundary. Make the ask observable: questions before judgment.

## Risks And Unknowns
- If the feedback becomes 'you are too aggressive,' defensiveness rises.
- If the PMs are reassured but the meeting behavior is not addressed, silence continues.

## Next Actions
1. Schedule a private conversation.
2. Prepare one specific example and one specific ask.
3. Debrief the next review for five minutes.

Full Markdown demo

# SBI: Review-Meeting Feedback

## Input Summary
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Classic Case Context
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Skill Used
- Situation-Behavior-Impact
- Give feedback with concrete context, observed behavior, and impact.
- Best for: Manager feedback, peer conversations, leadership, and tense moments.
- Can generate: Feedback script, observable facts, impact statement, and follow-up ask.

## Situation Judgment
A senior engineer repeatedly interrupts PMs; junior PMs are now quiet, but his technical judgment remains important.

## Executive Summary
The feedback should not evaluate personality. It should name the meeting situation, describe observable behavior, explain impact on discussion quality, and make a testable ask for the next review.

## Framework Analysis
| SBI block | Speakable script |
| --- | --- |
| Situation | In the last three PRD reviews, especially Tuesday's permissions discussion |
| Behavior | You said 'this requirement is pointless' before the PM finished the context |
| Impact | Junior PMs spoke less, and we lost the full user background |
| Ask | Next time, ask two clarifying questions before giving the technical judgment |

## Reusable Diagram
```mermaid
sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager->>Engineer: Name the specific review situation
  Manager->>Engineer: Describe observable interruption behavior
  Manager->>Engineer: Explain impact on PM participation
  Engineer-->>Manager: Shares intent or concern
  Manager->>Engineer: Ask for two clarifying questions before judgment
  Team-->>Manager: Next review shows more complete context
```

## Recommendation
Have a private 15-minute conversation. Acknowledge the value of his technical judgment, then set a clear meeting behavior boundary. Make the ask observable: questions before judgment.

## Risks And Unknowns
- If the feedback becomes 'you are too aggressive,' defensiveness rises.
- If the PMs are reassured but the meeting behavior is not addressed, silence continues.

## Next Actions
1. Schedule a private conversation.
2. Prepare one specific example and one specific ask.
3. Debrief the next review for five minutes.

Mermaid demo

sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager->>Engineer: Name the specific review situation
  Manager->>Engineer: Describe observable interruption behavior
  Manager->>Engineer: Explain impact on PM participation
  Engineer-->>Manager: Shares intent or concern
  Manager->>Engineer: Ask for two clarifying questions before judgment
  Team-->>Manager: Next review shows more complete context

Full Markdown demo

# SBI: Review-Meeting Feedback

## Input Summary
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Classic Case Context
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Skill Used
- Situation-Behavior-Impact
- Give feedback with concrete context, observed behavior, and impact.
- Best for: Manager feedback, peer conversations, leadership, and tense moments.
- Can generate: Feedback script, observable facts, impact statement, and follow-up ask.

## Situation Judgment
A senior engineer repeatedly interrupts PMs; junior PMs are now quiet, but his technical judgment remains important.

## Executive Summary
The feedback should not evaluate personality. It should name the meeting situation, describe observable behavior, explain impact on discussion quality, and make a testable ask for the next review.

## Framework Analysis
| SBI block | Speakable script |
| --- | --- |
| Situation | In the last three PRD reviews, especially Tuesday's permissions discussion |
| Behavior | You said 'this requirement is pointless' before the PM finished the context |
| Impact | Junior PMs spoke less, and we lost the full user background |
| Ask | Next time, ask two clarifying questions before giving the technical judgment |

## Reusable Diagram
```mermaid
sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager->>Engineer: Name the specific review situation
  Manager->>Engineer: Describe observable interruption behavior
  Manager->>Engineer: Explain impact on PM participation
  Engineer-->>Manager: Shares intent or concern
  Manager->>Engineer: Ask for two clarifying questions before judgment
  Team-->>Manager: Next review shows more complete context
```

## Recommendation
Have a private 15-minute conversation. Acknowledge the value of his technical judgment, then set a clear meeting behavior boundary. Make the ask observable: questions before judgment.

## Risks And Unknowns
- If the feedback becomes 'you are too aggressive,' defensiveness rises.
- If the PMs are reassured but the meeting behavior is not addressed, silence continues.

## Next Actions
1. Schedule a private conversation.
2. Prepare one specific example and one specific ask.
3. Debrief the next review for five minutes.

Mermaid demo

sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager->>Engineer: Name the specific review situation
  Manager->>Engineer: Describe observable interruption behavior
  Manager->>Engineer: Explain impact on PM participation
  Engineer-->>Manager: Shares intent or concern
  Manager->>Engineer: Ask for two clarifying questions before judgment
  Team-->>Manager: Next review shows more complete context

PDF-ready HTML demo

<!doctype html>
<html>
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>SBI: Review-Meeting Feedback</title>
  <style>
    body { font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; margin: 48px; color: #161a1d; line-height: 1.6; background: #fbfcf8; }
    h1 { font-size: 34px; line-height: 1.1; margin: 0 0 18px; }
    h2 { font-size: 20px; margin-top: 28px; }
    pre { white-space: pre-wrap; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 18px; overflow-wrap: anywhere; }
    .meta { color: #2563eb; font-size: 12px; text-transform: uppercase; font-weight: 800; letter-spacing: .08em; }
    .sheet { max-width: 940px; margin: 0 auto; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 32px; }
    @media print { body { margin: 18px; background: #fff; } .sheet { max-width: none; border: 0; padding: 0; } }
  </style>
</head>
<body>
  <main class="sheet">
    <p class="meta">ThinkOps AI PDF-ready output</p>
    <h1>SBI: Review-Meeting Feedback</h1>
    <pre># SBI: Review-Meeting Feedback

## Input Summary
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Classic Case Context
A senior engineer has interrupted PMs three times in PRD reviews and said, 'This requirement is pointless.' His technical judgment is valuable, but junior PMs are now quiet and the meetings feel tense. Use Situation-Behavior-Impact to write a direct feedback script, likely responses, and a follow-up ask.

## Skill Used
- Situation-Behavior-Impact
- Give feedback with concrete context, observed behavior, and impact.
- Best for: Manager feedback, peer conversations, leadership, and tense moments.
- Can generate: Feedback script, observable facts, impact statement, and follow-up ask.

## Situation Judgment
A senior engineer repeatedly interrupts PMs; junior PMs are now quiet, but his technical judgment remains important.

## Executive Summary
The feedback should not evaluate personality. It should name the meeting situation, describe observable behavior, explain impact on discussion quality, and make a testable ask for the next review.

## Framework Analysis
| SBI block | Speakable script |
| --- | --- |
| Situation | In the last three PRD reviews, especially Tuesday's permissions discussion |
| Behavior | You said 'this requirement is pointless' before the PM finished the context |
| Impact | Junior PMs spoke less, and we lost the full user background |
| Ask | Next time, ask two clarifying questions before giving the technical judgment |

## Reusable Diagram
```mermaid
sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager-&gt;&gt;Engineer: Name the specific review situation
  Manager-&gt;&gt;Engineer: Describe observable interruption behavior
  Manager-&gt;&gt;Engineer: Explain impact on PM participation
  Engineer--&gt;&gt;Manager: Shares intent or concern
  Manager-&gt;&gt;Engineer: Ask for two clarifying questions before judgment
  Team--&gt;&gt;Manager: Next review shows more complete context
```

## Recommendation
Have a private 15-minute conversation. Acknowledge the value of his technical judgment, then set a clear meeting behavior boundary. Make the ask observable: questions before judgment.

## Risks And Unknowns
- If the feedback becomes 'you are too aggressive,' defensiveness rises.
- If the PMs are reassured but the meeting behavior is not addressed, silence continues.

## Next Actions
1. Schedule a private conversation.
2. Prepare one specific example and one specific ask.
3. Debrief the next review for five minutes.
</pre>
    <h2>Mermaid diagram source</h2><pre>sequenceDiagram
  participant Manager as Manager
  participant Engineer as Senior engineer
  participant Team as Review team
  Manager-&gt;&gt;Engineer: Name the specific review situation
  Manager-&gt;&gt;Engineer: Describe observable interruption behavior
  Manager-&gt;&gt;Engineer: Explain impact on PM participation
  Engineer--&gt;&gt;Manager: Shares intent or concern
  Manager-&gt;&gt;Engineer: Ask for two clarifying questions before judgment
  Team--&gt;&gt;Manager: Next review shows more complete context</pre>
  </main>
</body>
</html>