My Photo

Your email address:


Powered by FeedBlitz

Interesting People to Know

August 27, 2007

Breaking the Negativity Habit

There always seems to be one on the team, the person who says, “we can’t do that” or “that isn’t my job,” bringing an attitude of negativity to your group.  Negativity in the workplace is like a cancer.  One person’s bad attitude can spread throughout the organization, severely hurting your business.  You need to confront this individual about their negative behavior by giving them feedback.

A negative reaction is not a personality trait, it’s bad behavior, and bad behavior often becomes a habit.  Many “negative” people don’t even realize that they are being negative.  Once you point out to them what they are saying, and how it affects you, they can begin to break the bad habit.  Work with the person to come up with ideas for a new way to respond to requests.  They probably need help with this because they are stuck in their current behavior and really can’t see any other way to act.  Praise them when you see a change in the negative behavior – this will help to reinforce the change by providing feedback that the change is working.

July 18, 2007

Separating 'People' from the 'Problem'

Often, when conflict erupts on our project, we begin to look for who is to blame.  It is easy to get caught up in the “fight” and in “winning.”  It’s a lot harder to get the issue resolved while ensuring that your relationships remain undamaged.  Don’t forget, everyone will still have to work together to complete the project.  Try the following steps to avoid being trapped in this vicious win/lose cycle:

1.  Seek to understand the problem – Ask probing questions to try to flesh out all aspects of the problem, no matter how angry or hostile the other parties seem to be.  Don’t become defensive; you are trying to understand the problem and the assumptions each of the other stakeholders have.  This will give you a clearer picture of what the real issues are.

2.  Don’t make it personal – Take an objective point of view – don’t become engaged in the battle!  Take the role of negotiator or fact finder.  As people get wrapped up in the battle and in trying to win, the more likely they are to start feeling that the issue is a personal matter.   Remember, it is a project issue.  Your success will depend on your ability to not take things personally.

3.  Don’t seek blame – Avoid the “blame” trap.  Seek solutions and understanding.  People generally act logically; your job is to find the logic behind their actions.  It is always there and often has nothing to do with the stated problem.

4.  Agree on the problem – Work to gain agreement on what the problem is before you attempt to find solutions.  If we don’t agree on what the problem is how can we ever agree on the solution?

If you follow these four steps, you will develop productive problem solving on your projects… and you will find yourself keeping your cool despite what others are doing.

June 20, 2007

The Chinese Finger Puzzle


Most children have at one time or another played with a woven straw cylinder that is a few inches long known as a "Chinese finger puzzle". There is an opening at each end just large enough for a finger to be inserted - and trapped. Trying to escape, you tug in the opposite direction, but the harder you pull the tighter the fabric stretches around each finger. Only by pushing inward, thus moving counter to the direction in which escape appeared to lie, can you get free.

This is a wonderful metaphor for how non-adversarial negotiating works. Instead of pulling toward our own self interests and protecting ourselves, we instead push toward the other people and the issues involved. We seek to really listen and understand , so that then, together, we can co-create a good solution to our problem. The more overlapping your interests are, the more ability you will have to co-create a solution that gives everyone what it is they need.

The problem with an adversarial approach is that we pull away from each other, like in the finger puzzle, and we get trapped. Now, it is very difficult to really talk to each other, to explore possible solutions, and to co-create durable solutions. Talking to each other, and not at each other, is the key to being able to agree on the core problem.

I often listen to both sides tell me their story. It seems to me that they have never really talked to each other. One side tells me that the problem is X and the other tells me that the problem is Y. But is my head I'm thinking of course they don't agree. Because, they don't agree on the problem. If they don't agree on the problem, of course they don't agree on the solution (which is what they have been arguing over for months and years).

For lawyers, an adversarial approach defuses a client's power and does a disservice to their ability to create solutions to today's problems. I envision that the lawyers of tomorrow will be facilitators who bring people together and help them resolve complex issues - and escalate along the adversarial continuum only as needed.

May 17, 2007

The Power of Leadership

Lately, many business articles and blogs have been concentrating on Leadership (Raven’s Brain, has been posting on how to be a good leader; this month’s Business 2.0 has the cover article, "Ripping Up the Rules of Management") . I would like to talk about the power of a leader during meetings. No one can stop a conversation faster than the person in the room with the most authentic power. When that person talks, everyone else stops talking and listens. They may listen because the leader has something worthwhile to say or, unfortunately, they could be listening because they fear retribution. In order to have a successful meeting, the most powerful person (or people) in the room needs to “step back” and allow the team to be empowered. Without empowerment a true partnership cannot develop. Relationships will be based on the hierarchy of each organization.

