This slide deck discusses why the widespread focus on efficiency improvements in software development (and beyond) very often is counterproductive.
It starts with a quick introduction what efficiency is and why it is desirable. Then it moves on to the observation that cost reductions which are the ultimate goal of efficiency improvements are only half the picture. The other side is the revenue which – as we see – usually has become unpredictable in today's post-industrial markets. As a consequence, efficiency improvements are pointless (or worse) unless we make sure that the thing we do actually creates value and based on this revenue.
This leads to effectiveness. While often confused with efficiency, effectiveness is something completely different. The slide deck defines effectiveness and discusses why it actually is much more important than efficiency and why it is (still) neglected so often.
A way to foster effectiveness in software development is presented and it is discussed how it helps to address the underlying issues that typically lead to (pointless) efficiency improvement pressure in a much better and healthier way.
Finally, some more sources of waste based on the relentless pursuit of more efficiency are briefly discussed and what an "average" person in software development (not being in higher management) can do to nudge a company's software development process towards more effectiveness.
As always, the voice track is missing but I hope the slide deck still contains a few useful ideas for you.