conflict-resolution-email

name	conflict-resolution-email
description	Writes professional emails that address workplace conflicts, disagreements, and difficult conversations with empathy, clarity, and constructive framing to reach resolution. Use when the user needs to address a disagreement, miscommunication, or interpersonal issue via email. Do NOT use for formal complaints (use `business-letter`), performance issues (use `pip-writing`), or rejection communications (use `rejection-letter`).
license	Apache-2.0
metadata	{"author":"foundry-skills","version":"1.0.0","tags":"email writing relationships","category":"writing","subcategory":"business-writing","depends":"","disclaimer":"none","difficulty":"advanced"}

Conflict Resolution Email Writing

When to Use

Use this skill when the user's goal is to preserve or repair a professional relationship, address a specific incident or pattern of behavior, or reach a concrete resolution through written communication.

Trigger scenarios:

• A colleague misattributed work, ignored a request, or undermined the user in a meeting and the user needs to address it without destroying the relationship
• The user received a hostile, passive-aggressive, or unfair email and needs to craft a response that de-escalates rather than retaliates
• A cross-functional partner or vendor has not delivered on a commitment and the user needs to address the gap without blaming or burning the bridge
• A peer or stakeholder has been communicating in ways that feel disrespectful, dismissive, or exclusionary and the user wants to name it clearly but professionally
• The user is heading into a difficult working relationship and wants to proactively address a simmering tension before it becomes a full breakdown
• The user made a mistake that affected a colleague and needs to address it with genuine accountability rather than a defensive explanation
• A recurring miscommunication between teams needs to be named and structured toward a systemic fix

Do NOT use this skill when:

• The user needs to file a formal HR complaint or grievance -- use business-letter for documented formal complaints
• The issue involves a performance problem requiring a documented improvement track -- use pip-writing
• The user needs to decline, reject, or turn someone down -- use rejection-letter
• The conflict involves potential legal liability, harassment at a severity requiring HR involvement, or employment law -- refer the user to HR or legal counsel; this is not a writing problem
• The user wants to send a mass communication addressing team-wide dysfunction -- use team-communication or memo-writing
• The conflict is between the user and a customer or client -- use customer-complaint-response for those scenarios
• The goal is to end a working relationship entirely rather than repair it -- severance or termination communications require different framing

---

Process

Step 1: Diagnose the Conflict Type and Temperature Before Writing Anything

Before drafting a single word, identify which of four conflict types you are dealing with, because each requires a structurally different email:

• Incident conflict: A specific, bounded event -- a meeting, a decision, a deliverable -- where something went wrong once. Resolution path: address the specific incident, describe impact, ask for acknowledgment and forward alignment.
• Pattern conflict: The incident is part of a recurring problem. Resolution path: name the pattern using specific dated examples (not "you always"), propose a systemic fix, and set a clear expectation going forward.
• Expectation conflict: Two people had different mental models of what was agreed. Resolution path: surface the misalignment without blame, restate shared understanding, confirm going forward.
• Values/style conflict: Underlying differences in how people work, communicate, or prioritize. The hardest to resolve by email. Resolution path: name the tension, propose a live conversation, use email only to set up the discussion -- not to resolve it.

Also assess emotional temperature using a 3-tier model:

• Cool (Level 1): Minor misunderstanding, no relationship damage, factual resolution possible in one exchange
• Warm (Level 2): Real frustration exists on at least one side, relationship trust has been dinged, needs careful framing and possibly a follow-up conversation
• Hot (Level 3): Significant tension, hostility, or betrayal is in play -- email is NOT the right resolution medium at this temperature; use email only to invite a live conversation, not to argue the case

Ask the user these questions before writing:

