你的工作是帮助你的团队说不。
Your job is to help your team say no.
你可能没有能力单方面做出决定，对某个特定的变更说不，但你可以帮助你的团队做出选择。
You may not have the ability to unilaterally make a decision to say no to a particular change yourself but you can help your team choose.
要做到这一点，您首先需要清楚的、毫不含糊的目标（谢天谢地，到此时，您已经设定好了）。
To do so, you first need clear, unambiguous goals (which you’ve thankfully already set at this point).
接下来，您可以为他们提供一个决策框架，以帮助他们根据相对重要性对工作进行排序。
Next, you can provide them a decision-making framework to help them rank the work by relative importance.
当你在为某个个人项目工作（比如婚礼或家庭翻新）时，最好的确定工作优先级的方法只是简单地根据偏好。
When you’re working on a personal project such as a wedding or a home renovation, the best method for prioritizing work is simply by preference.
与您的主管领导们一起工作，列举所有花钱或延长时间的事项，然后强制按顺序排列。
Work with your sponsors to enumerate all the items that cost money or extend time, and then force rank them in order.
当你们做这事儿的时候，你们就创建了能见度，能确切地看到他们将得到的该清单上有多少事项。
When you do this, you create visibility into exactly how many items are on the list that they will get.
这样，就使人开始觉得，那些排名垫底的事项更容易被砍掉。
The ones at the bottom of the list start to feel easier to chop.
在为产品开发项目设置功能优先级时，主要考虑这两个维度：速度和影响。
When setting feature priorities for a product development project, consider, primarily, these two dimensions: speed and impact.
根据您的项目所处的阶段，您对速度进行的测量内容和你对影响进行的测量内容可能有所不同。
Depending on the phase of your project, what you are measuring for speed and what you are measuring for impact may be different.
在项目的早期阶段，学习通常是最重要的，因为学习将在您计划构建的内容中发挥关键作用。
In the early phases of your project, learning is often the most important, as learning will play a key role in what you plan to build.
因此，您将优先考虑能够给予您最快进行学习的能力的那些测试。
Therefore, you’ll prioritize tests that will give you the ability to learn the most quickly.
当你在打造一个全新的产品时，增长潜力通常是决定首先做什么的主要驱动因素。
When you are building a brand new product, growth potential is typically the main driver for what to do first.
因此，您需要优先考虑对增长具有最大潜在影响的产品，以便能以最快的速度推入市场。
Therefore, you’ll want to prioritize products with the highest potential impact to growth that you can get into market the fastest.
一旦您的项目启动，并且那些软件程序错误或迭代增强需要需要优先考虑，那么最大的问题通常是用户影响。
Once your project has launched, and bugs or iterative enhancements need to be prioritized, then the biggest concern is typically user impact.
影响最多用户的程序错误通常也会转化为对收入影响最大的程序错误。
Bugs that impact the highest number of users will usually also translate to those that have the biggest impact on revenue.
因此，您会想要解决那些影响最多用户、你能首先最快解决的问题
Therefore, you’ll want to tackle the issues that impact the most users that you can resolve the fastest first.
最后，如果您正在优化或稳定某个已经发布的项目，您将需要针对获益所需时间，去权衡（从所提议的那些更新中你能获得的）风险或节省。
Finally, if you are working to optimize or stabilize a project that has already launched, you will want to weigh the risks or savings you can gain from the proposed updates against the time to get those gains.
Speed vs. impact types.
速度与影响的几个类型
图中文字翻译如下：
检验某个假设新产品
学习影响
最可能快速给你重大的学习的那些测试应该优先考虑。
最快学习
增长潜力
应优先考虑最有可能迅速成为增长的重大杠杆那些功能。
最快推向市场
功能及软件错误稳定与优化
用户影响
应优先考虑影响最多客户并且最快修复的那些问题。
最快修复
节省或风险
应优先考虑具有最高风险或节省并且能最快构建的那些问题。
最快节省
一旦你决定了对于速度和影响，你分别要测量什么，那么，取决于你的团队的风格，有两种有用的方法可以采用。
Once you have determined what you are measuring for speed and for impact, then there are two methods that are useful to try depending on your team’s style.
第一种是最轻量级的，但是需要便利贴和一面墙。
The first is the most lightweight, but requires Post-it notes and a wall.
我喜欢用便利贴，所以，这是我偏爱的方法，如果我能使人们当面在那些优先级上进行协作。
I love Post-it notes, so that is my preferred method if I can get people to collaborate on the priorities in person.
为了确定工作的优先级，你只需要写下所有的想法，然后，将它们绘制在一个纵轴是速度，横轴为影响的网格里。
To prioritize the work, you just write down all the ideas and then plot them on a grid that has speed on a vertical axis and impact on the horizontal axis.
在右上角里的事项是那些既是最快又是具有最大影响的事项。你应当总是先做这些事项。
The items in the upper right-hand corner are those that are both fastest and have the highest impact. You should always do those first.
其左边的那些事项具有影响但可能花费更长时间，应当在其后排序。
The ones to the left that have impact but may take longer should be prioritized next.
那些具有影响小但速度快的事项，可完美地归属于产品【积压、待办】需求列表，这样，在你有一些额外时间时，可以随时将它们取出来。
The ones that have low impact but are fast are perfect for product backlogs, so that they can be pulled in anytime you have some extra time.
最后，那些影响小、耗时长的事项可能会被搁置。
And finally, the items that have low impact and take a long time should likely be put aside.
未完待续
