Mika Heinonen's Blog
Counter
1365

Case Classification Code
Monday, 15 August 2005 01:02:00 EET

When you are dealing with many customers, and have limited resources, you need to optimize your work load in order to do the most important things first.

A new idea came up to have a classification code for each case, idea, event, etc..
The code consists of 2 characters: IS

I stands for Importance, and can be
A: Very Important
B: Important
C: Quite Important
D: Not so important
E: Not important

S stands for Size, and can be:
1: Tiny
2: Small
3: Medium
4: Big
5: Huge

For example if there is an very important case which can be done in very short time, the code would be: A1.
The codes are alphanumerically sortable by priority order, so the order of execution should be:
A1
A2
A3
A4
A5
B1
B2
B3
etc...

This means that all A cases are usually to be done before B cases, however using overlapping process queues in practical work, A3 will be on same level as B1, A4 like B2, A5 like B2, and B3 will be on same level as C1, etc..
A1
A2
A3B1
A4B2
A5B3C1
B4C2
B5C3D1
C4D2
C5D3E1
D4E2
D5E3
E4
E5


Xav'
1 Monday, 15 August 2005 13:10:24 EET
not a really new idea, is it?

Mika Heinonen
2 Wednesday, 17 August 2005 23:16:22 EET
Well, not new for some people, basically familar to some people, and conceptually new for some people. This is just common sense, and most people work in that way anyway, perhaps just not recognizing it. Analyzing the prioritizing methods scientifically, and making a logical model of it, can reveal new possibilites and optimize the process.

Richard Leslie
3 Friday, 19 August 2005 21:33:40 EET
Your two parameters are interesting, but my favorite are the pair offered by Steven COvey (10 Habits of Highly Effective People): Urgency vs Importance.

You create a Cartesian coordinate plane, with Urgent as the x variable and Important as the y, giving you a square with 4 boxes, labeled NU/I, U/I, NU/NI & U/NI (N=Not). Eliminate anything NU and NI, and focus on what is both Urgent & Important (big project for a big boss, say), and Not Urgent but Important (gotta do these sooner or later). It's a great filter for clearing out the chaff!

Mika Heinonen
4 Friday, 19 August 2005 22:24:14 EET
Isn't Urgent and Important kinda like in the same line though?
I wanted to seperate the Importance/Urgency from the size of the project, so that the result would be maximizing the number of completed projects with a weighting on important projects.