I have picked them from a longer list of recent project participants so they span the breadth of the customer-supplier relationship. This sampling is a cross section of disciplines providing each of us with something to think about on how we carry out our duties. It presents a small study in how people perform their jobs while their infectious enthusiasm inspires the team.
To be a good business analyst you need to be analytical and earn instant trust. This allows you to dissect the fiercest of business processes and present an unbiased view that allows people to make decisions. Ms. Brown is all this and more. Her smiling, gracious nature befriends everyone. Her answers are clear, complete, concise, and correct. Both direction and criticism are taken with an eye on how she can improve or help others improve. She understands her workload and gets tasks completed in the time frame she initially estimates. People are confident that her answers are objective and untainted with by her views, opinions, or filters. She now uses these traits as a Project Manager.
John Halseth, Customer Representative
The customer is the most important part of the project, without them there would be no project. However, customers often fail to understand that there are limits on what can be delivered. Mr. Halseth is different. He understands the meaning of give and take and its direct relation to success. Understanding what is actually needed in a solution is difficult; it requires leading a team to make decisions on the real importance of features. Remembering eighty percent of the value is in twenty percent of functionality elevates this customer far above the rest. He looks for the right solution, realizing that stubbornly sticking to a single solution is the recipe for failure.
Working in an operations center is tough. If everything works right people forget to thank you since smooth working operations centers are invisible. Response and stability are paramount. Mr. Huang understands the importance of stability, configurability, and consistency. While working in Taiwan with teams of non-native English speakers, I was always confident that he knew what I was saying. He takes active listening to new heights. From the direction he is given, he provides a sample of the preferred solution with all the pros and cons listed so that there is no question on what is being built. He works day and night to make the systems work by the deadlines needed. He coordinated his peers and communicated with a wonderful sense of humor—good luck doing that cross culture.
Being junior on any team is tough. Being a junior analyst transitioning into IT is even more difficult. Some junior people, Ms. Hudgins included, are so cautious about making the normal mistakes beginners make, that she underrated herself. The first team she worked with me on, her lead did not trust her. However, she was a finished diamond waiting to be removed from the box. She needed to be trusted, this would build her confidence to complete any task she was given. As I reduced the involvement of her lead on the team, I told her, "I have more confidence in you than you do. Go make it happen." All she needed was to shrug off the newbie bias. She has blossomed into a premier analyst.
Most top-notch programmer/architects know they are and it shows in how they deal with people. Condescension is the norm. Mr. Lemmond is different. He codes circles around others, develops designs, produces documentation for others to follow, and works with management to get designs to fit into the budgetary and time constraints of the project. He is a coding beast and a team builder. He sets his sights on a goal and achieves it. He never needs managing, although at times he needs to be asked to slow down.
Quality Assurance has immense pressure. It is the last hurdle between building and deploying and no one enjoys stopping the delivery. Mr. Litvin has a way of making this painless. Honest and open communication of the issues with a proactive way of working with developers and customers ensures the problem is properly defined in order to verify the failure is real and the fix is correct. It is not just the product that needs to be validated; the tests also need to be complete and correct. Redundant tests only slow the process and frustrate the team. Mr. Litvin sees what makes sense and cuts out the fat. When QA has completed their tests, they get the dubious honor of running them again. Mr. Litvin faces it with a smile.
Translating a large project's needs into infrastructure solutions is challenging. Virtualized environments help, but the cross-task coordination is still a nightmare. One needs to be proactive and aware of the subtleties of multiple projects at one time. The fact that there are multiple projects contending for the same hardware only make Ms. Nibbler smile at the challenge. As an IT infrastructure project manager, she anticipates and balances needs between the development and maintenance teams. Her cheery attitude, effervescent smile, and ability to pull people together, are only a few of the powerful tools at her disposal. She exhibits fantastic agility being able to change direction on a dime, with her team in tow, making them feel happy to make the change. She queues up people and resources getting them to a point where changes can be made in the last minutes before they is required. The infrastructure appears magically.
What Makes Them So Special
These people have many traits in common from needing minimal management to their ability to see the big picture. Their communication skills are described in superlatives and they only complain when they have a solution to accompany the concern. They are model team members and we can all learn from them. However, the true differentiator is their cheery can-do attitude and their humble approach to their exemplary capabilities.
Commemorate Your Own Heroes
Please add your own project heroes, in a comment below, including what makes them so special.