Posts Tagged ‘teams’

A diverse workforce: The smart thing to do

by Robert Driscoll on August 20, 2010

Business is no longer about what product or service you can provide in a local or regional marketplace.  Today it’s about competing in a global one.  The internet has allowed companies that once were only able to support a local or regional area to now make offers on a global basis.  Competing in the global marketplace not only means diversifying your products and/or services, but your most important asset as well: your workforce.

Some people still believe companies hire diverse workforces because it’s the politically correct thing to do.  What companies are finding out though is that hiring a diverse workforce allows companies to expand easier in to new markets with a diverse client base as they are in a better position to understand the demographics of the customers they serve.  At a high level, this is true, but just because you hire a diverse workforce will not guarantee you success in the marketplace.  Like with any group of employees, it’s what you do with them and how you use their diversities to your advantage in the marketplace.

Diversity in the workplace at your company should not only be limited to race, gender and age, but differences of views and personalities as well.  As a leader, you need to recognize these differences and align your people accordingly as it relates to their job function, whether it’s in sales, marketing, human resources, etc…  You wouldn’t have someone like Donald Trump head up your HR department unless you wanted everyone fired, right?  Understand your employees’ strengths and put them in positions where they will have the greatest impact.

At the same time, you need to get your diverse workforce to work together.  Simply putting them in a group setting and hoping they come up with unique and uncommon ideas will not happen on its own.  Without the proper guidance in a group setting they will talk about what they have in common rather than their differences.  All you will get is group-think and nothing innovative will come from them.  It is important to let the group know everyone’s background and who has knowledge in certain areas and to encourage them to share their unique knowledge.  But take it one step further.  Instead of just having the group share their unique knowledge, encourage an environment where they can debate so as to challenge the ideas of other members.  Yes, some disagreements and hard feelings might come of this, but it could lead to coming up with new and innovative ideas.  Ideas that could possibly change the marketplace you are in.

The landscape of the marketplace is diverse and constantly changing.  You must embrace it or you will miss out on new opportunities.  The same goes for your workforce.  Diversity in your workforce isn’t just the “right” thing to do.  It’s the smart thing to do.

robert_driscoll_color This article was contributed by Robert Driscoll, co-founder of Active Garage. You can follow Robert on Twitter at rsdriscoll.
  • Share/Bookmark

Quality #8: Best Practices are Contextual

by Tanmay Vora on November 18, 2009

Welcome to the eighth post in this 12-part series on QUALITY, titled #QUALITYtweet – 12 Ideas to Build a Quality Culture.

Here are the first seven posts, in case you would like to go back and take a look:

  1. Quality #1: Quality is a long term differentiator
  2. Quality #2: Cure Precedes Prevention
  3. Quality #3: Great People + Good Processes = Great Quality
  4. Quality #4: Simplifying Processes
  5. Quality #5: Customers are your “Quality Partners”
  6. Quality #6: Knowing what needs improvement
  7. Quality #7: Productivity and Quality

#QUALITYtweet The best practices are contextual – they

worked well for someone in a given context. Are you

applying them in the right context?

Imagine a doctor prescribing a standard medicine based on common symptoms without carefully analyzing other ailments and patient history. A doctor knows the best medicine to cure a particular ailment, but he would look at a patient’s context and then decide if the “best medicine” is really best for a particular patient.

Process managers play a role of doctors for the organizations. They have to identify all possible problems (symptoms) and then suggest a solution (medicine). Best medicines for different types of ailments are termed as “best practices” in business.

Best practices are a set of processes that, in a given context, have the best likelihood of delivering quality products or services. In equation of context identification, some of the variables are:

  • Your goals as an organization
  • Market segment you operate in
  • Your target customers
  • Nature of your product / services
  • Types of customer you already serve
  • Team capabilities and internal alignment
  • Management commitment and sponsorship to improvement initiatives
  • External market pressures (e.g. recession)

The list can go on. Best practices often tend to ignore these variables because they worked in past for someone in a particular context. Their context may be different, but never a static one. Implementing best practice without considering organization’s context is like prescribing a standard medicine without looking into symptoms. Both can be equally dangerous!

So how are best practices useful? Studying best practices can give you some very useful insights on possible solutions for your business challenge. They offer alternative perspectives on ideas that can minimize your risks.

For process improvement experts, having access to best practices can be their biggest asset. But their ability to apply those best practices in an organization’s context is absolutely mandatory for success. As a professional, there is no fun in having a best practice for everything and a solution for nothing!

As an organization, you can leverage best practices by carefully studying them and mapping with your unique business challenges. For this, improvement managers need to understand nuts and bolts of business. Once the context is understood, best practices can become your best guide so that you don’t have to re-invent the wheel. Depending on context, you can either implement a best practice as it is or select portions of a best practice that can be most useful for your context.

