Find a useful opening for a retrospective or difficult conversation

Name the job of the sentence

An opening question, a boundary and a decision request do different jobs. Before generating alternatives, write down which one you need. Also separate what you observed from what you concluded. “The handoff document was missing an owner on two occasions” gives the other person something specific to discuss; “you never take responsibility” adds a sweeping judgment.

For a retrospective, decide what improvement the conversation is meant to enable. The Scrum Guide describes the Sprint Retrospective as planning improvements to quality and effectiveness. That purpose is a useful reference when a meeting drifts into a list of complaints. It does not mean every difficult conversation belongs in a group retrospective.

• The Scrum Guide: Sprint Retrospective↗

Request different conversational moves

Eight alternatives can cover an observation, a clarification question, an impact statement, a boundary, an invitation, a disagreement, a decision request and a next-step proposal. These are writing directions, not eight independent judgments about the people involved. Use available agents to compare responses and remove lines that sound unlike you.

Supply only the context needed: roles, observed events, your own concern and the decision you can legitimately request. Do not ask the model to diagnose someone’s motives. A useful variant should remain fair even if the other person later explains a constraint you did not know about.

Help me prepare wording for a work conversation. Observed events: [facts]. My concern: [concern]. Desired next step: [request]. Relationship and setting: [context]. Give 8 short alternatives: observation, clarification, impact, boundary, invitation, disagreement, decision request and next-step proposal. Preserve the facts, avoid blame and do not infer motives. For each identify the assumption it makes and a respectful follow-up if the other person disagrees. Do not invent promises or authority I do not have.

Build a card you can glance at

Use a fictional handoff problem: two draft documents reached review without an identified decision owner. The speaker wants the next draft to have an owner. These exercise inputs are not a real team case, and the suggested lines are options to adapt rather than a proven conflict technique.

Rehearse the second turn, not only the opening

Ask for a plausible misunderstanding of your chosen line and rewrite only the part that creates it. If “can we” hides a decision already made, state that honestly. If you are proposing an experiment, do not phrase it as an instruction. If the person contests the facts, return to the specific event before discussing remedies.

Keep the card short: one observation, one question, one request and a fallback line. Read it aloud. Delete wording you would not use naturally. During the real conversation, listen and depart from the card when new information matters; the generated alternatives are preparation, not a substitute for participation.

End with a shared record of the next step

In Colay, compare drafts separately before requesting any synthesis. A combined answer should preserve unresolved differences, not turn them into artificial agreement. Start with one conversation card and judge its usefulness by whether it helps you state the issue clearly and hear the response, not by how many polished sentences it produces.

1. Check whether both sides describe the issue in compatible terms.
2. Write the action, owner and review point in ordinary language.
3. Record a remaining disagreement explicitly instead of smoothing it away.
4. Use the appropriate established process for concerns that cannot be resolved in this conversation.

Questions, answered