Nice take. Busy work without a clear objective spanning multiple tasks and milestones is a known trap teams can fall into. But I’ll do you one better: how about thinking on what outcomes are desired, and then figure out both goals, scopes and tasks. What do you think?
I don't watch a lot of movies. Would you be able to share the name of that movie you've referenced via the poster?
The Holdovers, also added it to the text. If you watch it lemme know!
Excellent advice!
Nice take. Busy work without a clear objective spanning multiple tasks and milestones is a known trap teams can fall into. But I’ll do you one better: how about thinking on what outcomes are desired, and then figure out both goals, scopes and tasks. What do you think?
A goal can be an outcome, but a goal doesn't have to be an outcome. It also depends on what definition of outcome you're using.
Seiden's definition: "A measurable change in human behavior that drives business results."
Not every change on a product alters human behavior or drives business results. But that doesn't mean it isn't important.
E.g. reducing technical debt may fall in this category. Refactoring a piece of code so it's easily to modify in the future.