roadmap-prioritization
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRoadmap Prioritization
路线图优先级排序
Transform a chaotic backlog into a high-ROI strategic plan based on evidence and appetite.
Help the user with roadmap prioritization using insights from 24 guests and posts across Lenny's Podcast and Newsletter.
基于证据和投入意愿,将混乱的待办事项列表转化为高ROI的战略计划。
借助Lenny's Podcast和Newsletter中24位嘉宾的见解与文章内容,为用户提供路线图优先级排序方面的帮助。
How to Help
如何提供帮助
- Audit the Backlog - Assist in gathering and categorizing ideas from diverse sources like churn data, support tickets, and strategic goals.
- Apply Scoring Frameworks - Guide the user through RICE or DRICE scoring to move from gut feelings to objective ROI estimates.
- Balance the Portfolio - Help the user allocate resources between incremental wins, big bets, and foundational table stakes.
- Draft the Roadmap Document - Structure the final output into themes and timelines that serve as a prototype for the company strategy.
- 待办事项审计 - 协助收集并分类来自不同渠道的需求想法,例如流失数据、支持工单、战略目标等。
- 应用评分框架 - 引导用户使用RICE或DRICE评分法,从凭直觉判断转向客观的ROI估算。
- 组合平衡 - 帮助用户在增量收益、重大押注和基础必备项之间合理分配资源。
- 起草路线图文档 - 将最终输出按主题和时间线结构化,作为公司战略的原型。
Core Principles
核心原则
Evidence-Guided Intuition
证据引导的直觉判断
Itamar Gilad: "I think every successful product company out there that you look at Amazon, Airbnb, anyone you will check, at least in their best periods they found a way to balance human judgment with evidence. They didn't try to obliterate human judgment and opinion just to supercharge them with evidence and they came up with very different models."
Prioritization should be a collaborative process where human intuition is enhanced by rigorous evidence, ensuring that leadership mandates are critically evaluated.
Itamar Gilad:“我认为你所看到的每一家成功的产品公司——亚马逊、爱彼迎,任何你能想到的——至少在它们的巅峰时期,都找到了平衡人类判断与证据的方法。它们不会试图抹杀人类的判断和意见,而是用证据来强化这些判断,并且它们提出了截然不同的模式。”
优先级排序应当是一个协作过程,通过严谨的证据强化人类的直觉判断,确保对领导层的指令进行批判性评估。
Roadmap as Strategy Prototype
作为战略原型的路线图
Janna Bastow: "The value isn't in your roadmap, the value is in the roadmapping process. What you're actually doing is laying out your assumptions of the problems that you're solving."
Treat your roadmap as a tool to validate strategic assumptions rather than a fixed execution plan. Focus on the conversations it triggers.
Janna Bastow:“价值不在于你的路线图本身,而在于路线图制定的过程。你实际上在做的,是列出你对正在解决的问题的假设。”
将你的路线图视为验证战略假设的工具,而非固定的执行计划。重点关注它所引发的讨论。
Structured Exploration
结构化探索
Paige Costello: "That process of going broad, and going narrow, and going broad, and going narrow forces people to get out of their opinion-driven lens because so often, we need to be curious quantitatively and qualitatively about what we're doing and why, and be more systematic and rigorous about getting there."
Use a systematic process like the Double Diamond to explore multiple options before narrowing down, which prevents opinion-driven decision-making.
Paige Costello:“这种先发散、再收敛、再发散、再收敛的过程,会迫使人们跳出以观点为驱动的视角,因为很多时候,我们需要从定量和定性两个层面对我们正在做的事情及原因保持好奇心,并且更系统、更严谨地达成目标。”
使用类似Double Diamond这样的系统化流程,在缩小范围之前探索多种选项,避免以观点为驱动的决策。
Fixed Appetite over Estimation
固定投入意愿优先于估算
Ryan Singer: "We're not going to take a big concept and then say, "What's the estimate for this thing?" We're going to go the other way around and we're going to say, what is the maximum amount of time we're willing to go before we actually finish something?"
Instead of asking how long something will take, determine the fixed amount of time the business is willing to invest and shape the solution to fit that window.
Ryan Singer:“我们不会先拿一个大的概念,然后问‘这个东西的估算是多少?’我们会反过来做,先问:在真正完成某件事之前,我们愿意投入的最长时间是多少?”
与其询问某件事需要多长时间,不如确定企业愿意投入的固定时间,然后调整解决方案以适配这个时间窗口。
Questions to Help Users
可向用户提出的问题
- "What is the ratio of incremental improvements to high-risk big bets in your current plan?"
- "Have you validated your top qualitative customer requests with quantitative data or experiments?"
- "What is the fixed appetite or time-box you are willing to invest in this specific initiative?"
- "Are you prioritizing the reporting needs of middle management over the daily workflows of your primary users?"
- "Which 3 to 4 high-level strategic themes are driving your team's choices this quarter?"
- “你当前的计划中,增量改进与高风险重大押注的比例是多少?”
- “你是否用定量数据或实验验证过你最优先的定性客户需求?”
- “你愿意为这项特定举措投入的固定投入意愿或time-box是多少?”
- “你是否将中层管理者的报表需求置于核心用户的日常工作流之上?”
- “本季度驱动团队决策的3到4个高层战略主题是什么?”
Common Mistakes to Flag
需要警惕的常见错误
- Reacting solely to user feedback - Common user requests are usually table stakes and rarely lead to the novel innovations required for sustainable differentiation.
- Prioritizing speed bumps for users - Building features for management reporting often introduces friction into the primary user's day-to-day workflow, leading to feature bloat.
- Maintaining fragmented roadmaps - Keeping separate documents for design, product, and engineering fragments accountability and prevents true cross-functional alignment.
- Falling into the planning fallacy - Asking engineers for time estimates often leads to over-scoping; it is better to define a fixed appetite and reduce scope to fit.
- 仅对用户反馈做出被动响应 - 常见的用户需求通常是基础必备项,很少能带来实现可持续差异化所需的新颖创新。
- 优先给用户设置“减速带” - 为管理层构建报表功能往往会给核心用户的日常工作流带来摩擦,导致功能膨胀。
- 维护碎片化的路线图 - 为设计、产品和工程团队分别维护独立文档,会割裂责任归属,阻碍真正的跨职能对齐。
- 陷入规划谬误 - 要求工程师给出时间估算往往会导致范围过大;更好的做法是定义固定的投入意愿,再缩小范围以适配。
Deep Dive
深入了解
For all 50 sourced insights from 24 guests, see
references/guest-insights.md如需查看来自24位嘉宾的全部50条来源见解,请参见
references/guest-insights.mdRelated Skills
相关技能
- Goal Setting Okrs
- Planning Cadence
- High Stakes Decisions
- Evaluating Trade Offs
- 目标设定与OKR
- 规划节奏
- 高风险决策
- 权衡评估