No, I'm just kidding! As much as today’s critique was harsh, it was really beneficial. It made me answer all the questions one forgets to ask while working on a project. These are questions that a good client would ask, so it's better if they get addressed in the safety of the classroom.
There are certain issues that I need to focus on with my current calendar:
- Ease of usability: it is not easy for mothers to interpret how much their baby weighs, even though there is a key explaining it. It is impractical to have to count 3000 squares for a 3kg baby and difficult to make an estimate too.- Hierarchy- different levels of information must be within the chart depending on how detailed the mother would like to look at it. One day if she is in a rush, she might like to look at the size of her baby visually, but when returning from the doctor's office, she might want to compare the specific size of the baby in centimeters to the figure on the chart. It would be right for me to allow for both options.
- Every element in the system must have significance. This means that the grid I placed behind the calendar has to have a reason although I put it there to look 'pretty'. Oops! It then evolved into a 'flexible' calendar where the user makes the boxes for themselves, but I definitely agree that if everything else on the page has significance, this should too. Maybe it could be used to record appointments or even comparisons of the estimated figures to the actual baby figures. It could then be kept as a memory for when the child grows up.
-Using monthly increments is perhaps too big of a progression, especially since babies grow so fast! So I could keep the same structure but divide each arm into 4. This will allow for a detailed (weekly) and less thorough view (monthly) I think this is a good solution to the issue of hierarchy.
back to work...:)
No comments:
Post a Comment