Symptoms of Defective Strategic Planning

To be successful, organizations need to ensure that their projects and project outcomes support their strategic goals. Poor strategic planning leads to failed projects and people working on projects that add no value to the organization’s bottom line.

Lately I have been interested in learning more about Strategic Planning and the role it plays in the success or failure of projects. I found the text below in the book, Advanced Project Portfolio Management and the PMO– by Gerald I. Kendall, PMP and Steven C. Rollins, PMP. The book is an excellent resource for the seasoned project manager looking to move his or her Project Management Office to the next level.

Symptoms of Defective Strategic Planning (pg. 73)

Project and resource managers often fight over resources. The organization’s arteries are clogged with too much work.

Priorities of projects frequently change, with resources reassigned.

Senior managers have the authority to unilaterally approve and release projects

Projects are released as soon as approved by a senior manager, irrespective of the availability of the resources to do the work

Senior management frequently complains about how long it takes to implement change

Even when a strategic idea is implemented, the company sometimes does not achieve major or expected improvement

There is no comprehensive document or portfolio that links all of the organization’s projects to the goals and the strategic plan

There is significant turnover at the senior management level, right up through the president

The strategic plan is presented as a list of ideas or initiatives. There is no attempt to validate if those initiatives are sufficient by themselves to meet the organization’s goals. The cause-effect logic tying those ideas and the resulting effects to the goals of the organization is absent

The list of ideas in the strategic plan is not sequenced. Therefore, each executive assumes that he or she must try to implement all ideas simultaneously, and that his or her functional initiative must be the top priority

The book goes on to talk about some of the problems that executives face when creating strategic plans. I have summarized some of the information below.

Root Problems of Strategic Planning Processes (pg. 75)

Executives don’t speak the same language. They tend to view the organization through the eyes of their experience and silo. They don’t understand the organization as a whole.

The organization has measurements and policies that are silo-oriented.

Executives lack the skill to build a strategy that has the commitment of the entire senior management team, meets the goals of the organization, and can be implemented with current or planned resources

Strategies ignore internal systems that are out of control. When executives attempt to improve something before bringing it under control, they often throw the entire system into chaos.

Closing Thoughts

Many organizations I have worked for experience the challenges noted above. As project managers we know that poor or ineffective planning can lead to failed projects. The challenges I currently face in the workplace can in many instances be tied back to the lack of an effective or poorly communicated strategic plan.

I really could use some feedback on this subject. I’m not an expert in this area and always welcome the e-mails I receive that offer additional information.

Free Project Management Software

In case you didn’t know, there are a couple of free software packages available that fit nicely into the Project Managers tool box. The first is Control CE 6.3. The vendor states that this free program can be used for Process Mapping, Business Improvement, Business Reengineering, Software Package Implementation, and Quality Management.

The vendor goes on to say “Whatever the project, it all starts with an understanding of the business from a process and metrics perspective. That means mapping processes, and identifying KPIs. To get REAL ownership and buy-in they need to be developed in LIVE workshops. Control-CE was designed to be used confidently by consultants with little training, in live workshops where people have a short interest span.
Whilst control-CE has some great process mapping functionality, it extends beyond simply creating hierarchies of diagrams”.

I have reviewed and used the Control CE software and find that it is quite powerful and worth a look.

The other free software program is Open Workbench. According to the vendor, “Open Workbench is an open source desktop application that provides robust project scheduling and management functionality. Already the scheduling standard for more than 100,000 project managers worldwide, Open Workbench is a free and powerful alternative to Microsoft Project.

Released in December 2005, Open Workbench 1.1.4 provides significant new enhancements and bug fixes. For more information on version 1.1.4, please review the Open Workbench 1.1.4 Release Notes. The source code for Open Workbench 1.1.4 is also available on SourceForge.

Open Workbench provides all the functionality and benefits that project managers expect in a world-class scheduling application:

• Open Workbench can be used and distributed free of charge throughout an enterprise.
• Open Workbench is a stand-alone desktop application that provides robust project scheduling functionality.
• Open Workbench provides the unique ability to generate project schedules based on resource constraints.
• Open source developers will find a ready-made community of business users interested in their enhancements and extensions.

