Pedro Arantes
HomeBlogMe

When Response Time Is Important, Measure Response Time

If the time on the critical path is worth a lot of money and a support group is on the path, you should measure the group on response time, not efficiency.
#agile
Zettelkasten, November 08, 2022.

Notes

If the time on the critical path is worth a lot of money and a support group is on the path, you should measure the group on response time, not efficiency.

Higher efficiency doesn't always lead to a fast response time because higher efficiency means not having waste, so the team doesn't have slack and operates at maximum capacity utilization.

If response times drive economics, you should align measurements and incentives for support groups to respond time. A straightforward way to move in this direction is to create a quality service agreement that spells out the response in time that users can expect from the department.

For example, in a development team, the developers are always on the critical path of projects. So you should measure how fast they respond to changes, not how many tasks they deliver in a week. This is the core of business agility.

References

  • The Principles of Product Development Flow
RecommendationsDo you want to see all posts instead?
Critical Path
Newsletter
On Tuesday (not weekly), I publish my most recent readings and thoughts. Subscribe to my newsletter if you want to follow posts about #startups, #product-development, #mental-models, and more.

By subscribing, you agree with Revue’s Terms and Privacy Policy.