4 ms·
> Difficult to couple OKRs with tasks Depends perhaps on what you mean by “task”, but I don’t get this one. Surely your OKRs are how you measure success of mos
by asplake 5y ago
> Difficult to couple OKRs with tasks
Depends perhaps on what you mean by “task”, but I don’t get this one. Surely your OKRs are how you measure success of most of what you do that quarter, and there are only a few of them. What value does task-level tracking really add?
I’d go as far as saying that task-level tracking may be of value to the individual, but progress generally should be tracked at the level of deliverables and outcomes. When I was a manager, I made a point of not looking at task-level data. To focus on them is a recipe for micromanagement.
- ravenstine 5y agoNot the OP, but let's say an OKR isn't achieved; having insight into all the work that went towards that OKR might be useful in understanding either when the goal of the OKR is met or whether the OKR should be reevaluated. I'm not saying that's a common thing to do, but I could see that being a case where task-level information would be beneficial.
- qudat 5y agoThanks for the feedback! The leaf of a circle heirarchy doesn't necessarily need to be a task -- that's just how many orgs operate. The theoretical OKR feauture-set of Wormhole could simply be a place for message boards, docs, and a way to manually add metrics. You could reference other circles inside an OKR circle if you'd like, but it's not mandatory. The main critique about OKR software that I don't like is that it's a separate system from where things get done. When thinking about a product team and having an OKR set, it's sometimes beneficial to think about what the team is doing every week that helps them achieve their OKRs.