Saturday, August 27, 2016

A511.3.3.RB - Directive and Supportive Behaviors



Kenneth Blanchard, et. al., developed a leadership approach widely known as Situational Leadership in which are defined four leadership styles or behaviors, and four follower categories.  (Northouse, 2016, Chapter 5) Included in the four leadership styles are two categories of behavior: directive and supportive.  The directive behavior is, as the name suggests, a “one-way” communication wherein the leader tells the subordinate (or follower) what to do, how to do it, when to get it done, etc.  Generally, the leader gives detailed instructions and the follower does as they are directed.  The supportive behavior is a “two-way” street wherein the leader and follower are mutually engaged in determining the what, how, and timeframe, etc. of the task (or tasks) to be performed by the follower.  Supportive behavior encompasses a participative approach that provides for emotional and social support to the follower on the part of the leader.

With these basic definitions in mind, I would like to reflect on my directive versus supportive behaviors as I exhibit (or exhibited) them in my various roles as a leader, follower, parent, child, friend, and I’ll even take the risk and throw in spouse.

I am an only child who grew up with a strict mother and father, where I learned my work ethic starting at a young age.  I had a 21-year career in the military and have now been a defense support contractor and consultant for approximately 11.5 years. I have been married for 33 years, and I am the father of two sons, now ages 28 and 26.  In my military career, I had many opportunities to lead teams, both small and large, and to direct a large acquisition program organization.  I also had many opportunities to follow leaders, most of whom I considered quite good at their jobs.  In my role as a support contractor and consultant to various acquisition program offices, I have had ample opportunity to serve as a follower, often as a follower of people in leadership roles who are considerably younger than I am.  This can present some interesting challenges and, if I’m lucky, can also provide me with mentoring opportunities.

But let’s start with my role as a child.  I was certainly a follower and throughout my younger years especially, my parents were directive leaders.  This is not to say that they were cold-hearted or distant; but when I was young, I was told what to do, how to do it, and generally when it must be done.  I had assigned household chores, like keeping my room clean, emptying the waste baskets in the house, and helping both parents with odd jobs around the house, in the yard, etc.  When my parents told me to do something, they always expected me to comply with their instructions and not have to be told twice.  Of course, I oftentimes violated those instructions and suffered the consequences.  I can remember, as I grew older, my dad’s seemingly favorite words of sage advice: “If you had spent half the time doing what I asked instead of complaining, you’d have it done by now.”  Those words were usually followed by the consequences of not doing what I was told, and having to be told more than once.

In my later teens, and living with my parents in northern Michigan, we heated our house with a wood furnace.  I worked at a local restaurant, often in the evenings, and didn’t arrive home until after midnight on a Friday night.  But I experienced many 7:00 am wakeup calls from my dad, telling me that we were going to go cut a load of wood.  My father was a carpenter and worked extremely hard his entire life (which is probably why he is now 85 and in many ways more fit than I am).  He expected his only son to grow up used to hard work without complaint.  I cut a lot of wood.  I did a lot of chores.  And though I didn’t completely realize it at the time, those experiences were preparing me to work hard, and diligently, as an adult.  My parents prepared me well for my military career.  Rarely was my parent’s leadership style a “two-way street”, but in my late teens there were instances where their leadership, their parenting, did both allow and even encourage me to participate in decision-making, as well as allowing me more flexibility on when I got things done (as long as they were done!).

When I became a parent myself, I expected things to work with my two sons in basically the same way that they had worked between me and my parents.  The thing is, my wife and I never really discussed our parenting approach before we had our first son.  My wife is one of five children who grew up in a small house, and whose parents were more lenient with the chores, with direction, and with consequences.  Looking back now, I can see that my wife’s parents had their hands full with five kids and the kind of directive approach that I had experienced growing up wasn’t nearly as feasible when dealing with five children instead of one.  The point is that my wife and I found ourselves at nearly opposite ends of the spectrum when it came to parenting.  I attempted to be directive and establish consequences for misbehavior.  My wife was almost entirely participative in her approach with our sons, even when they were quite young.  After some parenting-skills disagreements, I dialed down my directive approach and more or less followed her lead.  As a result, our sons usually listened to me and di what they were told; my wife had a harder time in that department but in the end she is today much closer to our sons than I am.  My sons respect me and my work ethic, but they usually turn to their mother first when they need help since mom always provided the social and emotional support in their formative years.

