I’m personally convinced that these companies are selling products that harm the companies that use them rather than help them. Using productivity metrics to measure individuals this way is akin to incident retrospects that identify human error as the root cause. It’s performative, and if you want to blame someone then just go ahead and blame someone, don’t waste your time getting arbitrary metrics to support it.
The real need here is capturing the data to support learning, and learning happens in batches. It’s useful to look at how the defect rate compares across teams, as long as you dig into understanding what those teams do differently.
Passages saved from iOS
from
Filed under:
Same Source
- most people “take far too much pleasure in their beliefs to give th...
- One of the consequences of demateralisation is that things that “re...
- What we call history is, in practice, what we can bear to think abo...
- A general heuristic I’ve come to use to ascribe “value” to (a porti...
- Find the best teachers and take all their classes, no matter the su...
- Census figures show there are 40,000 more Latinos in Chicago than a...
- Chicago remains the third largest city in the country with a popula...
- View all
Related Notes
- By replacing integration tests with unit tests, we're losing al...from Computer Things
- To determine what actions you can take to drive meaningful change i...from Ken Britton
- The only good advice I have here is to re-evaluate your metrics oft...from ferd.ca
- A product is useless without a platform, or more precisely and accu...from gist.github.com
- Potential SLIs for different types of components - Request-driven ...from Steven Thurgood and David Ferguson
- [Noriaki Kano](https://en.wikipedia.org/wiki/Noriaki_Kano), a Japan...from Folding Burritos
- As incidents continue to occur, teams generally respond by starting...from GitHub
- In order to uncover our customer’s perceptions towards our product’...from Folding Burritos