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?

At Agile Coach Camp Canada in June 2010, I lead a session on How to Transform a Hero Culture. It was the first session of the day, and a spirited discussion with many new friends, old friends, and people I admire.

Organizational culture is a critical factor in whether a new process or methodology will be successful. Whether you are an Agile coach, a change agent, or a natural leader, you recognize that if an organization’s culture is not in alignment with the new direction, and is unwilling to shift, the new direction will most likely fail. This is a big challenge!

I have worked in several organizations where a hero culture was prevalent. What I mean by this is that heroic efforts to rescue a failing situation are rewarded and encouraged. In this type of culture, whether fixing a critical issue or working 60 hour weeks, you are what everyone should aspire to be.

There are many types of heroes, for example:

• Someone who wants recognition, power, and rewards, and often happens to be in the right place at the right time to solve problems.
• Someone who doesn’t take care to do a high quality job the first time around, and then swoops in to clean up their own mess.
• Someone who does high quality work, has good judgement, tries to keep a low profile, yet is a natural leader for change and problem resolution.

If you are trying to create a culture that embraces teamwork and collaboration, regardless of the type(s) of hero(es) in your organization, you will want to help evolve the culture away from one that supports and rewards heroes.

How to Transform a Hero Culture

Michael Sahota and I summarized the key findings of the session at Agile Coach Camp Canada to transform a hero culture. You can watch it in the video below.

What do you think?

Do you think a hero culture should be encouraged?

Or do you think they should be transformed into something different? If so, what are your idea’s on how to transform a hero culture?

I look forward to your comments!

- Selena

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!

Note: I am not an advocate for McDonald’s, own no stock in the company, and would never ever step foot in one again if I can help it, due to a variety of reasons not relevant to these postings or this particular weblog.

One of the first things I learned working in the fast food industry was how important customers were. Customers are necessary for keeping a company operating, but are also important in shaping many business operations and decision points. Here are three things that stuck with me after working the daily grind at McD’s:

Customers keep the business running, and your job intact.

Seems obvious, doesn’t it?

Sadly, it doesn’t seem to be in many companies. I bet you can quickly think of at least three bad customer service experiences you have had in the last three months. Sub-standard customer service, interactions, and expectations have become common place in today’s society.

The good news is that companies who make customers feel valued, listen to them, and actually improve their business based on customer suggestions are further ahead of the competition. Customers return when they have had great experiences.

While working at McDonald’s I focused on ensuring customers had a great experience. It all started with the first friendly and happy greeting, through to listening carefully to their requests, filling the request quickly and accurately, and finishing with a friendly good-bye. If anything happened to go wrong with an order, I quickly stepped in to compensate before they became frustrated and upset.

Customers also keep the business running and our jobs intact in the software industry.

Whether you are a programmer, a tester, a project manager, in operations, or in any other role, we need customers so we have a business. The customer may be an actual end-user of a product or service, another company who is purchasing a product or service for delivery to another customer, or even an internal user of the software.

Regardless of who they are, it is our job to provide a positive experience for that customer. That means:

• Understanding what problem they need solved
• Learning what they need to be happy with the product or service
• Determining how they will actually use it, and
• Ensuring every interaction is focused on the customers’ satisfaction and happiness.

Customers drive future products, if you listen to them.

Every customer is going to have some sort of feedback about the product or service they obtained. It may be positive in identifying how well it works for them, recommendations for improvements to improve it’s usefulness for them, or even complaints about how it doesn’t satisfy their need at all.

Running a business comes down to understanding what customers need and why they will buy something. If you don’t provide something they need and will purchase, you’ll quickly be out of business. This makes sense, but how often do you take customer feedback into account?

Context: Restaurants located in Southwestern Ontario, Canada.

In the early 90′s there were several products that McDonald’s offered that I really liked. Salads and pizza. For whatever reason, neither product sold well enough to keep them on the menu. Corporate listened to the customer feedback (which was represented in sales numbers, and in surveys and feedback forms) and removed both of them from the menu. While I was disappointed, customers were happy when new burger selections appeared on the menu to replace them.

