News for hackers. Stuff that matters.
Re:What McKinsey got wrong about developer productivity by boxed on Tuesday October 24, 2023 @11:00AM (#38000147)
Another article missing the more fundamental point:

You can't measure any productivity that has any cognitive component.

Devs think it's ok when sales productivity is measured like this, and then they don't understand that this is the reason sales are selling features that don't exist. We need to all stand against this madness. This goes for teachers, sales people, programmers, doctors, everything.

Re:What McKinsey got wrong about developer productivity by ebiester on Tuesday October 24, 2023 @11:30AM (#38000538)
It's not that "devs think it's okay" - it's that we accept that sales thinks it's okay and we don't have the experience or judgement to say otherwise unless we've been in a sales org.

The fundamental point I think everyone misses is that as organizations get larger, the network cost of running is higher and nobody has solved that problem. Smaller problems are more quickly solvable and no amount of story points will change that.

Re:What McKinsey got wrong about developer productivity by dboreham on Tuesday October 24, 2023 @11:30AM (#38000547)
Lots of delusion and gaslighting in this area.
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @11:21AM (#38000420)
> You can't measure any productivity that has any cognitive component

Understanding and measuring productivity can be valuable to a business. Sure they can't measure productivity for some roles as precisely, simply, and accurately as say counting the number of jelly beans in a jar.

But that doesn't mean productivity can't be measured in a way that is useful to the business. There's just tradeoffs involved.

Re:What McKinsey got wrong about developer productivity by distortionfield on Tuesday October 24, 2023 @12:11PM (#38001233)
Anecdata but: In my almost ten years of software engineering engineering, I’ve never once seen an organization deploy developer productivity metrics and do anything useful with them except bludgeon developers that management already don’t like with the number that came out of The Machine ©
Re:What McKinsey got wrong about developer productivity by FireBeyond on Tuesday October 24, 2023 @01:04PM (#38002021)
Obligatory:

"Y.T.’s mom pulls up the new memo, checks the time, and starts reading it. The estimated reading time is 15.62 minutes. Later, when Marietta does her end-of-day statistical roundup, sitting in her private office at 9:00pm, she will see the name of each employee and next to it, the amount of time spent reading this memo, and her reaction, based on the time spent, will go something like this: Less than 10 min.: Time for an employee conference and possible attitude counseling.

10-14 min.: Keep an eye on this employee; may be developing slipshod attitude.

14-15.61 min.: Employee is an efficient worker, may sometimes miss important details.

Exactly 15.62 min.: Smartass. Needs attitude counseling.

15.63-16 min.: Asswipe. Not to be trusted.

16-18 min.: Employee is a methodical worker, may sometimes get hung up on minor details.

More than 18 min.: Check the security videotape, see just what this employee was up to (e.g., possible unauthorized restroom break).

Y.T.’s mom decides to spend between fourteen and fifteen minutes reading the memo. It’s better for younger workers to spend too long, to show that they’re careful, not cocky. It’s better for older workers to go a little fast, to show good management potential. She’s pushing forty. She scans through the memo, hitting the Page Down button at reasonably regular intervals, occasionally paging back up to pretend to reread some earlier section. The computer is going to notice all this. It approves of rereading. It’s a small thing, but over a decade or so this stuff really shows up on your work-habits summary."

--Neal Stephenson, Snow Crash

Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Tuesday October 24, 2023 @05:17PM (#38005754)
Thank you for introducing me to this!
Re:What McKinsey got wrong about developer productivity by ath3nd on Tuesday October 24, 2023 @01:04PM (#38002033)
In my 15 years of experience in software engineering, I've never found it either. I have, however, wasted 1000s of hours playing with poker cards and Fibonacci numbers instead of actually working. But I get paid for this, so, I guess: yay, end stage corpo capitalism!
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @06:54PM (#38006820)
I think this is a common misinterpretation that many people fall prey to. “It’s wasting my time so it must be bad.”

Your employers aren’t optimizing for your personal productivity and happiness. They don’t mind if you waste 1000s of hours with poker cards and Fibonacci numbers if their business goals are met. This can mean making one person upset and less productive if it makes progress towards a bigger goal.

Re:What McKinsey got wrong about developer productivity by distortionfield on Tuesday October 24, 2023 @07:36PM (#38007190)
But it doesn’t make progress towards the bigger goal. That’s their whole point.
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @09:18PM (#38007974)
All those companies failed to achieve their goals and went out of business?

Just because you don’t see the progress and don’t like the process doesn’t mean progress isn’t being made.

Re:What McKinsey got wrong about developer productivity by boxed on Wednesday October 25, 2023 @04:10AM (#38010458)
In business it's not about achieving your goals fastest, it's about not being the slowest. Just like running from a lion. This is why these businesses survive.

This is a common misunderstanding about market economies vs communism btw. In market economies there's a floor to the incompetence. In communism there is none. The ceiling isn't really different, but since there's a floor in one you will get a natural average higher in market economies. Pro-market people get this wrong all the time.

Re:What McKinsey got wrong about developer productivity by ath3nd on Wednesday October 25, 2023 @01:45PM (#38015730)
How is blindly emulating some practices that you just read about in a Scrum guide gonna contribute to the business goals of the company? The perversion of the industry is that sleazy manager/business/coaching/scrum types weasel their way into software engineering and somehow want both respect, attention, and people following what they prescribe is "THE WAY".

Imagine if the tables were turned. Developers present in all sales meetings and asking each individual sales person how much they think the call to this client is going to take in terms of story points. And how about we also go to HR and start interrogating them how many story points it takes to give somebody their office key? Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

After 15 years in the industry and being both an IC, a manager, and currently a VP of Engineering, I can confidently state that the best strategy one can take to achieve their business goals is to leave the software engineering to the software engineers and step the heck out of their way.

Wasting the time of people actually doing the work by arbitrary rituals you read about in a blog somewhere is not a good strategy for success. If we must go bother someone and treat them like children and force them to play cards, let's do it with another department for a change.

Re:What McKinsey got wrong about developer productivity by paulcole on Wednesday October 25, 2023 @02:40PM (#38016574)
> Imagine if the tables were turned. Developers present in all sales meetings and asking each individual sales person how much they think the call to this client is going to take in terms of story points. And how about we also go to HR and start interrogating them how many story points it takes to give somebody their office key? Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

I think we should do this!

> Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

A dangerous assumption to apply to all companies. Also the trick is deciding what "much less" looks like. Better hope you pick the right things.

I'm not saying it can't be done. It's just hard. And in some cases, you'd rather just be 10% less productive (but still productive) by following a process you hate.

Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Thursday October 26, 2023 @01:23AM (#38021901)
I like you.
Re:What McKinsey got wrong about developer productivity by mandelbrotwurst on Tuesday October 24, 2023 @11:20AM (#38000416)
> You can't measure any productivity that has any cognitive component.

Are you able to elaborate on why this is true please?

Re:What McKinsey got wrong about developer productivity by bane on Tuesday October 24, 2023 @11:23AM (#38000439)
How many units of thinking did you perform today? How do you charge or how are you payed per thinking unit?
Re:What McKinsey got wrong about developer productivity by RandomLensman on Tuesday October 24, 2023 @12:03PM (#38001098)
How much profit did that thinking create at the end of the year (or whatever the horizon is)?
Re:What McKinsey got wrong about developer productivity by Scarblac on Tuesday October 24, 2023 @12:27PM (#38001487)
I never understood how I'm supposed to know that.

The company as a whole makes a profit, how do you know what it would have been if feature X wasn't implemented? And ten people had a role in deciding to implement it, four in implementing it.

How can I possibly put a number on my contribution?

Re:What McKinsey got wrong about developer productivity by RandomLensman on Tuesday October 24, 2023 @12:52PM (#38001845)
You can at least start from the top: the overall thing you are working on, how much did that make? Are features you worked on a contributing reasons for a sale/how much extra did they bring? Are you directly linked to some sales because you provided something specific? If you are doing internal software, could be cost reductions associated with that or also additional business.

Your number won't be exact, but it doesn't have to be and double counting among the other people isn't always bad.

Re:What McKinsey got wrong about developer productivity by Scarblac on Tuesday October 24, 2023 @01:54PM (#38002727)
I make frontends for our products (that we sell to governments), but they're not what drives sales. Customers by our product got features of the backend, they assume there is some frontend. If I do good work users are happy, but they don't make the buying decisions either.

That I work on the front ends was only partly my choice, we all move around depending on where we need people at that time, and other people decide what needs to be implemented.

If we were to fire all developers, we would probably lose hardly any sales the first year. But over time, licenses would go down more and more. So part of this year's profit is due to the work of people who left us years ago.

I don't see any point in claiming some specific part of our profit. People would laugh at me, probably.

Re:What McKinsey got wrong about developer productivity by RandomLensman on Tuesday October 24, 2023 @01:58PM (#38002794)
You don't need claim, but you can at least associate with it. Even tracking happy users is a measure of sorts. It isn't an exact science and it doesn't need to be. And, yes, that isn't always fair to those gone from the company.
Re:What McKinsey got wrong about developer productivity by bane on Tuesday October 24, 2023 @01:02PM (#38002001)
Yup, it's a more or less worthless conversation, but one that many knowledge workers end up in.

I remember once being a similar conversation regarding a training program I was working on, and the customer was trying to assess the value of the training not on the improved performance of the employees, but on some measurable "knowledge unit" that had been transferred to the student (regardless of their ability to retain it).

It was beyond frustrating.

Re:What McKinsey got wrong about developer productivity by RandomLensman on Tuesday October 24, 2023 @01:10PM (#38002101)
If you think your contributions to the economics of a business are impossible to understand, then you are in a dangerous position (your admittedly bad experience notwithstanding).
Re:What McKinsey got wrong about developer productivity by bane on Tuesday October 24, 2023 @04:48PM (#38005331)
What I'm saying is that measuring output for knowledge workers in terms of some kind of unit other than business impact is not a great idea.
Re:What McKinsey got wrong about developer productivity by esafak on Tuesday October 24, 2023 @12:46PM (#38001750)
What if, as is usually the case, it created nothing until a whole team built the rest of the product that fits with my piece? What is the value provided by the front-end of a web app separately from the back-end?
Re:What McKinsey got wrong about developer productivity by RandomLensman on Tuesday October 24, 2023 @12:58PM (#38001944)
You can double count to some extend/doesn't have to exactly proportion but you worked on something that in the end had an economic impact.
Re:What McKinsey got wrong about developer productivity by staunton on Tuesday October 24, 2023 @12:03PM (#38001105)
That's not a good answer. We're not talking about thinking, we're talking about things with a cognitive component. Writing software has such a component and it's possible to tell if any software has been written (it's even sometimes possible to tell if it works or not).
Re:What McKinsey got wrong about developer productivity by bane on Tuesday October 24, 2023 @04:52PM (#38005391)
> You can't measure any productivity that has any cognitive component.
Re:What McKinsey got wrong about developer productivity by staunton on Tuesday October 24, 2023 @06:07PM (#38006349)
I'm not sure what you're saying...
Re:What McKinsey got wrong about developer productivity by bane on Tuesday October 24, 2023 @11:23PM (#38008788)
The irony of your joke took me a minute. Bravo.
Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @12:06PM (#38001141)
Obviously not.

The goal is to measure people's results. It might occasionally take a relatively-long time to find a seemingly-simple solution. But if an engineer /always/ takes a long time to find every solution, and upon inspection the problems were not actually difficult, then you most likely have a low-productivity engineer on your hands.

Re:What McKinsey got wrong about developer productivity by groone on Tuesday October 24, 2023 @02:41PM (#38003397)
That sounds really subjective
Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @03:35PM (#38004223)
Somewhat, but not entirely so. Managers can and should read git logs and bug tickets and design docs, and understand the architecture enough to have a reasonable sense of what the work entails. And managers should be engineers themselves and know that sometimes simple-looking work is actually very tricky… but at the same time it’s very unlikely that /every/ task looks like this.
Re:What McKinsey got wrong about developer productivity by boxed on Tuesday October 24, 2023 @03:23PM (#38004030)
The "solution" to a problem can be to totally redefine it. Another guy might redefine it EVEN MORE. So you get three people:

1. solved the original problem, took 2 days and thousands of lines of code 2. changed the problem, took 20 minutes 50 lines of code 3. changed the problem in another way, took 2 days and thousands of lines but this solution solved TEN problems

Now, which one is "better"? It makes no sense.

Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @04:32PM (#38005087)
In all your examples the solution came in 1-2 days. How about this common example? One guys merges one small change every week, of low complexity/difficulty by any measure. His teammate fixes several bugs every week, adds a feature or two also, and is on slack non-stop helping others out?

This is daily life in every tech company. It’s true that in some cases it’s hard to accurately rank between two people (because the work is multidimensional) but in many many cases the discrepancies in productivity are obvious.

Re:What McKinsey got wrong about developer productivity by boxed on Wednesday October 25, 2023 @04:07AM (#38010436)
No, case 2 took 20 minutes.
Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @12:02PM (#38001084)
> You can't measure any productivity that has any cognitive component.

So you're saying that it's impossible to measure developer productivity at all, since it's cognitive work? Strong disagree.

All of us here that work with other developers know that some of their peers get more done than others. Or conversely, that there's a few in the team who don't seem to get much done. The minute you make even that simple assessment, you've measured productivity.

One of the jobs of eng managers is to then make this measurement as accurately, realistically, and fairly as possible. This guides bonuses and raises, which should reflect people's contributions.

I'm not defending McKinsey's proposal here, but I agree with the general notion that it's possible to measure productivity and this is something management should always be doing.

Re:What McKinsey got wrong about developer productivity by Scarblac on Tuesday October 24, 2023 @12:24PM (#38001448)
But not very precisely. I know who is a lot better than others and who are a lot worse, but the rest are all in the pretty large group that is somewhere in the middle.

Especially because there are also skill differences and the differences in job title and salary that come with that. So the level of difficulty of the work people get to do is also different, and so on.

Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @12:33PM (#38001568)
Correct. It's brutally hard to measure with precision, in part because the work we do is so multi-dimensional. But it's not too difficult to divide people into at least three groups, of low, high, everyone-else.
Re:What McKinsey got wrong about developer productivity by tonyedgecombe on Tuesday October 24, 2023 @01:14PM (#38002152)
Yet I've seen plenty of companies that get that completely wrong. They will fire the most productive member of the team without realising what they have done.

The problem is people realise they can gain as much from playing political games as they can from improving productivity. Once that starts everything goes to shit.

Re:What McKinsey got wrong about developer productivity by hiAndrewQuinn on Tuesday October 24, 2023 @12:32PM (#38001565)
Even if you couldn't measure productivity exactly, it would be astonishing if you couldn't at least slap some kind of statistical distribution shape on it based off qualitative aspects of the work. Mathematicians have done it before.
Re:What McKinsey got wrong about developer productivity by boxed on Tuesday October 24, 2023 @03:18PM (#38003928)
It doesn't really work though. It's like measuring soccer based on goals or passes or some crazy shit. That's not how this works at all.
Re:What McKinsey got wrong about developer productivity by khazhoux on Tuesday October 24, 2023 @04:24PM (#38004956)
You’re saying there’s no conceivable way to discern which soccer players are better than others??

I don’t understand your position. Is it that all developers are equally productive, or that they do vary in productivity but it is immeasurable, an æther, with literally zero signals one could possibly mine to see how valuable a developer is to the team?

Re:What McKinsey got wrong about developer productivity by boxed on Wednesday October 25, 2023 @04:06AM (#38010425)
Team value is about bringing unique skills that can be a force multiplier. Measuring individual performance is antithetical to this very idea.

Soccer is a good metaphor because it's EASY to measure/see the value a good player that does not shoot a lot of goals make. In programming this is not the case.

It's certainly the case that managers that want hard numbers and don't know how to code won't be able to understand the situation at all. This is why this McKinsley nonsense is so dangerous.

Re:What McKinsey got wrong about developer productivity by hiAndrewQuinn on Tuesday October 24, 2023 @11:07PM (#38008703)
Or like modeling basketball games as random walks?

https://arxiv.org/abs/1109.2825

Re:What McKinsey got wrong about developer productivity by boxed on Tuesday October 24, 2023 @03:17PM (#38003914)
Peer review isn't measuring in this context. And often the value is hard to understand. I thought one guy on my team was clearly weaker than the rest... until I realized what he did that no one else did, which turns out freed up the rest of the team to do stuff we were great at.

"Better" isn't linear. It can multiply, and it can be highly dependent on the rest of the team.

Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Thursday October 26, 2023 @01:20AM (#38021888)
> until I realized what he did that no one else did, which turns out freed up the rest of the team

Can you elaborate?

Re:What McKinsey got wrong about developer productivity by barrysteve on Tuesday October 24, 2023 @02:08PM (#38002956)
I mean you can.

We take exams at school for basically the same reason.

You have to set up an institution or structured lessons to get the higher levels of cognitive measurement.

A company can use an educated guess for cognitive ability. Usually made up from completed tasks.

Selling features that don't exist is a side-effect of the company culture.

It's easy to observe the business culture in the West is often well divorced from academic truth seeking. As a matter of fact and good business.

Re:What McKinsey got wrong about developer productivity by boxed on Tuesday October 24, 2023 @03:20PM (#38003969)
Tests in school don't require creative problem solving. We can know this to be true, because if it did then checking the results would require it as well, which would mean we'd need 10x the number of teachers.
Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Tuesday October 24, 2023 @05:19PM (#38005785)
> Tests in school don't require creative problem solving

I’m not sure you can make such a broad statement.

Re:What McKinsey got wrong about developer productivity by staunton on Tuesday October 24, 2023 @06:16PM (#38006450)
> We can know this to be true, because if it did then checking the results would require it as well

This argument is blatantly false. (I mean the argument not the claim it's arguing for)

As just one counterexample, writing a mathematical proof often requires a lot of creative problem solving (it's not done a lot in school for this very reason). However, checking that a proof is correct is a rote task, even automatable (see proof asistants).