Given my upbringing, I was more or less ideally suited to the military’s typically directive style among the leaders for whom I worked as a junior officer.  I followed orders without question (although I did ask clarifying questions if I didn’t understand the task at hand).  As more work was pushed my way, I simply worked harder and longer because that’s what my dad did.  As the years went by, this became problematic for me when I would constantly be consumed by work to the detriment of family time.  I did not really know how to balance work and family, even though I heard that refrain countless times from senior military leaders.  So I missed much of my sons growing up, which is something I will always regret.  But my military bosses thought highly of my work ethic and I fared well on my appraisals.

As I began to assume leadership positions in my military career, I started out highly mission oriented and low on the social-emotional support scale.  I had grown up, and I had spent the first few years in the military, believing that mission was everything and people are just supposed to do as they are told.  Besides that, I was an introvert so the social side of things was not my strong suit early on.  But after five years on active duty, the Air Force sent me to the Air Force Institute of Technology (AFIT) to get my Master of Science in Systems Management.  I was lucky enough there to be exposed to professors who knew, and taught, the theories of people like Dr. W. Edwards Deming.  I quickly began to see that the people side of the whole leadership thing really mattered.  And one of Deming’s cardinal rules was that if an organization’s output was not right, it was the fault of management and not the workers.

When I finished at AFIT, I was assigned to an acquisition program office where I was given a significant leadership role.  And I began to act on the people side of the equation, while ensuring that our mission was successful.  I applied what I had learned about Deming, and about Blanchard (from my Organizational Behavior class at AFIT).  This introvert found that I actually liked the social-emotional aspects of leading teams.  I began to have off-sites; I structured meetings and reviews to give my followers direct participation in decisions about strategy, and execution.  Over the years, starting with that first assignment after AFIT, I have naturally tended toward what Blanchard would call a “supporting” and “coaching” leader.  I find that I’m happier at work, and my followers are happier at work, and we are more successful at accomplishing the mission when I hover between those two leadership behaviors.

Now that I’m a support contractor and consultant, I am back to being a follower.  I am fortunate in that I usually get to be a behind-the-scenes supporting and coaching leader of sorts in providing recommendations to my clients and even sometimes being asked to mentor some of the more junior government people.  I just need to be careful.  Some government personnel (military and civilian), and leaders, know how to best employ a support contractor’s skills and experience and tap into that knowledge for the benefit of all.  Other government folks can view contractors as “second-class citizens” who should be seen but not heard; those types of people take offense if a contractor “steps out of his lane” and tries to make suggestions or give recommendations about the conduct of the business of running acquisition programs.  I can work with both types of people in that regard, and I can still salute smartly and do my work quietly when required.  But I much prefer the two-way street when I am a follower.

Now we’re down to my roles as a friend and spouse.  As a friend, I am never directive.  In my mind, friendship is by definition a two-way street.  If asked specifically for advice, I will offer steps that I would take, or the things that I would do in a given situation.  But I would never presume to direct a friend.  Unfortunately, when my wife and I were first married, I did assume the role of a director at times.  Looking back, I don’t really know why I would have thought that was appropriate, but my upbringing and my youth (and lack of relationship experience) probably had a lot to do with it.  Needless to say, my directive approach as a spouse was met with more than a little resistance and I gradually began to learn (often the hard way) that directive behavior in marriage is the wrong approach.  I have that message, and these days I do not direct anything.  Sometimes my wife does, but that’s okay (listen up husbands!).  Marriage is a lifelong learning process and I continue to work on my supportive, social-emotional skills as a spouse.  I have found that I am a problem solver, so when my wife is concerned about something and brings it to me, I have to be careful not to try to immediately “fix” the problem.  Part of being a good husband is about listening and empathy, and not jumping in with directions in any situations unless specifically asked to do so…and even then one must be careful.  If anything is a true two-way street, it is (and must be) in marriage.

