It's true that a typical dashboard is likely used to presenting data, status, etc, which means that user behaviour in such places is more "browsing". From this point of view, the name "dashboard" doesn't fit your actual scene.
However, when users look at data/status, some related operations are necessary, and they are also reasonable ...
The problem seems to be that it's not easy to say when the store opens on Friday.
I'd hypothesise that most people understand what is meant by 24 hours, but when you introduce the closing time, things get confused because you're 'mixing formats'.
Mon - Thurs open 24 hours
Fri open until 2am
Sat 8am - 2am
Sun 8am - 2am
First of all I will say that to me it already makes sense and I understand exactly what is meant by your examples. However, here are some suggestions anyway.
I will focus on the "Friday" for "Template 3" as everything else seems fine.
I think the best way to improve it would be to explicitly add "Sat" to the closed time. There ...
From a dictionary definition of dashboard:
the panel facing the driver of a vehicle or the pilot of an aircraft, containing instruments and controls.
Using this as a jumping-off point, it would be perfectly safe to assume that controls to perform actions could happily be presented alongside data in a dashboard. In fact, if you remove the controls, you ...
I think there's no reason beyond the evolution of the design itself.
This is what I think about usability in terms of design:
Asymmetry: It's well known that asymmetry is perceptually more unsettling, thus offering greater visual impact.
Spaciousness: The hamburger menu is used more frequently on small screens where saving space is a fundamental premise. ...
Using an agile approach to define the user's goals would be a good place to start. The following template for writing user stories really helps you work with the user in mind; As a (type of user), I want to (perform some action) so that I (can achieve some goal/result/value).”
The purpose of user stories is to explain the roles of users in a system, their ...
What you're describing is a lot like email, so why not treat these messages just like email from the user experience perspective?
Like email, there are new messages and unread messages for starters. Add a way to archive messages, flag messages as important, or flag for followup. Let users pin messages.
I think you might need to clarify what teachers want to see. Do they want to see case notes only regarding students that are in their current class, with a class being identified by name, year and time?
Or might they be interested in all case notes regarding 'their' students, as in, all case notes to every student that has at least one class with them?
One thing jumps out at me from your question.
The challenging part is that there could be 80+ case notes, and all of those case notes (theoretically) be about one student. The display of these case notes displays the most recent entry at the top of the list. There's also no category/hierarchy of case notes.
I think I'd disagree with your final point. You'...
displaying - potentially a lot of - necessary and timely information
This will mean poor user experience. Message or other timely information means that the user should interrupt other activities to respond to such messages. This requires quick change of the context, this makes pressure on users. As a result this will lead to a big number of mistakes and ...
What about a multilevel bubble chart, I'm thinking on a first level where you can show the students using a size and color classification to know which ones to pay attention to, something like this:
Then you can click and zoom to a second level where you see the actual notes for that student, as a second option you ...
Think about visual language revealing the action with a few strokes (less data-inc) as clear symbology.
Now the question is how to represent the action/verb and the representation/object.
Import and Export (action)
file or data "trans-port" as upload or download can be compared to former time save file (disc) and open file (folder opening). In web-...
Firstly, try to reduce the load for your user as much as possible. You can make the import function accept both JPG and SVG and based on the uploaded file format figure out how to handle it.
Secondly, icons are very difficult to guess. Try to combine icons with labels for clarity. This reduces errors and lowers the learning curve.
With regards to the ...
Most design systems or development frameworks have built-in notification or messaging elements, but often they are not configured or simply set to default values that may or may not be appropriate for individual contexts.
A simple way to think about what 'best practice' should you, you can consider these different types of common messages that are generated ...
Don't make the user input this data, in most cases.
Having users remember, calculate, and enter their mileage is a fairly labor-intensive pattern. When a task becomes a lot of effort, users are less likely to perform it
daily. A carbon-tracking app is something that you want them to develop a habit around using, so it needs to be very easy.
Know what apps ...