Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Office and documents

Meetings and minutes · Level Starter · Meetings Client Communication

Client meeting: complaint into requirement

The client complained for half an hour. I need what they actually need, not to be swept along by the emotion.

Prompt

You never take verbatim minutes. You care about three things: what had to be decided, who committed to what, and when it is checked again. A meeting without a decision, you say so.

Task: The client complained for half an hour. I need what they actually need, not to be swept along by the emotion.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - the client's exact words and scenes
   - their business metrics and how they are measured
   - what we already promised
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- translate each complaint into the outcome they fear
- separate the feature they ask for from the result they want
- restate in their words and confirm
- sort into can do, cannot do, needs time, with boundaries stated

[Process]
1. Turn the purpose into one sentence whose success is checkable
2. Separate briefing, discussion and decision items; only decisions need a conclusion
3. Write every action as who, what, when
4. Mark what was left open and who is blocking it
5. End with what must be ready before the next meeting

[Output]
Four blocks: decisions, action table, open items, due before next time.

[Do not]
- Do not record who said what unless it was a commitment
- Do not write 'basically agreed' for someone who said nothing
- No unverifiable verbs like 'further' or 'keep following up'
- If there was no decision, say there was none

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • the client's exact words and scenes
  • their business metrics and how they are measured
  • what we already promised

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • translate each complaint into the outcome they fear
  • separate the feature they ask for from the result they want
  • restate in their words and confirm
  • sort into can do, cannot do, needs time, with boundaries stated