I know that Blake and Mouton have sharply criticized the Situational Approach (Robert Blake and Jane Mouton, 1981), asserting that only the Management Grid theory yields the one, best leadership style, but I find the Situational Leadership approach by Blanchard extremely useful and directly applicable to the real-world fact that leadership situations or scenarios vary.  Common sense tells us that we cannot act one way, and one way only in all situations.  For me, paying attention to directive behavior and social-emotional behavior has proven an important guide in my leadership, followership, friendship, marital and other roles that I have in life.  Adjusting those two behavioral factors in dealings with my adult children, as well as my aging parents, I find to be necessary with each situation that arises.

Saturday, August 20, 2016

A511.2.2.DQ_VoreDan




In his book “Leadership: Theory and Practice”, Northouse describes the Trait Approach to leadership, or “great man theory” as “focused on identifying the innate qualities and characteristics possessed by great social, political, and military leaders.” (Northouse, 2016, p. 19) He then goes on to cite several researchers who list several leadership traits that have been identified over the space of the last one hundred years or so which great leaders possess.  But the key point is that these essential qualities of a leader are “traits”; in other words, they are qualities that leaders are born with.  So either you have them, or you don’t.  The bottom line to this theory is that some people were born to be leaders, while others (the vast majority of others, I might add) were not.  Leadership then is open only to a select few who were born with some or all of the traits identified.

I want to state up front that I do not agree with the Trait Approach.  I believe that while certain individuals, through the effects of their early childhood development, may possess certain aptitudes that make leadership easier to learn and to come by, all individuals with a desire to lead may acquire the necessary tools, knowledge, and abilities to become a great leader.  I therefore believe more strongly in the Skills Approach as identified by Northouse in Chapter Three of his book.

That said, my task at hand in this Reflection is to identify some of my “traits” and to discuss the extent to which I possess them, or my lack thereof is hindering my leadership abilities.  I will further reflect on how the traits that I identify are important to my leadership style.

This then begs the question: What is my leadership style?  Reflecting back over my 32-year career in acquisition program management, where I have been a Team Lead (what was called an Integrated Product Team, or “IPT” Lead) on several occasions, and also as a Program Director or Division Lead of a large organization, I would have to say that my style is participatory, structured, coaching, mission-oriented, yet servant as well.  I tend to make as many decisions as I am able with the considered inputs of team members or key section leaders within my organization.  I value the opinions of others and I depend upon the expertise of the various functional discipline leads for their sage advice.  In terms of structure, I am mostly about centralized control and decentralized execution.  I delegate and I hold people accountable while checking up on them along the way and ensuring that I remove any roadblocks to success.  When necessary, I provide “top cover” to my people.  I highly value coaching and mentoring and so not only do I perform those functions as necessary, I encourage my subordinate leaders to do the same.  Ultimately, I do my best to take care of my people while ensuring that my organization and its assets are aligned to accomplish the mission.  I try to make my enthusiasm for the mission become an infectious example for others to see and thereby become inspired to work together and to work hard to achieve mission success.  Finally, I value servant leadership above all else.  I believe that the highest calling of a leader is to serve not only his or her leaders, but to serve their subordinates as well by supplying them with all of the tools, education, and support possible to enable them to succeed in their individual roles.

With all of that said, what are some of the traits that I possess, and where might I be lacking?  Northouse cites the work of Stodgill (1974), particularly his second survey that included 10 characteristics or traits associated with good leadership.  The first is a drive for responsibility and task (or mission) completion.  This one, I can see in myself.  Granted, I know that I have blind spots, but for purposes of this reflection, I am going to stick with what I believe is true of me.  I am driven; I seek out responsibility and even additional responsibility; whatever it takes for me to assure that I complete the mission.  I learned my work and responsibility ethic from my parents, mainly my father, and if anything, I drive too hard at times.  The second of the ten is vigor and persistence in pursuit of goals.  I believe this is closely tied to my drive for responsibility; I do have to be careful at times to not be overly persistent.  The third characteristic is risk taking and originality in problem solving.  I am all about that.

When I was a junior officer in the Air Force, I was put in charge of the Low Altitude Navigation and Targeting Infrared for Night (LANTIRN) Targeting Pod Production IPT.  When I took this position, the program was in serious trouble.  Because of the first Gulf War, Central Command (CENTCOM) demand for targeting pods was high.  But the production program had only just begun and we had fielded 17 pods that ended up being in 15 different configurations due to numerous production and performance deficiencies.  The support equipment did not work, and the technical orders were generally a mess.  These things happen when you rush a new system into the field.  One of my career mentors was the LANTIRN Program Director and she told me to go pick someone at (then) Martin Marietta to be my contractor counterpart, and then see what I could do, working with this person and the company, to fix the program.

