9 ms·
I’ve watched this backfire, too. It works great when everyone is delivering day-long or week-long incremental features that lend themselves to nice screenshots
by Aurornis 3y ago
I’ve watched this backfire, too.
It works great when everyone is delivering day-long or week-long incremental features that lend themselves to nice screenshots.
But then you slowly start accumulating a backlog of difficult tasks that everyone avoids because they won’t sound good for the week. Technical debt accumulates as people cut corners in the interest of getting their weekly presentations out.
You can theoretically avoid it with enough trust, but the trigger for our collapse was a round of layoffs where the people with the most visible features were spared while people working on important backend work and bug fixes got cut. After that, it was game over.
- yathaid 3y agoNothing in OPs comment says it should only be completed stuff that goes into the status. Also, if your team is optimising for the status report, your manager has already failed you.
- fjfuvucucuc 3y agoYes. The manager has failed you. Doesn't mean you should put your ass on the line to fix things for the business. That's why these kind of incentive structures are dangerous and why things like OKRs put such heavy emphasis on regular, company wide, failure. (I.e. they punish 100success rates)
- ranting-moth 3y agoAurornis didn't say that. He specifically said "because they won’t sound good for the week". With time and experience, you'll learn that those who can quickly churn out features and bug fixes are deemed extremely valuable to the company. Let's say we have a wicked bug that has very little chance of happening. But if it does, it'll bankrupt the company, no questions asked. Spending 3 weeks fixing it is nowhere as impressive to the company as Joe who's churned out 10 features per week while your status updates are "Hunting for the wicked bug", even if you describe it it more details.
- neeleshs 3y agoEven if the detail was something like, "if this wasn't fixed, we were at the risk of losing half our customers" ?
- nine_zeros 3y ago> Even if the detail was something like, "if this wasn't fixed, we were at the risk of losing half our customers" ? Yes, because this one task appears as a single line item for the manager's manager. They don't care for the complexity or consequences until the fire actually happens. And if the fire happens, they just blame engineers. If the industry incentives were changed such that manager heads would roll for mass outages, managers would start appreciating big fixes.
- withinboredom 3y agoIf you spend more than a few hours looking for a bug, you should start writing code to go around the bug completely. Even if it results in technical debt, if the company can go under if the bug isn’t fixed, you’d be stupid NOT to charge that TD card. That’s why devs who understand that survive layoffs and the ones who spend three weeks “hunting for an extinction level bug” don’t.
- yathaid 3y agoYou are describing a situation where management has failed. No amount of better practices can help in a situation where your management chain cannot evaluate your work correctly.
- commandlinefan 3y ago> if your team is optimising for the status report If you're providing a status report, you're optimizing for the status report. Period.
- DiggyJohnson 3y agoEh, my personal experience has been that just as often we have a mandatory status report that nobody cares about (including my direct and skip level managers). It's just something that needs to be done for contract compliance.
- yathaid 3y agoI admire the confidence with which you hold this opinion. Engineers are not providing status reports. The manager is collating them. How is it any different to a sprint summary?
- osigurdson 3y agoThis is why management needs to be technical. Otherwise you just end up with feature, feature, feature … death.
- javajosh 3y agoTechnical and smart. Otherwise you end up with fix tech debt, fix tech debt, fix tech debt ...death.
- kaashif 3y agoI have also seen refactor, refactor, refactor, oh actually it's now no better than before. Whoops! It's like imaginary tech debt.
- javajosh 3y agoOr even worse than before - and the sad part is that no-one intended that to happen. All bespoke software is effectively an experiment that may fail. I've become a lot more wary of the "failure is good" mantra that SV is famous for - it's not good in a zero-sum game where labor is spent on stuff that gives no value, and refactoring for DX is definitely expensive but only possibly valuable.
- manvillej 3y agoThis is why management needs to be competent. Average CEO is 58 years old. Their first jobs were in the late 1980s. The economics and tactics around technology has been revolutionized a dozen times over in the last 4 decades. Now, maybe a few rare individuals have kept up, but most likely, they all rely on outdated strategies from out of touch MBA programs & buzz words. Its the same reason the market kills public technology companies' innovation and they rely on acquisition. Its like gunpowder has just been invented and leadership still wants large formations marching against each other. "what if we invested in medical training and add washing our hands so we can keep more people alive?" "nah, more guns and marching"
- 3y ago
- the_snooze 3y ago>You can theoretically avoid it with enough trust I think it ultimately comes down to human values. What's important to the founders and the team? Do they have a clear articulation of those values? KPIs are useful if they're grounded in values that the organization absolutely won't compromise on; KPIs should be a means to an end, not the end themselves. Whether those values are "we want to make the most money" or "we want to make customers happy" or "we want a sustainable lifestyle for our team," KPIs will only help you pursue them, not define or prioritize them.
- marcosdumay 3y agoHere is the thing, in a high-trust environment, KPIs work fine too. In fact, almost everything work on that condition. But modern organizations are quick to destroy trust on any whim.
- Consultant32452 3y agoThe place I'm consulting for at the moment shut down offices for years due to the pandemic. Some people moved out of state and continued to work because there was no signal of ever returning to the office. Then last week they said everyone had to return to the office 3 days per week or be fired with no exceptions. We're losing an MVP on our team due to this. He now lives over 500 miles from the closest office.
- cesaref 3y agoThe way around this is to open an office just for them. It sounds dumb, but it meets the business requirement, and could also drive further recruitment around their location.
- meowface 3y agoIt seems like it'd be way more sensible and efficient to just make an exception for that particular employee (and maybe some other important ones). Though, in my opinion, the best option is to just let anyone work remotely as much as they want. Especially if you go years without ever indicating you intend to return people to the office. I think I'm luckily grandfathered in due to working fully remotely for years before the pandemic, but if that happened to me I would absolutely start looking for a new job.
- criddell 3y agoThat can be more expensive than it appears at first, especially if it's in a different state due to taxes. I've asked before if I can work remotely for a few weeks at a time and have been told yes, as long as I don't leave the state. In some places, just moving to a different county or city can trigger different tax requirements.
- efxhoy 3y agoThere are two types of devs at my job, those that care about shipping lots of new things fast, using new frameworks and pushing metrics. Then we have me and a few others fighting fires that the fast shippers leave behind. I’m fine with it, I enjoy analyzing database queries and figuring out what to index. As long as manager understands where the fires are coming from and why we need to spend time putting them out there’s no problem.
- ryandrake 3y agoUnfortunately, at far too many companies, those "ship new things fast" developers are the ones who get promoted, get rewarded with the best projects, and grow their careers and influence, while the firefighters just keep fighting fires.
- ants_everywhere 3y agoI'm curious if anyone has stories about making this work in the long run. It seems like such a natural division of labor that it appears everywhere. But I also feel like I've never seen a company explicitly optimize processes around it. So I'm curious to hear any battle stories.
- OkayPhysicist 3y agoThe problem that I'd imagine is a variation of "Why does Sales get paid so much?". Basically, the more obvious the connection between your contribution and the company making more money, the easier it is to reward you with a slice of the pie. In a codified "trailblazers and firefighters" model, the trailblazers are much more obviously tied to the company's bottom line. Feature X is required to close deal with company Y, this software team built this feature. Meanwhile, the people frantically cleaning up the mess the first team left is only nebulously connected to the company raking in more cash, relegating them to a second-tier position despite having harder work.
- spacemadness 3y agoYes, our team asks for demos every sprint which I find to be dumb and a remnant of every sprint needing a MVP when in practice that is just hilariously naive. Especially considering a screen that took 10 minutes to make is considered much more interesting than code that is more detailed really doesn’t lend itself to a “demo.”
- ChrisCinelli 3y agoWithout an outstanding company culture, most KPIs are almost useless. While working at a big corporation we had a velocity initiative supposedly aimed to lead the company toward continuous integration. "How long a PR stays open" was one of the KPIs in a dashboard. I said: "Be careful with that!" People started to close PRs and reopen new PRs with the same code. Middle managers and sometimes the person in the division that was the point of contact for the velocity initiative were asking to do that. The script measuring this KPI was improved to look at the branch name and the code diff. Result? People changing branch name and a change of EOL encoding in the new PR. Learnings? B and C players with questionable ethics screw companies quite rapidly. In this climate KPIs and aligning them with company values is futile.
- rented_mule 3y agoWhen I worked at a FAANG ~15 years ago, a new VP came in and heard, correctly, that our group didn't have enough automated tests. He created a requirement that every developer commit two new tests to the code base every workday. He had automation put in to monitor our compliance. Within a couple of weeks, scripts were circulating to auto-generate and auto-commit tests. If the JVM we were using had a bug in adding random numbers together, we'd have known about it very quickly. That's about the time I decided I should move on. I'm glad I did. The company I joined treated developers like adults and developers acted like adults. And we had great automated test coverage. Obligatory mention: https://en.wikipedia.org/wiki/Goodhart%27s_law https://en.wikipedia.org/wiki/Goodhart%27s_law
- networkchad 3y agoI’ve often wondered what is the solution to Goodhart’s law. Obviously a business can’t abandon metrics. Perhaps this is where qualitative management skills come into play - humans in the loop making good decisions instead of blindly marching to the output of an automated reporting system.
- bumby 3y agoI'd argue that the point Goodhart's law isn't that metrics are bad, but that all metrics aren't created equal. In the case above, it seems like the real goal was improved code quality. Number of unit tests isn't the best proxy for that goal, so it wasn't the best choice of metric. You don't want developers creating tests for the sake of creating tests. (There's some irony here in that it's not the type of behavior I'd ascribe to professionals). The "solution" is a metric that's a better measure of what you actually want.
- hliyan 3y agoSome examples of incrementally delivering tech debt and communicating it to stakeholders: "This week we found the root cause of why operation X sometimes fails - it's a slow database query which we plan to fix next week. For those interested, here's a command-line demo of the issue." "With 60 pull requests being submitted per week, and each one triggering a 12 minute automated test run, we were wasting a quite a bit of developer resources. This week we brought that time down to 4 minutes. For those interested, here's how we parallelised the tests." "Remember how the last accounting feature broke a lot of different parts of the system and it took 4 extra weeks to fix? This week we migrated 4 out of 18 core accounting functions to a service completely separate from our main code base. Once the remaining 14 are moved over during the next three weeks, accounting features can be built and tested independently without affecting the main system."
- ChrisCinelli 3y agoWhen you give people a target and it is the ONLY thing they care about, people find a way to hit it. So be careful what you measure and you reward. For every company cash flow and profits are undoubtedly the most important metric. It is almost impossible to argue that maximize those numbers should NOT be a goal. At the same time when that becomes the ONLY target that matters, the consequences are dreadful. At least in US, that is how we ended up with appliances that only last a small fraction of time that used to last 40 years ago. And even worse it is how we ended up with the food industry creating more and more addicting food resulting in 70% of the population be obese. And it is how we ended up with a heath system that costs multiples of what costs in any other country in the world, that, instead of healing people for good, make them "less sick" addicting them to a few pills for the rest of their life. Because there is no money to be made with a healthy person. When you build KPIs, make sure you "think a few moves ahead" and you put other correcting metrics and checks in place. At least make sure who establishes the metrics has a way to become aware of the possible shortcomings and plan corrections in a timely manner.
- HWR_14 3y ago> For every company cash flow and profits are undoubtedly the most important metric. It is almost impossible to argue that maximize those numbers should NOT be a goal. Except for VC backed startups. Actually, there are a lot of exceptions. But those mostly revolve around caveats surrounding riskiness and timelines.