The Value of Building the Right Team
|
I once worked with a fellow who processed information very differently than I did. We were contributors on the same team, but we would often "discuss" our differences in approach (most of the time in a civil manner). Although we had our disagreements, we were able to collaborate very well together because we appreciated our differences and came to discover that sometimes the perspective of a divergent view can force everyone to look more critically at the process or the proposed solution. Over the years, I have come to really appreciate the way we successfully worked together to accomplish our objectives. I've also worked with others who refused to collaborate or compromise (sometimes these were even project managers). Everyone was frustrated, nothing ever really got accomplished and projects often languished until they were abandoned or worse, ignored. Most of us have also worked with people who had no opinion of their own, refused to contribute anything but their butt in a seat, creating an even more frustrating collaboration environment than those who were intransigent in their opinions. So how do you create the perfect team?
I don't think it really matters what type of projects we work on, keeping the team working together is sometimes challenging when project teams are made up of people with different abilities and dispositions. With that in mind, we also need to remember that successful teams don't just happen. We need to use the technology and interpersonal skills at our disposal to foster a good team envirnoment where everyone collaborates and contributes together. What are you doing to keep everyone working together and successfullly collaborating? |
The Value of Building the Right Team
| A team is more than simply a collection of individuals working on the same project—or at least it should be. I once worked with a fellow who processed information very differently than I did. We were contributors on the same team, but we would often "discuss" our differences in approach (most of the time in a civil manner). Although we had our disagreements, we were able to collaborate very well together because we appreciated our differences and came to discover that sometimes the perspective of a divergent view can force everyone to look more critically at the process or the proposed solution. Over the years, I have come to really appreciate the way we successfully worked together to accomplish our objectives. I've also worked with others who refused to collaborate or comprimise (sometimes these were even project managers). Everyone was frustrated, nothing ever really got accomplished and projects often languished until they were abandoned or worse, ignored. Most of us have also worked with people who had no opinion of their own, refused to contribute anything but their butt in a seat, creating an even more frustrating collaboration environment than those who were intransigent in their opinions. So how do you create the perfect team?
I don't think it really matters what type of projects we work on, keeping the team working together is sometimes challenging when project teams are made up of people with different abilities and dispositions. With that in mind, we also need to remember that successful teams don't just happen. We need to use the technology and interpersonal skills at our disposal to foster a good team envirnoment where everyone collaborates and contributes together. What are you doing to keep everyone working together and successfullly collaborating? |
Working More, Enjoying it Less?
|
Although I have always felt that it is a good idea for everyone in the organization to be willing to pitch in and help when times are tough, I worry that too much "pitching in" will do more than lead to burnout—it will lead to exhausted workers who are frustrated and unmotivated to do anything more than what they must to survive (I guess that’s the real definition of burnout, isn’t it?). Which is not an environment where project teams can creatively problem solve or invent and create. Ultimately, this type of environment will lead to an even greater project failure rate and ultimately organizational failure. "Some experts say the superjob is the logical next step in management’s quest to make the workplace more cost efficient," writes Kadet. "The latest shift started when businesses redistributed the workload during the recession; last years nascent recovery intensified the process." Kadet says that a recent survey conducted by Spherion Staffing suggests that 53 percent of workers surveyed last year have taken on new roles, most of them without pay (only 7% got a raise or a bonus). "Now that sales are picking up, there’s even more work to do, but companies are reluctant to hire, say human-resource experts. Some are anxious about what the economic future holds," she writes, "while others are seeing their profits increase now that that their workforces are leaner." Although I believe there are probably a lot of great opportunities for careers to grow during this time, I agree with Kadet when she suggests that even the most hard-nosed bosses know they can only stretch employees so far. It’s pretty obvious that the current conditions are taking their tole on the workforce. "Indeed, a recent survey from the Conference Board found that just 43% of Americans are satisfied with their job—a record low," she says. What does this mean for project teams and the workforce at large? We’ve talked before about how multitasking can actually reduce productivity. In fact Kadet brings this up. We aren’t really neurologically wired to do dozens of unrelated things at once. At least we’re not wired to do them well. What’s more writes Kadet, "The sheer number of hours demanded by the superjob also can impair your performance as your brain gets fatigued, says Susan Koen, an organizational psychologist and consultant whose clients include Pfizer, Alcoa and Procter & Gamble." According to Kadet, "Of course, the ultimate responsibility for workload management falls to the employee. Experts say that in many cases, employers have no idea how many tasks they’ve loaded on one person, so workers have to ‘manage up.’" As project leaders, I think it’s important to have an understanding of all the work our project team members are engaged in. If we don’t have visibility into all work (not just project-based work), it makes realistic capacity planning problematic. Most people are not inclined to say no, so we need to help. I think that’s part of being an effective project leader. |
Simple Doesn't Mean Un-Important
| My daughter lives downtown—about twenty or so minutes away from where my wife and I live in the suburbs. We decided to stop by for a visit. It was the perfect weather for a short bike ride. Although I am an "epic ride" sort of guy; disappearing on the road for hours at a time, just before dark is my favorite time to ride. The light is soft, it's easy to see and somehow you can almost sense the day winding down. Even though it was a very short ride, it was still a "great" ride. Over the last couple of years project managers in many organizations are being asked to manage and organize many different types of projects. I've spoken with a number of project leaders who spend time regularly jumping back and forth between agile and waterfall projects (some may even be concurrent projects). It's pretty obvious to me, that a one-size-fits-all approach to managing projects and other work doesn't fit. For most projects, almost daily, software companies are developing sophisticated project management tools that offer resource grids, business case builders, bubble charts and interactive Gantt charts. Sometimes I wonder if we've forgotten that the point of project management is to get work done—not complicate the work. Although there are projects that might require a charter or sophisticated project plan, they aren't always needed. I'm not saying those tools and techniques aren't important. Like most of you, I work with projects of varying degrees of complexity, duration and urgency every day. Some are very structured and some are very informal. All of them are considered important to the organization (like last nights bike ride)—but does that imply that they all require the same level of formal structure? I don’t think so. With that in mind, here are three keys to simplify most project-based work:
Looking for the simplest solutions will help any project team be more effective. I was speaking with an analyst the other day who felt like most organizations do a really good job at managing major initiatives, but don't do well with other projects. Maybe it's time we started to focus less on our favorite methodology and more about the right methods for a wide variety of projects and project-based work. What are you doing to simplify the way your approach project planning? |






A team is more than simply a collection of individuals working on the same project—or at least it should be.