Remember, a good leader:
Opens up communications
Seeks to understand and resolve problems
Builds a team

April 03, 2007

The Root Causes of Miscommunication

Raven’s Brain, quotes an article written in ComputerWorld, “For IT Projects, Silence Can Be Deadly” . The article says


“The research suggests that the culprit in 85% of project failures is silence. The study showed that there is a definable set of project communication problems that are far more common than most senior leaders realize. An estimated 90% of project managers routinely encounter one or more of five critical problems in the course of a project, but the killer is the silence that follows.”

For the past ten years I have asked project teams “from your experience, what is it that makes one project succeed and another fail?” Over 95% of team members said that good communication was the reason for their success. After asking this question of 134 different project teams, and then working with each team to improve their results, I began to realize that often what the team believes to be a “communication” issue is actually a symptom of the real problem – or root cause. When a team identifies their problem as one of poor communication and then works to try and resolve the issue, significant improvement could not be made. Only by understanding and addressing the root cause was any improvement seen.

There are seven different root causes for team failure that the project teams misidentified as poor communication.

1. Fear – Fear makes team members feel the need to protect their own interests. When we feel to the need to protect we are not going to be open, therefore communication is going to be stifled.

To overcome fear you must work to develop trust among the team members. Trust develops when you do what you say you are going to do and by doing your part to help the team succeed. Trust erodes when someone feels they are being treated unfairly. So always talk about what is fair when you see fear erupting on your project. Then, work to find a way to resolve issues that is fair to everyone involved.

2. Misaligned expectations – When the team members each have a different expectation on how things are supposed to work (usually about roles, responsibilities and authority), you have misaligned expectations.

Draw a picture of how your team is organized. Who is doing what, how do people fit into the process? What is their role? Who has the authority to make which decision? What is the decision making process? By drawing a picture and allowing team members to ask questions, you will begin to align expectations by agreeing on how things are supposed to (or need to) work.

3. Confusion – When there is confusion, chaos will break out. Again, this can be over roles and responsibilities, or over processes.

Work to become a Trusted Leader. For a team to succeed, someone must be the leader. When there is no clear leader, people vie for power and position, and that never leads to success. Instead work to become a trusted leader. A trusted leader is someone who people follow because they trust them to lead the team to success. The leader can offer clear direction problem solving and decision making when needed.

4. Loss of Momentum – When everyone on the team is not in the boat, facing the same direction, and rowing toward project success, the project loses momentum. The more frustration there is, the more loss of momentum you will have.

Resolve issues quickly. Teams start out and gain momentum over time. When problems and issues arise it causes a loss of momentum. However, if the problem or issue is resolved quickly the momentum I sonly slightly diminished and the team continues to move forward and grow.

5. Dissatisfaction – Research shows that when project teams dread going to their jobs (the level of the job satisfaction is low) the project is in deep trouble.

Build in fun. Teams that have “fun” perform better and you can build in the fun. It is important to take time to laugh and enjoy each other. I have seen teams that play golf, have barbecues, share a joke at the start of each meeting, and learn to fish together.

6. Lack of Commitment – When people aren’t really committed to the success of your project or if there are inadequate resources, you can have “slack.” This is like slack in a rope. You don’t have a strong team focused on what it will take to succeed.

Manage the level of stress. Some people re just along for the ride and are not really committed to the success of your project. This causes enormous stress on other team members. You can manage the stress by celebrating accomplishment.

7. Unconscious Incompetence – Inexperienced staff can face a very steep learning curve. They focus on what is available to them: The specifications, contact and drawings. Documentation becomes the focus instead of problem solving.

Be open to mentoring. Both the experienced and inexperienced team members must be open to the possibility of sharing knowledge. Having a mentor can shorten the learning curve for new hires by decades.

March 07, 2007

Keeping Score

On his March 5th blog entry, Scoreboards & Construction, Dan Brown mentions an article written by Dennis Sowards called You Can Be Guided by Scoreboard, Dashboard.

