4 ms·
> "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 out
by jph 4y ago
> "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".
- kevsim 4y agoCo-founder at Kitemaker here. You're exactly right. However, when people start micro-splitting deliverables down into tasks, those metrics and outcomes tend to get lost in the shuffle. 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.
- SigKill9 4y agoThanks for your comment! Don't disagree, but issue trackers are mainly designed to make you track (individual) tasks. If you make your issue represent outcomes, we have found that teams often feel like they are trying to force a square peg into a round hole. Your mileage might vary, though :)