[irjustin]

> I find OKRs a little excessive for a small team

Can you explain this one a bit more? Are there specific pitfalls of the OKR system that don't work well for small teams?

Is it purely a size of the organization as a whole? i.e. If the whole company is <10 OKRs don't work. Or is it inclusive of team size? Any group/unit of <10 should not use OKRs, too single metric heavy.

[BrianOnHN]

For context, my understanding of OKRs is limited to the reading of "Measure what Matters."

In my understanding, OKRs are dependent on organizational clarity of the mission, vision, and metrics.

Now I'm sure there are plenty of teams that have matured in their space and have this organizational clarity.

But when I was referring to small teams, it was in the context of "we're small now, but if we make this work, we'll be bigger."

In the latter, decisions are going to be more bite-sized. And going through the OKR exercise could take as much time as the execution of the tasks.

Edit: in other words, OKRs are great for well-defined outcomes, where the time required is longer than what would be expected from an individual contributor during a week-long sprint.