Dennis talks about how it is important for companies to use a "Scoreboard" to keep track of the company’s profitability, customer and employee satisfaction, safety, etc., and a "Dashboard" to keep track of the details that get the company to the end result (for example: cash available, invoices outstanding, etc).

Projects also benefit from a Scorecard approach. A two-year study conducted by the International Partnering Institute showed that every project team that had a monthly scorecard improved over the life of the project. The study was based 13 different projects over the course of two years. Projects were primarily construction projects, but also included a strategic planning project and an information technology project. Each team came together at the start of their project in a “partnering” session. The partnering session allowed the team members to get to know one another and to agree on roles and responsibilities as well as how decisions would be made (process). Together the team created a commitment on how they would work together (behavior), goals for the project (results), and then they identified barriers to the achievement of those goals. Once they prioritized the barriers most critical for their success, they created ways to break down the barrier or mitigate the impact of the barrier. They made commitments to one another (commitments). All of these agreements were included in a monthly scorecard.

The scorecard was sent out to each individual team member every month over the course of the project. The individual rated how well the team was doing at living up to its commitments and agreements. Ratings were on a scale of 1 to 5, with 5 being Excellent and 1 being Poor. A report was sent to each team member monthly indicating where the team felt they were with regard to their behavior, process, goals and commitments. All scorecards and scorecard reports were sent to and from a neutral third party so that confidentiality was assured. It is imperative that the team members feel free to tell the truth from their perspective. That is what the neutral facilitator permits.

If you are interested in implementing a project scorecard for your team, here are some tips to help assure its success.

1. The team members need to be a part of developing the measures so that they buy-in and are committed to them. Measures need to be updated approximately every 90 days to make sure they are current and relevant.
2. Team members will not tell the truth if there is fear of retribution, so having a neutral third party implement the scorecard is important to its success.
3. Teams that review their scorecard results monthly were much more likely to be able to improve. The best results came when the scorecard was “required” and not optional.
4. Senior management who met together on a regular basis to review the scorecard results and then worked to support the team by removing barriers and providing resources significantly contributed to the success of the project.
5. Organizations that had several scorecards for different projects began to see patterns, thus identifying internal issues that were preventing project success.

February 25, 2007

Project Leadership

Projects are managed… sometimes very well, sometimes not. People are led. That takes good leadership along with good project management skills. Project leadership falls to those people who are in charge of the daily work on your project.

Leadership can be difficult to define. We do know that even a highly intelligent and skilled individual can fail at leadership. Another person with solid, yet not extraordinary abilities can soar. When promoting people we need to look not only at their intelligence and technical skills, but also (and maybe even more importantly) at their people skills. Research done on emotional intelligence indicates that if people don’t develop the five components of emotional intelligence their leadership abilities will fall short. They may even fail at their job. Fortunately, emotional intelligence skills can be learned. While most people are adept at one or more of the five components, all five need to be present for true leadership.

THE FIVE COMPONENTS OF EMOTIONAL INTELLIGENCE

Self-Awareness
The ability to recognize and understand your moods, emotions and drives, as well as their affect on others

Attributes
• Self-confidence
• Realistic self-assessment
• Self-deprecating sense of humor

Self-Regulation
The ability to control or redirect disruptive impulses and moods.
The propensity to suspend judgment – to think before acting.

Attributes:
• Trustworthiness and integrity
• Comfort with ambiguity
• Openness to change

Motivation
A passion to work for reasons that go beyond money or status.
A propensity to pursue goals with energy and persistence

Attributes:
• Strong drive to achieve
• Optimism, even in the face of failure
• Organizational commitment

Empathy The ability to understand the emotional makeup of other people.
Skill in treating people according to their emotional reactions

Attributes:
• Expertise in building and retaining talent
• Cross-cultural sensitivity
• Service to clients and customers

Social Skill
Proficiency in managing relationships and building networks.
An ability to find common ground and build rapport.

Attributes:
• Effectiveness in leading change
• Persuasiveness
• Expertise in building and leading teams

These components are as important to project success as good project management. Leaders in the field must learn these skills and take an active leadership role. By taking responsibility, not only for safety and budgets, but also for disputes, coordination, motivation, and communication, they will help assure that a project will be successful. If the project leaders accept these responsibilities, all the group members will be able to follow their lead.

February 17, 2007

The Four Barriers to Partnering

Listed below in order of priority are four barriers that can stop you from successfully partnering a project.