The source code and other developer information are available on SourceForge.

The open source distribution and community development model will now bring quality, innovation and cost advantages to the project management world. Open Workbench can also be used in a fully integrated fashion with CA's Clarity solution. Please visit www.niku.com/go/owb for more details”.

I have found Open Workbench to be a powerful standalone project management scheduling software package. Again, you will have to determine if Open Workbench's features and functions can work for you.

Hopefully some of you will find one or both of the above software packages useful. Your comments are always welcome.

Eight Stage Process of Creating Major Change

I like the process below for creating major change. It was taken from the book "Leading Change" by John P. Kotter (see source information at the end of the posting).

1. Establishing a Sense of Urgency
a. Examining the market and competitive realities
b. Identifying and discussing crises, potential crises, or major opportunities

2. Creating the Guiding Coalition
a. Putting together a group with enough power to lead the change
b. Getting the group to work together as a team

3. Developing a Vision and Strategy
a. Creating a vision to help direct the change effort
b. Developing strategies for achieving that vision

4. Communicating the Change Vision
a. Using every vehicle possible to constantly communicate the new vision and strategies
b. Having the guiding coalition role model the behavior expected of employees

5. Empowering Broad-Based Action
a. Getting rid of obstacles
b. Changing systems or structures that undermine the change vision
c. Encouraging risk taking and non-traditional ideas, activities, and actions

6. Generating Short-Term Wins
a. Planning for visible improvements in performance, or “wins”
b. Creating those wins
c. Visibly recognizing and rewarding people who made the wins possible

7. Consolidating Gains and Producing More Change
a. Using increased credibility to change all systems, structures, and policies that don’t fit together and don’t fit the transformation vision
b. Hiring, promoting, and developing people who can implement the change vision
c. Reinvigorating the process with new projects, themes, and change agents

8. Anchoring New Approaches in the Culture
a. Creating better performance through customer and productivity-oriented behavior, more an better leadership, and more effective management
b. Articulating the connections between new behaviors and organizational success
c. Developing means to ensure leadership development and succession


SOURCE: Adapted from John P. Kotter, “Leading Change,” Harvard Business School Press 1996

My Love/Hate Relationship with Project Teams

Project teams can be a project manager's greatest resource or can be a huge impediment to getting things done. I have a lot of opinions about project teams and most people would find them to be controversial. I will state them here and hope for feedback.

My general theories about project teams follow:

Project teams tend to waste a lot of time, and like to blame others (outside the team) for lack of project process

Project team members are rarely on the same page

Internal politics doom many project teams from the start

Project managers usually don't have the ability to reward or punish bad behavior

One or two "bad apples" can spoil the whole bunch

Many functional managers don't believe they have to support project teams, and at times they do all they can to undermine the team approach to managing projects

A "visionary" is a person that is usually disengaged from everything and accountable for nothing

Lack of leadership, direction, and follow-up from top management is the number one cause of project team failure

If you have a member of your project team that would rather be doing something else, do everything you can to grant their wish

Most project managers are wimps when it comes to managing individual members of their teams

Lots of organizations talk a good talk when it comes to project management and teams, then go about managing change using the same old failed processes

Many project team members are loyal to their functional departments, not to the project

Teams by nature are dysfunctional, and because of this fact the project schedule and estimates should reflect this

Dysfunctional project teams are the fault of senior management because of their refusal to attend important project team meetings

Many project teams are composed of the wrong people doing the wrong things at the wrong times.

Obiturary

Today we mourn the passing of a beloved old friend, Mr. Common Sense. Mr. Sense had been with us for many years. No one knows for sure how old he was since his birth records were long ago lost in bureaucratic red tape.

He will be remembered as having cultivated such value lessons as knowing when to come in out of the rain, why the early bird gets the worm and that life isn't always fair. Common Sense lived by simple, sound financial policies (don't spend more than you earn) and reliable parenting strategies (adults, not kids, are in charge).

His health began to rapidly deteriorate when well intentioned but overbearing regulations were set in place - reports of a six-year-old boy charged with sexual harassment for kissing a classmate; teens suspended from school for using mouthwash after lunch; and a teacher fired for reprimanding an unruly student, only worsened his condition.

