R&D organisation and performance
The Difference Between KPIs and Metrics in R&D
Metrics show how R&D work runs, KPIs show whether it reaches the goal. The difference explained, with examples for engineering teams.
Leadership, organisation and change
One company cancelled all 32 recurring meetings for a week. Only 8 were missed and no project slipped. What a full calendar really signals, and a simple test.
I once proposed to a company that they cancel every single recurring internal meeting for one week, really all of them. The first reaction was panic. “That’s impossible,” the managers said, “we won’t know what’s going on any more.” I asked whether they knew what was going on after those meetings. The room went quiet.
So we tried it: 32 recurring appointments, cancelled for one week. By the end of the week, exactly eight of them had actually been missed. The other 24 disappeared without anyone noticing a difference. No project slipped, no decision was left hanging, no customer complained.
People suddenly had time to think, to work, and for the conversations that were genuinely needed rather than the ones that simply lived in the calendar. We reinstated the eight missed meetings afterwards. The other 24 stayed cancelled.
A full calendar is not proof of productivity. More often it is a sign that someone is not protecting their time. We confuse busyness with performance with remarkable reliability, probably because busyness is visible and performance is not: whoever has many appointments looks important, and hardly anyone asks whether anything actually gets created in them.
The simple question to start with: which of your recurring meetings would genuinely be missed if they silently disappeared next week?
Confusing the visible with the important is a measurement trap of its own, which we unpack in The Difference Between KPIs and Metrics in R&D.
If you recognise your own organisation in this story, get in touch. The first 90 minutes of consultation are free.
Read on
R&D organisation and performance
Metrics show how R&D work runs, KPIs show whether it reaches the goal. The difference explained, with examples for engineering teams.
Leadership, organisation and change
The best design engineer retires in four months, with 33 years of knowledge in his head. How to reduce your bus factor and capture expertise in weeks.
Leadership, organisation and change
A key developer quit over a delayed raise, and the correct process cost 20 times the increase. Why slow HR processes lose key people, and what helps.