Simply believing that a best practice will work for you just because it worked for someone else in the past and applying them in vacuum can harm you more than it can help.

There are no silver-bullets in business and things like context and innovation does play a huge role. As one of the Dilbert comic says – “If everyone is doing it, best practices is the same thing as mediocre”.

Tanmay VoraTanmay is a Software Quality Management professional based out of India. He hosts QAspire Blog and tweets as @tnvora. He is also an author of the book #QUALITYtweet – 140 Bite-Sized Ideas to Deliver Quality in Every Project
  • Share/Bookmark

Check your ego at the door!

by guest on August 12, 2009

check my ego at the doorWhen I look back over all the important lessons that I have learned during and related to my career, some of the most important came before my career even started.

First, some background:

I had the distinct advantage of being an engineering intern at a large aerospace firm while I was a sophomore in college. It allowed me a unique viewpoint in that I was surrounded by exciting technology and incredibly accomplished people (and I knew I couldn’t be laid off, which was a plus). I viewed this time as an opportunity to learn about careers in advance of starting my own. The world was bright and full of possibilities. I soaked up as much as I could about the profession, about corporate America, and about careers in general.

It was during this time that I experienced one of the most important lessons that I have ever learned – to check one’s ego at the door.

One afternoon I was asked to join an engineering review meeting. The purpose of the meeting was to review the progress and share ideas for improvement of the 8 major components that comprised the device we were making. Each component was represented by the lead engineer. In addition, there was a project manager and myself. The 10 of us entered a conference room at 2:00PM for a 2 hour meeting.

What ensued was a lesson that I still reference today.

The engineer of component #1 stood up, gave his progress report, and stated some of the challenges he was experiencing and how he planned to solve them. The other 7 engineering leads then suggested alternative solutions and constructive criticism (and the suggestions were quite good). Upon each suggestion, however, the lead engineer of component #1 immediately shook his head and responded that his solution was superior and that there was no need to consider alternatives. The other 7 engineers became agitated that their views were not being fully considered. But the engineer of component #1 concluded his presentation and sat down. Following his presentation, the lead engineer of component #2 stood up, gave his progress report, and stated the challenges that he was experiencing. Again, the other 7 engineering leads gave suggestions and alternative solutions, but they were similarly dismissed by the lead engineer of component #2. Again, the other 7 engineering leads became agitated that their solutions were not being considered. The lead engineers of remaining 6 components, in turn, gave their presentations, listened to the suggestions and criticisms, and dismissed them. And in each case, the 7 other engineers were agitated that their views were not being considered.

In all, the “2 hour” meeting took 6 hours to complete, primarily due to the length of time that each engineer took to refute the proposed suggestions. In each case, the lead engineer expended immense effort to prove that his ideas were superior to all the others. And in each case, the other 7 engineers expended immense effort to prove that their alternative solutions were worth merit. But in each case, the engineers were willing to provide criticism but not receive it… or one could also assess that each engineer was capable of talking, but none was capable of listening!

As an intern, I found myself amused and chuckling quietly to myself. If this had been a graded exercise for one of my engineering laboratory classes, we all would have failed because while we would have succeeded in communicating ideas, we would have failed in sharing and accepting ideas for improvement. What I didn’t immediately understand was that if I, a sophomore in college, could perceive the problem, why couldn’t the lead engineers? What was the specific problem that was preventing them from learning from one another?

What was the source of the problem?

And then it struck me!

It was not about the problem or the best solution anymore… it had become all about the egos! Each engineer had committed the same mistake of allowing their ego to interfere with the exploration of a better solution. Their egos were preventing the learning process from occurring.

It became clear to me, at that point, that the key to a successful meeting (and career) is checking your ego at the door so that your mind is open to other possibilities. Leave your ego outside the conference room (or office building).

I am so glad that I learned that lesson during that day. At each stage of my career following that meeting, I have allowed for the possibility that – “for every solution I have conceived, there may be a better one.”

The biggest takeaway for me:

I have recalled this lesson time and again and it has helped me to NOT avoid criticism. In fact, I have learned to seek criticism and feedback, whether it be good or bad, at all times. For if I reach the point where I think my solutions are the best to the exclusion of all other possibilities, then I have reached the point where I can no longer learn. And if I cannot learn, then I cannot progress as a person.

—–
mike markey outside cropped Michael Markey has 16 years of engineering and software experience in various areas including aerospace, military, and commercial sectors. He currently leads a team of consultants that specialize in access control and commercialization of online content.

  • Share/Bookmark