I picked a guy who had some experience with the targeting pod, was several years older than myself, but someone who was highly regarded and had the reputation of being a good and strong leader.  I should note that by this time, we had gone through two Vice Presidents, and had even brought back a retired VP to try to resolve the issues but all had failed.  John, the man that I picked, and I hired a process improvement and statistical process control guy, one of the best in the country.  We sent him to the production floor and also to visit with the design engineers about all of the problems we were having.  At the same time, I flew to Luke Air Force Base and visited with the maintainers.  They had five targeting pods in the shop that they could not fix.  They showed me some of their issues with the support equipment and tech data.  I called up the VP and the Director of Logistics and told them to get on an airplane and that I would pick them up at the airport.  When I got back to Luke with the two of them, I drove directly to the pod shop, where the guys had put a pod in the intermediate-level support equipment, and I handed them their own tech data, and asked them to fix the pod.  They took off their coats and ties, rolled up their white sleeves, and began to follow the tech data to troubleshoot and then fix the pod.  In about ten minutes, I could see them flipping back and forth among the pages of the tech data, looking confused.  Within thirty minutes, they sheepishly look at me and said, “Okay, you’ve made your point.”  I got complete buy-in from the company after that and we went to work.  We began to identify the key mechanical and performance measures on the production line and to establish statistical process control.  Eventually, we ended up with nearly 500 measurement points.  We got the engineers involved where critical tolerances were specified and began to align the manufacturing operations with the design to a degree that had not been done before.  We also ensured that the support equipment in the field was calibrated to the same tolerances and indicators that were used in the factory to measure performance.  And we went to work on the tech data with the help of the Air Force maintenance personnel.  Within 14 months, we had the number of fielded configurations down to two, the support equipment fixed, and the tech data perfected.  The program when I inherited it was 16 months behind schedule.  It went on to finish all 454 pods one year ahead of schedule.

Now that was a long story so that I could say this: everything that we did to fix the targeting pod problems was a calculated risk and required the kinds of problem solving that had never before been done within the company, or on many Air Force production programs in general.  But once we began to achieve some successes, it caught fire.  Everyone became inspired and hugely dedicated to getting this program fixed and superior product out the door.  This brings me to the fourth characteristic: drive to exercise initiative in social situations.

I am an introvert by nature.  Give me a choice, and I’ll pick the good book and a quiet afternoon, or the small gathering over the big party any day.  But that does not mean that I cannot socialize and exhibit drive in social situations.  When I am in a leadership role and working should-to-shoulder with people to fix problems and succeed, I am in my element.  When I led the Suite 5 development and fielding (software and hardware modifications) to the A-10 aircraft fleet, I inherited problems.  Pilots and maintainers felt that they were not being heard and that the things that they needed were not making into configuration block upgrades.  We also had a software development and fielding process that took three years from start to finish.  Luckily, I had a few counterparts within the company that, along with me, loved a challenge.  With the lead Air Combat Command representative, all of the key software engineers, the project managers, and the contracting officials in a big conference room one afternoon, I and the lead company program manager led the discussion to overhaul the process.  We then committed to the pilots and maintainers on an historically large number of new function points and maintenance features that would be included in Suite 5.  We took the gloves off, we got extremely innovative, and without making this an overly-long story, we fielded Suite 5 in 363 days (hardware and software mods, along with complete tech data) without a single pilot or maintainer write-up on anything.  Unfortunately, due to several bureaucratic changes, mostly on the part of the Air Force, nothing like this has ever been accomplished since.  But our efforts were all about risk taking, drive, and initiative in intense social situations with scores of naysayers on the outside looking in (and even some actively trying to sabotage our efforts).

The fifth characteristic is self-confidence and sense of personal identity.  I make decisions as described above with a strong self-confidence.  The trick is to not let your personal identify get swallowed up in the larger picture.  I tend to identify strongly with what I’m doing as a leader when I know we’re moving in the right direction and I see tangible results.  In fact, my identity gets tied up in that whole process.  But through the years, I have managed to develop and maintain a good sense of personal identity that can remain apart from my work identity.

