A Review: The One Minute Manager Meets the Monkey

The One Minute Manager Meets the Monkey
by Ken Blanchard, Hal Burrows
ISBN-13: 978-0007116980

When I made the move to lead engineer from senior engineer my instinct was still to try and fix everything for my engineers rather than get them to complete their own tasks, or as Ken Blanchard puts it, Monkeys. It was useful and interesting to read about someone in a very similar situation, how it affected them and their family and how they eventually overcame it with four simple rules:

Rule 1: Describe the Monkey: The dialog must not end until appropriate “next moves” have been identified and specified.

Rule 2: Assign the Monkey: All Monkeys shall be owned and handled by the lowest organisational level consistent with their welfare.

Rule 3: Insure the Monkey: Every Monkey leaving your presence on the back of one of your people must be covered by one of two insurances:

Recommend, then act
Act, then advise.

Rule 4: Check on the Monkey: Proper follow up means healthier Monkeys. Every Monkey should have a checkup appointment.

I first read The One Minute Manager Meets the Monkey about ten years ago and by the time I reread it recently, I was well on my way to developing my own delegation strategy. The book helped me fill in some of the gaps, think about it in a different way and add some more, less engineering focused, practices.

Comments

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Paul Grenyer

Search This Blog