Project Management

Strategic Project Management

by
As an "accidental" project manager, it's very satisfying to contribute to the project management community online with anecdotes and stories I've picked up from my own experience. I hope you enjoy our daily conversation.

About this Blog

RSS

Recent Posts

Tell Me You're Going to Get This Done

Quiting Isn't Easy if You Never Do It

Getting in the Way of Peak Performance

The Agony of Defeat?

Nobody Likes Being the Heavy

Categories

decision-making, empowering team members, project leadership, project management, project management fundamentals, project success, project teams, struggling projects, work management

Date

Three Proven Decision-Making Tips for Project-Based Work

linkedin twitter facebook Request to reuse this  
The Magic 8 Ball is not a good project management decision-making tool.

In a blog post written by John McKee for TechRepublic a while back, I stumbled upon these three decision-making techniques that have been successfully utilized by great leaders:
  1. Trust the Marines: The US Marines have a tool they teach their officers called the 70% solution.  If you have 70% of the information you need to have, 70% of the analysis you think is required, and feel 70% confident that you are right—get on with it.  The Marines feel that a well-reasoned decision that is well executed has a fair chance of success, but no action has no chance of success.
  2. Take a clue from the coaches: Coaches are always asking questions.  By asking questions you will learn the good, the bad, and the ugly—helping you make the best decisions.
  3. Trust your feelings, Luke: Sometimes your "internal barometer" helps you make decisions and take action.  Of course, intuition, gut instinct, or "the Force" might not be a good way to make all your decisions, but it's often a good place to start.
The ability to make quick and informed decisions is part of what makes a good leader.  After all, leaders are paid to make decisions.  "Otherwise," writes McKee, "we could just populate entire organizations with lawyers presenting both sides of any case/problem to each other all day long."

Do you have any decision-making tips you'd be willing to share? Do you have project management tools that help you make good decisions?
Posted on: August 09, 2010 10:26 AM | Permalink | Comments (1)

Four Early Warning Signs of a Project in Trouble

linkedin twitter facebook Request to reuse this  

Underground mining is a dangerous occupation.  What's more, before the advent of sophisticated breathing apparatus, methane and carbon monoxide made it even more dangerous for the men working in the mines.  In the early days of underground mining, because their metabolism was susceptible to methane and carbon monoxide poisoning, canaries played an important role in keeping miners safe.

 

  1. They provided an audible warning: Canaries typically sing most of the time—when they stopped singing, it was a warning sign that they were being overcome by the toxic gas
  2. They provided a visual warning: When they started to sway and fall from their perch, it was a signal that they were succumbing to the poison gas.
Miners who paid attention to the early warning signs owed their lives to the canaries—they were able to recognize the danger and get out of the mine before it was too late.

I think everyone would agree that missing deadlines or exceeding budgets is evidence that a project is probably in trouble.  However, those symptoms are often recognized after it's too late to do anything about it.  Anyone doing project based work knows how important it is to recognize a project in trouble before it's too late.  Not too long ago, I came across this list of early warning signs that every project manager should be aware of:
  1. Direction from management is either missing or inconsistent: The only thing worse than project leadership that is missing in action, is direction that contradicts itself and changes frequently.
  2. Business management and project management aren't on the same page:  If the project gets consistent direction, but it's at odds with company business objectives, there is more than likely a problem.
  3. Project goals are not clearly articulated and understood by the project team:  Although every project usually has a business goal or two—projects without a business objective should probably be reconsidered, right?—often those goals aren't clearly articulated or understood by the project team.  Occasionally, the business objective is thought to be so obvious it's never clearly stated.  Unfortunately this could lead to misunderstanding and inconsistent presumptions about priorities.
  4. Team members don't communicate with each other:  Sometimes, even teams that get along well don't communicate well. Communication and collaboration are essential to any successful project.
Recognizing problems before it's too late to do anything about them is critical to work management success.  Addressing issues early is the best way to save a lagging project, as well as a project manager's career.  What early warning signs to do you watch for?
Posted on: August 06, 2010 10:39 AM | Permalink | Comments (6)

Three Keys to Redefining Work Management Success

linkedin twitter facebook Request to reuse this  

Completing projects on time and on budget has proven to be a pretty valid measure of IT project success—but should it be the primary measure?  I believe that pushing a project to completion on time is not the only objective—ultimately the project also needs to deliver business value.  Along with the worthy objectives of finishing projects on time and within budget constraints, here are some other objectives that should be considered:

  1. It should be about doing the right projects, not just doing them right.  Delivering business value and satisfying customers is becoming more important than ever—and it starts with the evaluation of which potential projects will meet those needs and provide that value in the first place.  Hopefully this has always been important, but organizations are realizing that they have to do more than give lip service to meeting customer expectations while meeting organizational goals.  It must become a primary measurement of how we determine the success or failure of any IT project.
  2. Project teams need to completely understand and address the business needs of every project.  Although everyone would agree that "quality" is very subjective, if everyone on the team doesn't have a thorough understanding of the cost of defects and rework, it doesn't matter what work management tool you use, it won't help.  Edward Deming used to talk about how organizations must build quality into the product, it can't be inspected in.  Quality assurance needs to be a part of every process from start to finish.  Smart organizations are looking at defects and their root causes through the project life-cycle to develop methodologies that improve the quality of their final deliverables.
  3. The final product needs to be stable, compatible, and easily maintainable.  It's just too expensive for organizations to maintain software that's incompatible with current systems or unreliable.  Because staff and maintenance budgets are at a premium, software that isn't will be abandoned for something that is.