The sixth characteristic is the willingness to accept consequences of decisions and actions.  I believe in this one with all of my heart.  More than once, when briefing my Team’s or Organization’s plan to address and fix broken programs, I have sealed the deal in telling the senior people at the table, “If I’m wrong, fire me.”  I stand behind everything that I do and I also take responsibility for the actions of my subordinates.  There is no alternative for me on that score.

The seventh characteristic is the readiness to absorb interpersonal stress.  I struggle with this one.  What I try most to achieve is to head off interpersonal stress through frank and honest conversation with the folks involved.  Talking it out up front and early is usually a recipe for success, before things get out of hand.  Twice in my career, I have had to call in the “warring factions” and close the door, and get very blunt about their attitudes and actions and basically tell them to knock it off.  I did so with respect and decorum and the situations were resolved.  Sometimes leaders have to do this, and I’ve found that subordinates will respect you for it if done with their best interests at heart.  Don’t let it get to where you are actually angry with someone before you call them in to chat.

The eighth characteristic is willingness to tolerate frustration and delay.  I struggle with this as well.  I am not a terribly patient person, but I can force it if I have to.  Once my Team and I have launched on a course of action, or comprehensive plan to achieve some goal or mission, I have little patience for those who circle back around and start playing the bureaucracy card on me.  I expect people to execute what we’ve all decided upon; and also to not bring me a problem without a few alternative solutions.  I am more than willing to help someone if they are stuck.  What I’m not willing to do is to tolerate someone who sits at their desks “admiring the problem”.

The ninth characteristic is ability to influence other people’s behavior.  I have to admit that this one is becoming more difficult with the passing years than I would like.  I say this because I don’t find the same work ethic in the majority of the workforce today that I could count on 20 or 30 years ago.  When I try to influence people’s behavior, I usually do so by appealing to their sense of personal pride and accomplishment; or to their willingness to rise to a challenge.  That personal pride and willingness to rise to a challenge is still out there, but increasingly I find it being replaced by a more bureaucratic mindset that wants to focus on all of the reason why we can’t do something instead of helping to figure out how we can do something.

Finally, characteristic number ten is capacity to structure social interaction systems to the purpose at hand.  I used to joke that I was a chemical engineer, not a social engineer.  To a large extent that was true.  But from the perspective of a leader, I actually find it gratifying and enjoyable to engineer the necessary social interaction that gets the job done and allows people to have some fun along the way.  I delight in seeing relationships spring up and take hold within the context of an organizational construct or timely introduction that I have made.  I like to put the right people together in a team setting to achieve success.  But I play straight up.  What you see is what you get.  When faced with hidden agendas or disingenuous people, I have issues and these situations are where I am prone to losing my temper.  So I am always careful with social interaction systems to try to make sure that I’m seeing reality.

In Chapter Two, Northouse goes on the present a table of various other traits that different researchers have evolved.  I chose to concentrate on the ten characteristics identified above.  As I said at the outset, I believe more in the Skills Approach, where leadership abilities are open to everyone who truly desires to learn them.  In that vein, the ten "traits" that I have addressed above, to me, are actually skills that I have learned over the years from mentors, good bosses, and hard-won experience.

Saturday, August 13, 2016

A511.1.3.RB_Vore_Dan


A511.1.3.RB_Vore_Dan



Leadership Is a Two Way Street That Can Be Life Changing



When I was a young Captain in the Air Force, I was assigned as the Team Lead for the Low Altitude Navigation and Infrared Targeting for Night (LANTIRN) Targeting Pod production program.  When I stepped into this role, the program was in terrible trouble.  The Company producing the Targeting Pods had only delivered 17 of them and they were in 15 different configurations.  Video issues plagued the performance of the pod, as did several mechanical and electrical problems.  The technical data was inaccurate and incomplete, the support equipment generally did not work, and the using command, while they loved the capability of the targeting pod, was complaining bitterly about their maintainability, reliability and performance in the field.  In short, things were a mess.  We had over 450 total pods to produce and with each new pod there seemed to come yet more new problems to add to the existing ones.

