A Project Is...

Project managers get in trouble when we try to complicate things. In my career, I have worked for many different types and sizes of organizations. Some have embraced Project Management and others have made excuses so as not to be constrained by what they believe is a process that slows things down (adds cost and overhead). I have preached the same message for years. Project Management is designed to help reduce or eliminate rework and surprises at the end of a project.

So why don’t some organizations see the value of Project Management? Usually it is because they do not understand the benefits of Project Management, they do not trust the Project Managers they currently have, or the ones they have encountered in the past. OK, we can accept that, however, what we should never accept is the idea that Project Management just adds cost and overhead.

We need to educate those around us about the difference between projects and other organizational work. Senior management needs to realize the fact that work is basically broken down into two areas: Operations (focused on Maintaining) and Projects (focused on Change). Most organizations do an adequate job of managing their operations; however, my experience (limited as it is) has shown that projects and the support of project management vary greatly.

Every organization has projects; sometimes they are just too busy to realize it. As project managers, we need to keep fighting the good fight of educating the influencers in our organizations about the benefits of Project Management. In addition, we need to realize that the benefits of Project Management are demonstrated in the successful implementation of projects. Do not preach the benefits of Project Management; demonstrate them by walking the walk and talking the talk.

So, a project is:

A temporary endeavor to create a unique product or service

Constrained by a finite budget

Constrained by a finite timeline (defined start and end date)

Composed of interrelated activities

Focused on attaining one or more clearly defined objectives

The last point needs to be stressed. Without clearly defined and agreed upon objectives your project is doomed to fail from the start. I would also add that your project does not have a chance for success unless you have an engaged, influential, and respected executive in the role of project sponsor.

Project Management Requires Discipline

Discipline is the act of encouraging a desired pattern of behavior. George Washington said: "Discipline is the soul of an army. It makes small numbers formidable, procures success to the weak, and esteem to all". In other words, discipline is the glue that holds organizations together. 

We can't have agile and effective project methodologies or organizational processes without discipline. In short, effective discipline requires effective organizational oversight.  Finally, discipline begins at the top and works its way down. Organizations with poor discipline have weak, ineffective leaders at the top.  Weak, unengaged, ineffective leaders kill organizations. Can you say Enron?

Remember, the lack of project discipline is the fault of all project team members, but the cause of a lack of discipline lies at the top of the organization.

Stages of Creating Major Change

The below was adapted from the book "Leading Change" by John P. Kotter (see more 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

    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