Flash forward to early years in the new millennium, and you may remember that salads made a comeback and were added back to the menu as customers became more health conscious in their dietary habits. Additionally, as consumers became more environmentally conscious, most of the styrofoam packaging was done away with and replaced with paper and cardboard products.

Customers should also drive product evolution and new product creation in the software industry.

I have worked in organizations where someone internal to the company came up with ‘the next big thing’, developed it, and it flopped. Why? Because customers didn’t need it, want it, or it didn’t satisfy all their needs appropriately.

Learning customer needs and wants is critical for developing successful products.

• Product Owners/Managers need this information to devise user stories/requirements that will actually satisfy customers and make profits.
• Programmers need this information to ensure they program a solution that satisfies customer requests, wants, and needs.
• Testers need this information to confirm that what is developed not only fulfills a need and desire, but is actually usable for the customer in the way they will use it, continues to evolve per customer feedback, and satisfies many non-spoken product/service requirements.

This requires time to research, learn, and understand customer desires.

Customers evolve company image and business direction.

Most companies are in business to make money. To make money, businesses need customers. To get customers, they need to know how to attract their target market(s). Understanding the desired customer base, their lifestyles, and their interests is paramount for promoting an image and devising a marketing strategy that attracts, and keeps, the people wanted as customers.

Context: Restaurants located in Southwestern Ontario, Canada.

Do you remember the marketing strategy that McDonald’s used in the 80’s and early 90’s? They targeted most of their efforts at children. If children desperately wanted to go to their restaurant, parents would take them. From now-classic characters such as Ronald McDonald, Grimace, and the Fry Guys, through to the bright and bubbly in-store decor and family-sized booths, the company image was all about the kids. Some stores even had train cabooses that were used to host birthday parties, much to the delight of many children.

In the mid-to-late 90’s, McDonald’s changed their target to be less child-focused and more adult and family-focused. In-store decor evolved to be more subdued to attract a new customer base, Children’s Play Places were added so parents could have a break from their kids while knowing they were safe and having fun while in the restaurant, the Monopoly game was introduced to collect pieces and win prizes, and the infamous characters were fading away. McDonald’s was growing up.

From there McDonald’s further evolved to focus predominantly on the adult and teenage market. The company image and direction shifted to obtain customers outside of the established children-and-family market. They became more trendy, hip, and grown-up by introducing the “I’m Lovin’ It” commercials, advertisements and commercials focused on the working professional, and updated decor reminiscent of upscale cafe’s. McDonald’s touted a cool and adult-friendly image.

Consider whether customers influence the image and business operations of your organization.

• Does your company evolve its image as the target customer base evolves?
• Do marketing strategies change to acquire new target markets?
• Does the company consider customer lifestyles and interests into how it promotes itself?

Customers aren’t just the people who make a purchase for an end product or service, but are also internal to a company.

• Does your internal organization modify and adapt it’s image as other organizations in the company evolve and change?
• Do you know how to appeal to them so that working relationships remain strong over time?
• Does your organization evolve as your internal customers evolve?

Let’s go one step further. 

Suppose you have an external customer who likes to be heavily involved in defining a project, makes many changes, and likes to have flexibility in what the final end-product is.

• Does your organization evolve to use more agile practices that can work with this customer more effectively?
• Or does it stick with heavy-documentation, everything-is-planned-upfront, and nothing-can-change approaches? Guess how well that customer relationship will work out.

This isn’t just about company image and branding.

It is also about the processes and methodologies you use to appeal to, work with, and satisfy the customer. That extends from sales and marketing, product management, programming and testing organizations, operations, and customer support. If your organization isn’t adapting how it operates in order to keep up with the customer needs, you will soon be left in the dust.

What’s Next?