• Who is the recipient and what is their hierarchical relationship to the user (peer, manager, skip-level, direct report, cross-functional partner, external vendor)?
• What specifically happened -- including date, context, and what was said or done?
• Has this happened before? If so, how many times and when?
• What does the user want as an outcome? (Options: an apology, a behavior change, a process change, restored trust, an acknowledgment, a specific action)
• Has there been any prior communication about this issue -- verbal or written?
• Is anyone else involved, copied, or affected?
• On a scale of 1-10, how emotionally activated is the user right now?

If the user rates their emotional activation at 7 or above, flag this explicitly: advise drafting now but waiting to send. A 90-minute cooling period is minimum; overnight is better for Level 2-3 conflicts.

---

Step 2: Separate the Incident Stack into Three Clean Layers

This is the most technically important step. Conflict emails fail when these three layers collapse into each other. Pull them apart explicitly:

Layer 1 -- Observable facts: What would a neutral third-party observer confirm actually happened? Use the "security camera test" -- if a camera was recording, what would it have captured? Keep only what passes this test.

• Acceptable: "The dashboard I built was not attributed to me in the Tuesday presentation."
• Not acceptable: "You deliberately took credit for my work."

Layer 2 -- Measurable or demonstrable impact: What actual business, project, or professional consequence resulted? This is where the email gets its legitimacy. Impact must be concrete:

• Project impact: "The change meant we missed the Sprint 3 deadline by two days."
• Reputation/career impact: "Leadership visibility on this project matters for my upcoming promotion review."
• Team impact: "The miscommunication meant two engineers duplicated work for a full week."
• Client impact: "The client received conflicting information from two different contacts."

Layer 3 -- Emotional experience: The user's feelings are real and valid, but they should almost never appear in the email verbatim. Your job is to translate emotions into impact language. "I felt disrespected" becomes "I want to make sure my contributions are visible to leadership." "I'm furious" becomes "This has made it difficult for me to move forward productively."

The exception: for close peer relationships or when the conflict is explicitly interpersonal rather than transactional, one sentence of authentic emotional language ("I'll admit I was surprised by this") can humanize the email and signal you are being genuine, not just procedural.

---

Step 3: Select the Right Rhetorical Frame

The frame determines the psychological position the recipient experiences when reading. Choose one primary frame per email -- mixing frames creates an incoherent tone.

The Curiosity Frame: "I want to make sure I understand your perspective on X."

• Best for: expectation conflicts, situations where you might be missing context, addressing a superior, early-stage pattern conflicts
• Opens with genuine uncertainty, not feigned uncertainty. Use only if you can genuinely acknowledge you might have incomplete information.
• Signature move: Ask a genuine question before stating your position. "I noticed X -- I may be missing context, so I wanted to check in before making assumptions."

The Impact Frame: "When X happened, the effect on [project/team/deliverable] was Y."

• Best for: incidents where the other person may genuinely not realize the downstream consequences of their behavior
• Opens by assuming good faith about intent while being explicit about consequences. Does not require the recipient to admit wrongdoing -- it simply reports reality.
• Signature move: Lead with the impact before mentioning the behavior. "The API integration deadline slipped by four days -- I want to walk through what happened so we can prevent it next time."

The Alignment Frame: "I want to make sure we are operating from the same understanding."

• Best for: expectation conflicts, miscommunications about scope, role confusion, process disagreements
• Completely non-confrontational because it positions both parties as working toward shared clarity rather than one correcting the other
• Signature move: Restate what you understood the agreement to be, invite them to confirm or correct it. "My understanding was X -- is that how you saw it?"

The Accountability Frame: Use when the user made the mistake.

• Lead with the acknowledgment before the explanation -- always. The explanation comes second, the fix comes third.
• Never use "but" between the acknowledgment and explanation. "I missed the deadline, but I had three other priorities" erases the acknowledgment entirely.
• Use "however" or start a fresh sentence: "I missed the deadline. Here is what happened and what I am doing to prevent recurrence."

Frames to avoid entirely:

