• Pssst. Over here…

    Are you enjoying what you are reading? I hope so. If you do please take a second to subscribe to my RSS feed. Thank you for visiting my site. If you would like to know more about Adrian3 be sure to check this out. Oh, and you should probably follow me on Twitter if you aren't already...





  • Flickr
    Facebook
    LastFM
    Netflix
    Flickr
    YouTube




    Stop Thinking of Yourself as a Problem Solver

    I have been thinking about the term “problem solver” today. Problem solving seems like such a desirable trait, but is it really all it’s cracked up to be? Isn’t that just the entry level skill that everyone must posses just to be considered qualified to do the most basic of tasks? While the education system is (arguably) failing to deliver graduates with even this most basic skill, I wonder if we should be expecting something more from people. We can set the bar much higher. So what is better than a problem solver? How about the ability to identify problems before they need to be solved? Let’s call that skill “problem identification.” Here are some thoughts about the difference between a problem solver and a problem identifier:

    1. A problem solver is reacting to mistakes that have already been made. A problem identifier can see potential mistakes and eliminate them before they become a problem.

    2. A problem solver looks good only when things go wrong. A problem identifier’s work may go unnoticed because their work isn’t accompanied by calamity.

    3. A problem solver is threatened by creative, untested ideas because they can’t apply their pre-determined formulas to fix problems they haven’t fixed before. A problem identifier can confidently embrace bold ideas without fear because they can address problems on the fly.

    4. Problem solvers are by definition looking for opportunities to do damage control because this is their opportunity to shine. Problem identifiers hate damage control because they see it as the result of poor planning.

    5. Problem solvers see job security in things that routinely fail. Problem identifiers will never make the same mistake twice.

    6. Problem solvers can identify blame quickly (as long as it isn’t their fault). Problem identifiers can identify mistakes just as quickly, but use these moments as teaching opportunities for the team.

    7. Problem solvers love the postmortem because they are good at pointing fingers in hindsight. Problem identifiers have sought out feedback throughout the process and rarely learn much after the fact.

    8. Problem solvers prefer problems that they know the solution for. Problem identifiers love new problems because they lead to new insight.

    9. Problem solvers don’t see the status quo as a problem that needs to be solved. Problem identifiers resist the status quo because it is the equivalent of stagnation.

    10 Problem solvers need conflict and failure to maintain their comfortable existence. Problem identifiers need new challenges and become uncomfortable when things become routine.

    11. Problem solvers don’t speak up until the problem is obvious. Problem identifiers have deep insight into a project and can articulate the implications of subtle adjustments within the plan.

    So the next time someone asks you whether or not you have good problem solving skills tell them no. They will undoubtedly be surprised by your answer and ask you why. You can answer confidently that you specialize in something far more rare than problem solving. You are a problem identifier.

    • http://migreyes.com Mig Reyes

      The other thing is, everyone is a problem solver. Fast Food restaurants need their food cooked. Enter burger flipper; problem solved.

    • http://joelglovier.com Joel Glovier

      Adrian this is really brilliant thinking. Thanks for sharing – and for challenging the status quo of professional mindsets. I’m going to take this to heart and think about what it really means to be a problem identifier.

    Switch to my mobile site