Chaos Theory (or Transition to Management)

A couple of months after first being promoted to a manager position, during a weekly one-on-one meeting, my supervisor asked me for a detail of a project one of my team members was working on. I did not know the information and admitted that I was struggling to keep up with all the ins-and-outs of all my direct reports’ projects. I said I felt like I was failing in this new assignment. Chuckling, he reassured me that I was doing fine and offered up some advice. Advice that, frankly, seemed stupid to me in the moment, but which, soon after, I realized was true and quite helpful, “You have to get comfortable feeling a little bit out of control.” As an individual contributor I had had a strong, direct influence on the outcomes of my projects, and, indeed, the success of those projects is what opened the door to the management role. As a manager, I had to learn to let go of that control and trust my team members to handle the details. Further, it’s not possible for one person to stay current on every detail of every project, that’s why we work in organizations. Most importantly, higher level managers don’t expect you to know every detail of others’ projects off the top of your head, only the critical items to help direct the needed outcomes of the business. If you’re asked for detail that you don’t know on the spot, just be sure to follow up and report back so you don’t leave your management wondering.
Over the years we’ve been exposed to Six Sigma, Juran, Deming PDCA, 8D, Dale Carnegie, A3, Shainin, and more. Each technique works pretty well, and has been demonstrated many times in a wide variety of industries and circumstances. At the core they are all essentially the same!
Each approach relies on an underlying logical flow that goes like this: [a] make sure the problem is clearly defined; [b] be open to all sources of information; [c] vet the information for relevance and accuracy; [d] use the process of elimination to narrow down all possible causes to the most likely few; [e] prove which of the suspects is really the cause of the issue; [f] generate a number of potential solutions; [g] evaluate the effectiveness, feasibility and risk of the potential solutions; [h] implement the winning solution(s); and [i] take steps to make sure your solution(s) don’t unravel in the future.
The differences between the paradigms resides in supplementary steps and toolkits. For example, 8D contains the important “In
Your primary role as a manager is to ensure your team’s success. Internalize this. Make sure your team members know this. Build an environment of trust and collaboration. A direct report of mine would frequently leave me out of the loop as problems escalated, preferring instead to “work harder”. It was clear that he felt uncomfortable delivering bad news to me (his boss) when things were not going according to plan. Let me tell you the rest of the story.
