Working Up

Working Up in Project Management, Systems Engineering, Technology, and Writing

Working Up header image 2

Right Problem, Wrong Method, or was It the Other Way Around?

January 28th, 2010 · No Comments

by Dwayne Phillips

There are problems and there are methods of solving them. Given these two items, there are four cases that can define projects. Let’s consider the cases and how to avoid the more painful ones.

In some of my books I have written about projects that went astray, i.e. they were disasters with money and time wasted and no useful products. I have also written about projects that went just as planned, but no one used the product.

This all seems to do with the problem we choose and how we attempt to solution the problem. We have two variables and at least four cases.

  • Case 0: Wrong problem, solved incorrectly
  • Case 1: Wrong problem, solved correctly
  • Case 2: Right problem, solved incorrectly
  • Case 3: Right problem, solved correctly

Now that we have the list out of the way, let’s describe each case. Time and space won’t permit a deep discussion this morning, but let’s start.

Case 0: Wrong problem, solved incorrectly

This is the worst of everything. We spend a lot of resources and produce nothing. Even if we had produced something, no one would have used it because no one wanted it. Why such waste? Who knows?

Case 1: Wrong problem, solved correctly

This is a frustrating case that has visited my life several times. Someone tells me what to build. I enlist the help of many others, we do everything right (I am pretty good at this), and hand the product to the sponsor. The product goes right to the shelf and collects dust. No one wanted it. We had done a fine job of solving the wrong problem.

Case 2: Right problem, solved incorrectly

This occurs often. We all agree on what we need, so we attempt to build it, but fail. It isn’t easy to build systems even when everyone agrees on what we need. For example, we need a car that runs on renewable energy, costs little, and does no harm. We just aren’t sure how to go about building that.

Case 3: Right problem, solved correctly

I fear that this case is the least occurring. I don’t have data on that and I suspect that I never will have the data as people don’t want to report candidly as they, er I mean we all, would look bad. Anyways, this is the success story. This is the Apple iPod, this is the cell phone, and this is the automobile. There was a need, a good product emerged, and people have used the product.

Conclusion?

This all means something, but what? First, before attempting to solve a problem, do everything you can to ensure that it is the right problem.

Walk around the building asking, “Who is dying to have this?”

If few or no people answer, “Me! Me! Me!” then you have the wrong problem. Run, don’t walk, away from it.

If a large group of people want the solution to the problem, call me. I do know a few things about solving problems correctly. And, by the way, there are a lot of other people in addition to me who also know about solving problems correctly.

Tags: General Systems Thinking · Management · Problems

0 responses so far ↓

  • There are no comments yet...Kick things off by filling out the form below.

Leave a Comment