5 ms·
If you are in operations, regardless of what kind exactly, a proper set of metrics is a basic necessity to succeed. Without data, and proper metrics built aroun
by hef19898 4y ago
If you are in operations, regardless of what kind exactly, a proper set of metrics is a basic necessity to succeed. Without data, and proper metrics built around them, you are running blind and every single decision, no matter how well informed you think it is, is just based on gut feeling. Granted that gut feeling can be good (I dare to think mine isn't to bad) but there is no way to tell whether your gut is right without metrics and data to back it up.
Pretending otherwise is just lying to yourself. It is very easy so, to convince yourself you actually have good metrics and data. That could be called "Spreadsheet Mentality", even I think actual spreadsheets are way better than highly sophisticated data analysis tools.
- bertil 4y agoThat’s the distinction that I make between having a complex set of KPIs that cover all the organization (which tend to alienate any challenge, what the author laments) and simple team objectives (that are only relevant for the team, and intentionally miss a lot of the complexity in the rest of the organization).
- hef19898 4y agoIf you metrics system fails to connect goal and performance measurement on the team level witu the bigger goals, I'd say the metrics systems is badly degined and implemented.
- avereveard 4y agoYou also need to make sure the process has the tool to improve in the metric it's measured, otherwise it's just going to be generating churn Like I've seen dev getting measured on sales goals. Sure the bigger goal is important, but devs what are supposed to do with that?
- hef19898 4y agoGreat example of a bad metric. Even if the dev would work for sales, he would at max drive sales indirectly. And if something is only influenced indirectly it is a bad metric use case.
- michaelt 4y agoConnecting things it's possible to usefully measure with the bigger goals is an insurmountable problem in almost every business, because some things are much easier to measure than others. For example, it's very easy to measure if the call centre answered a highly efficient N support calls per worker-hour. And it's very difficult to measure if people who deal with the call centre end up badmouthing your company to their friends, because your useless call centre always just tells them to reboot and never does anything to resolve the underlying issue.
- Archelaos 4y agoI think what the author meant by "spreadsheet mentality" is not the belief that metrics may be necessary, but that they are (more or less?) sufficient.
- cupofpython 4y agoIn addition to this, metrics do not need targets. repeating for emphasis: metrics do not need targets. You absolutely need measurements and data, and to highlight trends.. but target metrics are almost always bullshit. It reminds me of a psychology study done on kids that I wish I had the source for. IIRC when asked to perform a task for no reward (like, how many simple math problems can you solve in a minute?), many performed it well. then they gave the good performers gold stars. Immediately, the kids not getting stars started performing worse than originally. Then they took away the gold stars. Now the top performers started doing worse as well. People just want to be seen and heard. Measure the things that are important WITHOUT deciding in advance what is considered a "good job". this way you can do your 1:1 on the whole picture. "you're slow, but your quality is exceptional" The only exception to this is if the work is simple enough that you can measure it directly against your $$$, and you have a target that ensures you are green. Like maybe a strictly data entry position for a very consistent source of data. In this case, there arent 1:1's to be expected with your employees.. they either hit target or get fired.
- hef19898 4y agoTrue, if a metric has a target the metric is the target. If there ever was an incentive to game a KPI, that is it. SPC is tricky case in that regard. Because it, kind of, makes the trend and long term development of metric the target. Edit: You had me thinking. Settng a target, or rather target tolerances, for a metric can be necessary if that metric is directly measuring the output of one process that is used by another process. E.g. forecast accuracy, if downstream ops are expected to cope with, say, a deviation of 20 %, that tolerance kind of becomes the goal for the forecast accuracy. This is not some arbritary goal so. For me, setting limits on certain metrics is something different from a target. It is a thin line between those.
- cupofpython 4y ago> if downstream ops are expected to cope with, say, a deviation of 20 %, that tolerance kind of becomes the goal for the forecast accuracy. I think a forecasting target of 20% shouldnt be necessary unless you want to be around 19% deviation. Which might be the case if trying to reach 0% has diminishing returns and isnt actually cost effective. In other words, targets make sense when you are literally targeting a sweet-spot. If 0% deviation is desired, then the directive is still the same - try to be as accurate as possible. If "as accurate as possible" is consistently falling below 20% (which is the importance of measuring and data) then you need to address that. Maybe forecasting is broken or infeasible. On ops side, they might not be expected to handle deviations over 20%, but the directive is probably the same either way "do the best you can to manage the deviation". >For me, setting limits on certain metrics is something different from a target. It is a thin line between those. I agree with this in general. It can be tricky to communicate "here is a boundary that absolutely cannot be crossed, but keep in mind you should be nowhere near that boundary anyway" without it impacting peoples personal optimization strategies. You really have to weigh the consequences of what actually happens when that limit is reached, and if it's worth a possible depression of performance from the team.
- choeger 4y agoI would argue that software maintenance would also benefit from metrics. Heck, even development would. Unfortunately, maintenance is hardly ever done at all and sensible metrics for development are really hard to come up with.
- iso1631 4y agoI work in operations. Of course we have systems metrics, we know if our systems are playing up or not. We don't do metrics for people though.
- Karrot_Kream 4y ago+1. Metrics for systems have very clear benefits. It lets you know what's wrong and because systems are technical things, they (generally unless you run up against a work political boundary) have clear solution paths. People are nothing like technical systems.