做产品 PMaker
空格的键盘
选择客户 勾选记录 有未确认的? 否 生成对账单 是 先去确认 完成 中途退出 保存草稿 实线是主路径,菱形是判断,虚线是异常出口

主路径只有四步,但每一步都要想清楚:走不通的时候他去哪,中途走开了回来还能不能接上。

Map the User Journey

Draw one complete task as a line: where they enter, how many steps, where each step might branch, and what happens when they can't continue.

What you'll run into
  • 主流程能走通,稍微不按预期操作就卡死
  • 用户填到一半退出,回来发现全没了
  • 让 AI 一页页做,每页都对,串起来发现少了一步

How to draw it

步骤做什么
定起点用户从哪进来。首页、搜索结果、推送、还是别人发的链接。起点不同,他知道的信息不一样
列主路径顺利情况下的每一步。控制在三到五步,超过就该考虑拆或简化
标判断点每一步之后问一句:这里会不会有分支。用菱形标出来,两条路都要画
补异常出口每一步都问:他中途走了怎么办、失败了去哪、没权限怎么办
画返回路径每个终点都要能回到起点或某个稳定位置,不能是断头路
The emotion column isn't literary flourish—it directly drives the design decisions in the right-hand column. If you can't articulate the emotion, you probably don't know the scenario well enough yet.
主路径是顺利那条,但真正决定体验的是它下面挂着的东西 选择客户 勾选记录 确认金额 生成对账单 客户太多找不到 支持搜索、最近排前 中途被打断走了 已勾选的要保住 有未确认的记录 就地处理,别跳走 网络断了 给重试,别丢草稿 每一步都要问三句:这里会不会分支、他中途走了怎么办、这个终点怎么回到稳定位置。 主路径超过五步是个信号:要么任务本身该拆成两次,要么中间几步可以合并或用默认值跳过。 「用户中途离开」这条在移动端最要紧——假设他随时会被打断,每一步的中间结果都该被保住。 这条判断会直接改变你的数据设计,因为你得有个地方存草稿。
The emotion column isn't literary flourish—it directly drives the design decisions in the right-hand column. If you can't articulate the emotion, you probably don't know the scenario well enough yet.

Where branches come from

Four places tend to sprout branches. Ask each one as you draw.

The last one matters especially on mobile. Assume the user can be interrupted at any moment, and every step's intermediate result should be preserved—this judgment directly changes your data design, because you need somewhere to store drafts.

Add an emotion line

After the journey is drawn, mark the user's state under each step: anxious, hesitant, worried about mistakes, eager to finish. That's a user experience map.

步骤他在想什么于是这一步要
选择客户客户有点多,找起来烦支持搜索,把最近合作的排前面
勾选记录别漏了,漏了要重来显示已选数量和总额,支持全选
有未确认的又要跳走,回来还得重选就地处理,或者保住已勾选的状态
生成对账单格式对不对,客户能看懂吗先给预览,确认之后再发出去
The emotion column isn't literary flourish—it directly drives the design decisions in the right-hand column. If you can't articulate the emotion, you probably don't know the scenario well enough yet.