Mr. Sense declined even further when schools were required to get parental consent to administer aspirin to a student; but, could not inform the parents when a student became pregnant and wanted to have an abortion.

Finally, Common Sense lost the will to live as the Ten Commandments became contraband; churches became businesses; and criminals received better treatment than their victims.

Common Sense finally gave up the ghost after a woman failed to realize that a steaming cup of coffee was hot, she spilled a bit in her lap, and was awarded a huge settlement.

Common Sense was preceded in death by his parents, Truth and Trust, his wife, Discretion; his daughter, Responsibility; and his son, Reason. He is survived by two stepbrothers; My Rights and Ima Whiner. Not many attended his funeral because so few realized he was gone.

Author Unknown.

Estimates Are Always wrong?

I have been burned more times than I can count by bad estimates. What can a project manager do to help ensure the accuracy of estimates?

First we should understand the basics behind the estimating process (there are many more than I have listed here). Some are:

• The more unique the project, the more of a challenge it will be to get good estimates
• Estimates are only as good as the estimator is at predicting the future
• "Padded" estimates are not always bad as long as the padding is communicated (... and as long as the Project Manager is the one doing the "padding")
• An estimate is not a bid
• Estimates using sound estimating practices, performed by experienced estimators from clear specifications should never be negotiated
• Ballpark estimates are guesses and should be treated as much by the project team, management, and the project sponsor

Other items to consider when estimating are:

• Ensure the statement of work or contract is clear and understood by the person(s) doing the estimates
• Ensure that a schedule or mandated date doesn't drive the estimating thought process
• Include Risk Management in the estimating process
• Ensure that estimates take into account the skill level(s) of the person(s) that will do the work
• If your work breakdown structure (WBS) is flawed, your estimates will be inaccurate

Accurate estimating is an art and a science. The estimator (or team) must take into account historical data from past proejcts, the team's knowledge and experience, the project risks, the statement of work and other project information to make the best estimate possible.

Keep in mind when planning your project that estimates aren't hard and fast numbers. They are guesses, however they should be very good guesses if you have good estimators and are following tried and true estimating practices.

The Leadership Void

"What creates trust, in the end, is the leader's manifest respect for the followers" - Jim O'Toole, Leadership Change.

I read that quote this morning and after thinking about it I realized that in many of the places I have worked there has been a consistent lack of respect shown to the followers by the leaders, which ultimately results in a Leadership Void. A Leadership Void exists when the goals of the leaders aren't embraced by the followers. Respect, or lack of it plays a big part in helping to create this void.

So what do you do when you are in an environment with a Leadership Void. My advice is to start modeling the behaviors of tried and true leaders.

Some Leadership principles I have come to believe are:

Be consistent in what you say and do. Inconsistency shows a lack of focus. Being inconsistent will undermine your credibility with others.

As a leader you will need to provide focus, constancy of purpose, and clear direction to your team. The problem with many leaders isn't a lack of personality or charisma, it is a lack of focus and follow-through.

When leading remember "beware of no man more than thyself" - Thomas Fuller. Ask for feedback from others. Remember the higher the leader is in an organization the more blind spots he or she will experience.

A good leader is a master of the big picture and is knowledgeable of the details. A leader that isn't willing to get involved in the details is just plain lazy and won't have the respect of the team they are leading.

Be careful about negative assumptions. Leaders that are high achievers know their behavior tells the truth about their assumptions.

Leaders ensure that their followers know where they fit into the big picture.

Leaders who underestimate the intellect of others tend to overestimate their own.

Other things that are always displayed by a leader are the ability to:

Create and nurture a vision

Laugh!

Leave their ego at the door

Think before acting (not quick to criticize)

Be a risk taker

State and meet commitments

Be a role model

Be a risk taker

Have a can do attitude

Encourage success

and finally...

BE VISIBLE (IMPORTANT)

1. Walk around and talk to people (this doesn't happen much where I work)
2. Schedule monthly one-on-one interviews
3. Conduct regular formal group surveys and do something with the data
4. Pick areas where Quality is lacking and form teams to fix the problem

What do you think. I welcome your comments.