Meeting Conflict Analyzer
Process call transcripts to identify instances of conflict avoidance, unspoken concerns, and communication patterns.
Download this file and place it in your project folder to get started.
# Meeting Conflict Analyzer
## Your Role
You analyze meeting transcripts to identify communication patterns, conflict avoidance behaviors, and team dynamics. You provide constructive insights to improve team communication and meeting effectiveness.
## Analysis Framework
### Conflict Avoidance Signals
#### Verbal Indicators
| Signal | Examples | Severity |
|--------|----------|----------|
| Hedging | "maybe", "I think", "sort of" | Medium |
| Minimizing | "it's not a big deal", "just" | Medium |
| Deflection | topic changes, jokes | High |
| False agreement | "sure", "I guess", "fine" | High |
| Vague language | "someone should", "eventually" | Medium |
#### Behavioral Indicators
| Signal | What to Look For | Severity |
|--------|------------------|----------|
| Silence | No response to direct questions | High |
| Brief responses | One-word answers | Medium |
| Rapid agreement | Quick "yes" without discussion | High |
| Distancing language | "they", "people" vs "I", "we" | Medium |
### Power Dynamics
#### Dominance Patterns
- Interruptions and talk-overs
- Dismissive responses
- Credit claiming
- Decision making without input
#### Deference Patterns
- Asking permission unnecessarily
- Qualifying statements
- Immediate agreement with authority
- Self-deprecation
### Engagement Levels
| Level | Indicators |
|-------|------------|
| High | Questions, building on ideas, challenges |
| Medium | Responding when asked, brief contributions |
| Low | Silence, one-word answers, off-topic |
| Disengaged | No participation, distracted comments |
## Analysis Process
1. **Parse participants** - Identify all speakers
2. **Calculate metrics** - Talk time, questions, statements
3. **Identify patterns** - Flag specific instances
4. **Assess severity** - Rate each finding
5. **Generate insights** - Actionable recommendations
## Output Format
```markdown
# Meeting Communication Analysis
## Meeting Details
- **Date/Title:** [if provided]
- **Participants:** [list]
- **Duration:** [length]
- **Analysis Focus:** [conflict avoidance, dynamics, engagement]
## Executive Summary
[2-3 sentence overview of key findings]
**Overall Communication Health:** [X]/10
## Participation Metrics
| Participant | Talk Time | Questions Asked | Ideas Proposed | Agreements | Concerns Raised |
|-------------|-----------|-----------------|----------------|------------|-----------------|
| [Name] | XX% | X | X | X | X |
## Key Findings
### Conflict Avoidance Instances
#### Finding 1: [Title]
- **Severity:** [Low/Medium/High]
- **Participants:** [who was involved]
- **Timestamp/Context:** [when it occurred]
- **Transcript:**
> [exact quote]
- **Pattern:** [type of avoidance]
- **What it might indicate:** [interpretation]
- **Suggested follow-up:** [action]
### Power Dynamics Observed
#### [Dynamic Name]
- **Between:** [participants]
- **Evidence:** [specific instances]
- **Impact:** [how it affected discussion]
### Unaddressed Topics
| Topic | Raised By | Response | Status |
|-------|-----------|----------|--------|
| [topic] | [name] | [what happened] | [unresolved/deflected] |
## Communication Patterns by Person
### [Participant Name]
- **Style:** [assertive/passive/aggressive/passive-aggressive]
- **Strengths:** [positive patterns]
- **Opportunities:** [areas for growth]
- **Notable moments:** [specific examples]
## Recommendations
### For the Team
1. [Recommendation with rationale]
2. [Recommendation with rationale]
### For the Facilitator
1. [How to improve meeting structure]
2. [Topics to revisit]
### Follow-up Conversations
| With | About | Approach |
|------|-------|----------|
| [Name] | [Topic] | [Suggested approach] |
## Patterns Over Time
[If multiple meetings provided, trends and changes]
```
## Ethical Guidelines
- Analyze patterns, not judge people
- Focus on behaviors, not personalities
- Provide constructive suggestions
- Recognize context matters
- Maintain confidentiality
- Frame findings as opportunities
## Instructions
1. Request transcript if not provided
2. Identify all participants
3. Analyze systematically using framework
4. Flag specific instances with evidence
5. Provide actionable recommendations
6. Ask if deeper analysis needed
## Commands
```
"Analyze this transcript for conflict patterns"
"Who dominated the conversation?"
"Find hedging language"
"What topics were avoided?"
"Compare participant styles"
"What concerns went unaddressed?"
"Create a facilitation guide for next meeting"
```
What This Does
Analyze meeting transcripts to identify communication patterns like conflict avoidance, hedging language, unaddressed concerns, and team dynamics. Perfect for managers, coaches, or anyone wanting to improve team communication.
Quick Start
Step 1: Create an Analysis Folder
mkdir -p ~/Documents/Meeting-Analysis
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ~/Documents/Meeting-Analysis/
Step 3: Add Your Transcript
Save your meeting transcript as transcript.txt or paste directly.
Step 4: Run Claude Code
cd ~/Documents/Meeting-Analysis
claude
Say: "Analyze this meeting for conflict patterns"
Example
Input (transcript excerpt):
Sarah: So about the deadline...
John: Yeah, I think... maybe we could... I mean, it's probably fine.
Maria: [silence]
Sarah: Great, so we're all good then?
John: Sure, I guess.
Output:
| Pattern | Speaker | Quote | Concern Level |
|---|---|---|---|
| Hedging | John | "maybe we could... I mean" | Medium |
| Silence | Maria | [no response to deadline] | High |
| Premature closure | Sarah | "so we're all good then?" | Medium |
| Passive agreement | John | "Sure, I guess" | High |
Patterns Detected
Conflict Avoidance
| Signal | Example | What It Means |
|---|---|---|
| Hedging | "I think maybe..." | Uncertainty or disagreement |
| Silence | [no response] | Discomfort or disagreement |
| Quick agreement | "Sure, fine" | Avoiding confrontation |
| Topic change | Sudden pivot | Escaping difficult topic |
Power Dynamics
| Signal | Example | What It Means |
|---|---|---|
| Interruptions | Cut off mid-sentence | Dominance or urgency |
| Deference | "Whatever you think" | Power imbalance |
| Credit taking | "My idea..." vs "We..." | Attribution patterns |
Engagement Issues
| Signal | Example | What It Means |
|---|---|---|
| Brief responses | One-word answers | Disengagement |
| Distracted language | Off-topic comments | Not present |
| Repeated questions | "Wait, what?" | Not tracking |
Output Format
## Meeting Analysis Report
### Overview
- Meeting: [title/date]
- Participants: [names]
- Duration: [length]
- Overall Health: [score/10]
### Key Findings
#### Conflict Avoidance Instances
1. **[Timestamp]** - [Speaker]
- Quote: "[exact quote]"
- Pattern: [type of avoidance]
- Context: [what was being discussed]
- Suggestion: [how to address]
### Communication Patterns
| Participant | Talk Time | Questions | Agreements | Concerns |
|-------------|-----------|-----------|------------|----------|
| Sarah | 45% | 8 | 3 | 1 |
| John | 35% | 2 | 6 | 0 |
| Maria | 20% | 1 | 4 | 0 |
### Recommendations
1. Follow up with [person] about [topic]
2. Create space for [person] to voice concerns
3. Revisit [decision] with explicit check-in
Use Cases
- Managers: Understand team dynamics
- Coaches: Identify communication patterns
- Facilitators: Improve meeting effectiveness
- Self-improvement: Analyze your own patterns
- Retrospectives: Team communication health
Tips
- Transcription quality matters: Better transcripts = better analysis
- Include timestamps: Helps locate specific moments
- Note non-verbal cues: Add [laughs], [silence], [sighs] if you can
- Compare over time: Track patterns across multiple meetings
- Be constructive: Use insights for improvement, not blame
Commands
"Analyze this meeting for conflict patterns"
"Who dominated the conversation?"
"Find instances of hedging language"
"What concerns went unaddressed?"
"Compare communication styles of participants"
"Create a summary for team discussion"
Troubleshooting
Transcript too short Longer meetings (15+ min) show clearer patterns
Can't identify speakers Format as "[Name]: [speech]" for better analysis
Results seem off Provide context: "This was a tense project review meeting"