The way organizations measure the success of project based work is changing.  Managers who leverage project management tools to meet these new objectives are able to better address business needs and ultimately increase their value within their organizations.

Posted on: August 04, 2010 09:59 AM | Permalink | Comments (2)

Knowing When to Say Goodbye: Scrapping a Doomed Project

linkedin twitter facebook Request to reuse this  
On September 4, 1957, the Ford Motor Company introduced the Edsel to directly compete with GM's Oldsmobile brand.  It didn't take long before Ford recognized it had made a costly mistake.  On November 19, 1959, Ford decided to pull the plug on its $350 million ($1.55 billion in today's dollars) good idea gone bad.

Regardless of the project management tools you use, successfully managing project-based work sometimes requires that project managers recognize when good projects have gone bad and pull the plug before too many resources are needlessly wasted.  Thankfully, most project managers aren't staring at $1.5 billion project that needs to be terminated—but I know of one organization that saved an estimated $8-10 million by pulling the plug on an Edsel of a project.

Ideally, the criteria for putting a DOA project out of its misery should be determined prior to the project beginning.  What's more, project management best practice suggests that the "firing squad" should be identified before the project begins too.  Sometimes in the heat of battle, it's difficult to dispassionately consider discontinuing a troubled project.

There was no single reason why the Edsel failed.  Styling, quality, and a lack of internal support at Ford have all been cited as possible reasons.  However the Edsel was manufactured in the same factories as its more successful siblings, Ford and Mercury.  The same can be said for most projects that struggle—there's seldom a single reason why a project fails.  Regardless of the reasons, scrapping a doomed project is difficult for most project managers.  That being said, I often think of Henry Ford and how he killed the car he named after his son.

How do you determine when to scrap a lagging project?
Posted on: August 03, 2010 10:27 AM | Permalink | Comments (4)

Fly-Fishing, Project Management, and the Teacher

linkedin twitter facebook Request to reuse this  

What a great weekend. Four days in the high Uinta mountains of Utah fly-fishing with my family, enjoying the 20+ degree drop in temperature, and falling asleep to the sound of distant mountain thunderstorms. It just doesn't get any better than that.

The original plan included relaxing for a few days on the shore of a mountain lake, napping in the afternoon, roasting marshmallows as the sun went down, and otherwise just taking it easy. I took my fly-rod in case I got the urge to catch a fish or two, but when my adult children started to arrive, they and those they brought with them, all wanted to learn how to fish with a fly rod—so I introduced three willing learners (my boys had been introduced years ago) to the art of fly-fishing.

From morning until the sun went down in the evening, we fished from the shore, in the canoe, or along the river. I think everyone had a great time, I know that I did. I also re-learned something I haven't thought of in a while.

If you've ever seen Robert Redford's A River Runs Through It, watching Brad Pitt's character, Paul Maclean, "shadowcast" is a thing of beauty. Fishing with fly and fly-rod is an elegant and sometimes challenging way to catch a fish. As the narrator, Norman Maclean says, "My father was very sure about certain matters pertaining to the universe. To him, all good things—trout as well as eternal salvation—came by grace; and grace comes by art; and art does not come easy."

The basic technique of fly-fishing isn't really that challenging, but as I found myself correcting form, presentation, and otherwise tweaking little things here and there, I realized that there are many things we tend to take for granted if we have experience doing something for any length of time. Basic skills I've acquired over the years, things that are just automatic to me, I found weren't automatic to my neophyte fly-fishers. However, with a little instruction, they picked it up quickly and were catching fish.

I think the same can be said for project teams. I don't think it really matters what project management tools your organization employs or your particular work management methodology, there will likely be things that have become automatic to you that the rest of your team doesn't know. Leading the team sometimes requires a manager to be a teacher, which I think makes a big difference as to whether or not you are a real leader.

So take inventory of some of the skills that you take for granted as a project management professional and see if there are skills you can share with the rest of the team to help them grow. You might be surprised how effective a little instruction can be.

What do you do to share your experience and knowledge with the team?
 

Posted on: August 02, 2010 11:21 AM | Permalink | Comments (1)
ADVERTISEMENTS

"Laughter is the shortest distance between two people."

- Victor Borge

ADVERTISEMENT

Sponsors