Take a moment and consider whether you, your organization, and your company really value your customers.

• Are customers welcomed, appreciated, and treated as a valuable part of the company/organization?
• Is customer feedback gathered and regularly used to adapt in product creation and evolution?
• Does the company image and business direction evolve according to the needs of the target market?
• Do methodologies and approaches adapt to work seamlessly with customer needs and methods of interaction?

Watch for the next part in the Food Service Lessons series, Lesson #2: Teamwork.

I remember a lot about the training I received when I started my job, from the old out-dated cheesy training video’s, to the shadowing I did with existing employees at the customer counter. I also remember smelling like grease all the time, no matter how much I showered. But I digress…

This was back in the early 90′s when the classic McDonald’s characters were still around, though waning in appearances. Back then, at least in the restaurant that I worked in, most employee’s worked hard to deliver value (a.k.a. food) to the customers. I sure did! I was getting paid to work, and work I did. We still had fun while on the job, but never at the expense of the customer experience.

I quickly moved up the ranks from the main in-store counter, to the food delivery window in drive-thru, to the high pressure first drive-thru window (I was the multi-tasking queen!), and to new-hire trainer. I even revised the outdated training program to be more relevant, effective, and context appropriate.

Note: I am not an advocate for McDonald’s, own no stock in the company, and would never ever step foot in one again if I can help it, due to a variety of reasons not relevant to these postings or this particular weblog.

That said, I had many experiences and learned a lot during the three or so years I worked there, many of which I carry with me in my work today. Believe it or not, many of these lessons are readily transferrable to other companies, and to software development (which includes testing).

What I had intended to be a single blog post has somehow taken a mind of it’s own and evolved into a number of blog posts into a full-fledged series. As this was not expected, I am curious to see how these are received.

I hope you will follow along with me! Subsequent posts in this series will be added as links from this entry as they are published.

First stop, Lesson #1: Customers Are Key

That Good Morning Cup, by Wespionage on Flickr

I once worked for a manager who did a great job of smiling and saying ‘Hello’ to his employees every morning. He then spent most of his time in meetings during the rest of the day… he was a manager after all, and managers are busy people.

When he was available for his employees, he enjoyed having discussions with his senior staff members to make decisions, decide on new directions, and figure out how to handle challenges.

Sounds like a great person to work for! … Right?

Perhaps so…

… But perhaps only if you paid attention to WHAT they were doing…

… and not HOW they were doing these things.

For instance, you might begin to notice that while your manager made the rounds saying ‘Hello’ every morning, their tone of voice and the words used changed depending on whom he was speaking to.  You might even begin to notice a trend amongst your fellow colleagues in those differences (but what does it all mean?!).

Now let’s say you were one of the fortunate few to be a senior staff member to this manager.  Wouldn’t that be cool?!  To be on the inside track, working closely with your manager to set the direction of your team / department, and getting opportunities to take on more responsibilities.

That sounds like fun to me!

The opportunity would become less fun as you begin to notice that your ideas are rarely considered or used for making decisions or improving the team.   Now you are beginning to wonder what is going on… your ideas and perspectives have been highly regarded by others in the organization.

So what gives?  Why isn’t your manager respecting your ideas or supporting you?  Is this happening to everybody?

Upon further observation, you find that this manager does in fact appear to take ideas from a couple of your peers.  But wait a minute, those peers are just reframing something that your manager said!  They are repackaging his comments to simply agree with what he wants to have happen.

Your manager doesn’t want new ideas, or someone challenging his (obviously perfect) ideas.

Your manager wants ‘Yes’ Men!

People who will agree with what he says and not challenge his ideas.

Aha!  That explains why your ideas are rarely considered or used – you don’t blindly agree to whatever is thrown on the table because a particular somebody said it.

Thinking back to those morning greetings, you realize that the ‘Yes’ Men on the team get meaningful interactions with your manager in the morning… and the people who aren’t?  They are getting a syrupy-sweet-so-you-can’t-actually-complain-about-me-fake greeting that lasts all of one second.

