The Most Important Characteristics of High-Performance Teams

leadership.garden

13 points·ochronus··5 comments

What exactly is "high performance" in this context? As far as output is concerned, I can only find this in the article:

> meet their goals consistently

And how do we reach the goal? Through a series of aspirational assertions, accompanied by hand waving.

How are being "team first" or "continuous learning" always prerequisites for meeting goals consistently? I can only assume the answer has something to do with faith, because it isn't at all clear here, though the author seems quite earnest.

I think, way way down, it highlights these metrics:

Deployment frequency: How often an organization deploys to production.

Lead time for change: The time it takes to get committed code to run in production.

Change failure rate: The percentage of production deployments leading to degraded service and remediation (e.g., rollback).

Time to restore service: How long it takes to fix a failure in production.

I don't understand how deployment frequency is a useful metric.

It's not a silver bullet but in usual agile scenarios it's a good proxy for CI/CD health and velocity. Smaller, continuous daily deliveries usually mean easier experiments, testing, deployment, and rollback if something goes wrong (of course, depending on other factors). Metrics are not 'useful' in themselves, it's about how you use them. If you feel it doesn't make sense for your scenario, simply don't use it :)

This stock photo is giving me claustrophobia.

Reply on news.ycombinator.com