| "1. Start tracking and improving performance based on relevant metrics I'm talking about bounce rates, conversion rates, click rates, followers, value per visit, return on investment on ads, customer satisfaction, and so on. Granted, some of those are vanity metrics, but we'll touch on that another day." "based on relevant metrics"; "some of those are vanity metrics"; rage quit. Aside from that, the point he's making is superficial. There are certain, very important, things that are extremely difficult to track back to a simple metric. This argument comes up all the time in code refactoring. You can't tie a refactor back to a trackable metric like what he's pointed out. However, refactoring code can lead to many performance boosts, such as decreased bugs and faster development of future features. But this is very difficult to attach a number to. You can't say "for every X lines of code we refactor we diminish future feature development by 10% and reduce bugs by 50%". It's just not possible. Also noting that things like "customer satisfaction" or "number of bugs reported" weren't on this guys list of "relevant metrics". Neither were items like "employee happiness" or "pride in your work". Look, I'm a big fan of data-based decisions, but that can't be the end-all-be-all of your decision making process. Honestly, just the first point of this article makes it sound like working for this guy would be like working in a development sweat shop. So, nope, not even reading your other 2 points because your first one is just that bad. |