Moreover, you realize that your manager thrives on a dictatorship.  He is happy when he tells people what to do, and they do it.  He supports the senior staff who continue that behaviour with other team members.    So, opportunities on the team for growth and advancement are only given to those ‘Yes’ Men.

Not so nice anymore, is it?

This type of person does exist!

I did in fact work for someone like this after a good manager left.  I ended up leaving the team when I pieced together what was going on.  To say the least, it was a toxic environment, and I stayed in it much too long.

I learned a lot from that experience though, such as:

• Recognizing when I am working with someone like this
• Understanding myself and my own limits better
• How to view painful experiences as valuable learning opportunities
• When to try to work past differences with other people, and when to move on
• How NOT to behave if I wanted to be a good (or even great) manager

On the Flip Side

I did have a manager who did all the things I described in the first two paragraphs who was very sincere in their discussions and greetings, who truly valued their employee’s input, collaborated often to make decisions and generate ideas, and empowered their team to be responsible, creative, hard-working, and have fun.   Paying attention to HOW she behaved, not just WHAT she did, made this obvious.

I have even been this positive manager myself over a number of years in managing teams… but more on that in another entry.

Now, I would like to hear from you!

Have you worked with or for someone who is a dictator-type who thrives on working with ‘Yes’ Men?  What has your experience been like?  Were you able to find a way to work with them, or to deter their behaviours?

Please share your stories!

Today I actually read the weekly LinkedIn update I receive, and noticed that one of my connections had added a book to their recommended reading list.  I had no idea LinkedIn had an application for that!  Very cool.  This will save me some time by not having to track all my books on this site, which I had intended to do (yes, that means you need check out my LinkedIn profile for books for the time being).   So, the first thing I did was throw up a number of books I’m reading right now – admittedly there are a few others I’m in the middle of as well, but those will wait for another time.

From there, I wondered if there was anything of interest in any of the groups I was a member of.  I noticed that I had a group for PSL (Problem Solving Leadership, a course I took with Jerry Weinberg, Johanna Rothman, and Esther Derby about 1.5 years ago).  I had completely forgotten there was a group for it, never mind that I had joined it!  I felt like I had found $20 I had hidden in a pocket months ago – what a great feeling!

Clicking on the link, I found a message on the PSL news list titled ‘A Profound Learning Experience in PSL’.   Given my experience with PSL, I had to agree that it was an incredibly profound experience.  I was curious to read about this person’s experience.  It turns out that the author, David Barnholdt, had recently taken the course, and had learned more in one week at PSL than he had in months.  His debrief of his experience at PSL is worth reading, so be sure to check it out.

At some point, I will summarize my experiences, insights, and outcomes of my own experience at PSL.  As soon as I’m ready to share the very personal nature of the week with the world wide web.  That is pretty scary to think about, but I think I’m nearly there.  :)

I have recently found myself in a bit of a slump.  There are a lot of things I want to do, but I’ve been having difficulty focusing in on one at a time – both at work and personally.  After some reflection, I have discovered that this stems in part from being frustrated in my seeming inability to empower and enhance the environment with colleagues at work recently.  To put it bluntly, some people are annoying the heck out of me, and I’m having trouble getting past that to be at my best.

David’s post was a really great grounding agent for me, reminding me of what I had personally experienced and learned while at PSL.  It also brought to light how effective I can really be in shaping a positive environment around me with only a slight change in how I approach each day and in interactions with other people.  I really needed this!  I am looking forward to seeing how I improve through the rest of the week with people around me.

My final thought for today:  The Problem Solving Leadership course is a wonderful, and life-altering experience.  It will challenge you in ways you could never expect, but also help you find parts of yourself you didn’t know you could ever find.  There is another offering being held in March of 2009.  Please do attend if you can find a way to make it happen.  I can guarantee that you won’t regret it!