I began a series of reviews, including an extended trip to one operating location where the pods were being used on the F-15E aircraft.  I visited the intermediate-level maintenance shop where they had five pods in-house that were not working and which they could not fix with the existing technical data and support equipment.  I had them show me some of the examples and late that same evening, I called the Company VP and his Director of Maintenance and Logistics and told them to get on an airplane in the morning and that I would pick them up at the airport.  When they arrived, I took them straight to the “back shop”, had them take off their ties, roll up their sleeves, and try to diagnose and repair one of the pods using their tech data and support equipment.  Within about ten minutes, they threw up their hands.  I had their attention.

The Colonel for whom I worked at the time told me to pick someone within the Company to be my industry counterpart as their lead Program Director for the Targeting Pod Program.  I made my selection, that gentleman was promoted and handed the reins.  From the start, he was one of the best leaders with whom I have ever worked.  In a very real sense, we worked for each other.  Together, we had the responsibility to right the ship, and we had our work cut out for us.  We quickly agreed at the outset that together we would work on a handshake and that when we said we were going to do something, we could trust each other’s word that it would be done.  So how were we going to take this broken program, with a whole workforce that was demoralized (on the Company side), and several military organizations and offices (on my side) that were completely disillusioned and make it into a successful program?

This gentleman and I did a lot of talking, strategizing, and interviewing of several people on both sides of the table (USAF and Corporate).  Up to the point of my selecting this man to become the new Company Program Manager, the Company had gone through several of its top executives, engineers, logisticians, and production managers to no avail.  But we began to sift through all of the problems and issues and gradually some patterns began to emerge.  We also formed a lifelong friendship and healthy mutual respect for one another, the likes of which I have never since experienced.  A real, solid partnership emerged fairly quickly.

We hired two process control experts and paired them up with design engineers, manufacturing engineers, and logisticians.  We sat down with the folks on the manufacturing floor who actually built the targeting pods.  Likewise, we sat down with the folks who produced the support equipment and the technical data.  Following the guiding principles of Dr. W. Edwards Deming, we began to identify key processes and key variables where measurements were needed.  To make a long story short, we implemented a system-wide statistical process control system wherein the critical design variables that were identified by the design engineers were evaluated on the production line.  A whole new picture emerged, data was analyzed, processes were adjusted, tolerances were re-evaluated and adjusted as required, and the measurement criteria used for acceptance testing of the pods was aligned with the test variables and measurement techniques of the support equipment.  The technical data was overhauled and corrected.  In the end, we went from 15 configurations of pods to two, and we went from more than 18 months behind schedule to finish all 450-plus pods one year ahead of schedule, and the mission capable rate in the field, as well as overall performance was exceptional.

That’s a long story and a lot of technical detail to make the point that leadership is indeed a process.  It is a process of establishing mutual trust, mutual goals, of keeping those goals and indicators on how well you are doing visible to all people involved; to show everyone that necessary changes are being made and that they are achieving favorable results – that we are “winning”.  Winning is motivation.  Being on a winning team, solving difficult problems working shoulder-to-shoulder is motivation.  Morale skyrocketed as followers became justifiably proud of their efforts, their work, and their products.  And for the two of us as the leaders (myself and my Company counterpart), we learned more from the followers about the product, the manufacturing processes, and how to “fix” problems like this than we could have ever imagined.  On top of that, we got the privilege of directly implementing and experiencing the teachings of Dr. Deming and seeing the results.  As I worked with my Company counterpart, I get to learn how leadership works inside and industrial organization.  I learned more about leadership from that man than I have ever learned from anyone before or since.

As I said, my Company counterpart and I became lifelong friends.  In recognition of his efforts and successes, the Company promoted him to Vice President.  I saw him a couple of times when he came to The Pentagon to discuss what eventually became a Navy program to put targeting pods on F-14s.  Everyone won.  It was the most rewarding experience in my professional life.  Unfortunately, a few days before I was to travel to Orlando, where he and his wife and young daughter lived, to visit him, he died in a diving accident at the age of 54 (the same age that I am now).  So instead of going to his house for dinner, I went to his house for his wake and to express to his wife how terribly sorry I was about his very untimely death.  Leadership experiences, if you are very lucky, can come along that will change your life for the better and forever.  I was one of the lucky ones.