3 ms·
If you build something that doesn't solve problems with impact to the business, your real productivity is zero. How does this account for that? https://blog.pr
by jaredsohn 2y ago
If you build something that doesn't solve problems with impact to the business, your real productivity is zero. How does this account for that?
https://blog.pragmaticengineer.com/the-product-minded-engineer/ https://blog.pragmaticengineer.com/the-product-minded-engine...
- adchurch 2y agoYou're totally right! And we do not account for it at all. We don't give any insights into product decisions, just engineering output. If engineering output is high but business results are bad, that indicates there's a problem somewhere else in the business. But it's still good to know that engineering output is high!
- jrs235 2y agoAgreed. Focusing on outputs leads to busy bodies and doesn't necessarily mean better productivity, just more busyness. "We generated all this output over the past sprint! Nevermind the outcome that had new business value only required a few hours and a days to delivery... But we managed to take 5 times longer to get that to the customer!" I'd rather engineers slow down and think before just producing noise to show they were thinking. I see knowledge work management and business leadership is falling back to vanity again.