• Blame frame: "You caused X" -- triggers defensiveness, shuts down resolution
• Ultimatum frame: "If you do not X, I will Y" -- only use in writing when you have already attempted direct conversation twice and are prepared to follow through
• Passive-aggressive frame: "I just wanted to make sure you were aware..." -- signals contempt, destroys credibility

---

Step 4: Build the Email Architecture

Conflict emails have a specific structural logic that differs from standard professional emails. The order of sections is not stylistic -- it is strategic, because each section lowers defensive reactivity before the next section introduces friction.

Section 1 -- Disarming opener (1-2 sentences): Establish shared ground, acknowledge a positive, or state collaborative intent. This is not flattery -- it is a psychological pattern interrupt that signals "this email is not an attack." The opener must be genuine. A forced compliment reads as manipulative.

Section 2 -- Context anchor (1-2 sentences): State what you are writing about with neutral specificity. Use dates and observable events. This is the "what happened" without any judgment attached. "On Monday's presentation to the leadership team" is a context anchor. "When you embarrassed me in front of leadership" is not.

Section 3 -- Impact statement (2-3 sentences): Describe the consequence using business or professional terms. This is where the email earns its legitimacy. If you cannot articulate a real impact, reconsider whether this warrants a written conflict email at all.

Section 4 -- Perspective invitation OR forward proposal (1-2 sentences): Give the recipient a role in the resolution. There are two options:

• Perspective invitation: "I may be missing something -- I would welcome your take on this." Use when you genuinely might be missing context.
• Forward proposal: "Going forward, I would suggest X. Does that work for you?" Use when the facts are clear and you just need alignment on next steps. Do not use both in the same email -- it dilutes the ask.

Section 5 -- Collaborative close (1 sentence): Reinforce the relationship frame. Signal that the goal is resolution, not victory. The relationship survives the incident.

Length targets by conflict level:

• Level 1 (Cool): 100-150 words. Brevity signals low drama and high confidence.
• Level 2 (Warm): 150-220 words. Enough space to be thorough without being overwhelming.
• Level 3 (Hot): 75-100 words maximum -- and those words should be an invitation to talk, not an argument by email. Never try to resolve a Level 3 conflict in writing.

---

Step 5: Write the Subject Line with Precision

The subject line does more work in a conflict email than in any other professional email type. It is the first signal of your intention and frames the recipient's emotional state before they read a single word.

Rules for conflict email subject lines:

• Describe the topic, not the conflict. "Follow-up on Monday's presentation" not "Credit for my work"
• Use "follow-up," "check-in," or "quick question about" as openers when the situation is sensitive -- these signal low stakes even when the content is significant
• Avoid accusatory or emotionally loaded words in subject lines: "issue," "problem," "concern," "disappointed"
• Make the subject specific enough to identify the context without triggering alarm: "API integration timeline" not "API integration delays (again)"
• For pattern conflicts requiring systemic discussion: "Process alignment -- [topic]" signals you are proposing a structural solution, which is less threatening than "recurring issue with [person's name or team]"

Subject line red flags to catch and fix:

• "We need to talk" -- triggers fight-or-flight in almost every reader
• "FYI" on a conflict-related email -- passive-aggressive
• A subject that includes the recipient's name when they are the only recipient -- "Mike's behavior on project X" -- sounds like a formal complaint
• Forwarding a previous hostile email with added commentary in the thread -- start a fresh email

---

Step 6: Apply the Four-Pass Review

Do not send after the first draft. Run four specific review passes:

Pass 1 -- Accusation scan: Read every sentence and ask: "Does this sentence attribute intent, motivation, or character to the recipient?" Remove or reframe every sentence that does. "You clearly do not respect my time" → "The meeting was rescheduled three times on short notice, which made it difficult to plan my week."

Pass 2 -- Absolute language scan: Find every instance of "always," "never," "every time," "constantly," "repeatedly" (when not followed by a specific count and timeframe). Replace with specific instances. "You never respond to my Slack messages" → "In the past two weeks, I sent three Slack messages that went unanswered for more than 48 hours."

