Friction Audit
Point your Copilot at your inbox. Find where the team is slowing itself down.
What this does
This sequence asks Copilot to analyze your actual email threads and team communications to surface the sludge — the invisible friction that slows execution, creates rework, and erodes clarity across the HR matrix.
It maps directly to the five friction archetypes:
1. The Orphan Task — work stalls because ownership is assumed, not assigned
2. The Infinite Loop — decisions bounce back for "more alignment"
3. The Shadow Decision — someone bypasses the agreed process
4. The Courtesy Copy — CCs used for visibility, not action
5. The Waiting Game — work sits idle waiting for sign-off
This is not about individual blame. It is about seeing the patterns — the operating habits that create drag across the system.
The Sludge Detector
Act as an organizational psychologist specializing in matrix operating models and cross-functional HR teams. I want you to analyze my recent email threads for friction patterns.
LOOK AT: My last 15 email threads involving more than 2 people from different parts of the HR function (e.g., threads between HRBPs, CoEs, Country HR, People Services, or regional teams).
For each thread, identify:
1. Ownership clarity: Is it obvious who owns the outcome? Or does the thread drift without a clear "D" (decision-maker)?
2. Loop detection: Does the thread go back and forth more than 3 times without resolution? Is someone asking for "alignment" without specifying what aligned means?
3. CC inflation: Are people added mid-thread without a clear reason? Is the CC line growing as a substitute for trust?
4. Waiting patterns: Are there gaps of 48+ hours where the thread goes silent because someone is waiting for permission or sign-off?
5. Shadow decisions: Does the thread reference a decision that was already made elsewhere, or does someone introduce information that contradicts the thread's direction?
Classify each thread by which friction archetype it most resembles: Orphan Task, Infinite Loop, Shadow Decision, Courtesy Copy, or Waiting Game.
Do not give me solutions yet. Just show me the patterns. Where is the sludge?
Point Copilot at your inbox. It will find the patterns you have stopped noticing.
Act as an organizational psychologist specializing in matrix operating models and cross-functional HR teams. I want you to analyze my recent Teams conversations and group chats for friction patterns.
LOOK AT: My last 10 group conversations in Teams channels or group chats that involve cross-functional HR collaboration (e.g., project channels, regional HR channels, initiative-specific chats).
For each conversation, identify:
1. Ownership clarity: When a task or action is discussed, does someone explicitly own it? Or does the conversation end with "let's align" and no named owner?
2. Decision drift: Are decisions being made in the chat, or are they being deferred to "a call" or "a meeting" that may or may not happen?
3. Information hoarding: Is anyone asking questions that someone else in the chat could answer but doesn't? Are there long silences after direct questions?
4. Escalation patterns: Does the conversation escalate upward (tagging leaders) instead of resolving laterally?
5. Repetition: Are the same topics, questions, or status updates appearing across multiple threads or channels?
Classify each conversation by which friction archetype it most resembles: Orphan Task, Infinite Loop, Shadow Decision, Courtesy Copy, or Waiting Game.
Do not give me solutions yet. Just show me the patterns. Where is the sludge?
Let Copilot read your group chats. The sludge hides in the threads you have stopped reading.
Act as an organizational psychologist specializing in matrix operating models and cross-functional HR teams. I am going to describe how work typically flows through my team, and I want you to identify friction patterns.
HERE IS HOW WORK MOVES THROUGH MY TEAM:
[Describe your typical workflow here. For example: "When a business leader requests a new hire, it goes from the HRBP to the CoE for job architecture review, then to People Services for posting, then back to the HRBP for shortlisting, then to the hiring manager..." — describe 2-3 of your most common cross-functional workflows in as much detail as you can.]
ALSO CONSIDER:
• Who typically initiates work? Who gets pulled in later?
• Where do handoffs happen? What gets lost in the handoff?
• When a decision needs to be made, who makes it? Who gets consulted? Who finds out after the fact?
• Where does work stall most often? What is it usually waiting for?
• Are there things that get done twice by different people because ownership is unclear?
Based on my description, identify:
1. Ownership gaps: Where does the "D" (decision-maker) disappear or become ambiguous?
2. Unnecessary loops: Where is work bouncing back and forth that could be resolved in fewer steps?
3. Bottlenecks: Where does work queue up waiting for one person or one team?
4. Duplication: Where are multiple people doing the same thinking or the same work without knowing it?
5. Communication gaps: Where do people find out about decisions too late to influence them?
Classify each issue by which friction archetype it most resembles: Orphan Task, Infinite Loop, Shadow Decision, Courtesy Copy, or Waiting Game.
Do not give me solutions yet. Just show me the patterns. Where is the sludge?
No inbox access? No problem. Describe how work moves and Copilot will find the friction.
The Pattern Mirror
Based on the sludge you identified, now analyze my specific role in these patterns. I am part of a matrix HR team (HRBPs, CoEs, Country HR, People Services, regional teams). Look at my behaviour across these threads:
1. Am I creating orphan tasks? — Do I raise issues without assigning clear ownership? Do I forward threads without specifying who should act?
2. Am I feeding infinite loops? — Do I ask for "alignment" without defining what aligned looks like? Do I request input from people who don't need to be consulted?
3. Am I a shadow decision-maker? — Do I go around the agreed process? Do I ask the same question to multiple people hoping for a different answer?
4. Am I inflating the CC line? — Am I adding people for visibility rather than action? Am I using CC as a substitute for trust?
5. Am I the bottleneck? — Are threads waiting on me? Am I holding decisions that could be made closer to the work?
Be direct. Show me where I am part of the sludge, not just affected by it.
This is the mirror. It is not comfortable. That is the point.
The One Loop to Kill
Based on the patterns you found, identify the single highest-impact loop I can kill this week. The one that, if fixed, would create the most relief across the team.
For that one loop, give me:
1. The friction archetype it belongs to (Orphan Task, Infinite Loop, Shadow Decision, Courtesy Copy, or Waiting Game)
2. Who is affected — which roles or people in the matrix are being slowed down by this pattern?
3. What I should do differently starting Monday — one specific, concrete behaviour change. Not a process redesign. A habit shift.
4. The exact message I could send — draft a short message (email or Teams) that I could send to the relevant people to clarify ownership, kill the loop, or remove the unnecessary step. Make it direct, warm, and clear.
5. What "good" looks like in 2 weeks — how will I know the sludge is gone? What will the thread look like when this pattern is no longer active?
One loop. One week. One habit. That is how operating habits change.
The Team Sludge Report
Now zoom out. Looking across all the threads you analyzed, create a Team Sludge Report that I could share (anonymized) with my team. Structure it as:
HEADLINE: One sentence summarizing the dominant friction pattern across our team communications.
THE DATA:
• How many threads showed clear ownership vs. ambiguous ownership?
• How many threads resolved in under 3 exchanges vs. those that looped 5+ times?
• How many people were CC'd on average vs. how many actually took action?
• Average time from "request made" to "decision confirmed"?
THE QUESTION FOR THE TEAM: Based on this data, write one provocative question I could pose to the team that would open a conversation about our operating habits without pointing fingers.
THE COMMITMENT: Suggest a single team norm we could trial for 2 weeks that would directly address the dominant pattern.
Share the patterns, not the blame. The system creates the sludge. The team can choose to clear it.
The sludge is in the threads you have stopped reading.
Point Copilot at your inbox. Run this sequence once a month. Watch the patterns shift.
Friction is not always bad. Sludge always is. Know the difference.