CIO Mind

Do you REALLY want to know what’s inside?

How to solve any problem – 3 simple steps

Posted by Felix Enescu on November 9th, 2006

For any manger solving problems is an everyday job. One can apply various methodologies. I propose you a simple approach guaranteed to solve all problems:

Problem Solving Flowchart

Ok. Enough joking. Take a look at this post by Carmine Coyote on the Slow Leadership blog:

If the sh*t was a random event, your job as boss is to reassure, comfort, and display undiminished trust and loyalty. Doing anything else proves the asshole bit.

The attitude under stress will show the real character of people. If you can stand up, take your part of the blame then you are a man of character.

If you can protect your people, if you can take the blame of the organization for them then you will earn the loyalty of your people.

What is you problem solving methodology? Leave a comment to tell us.

3 Responses to “How to solve any problem – 3 simple steps”

  1. Mihaï Says:

    Depending on the system status : new/old, there are two ways to solve problems:
    a. designing, creating new solutions/systems – this is nicer
    b. solving errors in existing systems – this is the uglier (as it is under stress because the system is usually online)

    For a, the basic steps are:
    a.1 – research
    a.2 – execute/implement

    For b, the basic steps are:
    b.1 – research for information: error’s conditions ( … who’s to blame also )
    b.2 – solving / implementing solution in 2 ways:
    b.2.a – repairing within existing old tools/systems
    b.2.b – creating new system/solution : call (goto) a.1

  2. Felix Enescu Says:

    Thanks, but the post was actualy about people…

  3. Mihaï Says:

    Personally I see some similarities between new/old teams and new/old systems

    In new teams, almost all events could be called random events as they are during arranging time, and it is clear that it is the leader job to support the team

    But in old teams, the expectations are higher, that’s why even a random event it is not seen as it is ; in these cases we see how good is the boss in supporting the team in how he distinguishes random by repeated events.

    I have a larger post in Romanian http://blog.360.yahoo.com/onofreiciuc?p=361 about how a leader should create support inside the team, by keeping the team compact; as usually on the hard times the team is disintegrating: the best are going ahead and the slowest are remaining at the end.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>