Pass 3 -- Tone-inversion test: Read the email imagining you are the recipient who has had a genuinely bad week and is already feeling defensive. Does any sentence -- even a well-intentioned one -- land as condescending, dismissive, or sarcastic? This is especially important for phrases like "As I mentioned previously," "As you know," "I would have thought," and "I assumed you understood."

Pass 4 -- Outcome alignment check: Does every paragraph serve the stated outcome? If the user wants a behavior change going forward, does the email actually propose the change clearly? If they want an acknowledgment, does the email create space for the recipient to give one? Remove content that relitigates grievances without advancing toward the resolution.

---

Step 7: Determine CCs, Timing, and Escalation Logic

CC decisions:

• For peer-level conflicts: no CC on initial email, ever. CC is an implicit escalation move.
• For cross-functional conflicts where a shared manager needs visibility: BCC your manager on the initial email with a separate "heads up" note, or CC them only after one failed direct resolution attempt.
• If the conflict itself involves a group decision or shared accountability: suggest a meeting rather than a group email thread. Group conflict threads almost always escalate.
• Reply-all to a hostile group email: break the chain. Start a new thread with only the relevant parties.

Send timing:

• Never send a conflict email on Friday afternoon -- the recipient has the whole weekend to ruminate without being able to respond
• Monday mornings are also suboptimal -- people are in high-task mode and read conflict emails as additional burden
• Best window: Tuesday-Thursday, mid-morning. The recipient has their week oriented and has bandwidth to respond thoughtfully.
• If a conflict email requires a response, include a soft deadline: "If I do not hear back by Thursday, I may loop in [shared manager] so we can resolve this together." This is not an ultimatum -- it is a structured escalation path.

Escalation logic: Establish a clear rule for users: one direct email attempt, one follow-up if no response within 5 business days, then a live conversation (not a second email), then escalation to a manager or HR if the pattern persists despite direct attempts.

---

Step 8: Recommend the Right Follow-Up Channel

Email resolves simple, bounded conflicts efficiently. It fails for everything complex. Advise the user on what comes after the email:

• If the conflict is Level 1: email alone is likely sufficient. Propose alignment in the email and confirm via email response.
• If the conflict is Level 2: email opens the conversation; follow with a 15-minute video or phone call to confirm alignment. Do not try to fully resolve Level 2 through email.
• If the conflict is Level 3: use email only to request a live conversation. The email should contain zero argument, zero detailed incident description, and no proposed resolution. It should say only: "I want to connect about [topic] when you have time. Would [time option A] or [time option B] work this week?"
• If the recipient responds defensively to the email: do not reply to the defensive response by email. Pick up the phone.

---

Output Format

Deliver the complete email using this structure. Annotate each section briefly for the user so they understand what it is doing and can adjust it:

CONFLICT EMAIL DRAFT
─────────────────────────────────────────────────
CONFLICT TYPE: [Incident / Pattern / Expectation / Values-Style]
TEMPERATURE LEVEL: [1-Cool / 2-Warm / 3-Hot]
FRAME USED: [Curiosity / Impact / Alignment / Accountability]
RECOMMENDED SEND TIME: [Day and window]
FOLLOW-UP RECOMMENDATION: [Email sufficient / Call after / Call instead]
─────────────────────────────────────────────────

SUBJECT: [Neutral, topic-specific subject line]

---

Hi [First Name],

[DISARMING OPENER -- 1-2 sentences]
[Establishes shared ground, positive context, or collaborative intent.
Signals this is a problem-solving email, not an attack.]

[CONTEXT ANCHOR -- 1-2 sentences]
[States what happened with factual specificity: date, event, observable
action. Zero attribution of intent.]

[IMPACT STATEMENT -- 2-3 sentences]
[Describes the consequence in business or professional terms. Connects
the incident to a real cost: timeline, visibility, team clarity, etc.]

