Skip to main content

Checklist for problem solving


The VirtualSalt problem solving checklist:

  1. Take time to examine and explore the problem thoroughly before setting out in search of a solution. Often, to understand the problem is to solve it.
  2. Breaking the problem into smaller parts will often make solving it much easier. Solve each part separately.
  3. The resources for problem solving are immense and ubiquitous.
  4. You can always do something.
  5. A problem is not a punishment; it is an opportunity to increase the happiness of the world, an opportunity to show how powerful you really are.
  6. The formulation of a problem determines the range of choices: the questions you ask determine the answers you receive.
  7. Be careful not to look for a solution until you understand the problem, and be careful not to select a solution until you have a whole range of choices.
  8. The initial statement of a problem often reflects a preconceived solution.
  9. A wide range of choices (ideas, possible solutions) allows you to choose the best from among many. A choice of one is not a choice.
  10. People work to implement their own ideas and solutions much more energetically than they work to implement others' ideas and solutions.
  11. Remember the critical importance of acceptance in solving problems. A solution that is technologically brilliant but sociologically stupid is not a good solution.
  12. When the goal state is clear but the present state is ambiguous, try working backwards.
  13. Procrastinators finish last.
  14. Denying a problem perpetuates it.
  15. Solve the problem that really exists, not just the symptoms of a problem, not the problem you already have a solution for, not the problem you wish existed, and not the problem someone else thinks exists.
  16. A maker follows a plan; a creator produces a plan.
  17. Creativity is the construction of somethings new out of somethings old, through effort and imagination.
https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels/

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi