From the Google examples: > a team is encouraged to set as goals about 50% more tasks than they are likely to actually accomplish. > If a team scores signific

From the Google examples: > a team is encouraged to set as goals about 50% more tasks than they are likely to actually accomplish. > If a team scores significantly higher than that, they are encouraged to set more ambitious OKRs for the next quarter. I lived through this in Scrum sprints. There is a baked in incentive to sacrifice some iterations every once in a while to ajust the average expectation, while keeping an overall positive look. Otherwise without having used it seems to me that OKRs are another rather plain tool that works for clever organisations but fails when applied dumbly. Is there anything specific to it that makes worst case scenarii better ?