Bill had many characteristics that today, I might recognize as potentially being autistic, he didn't make eye contact, kept to himself, he preferred to work late at night when management wasn't around to bother him. You know, actually, I did understand that one. And frankly, I was a little jealous. One of the other engineers on my team must have had some personal experience with autism. Because he insisted that he managed the communication between bill and myself, rather than having me do it. This is a little out of the ordinary. And frankly, I was very hesitant to do this, I was chief engineer, was my responsibility to make sure that everything was working in sync. But this normally quiet engineer, dug his heels in and insisted that he managed this communication. So I agree. Now, I watched these communications from a distance. And I'm not sure exactly what this fella did. But I believe that he knew from personal experience, what Francesca hoppy later proved through research, they Bill had deep specific skills, but needed more help than most and understanding the gist of the situation. Bill was very comfortable with these conversations. Bill did a great job. Bill made a critical contribution to this project, a contribution I could have never made personally. So I benefited enormously from a very small modification to my leadership approach, a modification that let bill find a way to comfortably fit in to make his contribution to the project and to the company. The first time I told this story, a listener told me that I had treated the person with autism differently. And that that was wrong. I suspect she was concerned that I was othering. Bill. I have to admit, this was a different perspective for me. Now, when someone criticizes my thinking, I tried to take it seriously. I internalize it, I examine it, I tried to determine the validity of the criticism. This usually takes five, maybe 10 seconds, and then I can counter attack. But seriously, I did reflect on this constructive criticism about the development of my leadership style. And this was a watershed moment in the development of my personal leadership style. I was being told by people whom I respected that now that I was chief engineer. My job was to give orders and chew people out. I was really uncomfortable with this. I was completely dependent on my team for my personal success, barking out orders and yelling at people who knew more than I did seem very risky. Eventually, I figured out that what I had to do wasn't to boss people around. He was to find a way for everyone to work together. I had to manage the interfaces between both the subsystems and the personalities of the project. This was more difficult than I thought it would be. For instance, one of my team members was very risk averse. His inclination was to ask for so many of the project resources to minimize his subsystem risk that it would have put the other subsystems at risk. Now, I could have just told him, I could have ordered them to take the risk. I was the chief engineer, but that would have alienated him from the project. So instead, I worked with him. I worked with him to find ways to minimize the risk to his subsystem without monopolizing the project resources. I worked with him so that he was confident in taking the risk that I needed him to take. There was another manager, who was very, very concerned about the political ramifications on him personally. If the cost mandated testing methodology were to fail. I had to find a way to give him political cover to get him on board with the project. And as I reflected on this, I realized that almost everybody on this team had some barrier that prevented them from fully committing to this project. And I had to take an action to remove each of these barriers. So as I reflected on these incidents, where my intervention was required, it occurred to me that the criticism I had received about treating the person with autism differently, was an accurate criticism. I did treat him differently. And I treated the people without autism differently. I treated everyone differently, so that I could remove the individual barriers that kept each and every team member from fully committing to the project.