Back to home

Compare

Comparing: When Clients Can’t Explain What They Need, I Write My Way Clear & 客户需求说不清时,我用写作替自己理清思路

AEN
写作需求地图自由职业者一人公司·

When Clients Can’t Explain What They Need, I Write My Way Clear

Last Friday, “Make it more premium” left me speechless

At 4 p.m. Friday, I was revising a client proposal in a Hangzhou café. The client wanted a mini-program and opened with, “Make it more premium.” I questioned them for ages, but still couldn’t pin down what they meant. I nearly sent the quote—then stopped myself and protected my budget from rework. This was a mistake I used to make all the time: guessing requirements out loud until my own head became a mess.

Writing isn’t homework—it helps us see the problem

These days, I don’t rush into a proposal. Instead, I write down what I heard, line by line: who is using it, in what situation, where they’re stuck, and why the problem is worth solving. Then I circle the points that genuinely need confirmation and ask the client to fill in each one. Murat Buffalo has shared a similar idea on his blog: writing reveals the parts of your thinking that haven’t taken shape, even when you thought they had. We don’t need polished prose. We just need to expose the gaps in our thinking.

Copy this today: you can start without software

Cost: ¥0—use a phone memo app or a free document. Time: spend 20 minutes on a first draft, then book a 30-minute client confirmation call. Technical barrier: none; typing is enough. First step: create a document titled “What the client really wants to solve,” then paste in the exact words from your latest three conversations. Don’t polish anything yet, and don’t jump straight to a proposal.

Here’s how I adapt it at each stage

When I was just starting, I used a four-line template for every request: client, situation, problem, outcome. Once I had one or two clients, I sent the “client’s exact words” back for line-by-line confirmation so I wouldn’t fill in the blanks myself. Now that I’m scaling, I keep a separate needs map for each client, then combine them into rules my team can understand. Writing won’t tell us whether we’re right, but it helps us uncover mistakes earlier. There’s no pressure to try now; the next time a client’s request feels vague, write for five minutes. That’s enough to begin.

BZH
写作需求地图自由职业者一人公司·

客户需求说不清时,我用写作替自己理清思路

上周五,我被一句“做得高级一点”问懵了

周五下午四点,我在杭州的咖啡馆改客户方案。客户要一个小程序,张口就是“高级一点”,我问了半天也说不清他要什么。差点把报价单发出去,又硬生生留了返工钱。这也是我以前常犯的错:嘴上猜需求,心里越猜越乱。

写作不是交作业,而是帮我们看清问题

我后来不急着出方案,而是把听到的话逐句写下来:谁在什么场景下使用、目前卡在哪一步、为什么值得解决。然后圈出真正需要确认的地方,再请客户逐条补充。Murat Buffalo 在博客里分享过类似思路:写作能暴露脑中尚未成形、却以为自己已经想明白的部分。咱们不需要写得漂亮,只要能看见思路里的空洞。

今天复制一下:不用软件也能开始

钱:0 元,用手机备忘录或免费文档即可。时间:先用 20 分钟写初稿,再约客户确认一次,约 30 分钟。技术门槛:没有,只要会打字。第一步:新建文档,标题写“客户真正想解决什么”,然后贴上最近三次沟通里的原话。先别润色,也别急着给方案。

如果你正处在不同阶段,我会这样做

如果你刚起步,我会先用四行模板整理每次需求:客户、场景、麻烦、结果;如果已有 1—2 个客户,我会把“客户原话”发回去逐条确认,避免自己脑补;如果正在扩规模,我会给每位客户留一份独立需求地图,再汇总成团队能看懂的规则。写作不能替我们判断对错,但能让错误早点露出来。现在不试也没事,下一次客户说不清时,拿张纸写五分钟就够了。