第十五章 Move On 繼續前進¶
Let the storm pass 讓風暴過去¶
Shipping can actually generate new work if you’re not careful. Feature releases beget feature requests. Customers say “Okay, that’s great, but what about that other thing we’ve been asking for?” Bugs pop up. Suggestions for improvements come in. Everyone is focused on the new thing and reacting to it.
如果不小心，發佈新功能反而可能會產生新的工作。功能發布會帶來更多功能需求。客戶會說：「好的，這很棒，但那個我們一直在要求的東西呢？」錯誤會出現，改善建議也會湧入。每個人都集中在新功能上，並且對其作出回應。
The feedback can be especially intense if the feature you shipped changes existing workflows. Even purely visual changes sometimes spur intense pushback. A small minority of customers might overreact and say things like “You ruined it! Change it back!”
如果你發布的功能改變了現有的工作流程，回饋可能會特別強烈。即便是純粹的視覺變更，有時也會引發強烈的反彈。一小部分客戶可能會過度反應，說些像是「你把它搞砸了！把它改回來！」的話。
It’s important to stay cool and avoid knee-jerk reactions. Give it a few days and allow it to die down. Be firm and remember why you made the change in the first place and who the change is helping.
這時保持冷靜並避免本能反應是非常重要的。給自己幾天時間，讓情緒平復下來。要堅定，並記得當初為什麼做出這個改變，以及這個改變是為了幫助誰。
Stay debt-free 保持無負債¶
It can be tempting to commit to making changes in response to feedback, but then you no longer have a clean slate for the next cycle. Remember: these are just raw ideas coming in. The way to handle them is with a gentle “no.” Saying “no” doesn’t prevent you from continuing to contemplate them and maybe shape them up into future projects. Saying “yes,” on the other hand, takes away your freedom in the future. It’s like taking on debt.
面對回饋時，可能會很容易承諾進行改動，但這樣會讓你在下一個循環中失去一個乾淨的起點。記住：這些只是進來的「原始想法」。處理這些想法的方式是輕柔地說「不」。說「不」並不意味著你不能繼續思考它們，或許未來可以把它們形塑成新的項目。而說「是」，則會奪走你未來的自由，就像承擔債務一樣。
Remember, the thing you just shipped was a six-week bet. If this part of the product needs more time, then it requires a new bet. Let the requests or bugs that just came up compete with everything else at the next betting table to be sure they’re strategically important.
記住，你剛剛推出的東西是一個六週的「賭注」。如果這部分產品需要更多時間，那就需要重新下注。讓這些剛剛出現的請求或錯誤與其他所有事項一起競爭，進入下一輪「賭桌」，以確保它們在策略上是重要的。
Feedback needs to be shaped 反饋需要塑形¶
Here we come full circle. The raw ideas that just came in from customer feedback aren’t actionable yet. They need to be shaped. They are the raw inputs that we talked about in step one of the shaping process: Set Boundaries.
回到原點。剛從客戶反饋中收到的原始想法還無法直接執行。它們需要進行精煉。這些正是我們在塑形過程的第一步中所提到的原始輸入：設定邊界。
If a request is truly important, you can make it your top priority on the shaping track of the next cycle. Bet on something else for the teams to build and use that time to properly shape the new idea. Then, when the six weeks are over, you can make the case at the betting table and schedule the shaped version of the project for the greatest chance of success.
如果一個請求真的很重要，你可以將它作為下一個週期塑形階段的首要任務。選擇其他內容作為團隊的建設重點，並利用這段時間來妥善塑形這個新想法。然後，在六週結束後，你可以在賭注桌上提出這個想法，並將經過塑形的版本安排在最有可能成功的時間點。