[PERSPECTIVE INVITATION or FORWARD PROPOSAL -- 1-2 sentences]
[Either: invites their perspective if context might be missing.
Or: proposes a concrete forward-looking solution with a clear ask.]

[COLLABORATIVE CLOSE -- 1 sentence]
[Signals the relationship matters and you want resolution, not a verdict.]

[Professional sign-off],
[Name]

---

WORD COUNT: [X words]
REVIEW FLAGS: [Any remaining watch items the user should review before sending]
ESCALATION NOTE: [What to do if there is no response within 5 business days]
─────────────────────────────────────────────────

---

Rules

1. Never attribute intent in the email body. "You took credit for my work" is intent attribution. "My contribution was not mentioned in the presentation" is observation. The email should contain zero sentences that explain why the other person did something -- you do not know, and guessing will derail the conversation.

2. Specific instances beat generalizations every time. "On March 14th, the API spec was submitted three days past the agreed date" is actionable. "You always miss deadlines" is a character attack. If the user cannot name a specific date or event, the conflict is not concrete enough for an email -- they need to think it through more before writing.

3. Never CC to apply social pressure. Adding a manager to CC on a first email is not transparency -- it is escalation theater. It signals to the recipient that you do not trust direct communication and immediately raises the stakes. Direct first, then escalate structurally if direct fails.

4. Emotional activation above 7 out of 10 means draft only, do not send. The email written in anger will make the situation worse even if every word is technically accurate. The goal of a conflict email is resolution, not catharsis. Flag this for users who are clearly still in the acute emotional response.

5. Absolute language automatically triggers defensiveness. The psychological research on conflict communication consistently shows that "always" and "never" shift the recipient's brain from problem-solving mode to self-defense mode. Remove these words entirely. Specific quantified instances achieve the same communication goal with a fraction of the defensive reaction.

6. Length correlates inversely with resolution in conflict emails. A 400-word conflict email reads as a brief. The recipient's defenses go up proportionally. Under 220 words for most conflicts. Under 100 words if inviting a conversation rather than resolving the issue in writing. If you cannot make the case in 200 words, you need a conversation, not a longer email.

7. The subject line must not betray the content's emotional weight. If the subject line triggers anxiety, the recipient will be in a defensive posture before they read the first word. Neutral, topic-specific subject lines are not dishonest -- they are respectful of the other person's right to approach the conversation without pre-loaded adrenaline.

8. The collaborative close is not optional. Conflict emails that end on the impact statement or the ask feel like indictments. The final sentence must signal that you value the relationship and want resolution. Omitting it leaves the recipient with no emotional ramp down at the end of the email.

---

Edge Cases

Responding to a Hostile or Aggressive Email

Do not match tone. Do not defend every point raised. Respond selectively and calmly to the substantive claims while declining to engage with the emotional register. Practical approach: copy the hostile email into a separate document, identify the 1-3 substantive business claims inside it, and respond to those only. Ignore the insults, the hyperbole, and the emotional language entirely. Opening language: "Thank you for flagging this. Let me address the specific points you raised." This signals you are taking the substance seriously without validating the delivery method. If the email contains personal attacks that cross a professional line, note factually: "I want to keep this conversation focused on the project rather than personal characterizations -- I think we will get to resolution faster that way."

The User Is the Party Who Made the Mistake

This is the highest-stakes conflict email type because it sets the tone for how the user will be perceived professionally afterward. The structure must be: acknowledgment → impact → fix → prevention. Never reverse this order. Never put the explanation before the acknowledgment -- it reads as defensive. Never use the word "but" between acknowledgment and explanation. Specific language: "I should have flagged the scope change before the sprint planning session. That gap caused the team to commit to deliverables that did not reflect the revised scope. I have already updated the project tracker and will send a revised timeline to the team by end of day. Going forward, I will confirm scope with you before any sprint commitment." Four sentences, all four steps, nothing extraneous.

The Conflict Has an Audience -- Others Were Present or Are Aware

