# Design The Conversation > Design where a message leads before writing it. Use before sending or drafting any outreach, cold email, follow-up, LinkedIn note, text, or reply whose purpose is to move a real relationship forward: map the destination, write the closing turn first, work backwards, then branch-test every question so that each plausible answer has a next move. Use whenever a draft ends in a question and nobody has said what the answer unlocks. Do not use for a message that only has to inform, confirm, or thank. - Skill: `seryozh/design-the-conversation` (Agent Skill, multi-file: 4 files) - Install (CLI): `npx skillmds@latest add seryozh/design-the-conversation` - Raw SKILL.md: https://api.skillmd.com/api/skills/seryozh/design-the-conversation/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: Seryozh (https://skillmd.com/u/seryozh) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/seryozh/design-the-conversation --- # Design the conversation A message that ends in a question is not finished. It is finished when you can say what happens after each answer, and where the exchange lands if it goes well. The failure this prevents is the research interview wearing a sales suit: a smart, specific, well-researched question whose answer teaches the sender something and leaves the reader with nothing to do. The reader senses it, and the reply never comes. When it does come, the sender is holding a fact and no next move. ## The method **1. Name the destination.** Not the reply. The real thing: a signed agreement, a funded case, a decision made, a door opened. Write it in one sentence with who has to say yes. **2. Write the closing turn first.** What is the message that gets that yes, and what must the reader already know and believe by the time it arrives? That belief list is the work the earlier turns have to do. **3. Work backwards to turn one.** Each turn earns exactly one thing. If a turn is not moving the reader closer to the belief list, it is decoration and it costs you a reply. **4. Branch-test the question.** Write out every plausible answer, including the discouraging ones and the one-word ones. For each, write your actual next sentence. - If any branch leaves you with nothing to say, the question is wrong. Replace it. - If every branch leads to the same next move, the question is theater. Skip it and make the move. - If a branch leads somewhere better than your planned path, the question was better than your plan. Follow it. **5. Make the answer worth giving.** Their reply should unlock something they cannot get on their own: a number computed from their own figures, an honest comparison with what they already use, access, a decision they have been unable to make. Say so in the message, in one clause, so the reader can see what their answer buys them. "Whichever way you answer, I can tell you X" turns a question into a trade. **6. Keep the cost of replying near zero.** One question per message, answerable in a single line from a phone. A question that requires them to look something up, poll their team, or compose a paragraph is a question you will read about in your unanswered-mail folder. **7. Put the heavy ask where it has earned its place.** A first message that asks for a meeting is asking a stranger to spend time before they know why. The ask belongs in the turn after their answer, when their own words have made it obvious. If you cannot wait, you are not designing a conversation, you are running an ad. ## The test before sending Say out loud: "They reply with ___. Then I say ___. Then they ___." If any blank cannot be filled with a specific sentence, do not send it yet. ## Worked example A software support team publishes a four-hour first-response promise. A queue-triage consultant wants to find out whether one small paid pilot would help. - Destination: the support lead approves a one-week pilot on one queue. - Closing turn: "Send one anonymized week of that queue, and I will return the routing plan on Friday." - What they must believe by then: that the delay is concentrated enough to diagnose, the sample is safe to share, and the pilot does not require a system migration. - Turn one question: "Which ticket type most often misses the four-hour target?" - Branch A, a ticket type: show how that type would be separated and ask for the one-week sample. - Branch B, "none": do not force the pilot. Ask whether resolution time, rather than first response, is the actual constraint. - Branch C, "we do not track it by type": offer a lightweight measurement sheet before discussing a pilot. - Each answer earns a different immediate move. The conversation may still converge later, but the first question is doing real work rather than decorating a predetermined ask. ## Guardrails - Designing the path never licenses a claim you cannot support. No invented exclusivity, no fabricated urgency, no numbers the reader did not give you. - Never write a branch that depends on the reader misunderstanding you. - A conversation the reader would not want if they saw the whole map is a manipulation, not a design. If the map embarrasses you, change the offer, not the wording.