Mr. Creosote.

Some of you may know the name. He was a character in Monty Python’s The Meaning of Life. Portrayed by Terry Jones, Mr. Creosote ate and drank massive quantities in a French restaurant. At the end of the meal, the server (played by John Cleese) offered Mr. Creosote a wafer-thin mint. After some objection, Mr. Creosote agreed to eat the mint, which caused an unfortunate reaction.

Those of you who know the skit (or just searched for it) know my description cleaned things up quite a bit. While most could have easily eaten the small mint without any adverse consequence, for Mr. Creosote it was just too much to handle. He had hit a saturation point.

This analogy applies directly to how much newness an organization can absorb before things start breaking. It’s the organization’s saturation point.

Read more at ProjectManagement.com.

Recently, my wife and I were watching a college football game between two highly ranked teams. Deep into the third quarter, only a few points separated the two teams. The quarterback took the snap, scrambled while looking for someone to pass to, and let the ball fly. The ball was intercepted by a linebacker and, with three teammates as an escort to block opposing players, made his way to the end zone.

The linebacker, thinking he was in the end zone, dropped the ball to celebrate with his teammates. Upon replay, the linebacker dropped the ball at the 1-yard line—and a quick-thinking opposing team player pounced on the ball while the linebacker and his teammates reveled in what they thought was a touchdown.

Then the referee signaled “fumble with recovery by the defense” at the 1-yard line. The look on the linebacker’s face was one of “Oh, $*&$!” after he learned his all-but-guaranteed touchdown would now go down as a fumble with a recovery by the opposing team. Even worse was the fact that two of the linebacker’s teammates ran by the ball bouncing at the 1-yard line, more focused on the celebration than the ball. Fortunately for the linebacker, his team still went on to win the game.

Afterward, the head coach was being interviewed. He stressed the importance of doing the little things right—including not dropping the ball before hitting the end zone. I can only imagine the conversations that the linebacker had with his coaches after the game.

Read more at ProjectManagement.com.

Years back, I hired a person I’ll call Del who came highly regarded with a strong resume. Del went through an interview loop that included one of my peer directors. I got my peer’s feedback—along with a “no hire” recommendation. After talking with my peer, I decided to hire Del anyway.

Del made an almost immediate positive impact with the client organization he serviced. Shortly thereafter, though, I started hearing rumblings from Del’s peers within my organization about how he constantly said how busy he was and that he should not have to do some of the things his peers were expected to do. Worse still, Del claimed that he should have special treatment because he was more experienced than his peers.

Needless to say, this did not sit well at all with the rest of my organization. Del was very competent in his skills, but the negative impact he had on the rest of the team far outweighed the benefit he provided. I thought back to the discussion with my peer and her no-hire recommendation. She warned me that Del might be disruptive to my organization, which was the basis for her recommendation. The bottom line was that I should have listened to my peer and not hired Del. It wasn’t worth the upheaval in my org.

Read more at ProjectManagement.com.