Tag Info

New answers tagged

5

When mixing data units, explicit is better It's very easy to confuse mixed units in a table, so best practice is to make the units explicit. If you can avoid this situation (e.g. using sections or different columns) that is usually better. But sometimes it's unavoidable because of space constraints, or for other reasons. Avoid using icons because it ...


0

A quick solution is to get rid of the type column and just have different size columns: But you mentioned that it will have a lot of columns so maybe the better solution is to seperate the table into one per type: The reason for these two ideas come from one question I have with your current table concept: Why do you have a table with incomparable ...


5

A simple icon can clarify what units are implied in each case. This should solve the problem of the user inadvertently copying the units along with the actual value, and get a quick mental feedback of what's to be expected: EDIT: See Tohster's answer below, which appeals to me as the better solution.


1

There are several ways to do this...tailor it to the shape of your data First, don't use the – symbol. In finance and business, the – symbol is often used to represent the number 0, so this could be confusing to users. For most data tables, it's important to present numbers consistently. That means if you have a series of 8's, you should display an 8 in ...


0

It seems to me that your issue seems to be with the visual highlighting of the values in the time series grid (assuming that it is the best solution to the problem). So I can offer some suggestions: Varying the size of the value displayed, at least so that 0 values are displayed in a much smaller size Varying the colour of the value displayed, at least so ...


0

I would look to implement a similar UI pattern to Apple Mail / Messages. This involves keeping the edit button in the top right hand side of the header, but moving the add new into the footer. This pattern would work if you have just a simple list, however if your list-items are buttons that relate to more information (like in mail) you should consider ...


0

If all tables are related to "users" and the only difference between the different data sets is the user group then your suggested solution of accessing each group table via dedicated tab will work. You can also further improve overall layout and provide more structure to the data set by using a list. This provides a more scalable solution and adds ...


0

I would make it fully in-line, both before and during the edit. Pros: Speaks for itself. Saves space. User do not loose context (like with modal dialog) download bmml source – Wireframes created with Balsamiq Mockups


0

You want the user to make 1 task (to add a column) so I woulnd't "disperse" too much the actions needed to finish that task. I'd take the same approach as KanbanFlow: 1) "Add Column" button. 2) Modal with Column name Input + Position to be inserted. This way the user doesn't have to look for the column to change it's value + they know exactly where ...


1

Tables and visual noise Based on the example you shared ( Employees/ Location/Salaries) I would say you should move away from the table format which are quite difficult to manipulate and add too much visual noise. Luke Wroblewski wrote this interesting piece about reducing visual noise in tables: The problem is that excessive visual noise and ...


0

There are different kinds of visualisations depending on your need (particular case). Also is very important if those tags play a "functional role" in your flow, if they have actions, filters or more related details, then you should consider keeping them visible & ordered in a simple manner. Here are some examples: You should also consider aligning the ...


1

You can add a new column on to the end of this: download bmml source – Wireframes created with Balsamiq Mockups ... wherever the end of those columns are. The user can then try to click that save button squished inside the column header. Or add a column on to this: download bmml source


0

From the two option i like option 1 Will this help to enhance option 1. How about you drop the "Save" button and just keep the edit box and let the user key in the column name and on (focus) change the save happens. If the user wants to edit the column again he or she can click on the edit box again. You can use simple CSS tricks for micro interactions ...


1

Your question is not which A or B is better, but: What end user does with provided data and how use it (broder context)? Data is a source for decisions, so you need to know if end user needs to: find a single row to spot an anomaly or analyse particular part (add filters) recognize a pattern or min/max value (add sorting) analyse whole set or local ...


10

Exporting data can be more time consuming Ultimately it depends on how your users feel about it but exporting data requires users to think more and can add friction to their work flow. If I could only choose one option or the other I would go with option 1, however, export to Excel sounds like a very useful function so consider the following example. Show ...


1

If you are filtering the data 'Date, year and month' wise then you don't need to do anything. Show the user data upfront and let user export it.


2

I'm of the mind that you've answered your own question, with a couple of caveats. You have two examples, so effectively you have your own A/B test. If you are already talking to end users and consumers of this data and have garnered their opinion, after you have explained why you believe the second example is better (quick scan overview, simple to download, ...



Top 50 recent answers are included