Problem-Solving Success Tip: Use Your Time for Problems that are Truly ImportantLearn Management Articles on management-info.biz. Problem-Solving Success Tip: Use Your Time for Problems that are Truly Important article will help answer your questions on Management Articles.We at management-info.biz specialize in Management Articles. Management Articles at management-info.biz provides the most up to date news and articles. If you have questions please do not hesitate to contact us.
Hard as it may be to walk away once you're aware of it, just because a problem is there doesn't mean you have to solve it. Ask yourself and your colleagues, 'What will happen if we don't solve this problem?' If the answer is, 'not much,' then turn your attention to something more important. If you don't know what will happen, find out before you undertake a problem-solving project. It should be clear to you and everyone else involved that the problem is worth the effort--and expense--to fix it. Quantify the cost of the problem quickly, but as realistically as you can. Include lost opportunity costs as well as real expenses such as staff time to deal with the problem, travel expenses, etc. Use actual costs where you can; estimate where you can't. Then guesstimate what it will cost to analyze and fix it. Write your analysis down, stating all your assumptions explicitly. Get a colleague to verify that your assumptions and estimates are reasonable. Start with a rough 'order of magnitude' estimate. That may be enough to answer the question of whether you should proceed. If it's not clear, especially if the cost to solve it will be high, do a more careful analysis. If it will cost more to fix than to live with the problem, or if the number is even close, perhaps your resources (time, people, money) are better spent on other projects. If you decide to proceed anyway, you can do so with a better understanding of what you're undertaking. On the other hand, if you can demonstrate that the cost of the problem is much higher than the cost of solving it, using estimates based on reasonable assumptions, it will generally be much easier to get the resources you need. You can use your written analysis as a sales tool to help win support for your decision to proceed or not. We have to learn to distinguish those things that are truly important from those that are merely urgent. --Jerry D. Campbell
copyright 2005. Jeanne Sawyer. All Rights Reserved. |
More Articles:1. Problem-Solving Success Tip: Don't Leave Your Key Stakeholders Guessing By Jeanne Sawyer Communicate! Don’t leave you key stakeholders guessing.We are generally not very good about keeping others informed about the progress we’re making, especially if there isn’t much. You’re more likely to get support and understanding if you get the word out honestly about what is and isn’t happening. As you start your problem-solving project, establish a communication plan and follow it. Specify who needs what information about your effort, when they need it and how you are going to provide it.… 2. Why Do Managers Create Low Morale? Or Does My Bum Look Big In This? By Peter Hunter Why do managers create low morale as a product of their management and what can we do about it?The answer to the initial question is easy.We all know what managers do to the workforce that causes the workforce to feel the way they do about their jobs.The managers never listen to the workforce, they never give the workforce any respect, they don’t value the workforce and they spend their time “managing” by telling people what to do.The much harder question is “What can we do about it?”It is fir… 3. Safety Policy Sample Outline By Lance Winslow Writing a safety manual is a tough job and most larger corporations outsource such jobs or they have someone on staff with the proper credentials in risk management. Imagine writing the safety manuals for NASA? I had the opportunity to be in the unique position of being able to imagine just such a thing when writing our company safety manuals. It takes lots of studying and review of case law to do it properly. Each industry is somewhat different and hopefully you know your industry and company… 4. The 70% Solution: Practical Testing and Version Control By Steve Pickard "What do you mean you need to push back the launch date?" Says the CEO. Says the CFO. Says the user community. CTOs, CIOs, and all officers who oversee major development projects have had to deliver the dreaded message. But a deadline for the sake of a deadline is a dangerous pitfall that can consume an entire project and stymie it to the point that it never launches. Over the years I've come up with six simple rules that help deadlines become more meaningful, while keeping the developers… |
||||