When the conflict occurred in front of others (a meeting, a Slack channel, a group presentation), the user often wants to address it publicly or CC the group. Advise against this unless absolutely necessary. Public resolution attempts create spectators, which raises the stakes for the person being addressed and almost guarantees a defensive response. The one exception: if the incident occurred in a public channel and caused public confusion, a brief clarifying statement to that group may be warranted -- but it should not name or address the other party's behavior publicly. Address the incident one-on-one, then optionally address the group with a neutral clarification.

The Other Person Has Repeatedly Not Responded to Previous Direct Attempts

At this point, email is no longer the right tool for resolution -- it is a documentation tool. Advise the user that the conflict email at this stage has two purposes: (1) creating a written record that direct resolution was attempted, and (2) providing notice before escalation. The tone shifts slightly: "I have reached out [twice/three times] about [topic] without a response. I want to give you one more opportunity to address this directly before I loop in [shared manager/HR/project lead]. If I do not hear from you by [specific date], I will escalate through the appropriate channel." This is not a threat -- it is a structured escalation notice, and it is legitimate.

The Conflict Is Rooted in a Cultural or Communication Style Difference

Some conflicts that feel like willful behavior are actually style or cultural norm mismatches -- directness norms, hierarchy expectations, meeting etiquette, response time expectations. When there are signals this might be the case (the conflict involves communication style rather than a specific incident; the other party is from a different functional background or cultural context), use the alignment frame and explicitly name the style difference without judgment: "I think we may have different working norms around response timelines -- I typically expect a same-day response on project-critical messages, and I realize that may not match your workflow. I would like to align on what works for both of us." This reframes the conflict as a coordination problem rather than a behavioral failure.

The User Wants to CC HR or Legal on the Initial Email

Advise strongly against this in most cases. CC'ing HR or Legal on an initial conflict email signals that you are initiating a formal process, which triggers legal and HR protocols on the recipient's side and removes the possibility of an informal resolution. The response you get will likely be drafted by HR or Legal themselves. Reserve CC'ing HR for situations where: (1) the behavior constitutes harassment, discrimination, or policy violation; (2) direct resolution has been attempted and failed twice; or (3) the user has been advised by HR to document. For the vast majority of workplace conflicts, HR involvement should be the escalation path if direct resolution fails -- not the starting point.

The Email Chain Has Already Escalated and the User Is Responding to a Hostile Thread

Stop the chain. Do not reply-all to a hostile thread. Start a fresh email directly to the key party with a subject line that names a forward path: "Setting up time to talk about [topic]." The body should be 3-5 sentences maximum: acknowledge that the thread has gotten heated, express desire to resolve it directly, propose two specific times to connect by phone or video, and close with collaborative intent. Do not relitigate any points from the previous thread. The purpose of this email is solely to get off email and onto a medium that can actually resolve a Level 3 conflict.

---

Example

User Input: "I need help writing an email to my colleague Sarah. She's a senior engineer on a cross-functional project I'm managing. She's been consistently not showing up to our weekly syncs -- she's missed 4 of the last 6 meetings -- and when she does show up she leaves early. It's creating a problem because the other team members feel like their time isn't valued and I keep having to re-brief her separately. I've mentioned it verbally once but it made no difference. I'm frustrated but I know I need to handle this carefully because she's senior to me in role and I need her cooperation to finish the project."

---

AI Assessment (shared with user before drafting):

• Conflict type: Pattern conflict (4 of 6 missed meetings in a documented time window -- three or more instances qualifies as pattern)
• Temperature level: Level 2 -- Warm (real frustration, one failed verbal attempt, relationship dependency)
• Frame recommendation: Impact frame leading into Alignment frame -- Sarah may not realize the downstream effect on the team; position this as a structural coordination problem, not a behavioral complaint
• Hierarchy consideration: Sarah is senior in role, so the user needs to avoid a corrective tone -- frame as "help me understand and solve" not "this is a problem you are causing"
• Not recommended: Copying the project lead or Sarah's manager on this email. That is the next step if direct resolution fails.
• Escalation threshold: If no positive response within 5 business days, user should request a one-on-one conversation before escalating to shared management

