前言
最近Uncle Martin又重开小灶
鉴于之前都没有好好思考输出笔记
零零碎碎的，未用先忘，搞得TA血压蹭蹭蹭的往上升
所以决定认真做做笔记
产品和需求的区别
Uncle Martin：What‘s the difference between product and requirement ? How to define them?
Me：Umm... I don't know...
Uncle Martin: What...
产品
产品是抽象的概念，代表着从0-1的过程；连接美好的蓝图和愿景，注入情怀和匠心，这样才可能成为好产品；好产品
好的产品首先是对用户有价值的，进而是用户所喜欢的
好的产品不仅仅从表象去满足用户的需求，更深层次地是要从内心去震撼、刺激、并燃起用户消费的欲望需求
需求是具体的实现，代表着从1-n的过程，关乎落地→细化→执行
用户故事
Uncle Martin: Now give me an example of the requirements you mentioned, in user story.
Me: Well, it's xxxxxx（focus on function）
Uncle Martin: unclear expression，and will depressed engineer's motivation
-
核心三要素
who
what
why (most important)
note: For PM，it's important to clarify why to do; for team members, it's important to know why it worth to do
-
需求流程
brief → user story → flow → detail
note: brief and user story take about 60% of time
- 举个栗子
brief：订单变更自动提醒
user story： 为了将整天盯着屏幕刷单的一不小心会遗漏重要订单消息的客服童鞋从重复繁琐中解脱出来，一旦订单状态变更，则系统自动发送微信消息给客服人员
flow：订单监控 →(状态检测)→ IF 符合检测条件 then 发送消息
detail：状态检测条件：新增的待发货订单
讲故事
Telling story, not just express the facts, but most important is to describe what your expectation and better to visualize it, which makes your audients feel passionate and longing for your product
创业公司和成熟公司
创业公司： 灵活、重任、自由；敏捷开发，小步快跑，快速迭代 ...
成熟公司： 制度、流程、体系、规范完善；资源充足，用户基础 ...
后记
确实，很多东西都处在一个知道或有印象的状态，并没有去用起来
现在80%的时间都在需求文档细节上了，ROI极低
Anyway, practice makes perfect.
And it's important to know both how and why.
脑子不常动，容易生锈，赶紧买点核桃补补脑去Ta-ta
