![]() ![]() Human perception of light is logarithmic, not linear. You can barely see the bar on the left but you can see a lot better the bar on the right. Here is a uniform gradient bar with a small 10% width bar on each side. Let us assume you use one single shade of red. Points 3 and 4 will render some classification complicated because the color is a three-dimensional model. One is more yellowish, In painting, this shift is used to represent a more "perceptually correct" lighter. Here are some circles with two lighter greens on each side. do you know brown is a dark orange? How dark? But I'm pretty sure you will have no idea if it is lighter, darker or equal than the previous one. You can have two shades of green next to each other and see if one is "lighter" than others.īut let us assume you need to scroll down a bit. Yes, humans can perceive a lot of colors. I just have 10 and it is not logical at all. Imagine the priorities translated to words. Of course, you can have subcategories but for special purposes like searches and classifications. Humans struggle if you have more than 6-8 categories. Prioritize means to give categories so humans can detect and compare, and then do some actions based on that value of rank, urgency, etc. I know that we should answer based on your requirements, but in this case, there is a chance your requirements are wrong. A better choice would be to have 1 or 2 red, 2 orange, 2 yellow and the rest green and blue. ![]() the number or whatever is relevant in your scenario.Īlso the colour choices in example 2 shouldn't be used exactly only the idea that the colour shouldn't change at equal intervals (e.g. Have an additional method to depict the priority e.g. Additional ConsiderationsĪs with the majority of UI choice, don't rely solely on the colour to depict the priority. I assume its less important to quickly spot a low priority so those ones have a lot more shades and causing possible confusion with specific priorty level is less impactful. For example if you split equally 4 shades each (like I suggested initially) higher priority shades of orange might be confused with a shade of yellow that is much lower priority. That way if anything is coded red, orange, or yellow you know its near the top of the priority. I quite like the idea of having the critical, high and medium level priorities only spanning the first 6 or so colours. Level decreases, corresponding color tones become closer to the colorīlue, which represents the least important priority level interval, Hottest color tone in the scale, that is, color 'red'. Which is the interval between 100 and 96, is represented with the Schema, as shown in the screenshot below. I assume this is so the critical and high priorities stand out particularly from the others.Ĭolor coding for priority levels divides this 1-100 interval into 20Įqual pieces and each interval is represented by one color in the Instead there are more shades of green and blue than red and orange. However the split isn't equal for 4 shades each. Here is an example of 20 different priority levels, ranging from red to blue again. Red > Orange > Yellow > Green > Blueīut you could choose 4 shades of each in your case Low priorities - 5 shades of (grey or green?).You could break your priorities into these groups then set 5 different shades of the same colour for each level: For example: For example on Microsoft TFS (collaboration tools for software projects) there are 4 severity levels you can set against a bug. I would split the 20 priority levels into 4 distinct sets (for the sake of colour coding at least). Hence the 20 levels (with increments of 5 if it's an arithmetic progression, or variable if it's some geometric progression) help me provide this information to the user.Īlso, thanks to everyone for the responses, many are very useful and interesting. ![]() And since I have a constraint of not being able to show the numeric value, I want to help the user gauge (not necessarily identify very clearly) relative priorities. The thing is, I have a priority score in the range of 1 to 100. I understand that 20 priority levels normally is too much, but 20 here is just a proprietary number, it can be 10 as well. Is there a sound mathematical approach to arriving at these colours? I prefer to get the colours in hex values. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |