Lack of Communication Leads to Project Death

Communication is so critical to medical device product development.

Communicate early. Communicate often.

But My Project Team Won’t Talk to Me

Last week I was told by a project team member that I would receive a certain work product by yesterday. It didn’t happen.

Friday, I was told by a team member that some minor updates were necessary and be ready by the end of the day. It didn’t happen.

Yesterday, I called each individual team member to get status updates on their specific tasks. I got to talk to each person’s voice mail.

I followed up with email messages. No responses.

I spent most of the day in a grumpy / frantic mood. Why was I not getting updates? Why were commitments made and not kept?

Okay, this is not the first project I’ve managed. While the statements listed above are all true tales, none of these are unusual. In fact, each of these scenarios is very common for every project and will most definitely repeat themselves again on this one. Despite my best attempts otherwise.

So I just keep at it. I did get a phone call update around 5:00pm last night from one resource and spoke to a second around 8:00pm. Not the responses I wanted in either case, but at least communication was happening.

Pass The Bricks. I Need To Make Our Wall Stronger.

Have you ever worked in a company where every functional group had their own “kingdom”? I have. It was frustrating. I’ve also had the pleasure of consulting for companies where the objective seems to be “How can we screw the other groups?” and communication seems to be discouraged. Here is a short story based on an actual meeting I attended. The names and places have been changed. I might have added a little “color” to make the story funnier.

Introduction

I was recently part of a project for a medical device company that required changes to many products due to changes in regulations. During the exercise, some of the company personnel decided now would be a good time to assess product sales and to eliminate products with little to no sales during the past few years. However, this company has never eliminated products, regardless of sales performance.

Chapter 1

The sales and marketing resources look over the list of affected products. They decide to exit the market on about 10% of the products. There haven’t been significant sales for quite some time. Several of the products have also been replaced by newer and better products. Keeping these products active is a burden on company systems, inventories, etc. and would require additional expenses and maintenance to keep regulatory registrations up to speed. Everyone reviews the list and agrees.

Chapter 2

The team proceeds with eliminating the products from the market. A decision is made to scrap quite a few of the products on the shelf. For some of the others, the team decides to keep the inventory and allow slow sales to deplete the remaining inventory. In all cases, no more product will be manufactured. In all cases, the products will not be re-registered or marketed. But it makes sense; some doctors still might use existing quantity on hand.

Chapter 3

The team works hard but makes the project deadline. This is a real deadline because the regulations go into effect. Any product not meeting the new regulations by this date represents a compliance issue. The team is happy and celebrates success with a small party–unusual in the corporate world these days.

Chapter 4

Weeks after the project is done, requests stream in demanding that several eliminated products be reactivated. In a couple of cases, there might have been some errors. Humans make mistakes. The team works to correct the errors and all is good.

The requests continue. Not a lot, but more than the team expects. The team members have moved on to other demanding projects. Didn’t everyone review the list of products slated for elimination?

Chapter 5

As it turns out, not everyone did review the list. As it turns out, the team’s interpretation of “elimination” is not shared across the company. As it turns out, the systems the team used to eliminate products are not used by other functions in the organization. Bummer. This project was pretty smooth until now.

Other functions, not a part of the original team, start demanding reactivation of several products. “You need to reactivate this product. If not, we will lose a couple thousand dollars in sales.” Unfortunately, it would cost the company at least this much to reactivate the products just to fill the small order and then eliminate it again.

Conclusion

The team calls a meeting, this time including the “other functions”. The attendees all learn a little about one another and the importance of their roles. More importantly, the attendees learn that none of the enterprise systems that each functional group uses communicates with the other. Most importantly, the attendees learn that the functional groups are terrible about communicating with one another.

Epilogue

Regardless of size, companies need to understand the importance and usefulness of cross-functionality and active communication. Building kingdoms went out of fashion during medieval times. We need to establish cultures of communication. Stop building walls and figure out how to tear them down. Understand that change is part of life. Realize that any change should be examined holistically. Understand both short-term and long-term ramifications and benefits of change.

Reblog this post [with Zemanta]

The Tyranny of Email

I caught about 10 minutes of NPR today. Author John Freeman was on the Diane Rehm show. Freeman was talking about his latest book, “The Tyranny of Email: The Four-Thousand-Year Journey to Your Inbox“. I have not read the book nor did I catch enough of the interview to comprehend the author’s point of view. However, Rehm offered a statistic that I think is remarkable: employees spend 40% of their work day dealing with emails.

I did catch a couple of points from Freeman as “alternatives” to email that I find interesting:

  • write letters, postcards, etc.
  • pick up the phone and call people
  • set up face to face meetings

I’ll admit my self-perpetuated reliance on email. I’ve noticed when I send fewer emails, I have fewer to respond to. While we can’t completely eliminate emails, CQ will be evaluating our communications and will incorporate “old school” communications more.

Reblog this post [with Zemanta]

Communication Break Down (Updated)

During the past week, I was approached by two people asking me if I would like to join and be part of an advisory board for a networking group–let’s call it “CloudKickers” (name changed to protect the innocent). In each case, I told the person I used to be a member of CloudKickers but resigned my membership a couple months ago. Neither realized I used to be a member. Both mentioned, though, that my name came up often by the leadership of CloudKickers as a person to target for membership.

Do these people communicate?

My primary reason for leaving CloudKickers was personal. I just didn’t have the time to devote to meetings and networking within this group because of other commitments. But the communication, or rather lack there of, was a minor concern.

Here is a tip for any networking group, project team, company, relationship, etc. Your communication is always inadequate. Perfect communication is not attainable. However, striving for perfect communication will result in excellent communication.

Update: I received an email yesterday from the CloudKickers organization. Here it is (again, names have been changed to protect the innocent):

We have compiled a list of CloudKickers that seem to fit the ideal member for “Walkways to Excellence” and YOU made the list.
“Walkways to Excellence” is one of our program hubs (program meaning it is speaker-driven rather than an activity-driven event).  The speaker is an intergral part of big business here in the city.  All of the speakers we have had so far have been really great!
Consider “Walkways to Excellence” a filter that gets all of the people who provide products and services to large companies ALL IN ONE ROOM!
The person who sent this email definitely knows I have NOT been a member for a few months. Despite my requests to be removed from all CloudKicker email lists, I still remain on a few. Of course it’s easy to delete an unwanted message. No big deal. However, I’ve talked to many, many people who are on CloudKicker email lists, have asked to be removed, and yet continue to receive messages.
Communication break down.