前言
最近Uncle Martin又重開小灶
鑒于之前都沒(méi)有好好思考輸出筆記
零零碎碎的，未用先忘，搞得TA血壓蹭蹭蹭的往上升
所以決定認(rèn)真做做筆記
產(chǎn)品和需求的區(qū)別
Uncle Martin：What‘s the difference between product and requirement ? How to define them?
Me：Umm... I don't know...
Uncle Martin: What...
產(chǎn)品
產(chǎn)品是抽象的概念，代表著從0-1的過(guò)程；連接美好的藍(lán)圖和愿景，注入情懷和匠心城瞎，這樣才可能成為好產(chǎn)品；好產(chǎn)品
好的產(chǎn)品首先是對(duì)用戶有價(jià)值的疾瓮，進(jìn)而是用戶所喜歡的
好的產(chǎn)品不僅僅從表象去滿足用戶的需求脖镀，更深層次地是要從內(nèi)心去震撼、刺激狼电、并燃起用戶消費(fèi)的欲望需求
需求是具體的實(shí)現(xiàn)蜒灰，代表著從1-n的過(guò)程，關(guān)乎落地→細(xì)化→執(zhí)行
用戶故事
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
- 舉個(gè)栗子
brief：訂單變更自動(dòng)提醒
user story： 為了將整天盯著屏幕刷單的一不小心會(huì)遺漏重要訂單消息的客服童鞋從重復(fù)繁瑣中解脫出來(lái)，一旦訂單狀態(tài)變更腾务，則系統(tǒng)自動(dòng)發(fā)送微信消息給客服人員
flow：訂單監(jiān)控 →(狀態(tài)檢測(cè))→ IF 符合檢測(cè)條件 then 發(fā)送消息
detail：狀態(tài)檢測(cè)條件：新增的待發(fā)貨訂單
講故事
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
創(chuàng)業(yè)公司和成熟公司
創(chuàng)業(yè)公司： 靈活、重任削饵、自由岩瘦；敏捷開發(fā)未巫，小步快跑，快速迭代 ...
成熟公司： 制度启昧、流程叙凡、體系、規(guī)范完善密末；資源充足握爷，用戶基礎(chǔ) ...
后記
確實(shí)，很多東西都處在一個(gè)知道或有印象的狀態(tài)严里，并沒(méi)有去用起來(lái)
現(xiàn)在80%的時(shí)間都在需求文檔細(xì)節(jié)上了新啼，ROI極低
Anyway, practice makes perfect.
And it's important to know both how and why.
腦子不常動(dòng)，容易生銹刹碾，趕緊買點(diǎn)核桃補(bǔ)補(bǔ)腦去Ta-ta
