<aside> 📋 Frequency: Trigger-Based | Time: 30 min | Trigger: When a sensitive topic needs to be raised with a client

</aside>

Walking into a difficult client conversation without preparation is how minor friction becomes a damaged engagement. Whether you're addressing scope creep, missed deliverables, or a misaligned expectation, the outcome is set before you open your mouth. This SOP gets you into the conversation with a clear position, a fallback, and language that holds the relationship while it holds the line.

Prerequisites

Procedure

  1. Write a one-paragraph description of the issue: what happened, what the expected state was, and what you need to resolve. Keep it factual — no blame, no tone.
  2. Run the Difficult Conversation Prep skill with the issue description, client relationship context, and desired outcome as input. Review the output for language calibration — adjust any phrasing that doesn't match your relationship register with this client.
  3. Review the output's fallback options. Identify the one you'd accept if the client pushes back — enter the conversation knowing your floor.
  4. If scope is at issue, run the Scope Creep Response skill with the relevant SOW section and the requested out-of-scope work described. Use this output to frame the boundary clearly and introduce the change order path without making it adversarial.
  5. Prepare your opening — the first 2-3 sentences you'll say. Write it out. Vague intentions collapse under pressure.
  6. Schedule the conversation within 48 hours of completing this prep. Delayed difficult conversations get worse, not easier.

Expected Outcome

You'll have a written issue brief, prepared opening language, a clear desired outcome, at least one acceptable fallback position, and — if applicable — a scope response ready to introduce. You walk in prepared, not reactive.

<aside> ⚠️ Common mistakes:

Preparing only the case for your position — if you haven't thought through the client's likely response, you'll get caught flat-footed and either over-concede or escalate unnecessarily.

Waiting until you're frustrated — prep done while you're irritated produces language that sounds adversarial on the page and defensive in delivery. Run this SOP when you first identify the issue, not after it's been sitting for a week.

</aside>