Barrier #1: Lack of commitment to, or believe in, the process and concept of partnering. This lack of commitment can range from seeing partnering as a waste of time to blatant hostility to partnering because of a belief that it gives someone else an advantage.

Barrier #2: Not bringing key stakeholders to the partnering sessions. Key stakeholders include anyone who can negatively effect the project. Often only the project management team members are invited to partnering sessions. Bring in senior management, field crew supervisors (i.e. foremen, superintendents, inspectors, etc.), subcontractors, designers and third parties such as utilities, cities, suppliers, etc.

Barrier #3: Lack of the skills required to effectively partner, in particular the stakeholders’ lack of ability to negotiate good agreements on their own after the partnering session and throughout the course of the project. As a result, the partnership breaks down as soon as there is a disagreement, a conflict, or when one party fears they are being taken advantage of. Everyone goes to their corner and comes out fighting.

Barrier #4: Lack of accountability makes the partnering session an “event” instead of setting norms that will be used for doing business on the project. If no one is responsible or held accountable for making the partnering successful (which in turn makes the project successful), then it is not likely the partnering will be successful. At the first sign of conflict the partnership will go out the door. Safety became a part of the job site culture when bonuses and reputations were tied to preventing accidents. The same is true with partnering – what gets measured and rewarded gets done.

Evaluate the potential for a successful partnering by looking at these four barriers. Determine to what extent each is present on your project. The Construction Industry Institute says we have not yet tapped the full potential of what partnering can offer our projects in terms of cost, schedule, innovation and job satisfaction. Get these four barriers out of the way to reach that potential.

Women for Wealth

I would like to thank Liz Uible, Christine Harvey and the Women for Wealth for the opportunity to speak with them. If you would like to hear the interview, please call 1-641-985-5999 and enter code 22882#. In addition, Christine Harvey has posted parts of the interview on the Women For Wealth blog.

January 25, 2007

Building Project Team Relationships

Hal Macomber just posted a great article on the Reforming Project Management online Magazine entitled Ten New Rules for Project Mangers. One of item on his list caught my eye:

6. Build relationships intentionally.
 Project teams come together as strangers. To do great work…innovation, learning, and collaboration…all take people who like and care for each other. Don't leave that to chance. Start your projects by building relationships among team members.

Here are ten tips for developing relationships among team members.


  1. 80% of your results will come from 20% of your effort. This is known as the Praeto principle. Try and stay focused on that important 20% of your work that will lead you to 80% of your results.
  2. Nothing will change until you act. If, while standing in the middle of the road, you see a truck coming at you and you fail to get off the road you will get run over. This is known as the prominent outcome. How often do we see project issues coming at us yet fail to do anything? You must take action; it is easy to predict what will happen if you don’t.
  3. Create solutions, not winners/losers. Don’t worry about winning or losing when you are trying to negotiate. Instead, focus on creating solutions that work for everyone. Winning and losing is old baggage from our adversarial relationships.
  4. Agree on the problem. If one person sees the problem as X, and the other person sees it as Y, then naturally they aren’t going to agree on a solution. It is critical that you talk to each other enough to agree on the problem, and then you are likely to be able to find a solution.
  5. Allow people closest to the problem to resolve the issue. Quality decisions come from those closest to the issue. Quality goes down as issues move away from the project level and issues tend to grow in cost and time.
  6. Keep perspective. Too often we see our job as putting out fires. Everyday there is the problem-of-the-day or moment to contend with. Over time, we begin to lose perspective. Remember that 90+% of the project is running along fine; it’s only a small part that has problems.
  7. Celebrate successes. It is important to celebrate your successes along the way and to have fun. It will help diffuse the stress level and open up communication within the project team. After all, we’re just people who’ve come together to build a project.
  8. Build on common ground. When creating project objectives, focus on those things that you all have in common: quality, safety, being on time and on budget. All of these things make for a successful project and are common goals for everyone. Keep focused on those things you have in common, NOT on your differences.
  9. Make conflict constructive NOT destructive. Conflict need not be destructive, destroying relationships and communication. Conflict can be constructive, spurring discussions and pointing out areas in need of work, helping the project to improve. It’s all a matter of attitude and approach.
  10. Always put fairness on the negotiating table. Start every negotiation or issue resolution session by first putting fairness on the table. Always ask, “What is a fair way to resolve this issue?” You will never be too far apart.

Sue's Web Sites

Blog powered by TypePad