What organizations promote as ‘heroism’ is rarely how I would define ‘heroism’ (see photo). In this post, I talk about a ‘hero culture’ and ‘heroism’ in terms of how I have seen organizations promote them. You can be a true hero in a team-encouraged environment, but it works differently than a hero-encouraged environment.

Consider the firefighter who saves a child trapped in a burning building, who is able to do so because of the support of his team; and the team who saves the building. Firefighters work as part of a team where each individual plays a role to keep themselves safe and save whomever or whatever it is they hope to save. The team is heralded for the work they did to save the building, and the individual heralded for rescuing the child. They all do their best work possible, support one another, and get the job done no matter what. Team cultures celebrate both the successes of the team, and of the individuals within the team. Neither is done at the expense of the other. If a ‘hero culture’ such as those I have seen in organizations were promoted in a firefighting department, you would hear about firefighters scrambling over themselves to be the one who saves the child, no matter what, so that they are heralded as the most important hero who saved a person. It is that type of ‘hero culture’ that I speak of in this post.

My Message

The notion of a hero as someone who does things because it is the right thing to do should not be done away with. It is how a ‘hero culture’ is promoted and encouraged in organizations that needs change.

The issue I have is when heroism is upheld above everything else, particularly the Team. Companies can not succeed on one or two individuals alone, at least not in the long term (in my experience and observations). The ability of a Team to pull together to prevent problems they can foresee and solve problems that do arise is important. We need different perspectives, skills, and experiences to prevent and solve problems in the best way possible at a given point in time. When all team members feel like they are contributing to the best of their ability and that management supports them as such, teams can accomplish far more than an individual hero can.

The promotion of heroism in organizations limits teams from accomplishing their potential as a team. Many people seek to achieve individual rewards, to get the top raise, to get the most recognition because the organization encourages it – even if they unknowingly hurt the team, the project, and the organization as a result.

I admit that I have been that person, and I know from experience that some colleagues will shut down and decline to contribute as a result. I have been the person who works 60-80 hour work weeks to solve problems, do the right thing, and help save a project from disaster. I have been the person who stays under the radar doing all the right things, and was recognized as a leader and someone who will save the day.

At the time, I thought that competition was a good thing, as it would help us all raise the bar and do the best work possible. I only understood later that if your bar is so high that other smart, capable people can not reach it, they just won’t bother. So then you have a ‘team’ of people who succeeds only on the efforts of an individual. Why bother having a team then?

I have learned from experience that Teams need to be recognized for the heroic efforts they do, not individuals. Teamwork results from people who trust each other, support each other, and can build relationships with each other. It is difficult for most people to build healthy working relationships that accomplish amazing things together when they feel they are in competition with each other.

So, I will continue to do all those things I’ve done when I feel it necessary, and yes, I want recognition when I do those things. I wouldn’t be human if I didn’t. That said, I work hard to balance this with the promotion of a team-based culture, as the strength of a high-functioning team far outreaches my ability as an individual.

I thus promote Team-culture over Hero-culture; provided the needs of the project, company, customers, and investors, are met, and dare I say, exceeded.

Some Examples

Some specific experiences I have that highlight problems in a “hero culture”:

• A hard-nosed believes-he-is-right-about-everything programmer insists that he doesn’t have time to do things right, and tells everyone he does not test his code before releasing it to testers. He says he is too busy to bother, and it’s their job anyway.  Throughout a 5 month project his features are consistently not testable because they are so broken. This persists until a couple weeks before release when he is finally able to fix the most critical known bugs in the software. Management heralds him as a hero for solving these really difficult problems, and promotes his behaviours as what they want to see in everyone. His poor decisions earlier on are not discussed and are allowed to continue in his future work.

• A senior manager spends the majority of his time talking to people about how bad a shape the company is in, and how he would do things differently if it were his company. He spends most of his evenings and weekends in the office ‘checking up’ on people’s work and getting face time with the CEO who is often in the office. This is because his family and friends live back home many hours away, and he has nothing else to do while living in the city for this job, so he spends waking time at the office. He is quick to point out employee faults, and quick to take credit for employee successes. He is promoted as a hero by his superior’s because he spends so many hours in the office, and was crafty enough to take credit for successes that were not his (without his superior’s catching on to that).

• A team works incredibly hard to release a challenging project. Everyone works together to understand and prevent problems, solve problems as they arise, and put in equal amounts of overtime. They are a high functioning team. Each time a serious problem is averted, two individuals on the team are heralded by those outside the team as the ones who save the day. The rest of the team is demotivated by this and wonders why they bother with their contributions when the other two team members always get the credit. It was a team effort and it should be recognized as such.

While these are specific situations, I have seen many other cases where the promotion of heroism hurt the abilities of teams and organizations. In each of these specific cases, the individuals involved could have behaved differently:

