ONE THING on Scary OKRs Story

Just in time for Halloween, we have a scary Objectives and Key Results (OKRs) story! In this ghost story, different departments are at cross purposes! Evil cackles all around...

I once worked with a company where the QA team was rated (and bonused) on the number of bugs filed. Meanwhile, the developers were bonuses for shipping on time, and the Product team was bonused on how many features they shipped.

Notice that no one was rated on whether customers were happy!

To measure OKRs intelligently, ratings should be at the product level, with all departments aligned on one set of metrics.

Got any scary Halloween incentives stories?(Points for creaky doors, spider webs, zombies, etc.) Discuss.

Events
I'm giving a free talk on "OKRs for Product Teams" with the folks at Product Focus on November 2. Register!