product teams deliver outcomes, not ouputs
post: steve messer
introd: A colleague at Government Digital Service recently told me that they’d adopted objectives and key results (OKRs) in their team, but they were struggling with the objectives (plural) their leadership had set. The objectives just described the things that the leadership team wanted them to do rather than problems to solve. They had been given a list of outputs, not outcomes. This meant the team was finding it hard to buy into the mission and worried they might not explore the problem space enough.