---

Output:

CONFLICT EMAIL DRAFT
─────────────────────────────────────────────────
CONFLICT TYPE: Pattern Conflict
TEMPERATURE LEVEL: 2 -- Warm
FRAME USED: Impact → Alignment
RECOMMENDED SEND TIME: Tuesday or Wednesday, mid-morning
FOLLOW-UP RECOMMENDATION: Follow with a brief check-in call if positive
response received; if no response in 5 business days, request live
conversation before escalating
─────────────────────────────────────────────────

SUBJECT: Weekly sync attendance -- want to find a setup that works for you

---

Hi Sarah,

Your technical input on this project has been genuinely valuable, and I
want to make sure the meeting structure is set up in a way that makes
your time worth showing up for.

I wanted to raise something directly. Over the past six weeks, the
Wednesday sync has been hard to keep you in -- you have missed four of
the six sessions and left early on one of the two you attended. I have
not flagged this more formally because I suspect the timing or format
may not be working for your schedule, and I would rather fix the
structure than create friction.

The practical impact is that I have ended up re-briefing you separately
after most syncs, which doubles the time cost for both of us, and a
few team members have noted that the gaps make alignment harder. On a
project at this stage, your perspective in the room significantly affects
the quality of our technical decisions.

Would you be open to a 15-minute conversation this week about what would
make the sync more useful for you? I can adjust the timing, agenda, or
format if that helps. I want to make sure you are able to contribute in
the way that works best, because your involvement genuinely matters to
how this ends.

Happy to find what works,
[Name]

---

WORD COUNT: 196 words
REVIEW FLAGS:
- Confirm the meeting count (4 of 6) is accurate -- specific numbers
  in pattern conflicts must be precise. Do not estimate.
- "Your input has been genuinely valuable" should only stay if it is
  true -- remove if it will read as flattery given your actual relationship
- "A few team members have noted" -- confirm you are comfortable citing
  this; if Sarah asks who, be prepared to either name them or soften to
  "the team's ability to align has been affected"
ESCALATION NOTE: If no response in 5 business days, send a single brief
follow-up: "Just wanted to make sure this did not get buried -- happy to
find a time to chat about the sync setup when you have a few minutes."
If that also receives no response, request a three-way conversation with
your shared project lead framed as a "project coordination check-in,"
not a complaint about Sarah specifically.
─────────────────────────────────────────────────

---

Why this email works -- technical breakdown:

• Disarming opener acknowledges Sarah's contribution genuinely and immediately signals this is not an accusation email, it is a problem-solving email. The phrase "make your time worth showing up for" subtly puts the agency on the user's side -- "help me make this better" -- which is strategically smart given Sarah's senior status.

• Context anchor uses the specific ratio (four of six meetings) which demonstrates the user has been tracking this objectively, not reacting emotionally. "I have not flagged this more formally" signals proportionality -- this is a first direct step, not a formal escalation.

• Impact statement gives Sarah two concrete reasons to care that do not require her to feel guilty: (1) double time cost for both parties -- self-interest argument, (2) decision quality -- professional stakes argument. Neither frames it as "you are letting the team down."

• Perspective invitation is genuine -- the user actually does not know if the time or format is the problem. This is real curiosity, not performed curiosity, which makes it effective. The proposal to adjust the format gives Sarah a face-saving path that does not require her to admit anything.

• Collaborative close ends with "your involvement genuinely matters," which reinforces the message that this is not a complaint -- it is an expression of need. This makes Sarah more likely to respond constructively.

• The subject line is the most strategically important element: "want to find a setup that works for you" signals that the email is about solving her problem, not correcting her behavior. This almost eliminates defensive reactivity before the email is opened.