> "why can’t issues represent outcomes?"
They can and should. And it turns out that teams can improve an existing task writeup simply by adding an explicit outcome goal and metric, such as: "Aim for outcome X as measured by Y".
They can and should. And it turns out that teams can improve an existing task writeup simply by adding an explicit outcome goal and metric, such as: "Aim for outcome X as measured by Y".
The way we're structuring things in Kitemaker (large, collaboratively edited work items) is an attempt to prevent that. But of course it's not the only way to achieve it.
Awesome if you can make it work in your current tool of choice! As the article mentions, another way teams have solved this is by augmenting their issue tracker with a document-based tool like Notion or even Google docs and motivating their team to stay on top of those outcomes.