The Squawk Point

Organisational Mechanics

  • Home
  • Blog
    • People
    • Data
    • Process
    • Wild Cards
    • Index
  • Podcast
  • Book

The Problem with Problem Statements

7 July, 2012 by James Lawther 5 Comments

Things I wish I had said:

The secret to success is to get your arms around a problem and knock it off ~ Anon

Worse than not saying it myself is the fact that I don’t entirely know who did say it, but we shouldn’t dwell on my failings.

On a more positive note, quotes that I can attribute include:

A problem well stated is a problem half solved ~ Charles F. Kettering

(If I had sixty minutes to save the world) I would spend fifty-five minutes defining the problem and only five minutes finding the solution ~ Albert  Einstein

Poorly structured logic

I shouldn’t base a logical argument on a bunch of quotes, but take the mental leap with me, it is clear that being able to define a problem well is a skill worth having in life.

Which leads to the question…

How do you define a problem?

I have had a good look on Google, but I am afraid it all becomes a bit woolly and vague, let me give you a summary of the top 8 tips:

1. Chunk the problem down:

Some problems are just a little too difficult.  If you can split them up you stand more chance.  Putting a man on the moon is a big ask, a sensible problem to start with might be: how do you put a dog into space?

2. Chunk the problem up:

Some problems aren’t really the problem; you should find the bigger problem you need to solve.  Is the problem that you need to go to the gym?  Or is it really that you want to live a long and healthy life?

In which case maybe you should chunk the problem back down and stop smoking.

I do hope this is becoming clear

3. Get specific:

Get the facts and write them down.  Problems are rarely “always”, “everywhere” and “everybody”.

If in doubt about the facts go and look at the problem (there is no better way)

4. Be explicit:

Expose the assumptions, ask what they are and the write them down.  Make them as explicit as possible and then you can challenge them.

Trite but true: if you “assume” you make an “ass” out of “u” and “me”.  (My 9-year-old daughter told me that).

5. Follow the formula:

A problem statement should have an object and a defect; it should not contain a solution, otherwise it wouldn’t be a problem would it? (see below)

6. State the pain:

If the problem is “we need a bandage” then technically that is a solution looking for a problem.  Solutions looking for problems are very expensive things (usually involving multi million pound IT investments)

Write down where it hurts, not that you need a bandage.  P.S. You can do this by following the formula. (see above)

7. Tell me what the problem isn’t:

Write down all the things that aren’t the problem, “everybody is late” and “everybody is late except Tony and Sue” are two very different propositions to deal with.

It is best to do this with things that are closely related to what the problem is, or you could go on for a very long time.

8. Rephrase the problem:

How you state a problem determines how they interpret it:

  • “Ways to increase productivity” sounds like job cutting
  • “Ways to make our work easier” sounds like knocking off early.

I guess you will get more traction with the latter

The problem with writing problem statements

All of this is sound advice, but none of it is very definitive.  There aren’t any golden rules.

How about this as a sense check?  If you honestly think that if you can:

Get your arms around [insert your problem statement here] and knock it off

Then you might just be successful in life.  Unfortunately that is kind of where we started.

If you enjoyed this article and would like to learn more  sign up for the e-course

 Bit of a Problem

Read another opinion

Image by aturkus

Filed Under: Blog, Operations Analysis Tagged With: clarity, problem solving

About the Author

James Lawther
James Lawther

James Lawther is a middle-aged, middle manager.

To reach this highly elevated position he has worked in numerous industries, from supermarket retailing to tax collecting.  He has had several operational roles, including running the night shift in a frozen pea packing factory and carrying out operational research for a credit card company.

As you can see from his C.V. he has either a wealth of experience or is incapable of holding down a job.  If the latter is true this post isn’t worth a minute of your attention.

Unfortunately, the only way to find out is to read it and decide for yourself.

www.squawkpoint.com/

Comments

  1. Adrian Swinscoe says

    8 July, 2012 at 10:53 am

    Hi James,
    A wise colleague of mine once told me a story of an old colleague of his which went: If you can’t draw it then you don’t understand it.

    Adrian

    Reply
    • James Lawther says

      8 July, 2012 at 11:26 am

      Absolutely

      James

      Reply
  2. Bernie Smith says

    8 July, 2012 at 2:08 pm

    Another one to add, is paying obsessive attention to any patterns regarding when and where the problem happens. A pattern spotted at the definition stage can make the difference between some very challenging problem solving and a completely self-evident solution. As one of my workmates often used to say “let looking replace thinking”. I’ve noticed that many people are much more comfortable theorising than observing (carefully) and watching what is really happening. It’s careful observation that is the hallmark of all the best problem solvers I’ve met.

    Reply
  3. maz iqbal says

    20 July, 2012 at 3:20 pm

    Hello James

    I say that you have to live with the problem so that you get a feel for the problem, that you become intimate with it, that you see it in its fullness – in terms of breadth, width and how it plays out over time.

    Furthermore, I say it is not so much the definition of the problem that matters as much as who cares enough to grapple/wreste with the problem.

    Finally, I say it is more effective to focus on what you want rather than what you do not want.

    maz

    Reply
    • James Lawther says

      21 July, 2012 at 9:38 am

      Thanks for your comments Maz, I particularly like the last one, “it is far more effective to focus on what you want than what you don’t”. I guess the world would be a far better place if we all took that to heart.

      James

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Explore

accountability assumptions beliefs best practice blame bureaucracy capability clarity command and control communication complexity continuous improvement cost saving culture customer focus data is not information decisions employee performance measures empowerment error proofing fessing up gemba human nature incentives information technology innovation key performance indicators learning management style measurement motivation performance management poor service process control purpose reinforcing behaviour service design silo management systems thinking targets teamwork test and learn trust video waste

Receive Posts by e-Mail

Get the next post delivered straight to your inbox

Creative Commons

This information from The Squawk Point is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Creative Commons Licence
Customer Experience Update

Try This:

  • Fish Bone Diagrams – Helpful or Not?

  • Regression to The Mean

  • Should You Punish Mistakes?

  • The Alpha Male Paradox

Connect

  • E-mail
  • LinkedIn
  • RSS
  • YouTube
  • Cookies
  • Contact Me

Copyright © 2025 · Enterprise Pro on Genesis Framework · WordPress · Log in