The same problems seem to keep cropping up...
 

• defects
• software bugs
• customer complaints
• missed deadlines

...but each department blames another [or many other] department[s]...or suppliers...or customers...or shippers.

You bring people together as a task force to zero in on the problem. But everyone seems to have a different way of looking at things. You suspect that it is at least partially true since some of them seem to describe and define problems in terms that make them look good and someone else to blame.

You think that maybe a more formal system is needed to define and track issues. So you investigate...and sure enough, there are some systems out there...good systems... web based to provide lots of flexibility and power. 

But, whoa...we're not out to solve the national crisis! We're not THAT BIG!  And surely our problems aren't THAT BIG!

Surely there's some reasonable solution...?

You see, as an 
 

• IT Project Manager,
• Chief Financial Officer,
• Public Accountant,
• Director of two large financial institutions,
• Service Club President,
• and now that I am "retired", a web master...

...I have been involved with and managed a lot of projects! A lot! And with some of them, I wasn't called in until the fires were raging and the battle lines were already drawn and in full charge!

And out of this diversified, project-oriented career, I have developed a powerful little tool for Issue Tracking.

In most cases, at least at first, it isn't so important how you define an issue as it is simply to recognize that something has become an issue and agree to try to resolve it. If parties think there is a problem, then there is a problem. [True, once you get into solving it, you must often dig  into it more deeply and sharpen up definitions, but it is amazing how many "problems" turn out to be misunderstandings rather than true problems.]

So, getting it recorded and assigned to someone is  important. As is being able to track progress as people work on the solution.

Assigning priority is almost always important. And in recent years I have added a couple of fields to track secondary information that is useful in reporting.

The tool is a spreadsheet...Microsoft Excel 5. 

Spreadsheet because that is easier for structure and organization than word processor, but not as difficult as a data base. More people are familiar with spreadsheets so more people can share it during a project.

Excel 5 since that is the version that will be readable by the largest number of people, either directly or because your particular spreadsheet is able to read Excel.

The spreadsheet is quite simple as it is set up and delivered. But I have included a couple of pages of notes and examples of how I have used it or seen it used in different project and reporting situations. And that is really one of the strengths and prime benefits of this tool - it is so flexible.

When you order it and download it, you'll be up and running immediately...no set up, no lengthy installation. Take a few seconds to make a backup copy then start using it!

After a short while, you'll be amazed at the number of situations where you'll see how it can be used as is or modified and adapted to your problems.

But do take a couple of minutes to read my notes...there are many ways to use this tool!
 

• Besides Project Management, here are a  few other uses for Issue Tracking...

• Software Developer. Bug tracking. Coding errors affect current or potential customers.

• Risk Manager. Requires audit trail to identify and manage risks.

• Service Provider. Missed deadlines result from incomplete information.

• Contractors in every field. Make sure you and your customer and your sub-contractors all know  what problems are being handled and solved.

• Manufacturer. Defects result in scrapped material and lost customers.

• Help Desk. Here's where the company's reputation is at stake with its customers.

• Prototype Development. Before you select an elaborate issue tracking system, use this model to build your own prototype. 
• Use the Priority, Type and Responsibility fields to track useful information using simple coding that is appropriate to your needs. 
• Change the order of the fields. 
• Change the name  and use of the fields. Add or delete fields. 
• Watch over time as you actually use the Issue Tracking file in your operation. 
• You'll soon start to see trends and emphasis on what you really need. 
• Then you'll know what to shop for if you need something more elaborate.

PS
This comes with a Full Satisfaction Guaranty...

If you aren't fully satisfied, for any reason, contact me for a full refund. No questions. No hassles.

David Jones
Wizard Publishers
itsdavid@wizardpublishers.com