When Good Managers Fail: The Law of Problem Evolution
That's the Law of Problem Evolution. The law is this: The problems a manager faces will evolve over time to escape the solutions the manager has in her or his toolbox.
Of course, most operational problemssay the group being chronically late on deadlines or failures of packaged software to function as documenteddon't actually conspire to elude a manager's solution.
Problem staff will sometimes change their behaviors to subvert a manager's attempted solution, but those are exceptions.
The Law of Problem Evolution is one of the reasons why new managers, even ones with less experience or even with less skill than their predecessors, can turn around a challenged group fairly quickly, even when the predecessor couldn't.
It's common sense that, as you stay on a job, the problems you naturally solve easily get solved, and the ones you're blind to or have a challenge solving tend to remain unsolved. Over time, the percentage of problems you find challenging will become an ever-larger proportion of the total remaining challenges, because the ones you just chew up are out of the scream pool.
If the manager's own supervisor is paying attention, it'll appear that things are "getting worse." If that supervisor is asleep at the wheel, they may not notice, but either way, limitations in the manager's abilities are silting up the flow of progress. Eventually even the good manager is "a problem," a barrier to improved performance.
One of my clients in the late '90s was a regional financial services concern that had always contracted its IT services through its hardware supplier. The company wanted to move to more diversified platforms.
They hired Herbert as their IT director, and Herbert was a wizard with equipment, a tireless warrior who put in dozens of hours of overtime most weeks. Herbert's strengths included strategic thinking about technology and the hands-on touch that looks like faith-healing to most executives.
He took joy in his department's ability to keep systems running and keep new gadgets and platforms rolling into the mix. He was passionate about building budgets, maintaining them and delivering results according to them.
Herbert, like all managers, had weaknesses. He was incapable of delegating. While his department was able to meet every service-level target and tended to meet deadlines, he never delegated the requirements to master specific tools.
When enough new systems came along and they were diverse enough, Herbert became a problem because his time was not limitless, and he was the only expert on four critical systems. You couldn't always get Herbert's attention, and there was no one else who had the expertise to unstick many sticky challenges.
Everything that Herbert could solve, he did. More and more of what appeared to be the problems at Herbert's company were challenges he was incapable of solving because he could not delegate. His excellent performance was limited in a way that devastated the excellence of what he was good at. The problem evolved in a way that no matter how hard he worked, he couldn't solve it.
Next Page: The manager who can't give negative feedback.
The Role of Standards in Cloud Security
Security is often cited as a primary cause for concern...Watch Now
Ensuring Resources for Mission Critical Workloads
Application workloads can thrive in cloud environments,...Watch Now
Improving Security in the Public Cloud
One of the main concerns about moving data to a public...Watch Now