- May 18, 2001
- 7,869
- 361
- 126
We have a home-grown software app that allows users to report problems with anything IT-related (software, hardware, network, etc.). When a problem is reported, the reporter has to select one of four priority levels. Here is the wordage currently used in the software:
4 ? EMERGENCY ? Immediate correction needed (Directly affects deadlines/$)
3 ? CRITICAL ? Somewhat immediate response needed (No work around for the problem)
2 ? URGENT ? Quick response needed if possible (Difficult to continue, but surviving)
1 ? IMPORTANT ? Respond as time permits (Just don?t forget about it)
I've been tasked with coming up with phrases that aren't as vague. For example - "somewhat immediate response needed" could mean a lot of different things to different people, so I need to come up with something a little more precise.
I'm sure other software people out there have a system like this. Does anyone have any good suggestions?
4 ? EMERGENCY ? Immediate correction needed (Directly affects deadlines/$)
3 ? CRITICAL ? Somewhat immediate response needed (No work around for the problem)
2 ? URGENT ? Quick response needed if possible (Difficult to continue, but surviving)
1 ? IMPORTANT ? Respond as time permits (Just don?t forget about it)
I've been tasked with coming up with phrases that aren't as vague. For example - "somewhat immediate response needed" could mean a lot of different things to different people, so I need to come up with something a little more precise.
I'm sure other software people out there have a system like this. Does anyone have any good suggestions?