• The programmer could have put his best effort into doing quality work with integrity, including testing his code before sending it for testing. It’s one thing to do your job with integrity and quality and be seen as a hero for solving a problem later on. It’s quite another thing to knowingly do crap work and then come in as the hero to fix the problems you created as a result of your crap work.

• The senior manager could have tried to help the organization improve and do better, instead of complaining to anyone who would listen. He could have informed others that the work people were crediting him with was actually someone else’s. He also could have worked from his in-city apartment (as he had a laptop and VPN access) to do whatever work he was portraying himself as doing during evenings and weekends – he instead chose to be in the office to get credit for just being there.

• The individual team members could have responded to the proclamation of their heroism that it was a team effort (because it was), and that they should be recognized as a team for those efforts.

Final Thought

These examples also highlight issues with management. Management plays a very big part in the culture of organizations, as they have ‘power’. The culture that traditional management encourages is one of individual heroism, which is detrimental to team culture. Now, I’ve often encouraged culture change from the ground up, and have been successful in some cases, but it’s a tough road, and one that many people aren’t willing to attempt.

If you prefer to work in hero-encouraged environments, be my guest. If it works for you, great. I challenge you to consider your motivation in wanting to work in that type of organization – you may have reasons that I completely agree with, or possibly not.

If you want to work in a team-encouraged environment, I implore you to listen to the YouTube clip linked to in my previous post. I summarize some things you can do to help encourage your organization to transform into one.  I challenge you to consider other ways to encourage that transformation and share them here.

Thoughts?

The Software Test Professionals Conference is quickly coming up Oct 19-21.

Have you registered yet?

If so, I look forward to seeing you there!

If not, what are you waiting for?!

Read on for 5 reasons to attend:

1) You are a Software Test Professional – if so, you need to be there! This conference is all about people like you who want to learn, improve themselves, connect with like-minded people, and grow themselves professionally. If any of these apply to you, sign up now!

• You are a tester, a manager of test teams, a project test lead, a programmer who tests, someone who manages beta testers or usability testers, or someone just interested in increasing the value of testing.
• You spend time improving your skill sets (or want to), and believe that continuous learning and challenging yourself is a necessary part of your job.
• You want to increase the value of testing in your organization.
• You are not interested in being a robot who blindly does what you are told, but finds ways to improve the way you do your own work so you can do your best work possible.  You also encourage this in others, by leading by example.

2) Learn by Doing, Not Listening in the Hands-On Testing Techniques Lab. The best way to learn new skills is to practice them hands-on while you are learning them. Come and challenge yourself with new methods in a safe environment with instructors and other students. This is a rare opportunity at any conference, so be sure to take advantage of the opportunity (and bring your laptop!).

3) Attend My Sessions & Talk With Me! There are many other great presenters to check out as well – but I know you’ll want to attend mine. ?

My pre-conference workshop, Test Management Clinic, will help you explore and learn techniques for solving real-life test management challenges. You may even leave with appropriate solutions to challenges you are currently experiencing. Register ASAP to reserve your seat now!

My session Explore Beyond the Obvious in the Hands-On Testing Techniques Lab will allow you to try different testing approaches to dig deeper into seemingly simple applications, and learn new information about products you test.

The panel I am speaking on about Reducing the Cost of Testing will help you gain ideas in reducing test costs, understand tradeoffs in doing so, and learn how to talk about testing costs with management in a reasoned, articulate manner.

4) Improve Your Career via the multitude of opportunities awaiting you. Network with people who are driving changes in the industry and understand their strategies so you can too. Connect with people around the globe who can help you with some of your challenges, and vice-versa. Learn leadership strategies to champion initiatives and changes in your workplace. Improve your skills in working with management, and making testing a valuable part of the organization.

5) STP Conference is in Las Vegas! Seriously, how much fun will that be? If you ever needed an excuse to get yourself to Vegas, this is it. Imagine – spending days learning to your hearts content and talking with fellow test professionals, then enjoying evenings in the fun of Las Vegas while connecting with fabulous testers from around the globe.

Register Now – The Early Bird Deadline ends this Friday August 20, which provides a $500 savings off the conference package.

See you in Vegas!

April is near upon us, and that means the Kitchener-Waterloo Software Quality Association (KWSQA) Targeting Quality Conference will soon be here!  This is the must-attend conference for the tri-city (and Guelph) area.  It is local, put on by local practitioners, an incredibly good value, and chalk full of talented speakers. As of today, there are only 4 days left to get the early bird rate!  Sign up before you miss out on that great deal!  Visit www.qualityconference.ca right away for all the details!

Yours truly will be one of the speakers with a session at the conference.  This year I will be helping people find solutions to complex problems in test management and leadership.  The session will be very interactive and facilitated – this will not be a session where I stand at the front of the room and try to teach everyone things.  The goal is to have everyone learning by doing.  It will be fun!  Check out the conference schedule for my timeslot.

I hope to see you at the conference on April 22, 2009.

Even better, I look forward to seeing you at my session!