The only exception is your headers should be slightly larger and contrast with the rest of the data. Chances are, your enterprise product table contains quite a bit of data. Cell Padding and Heightīe consistent with cell padding and height throughout your table. Maybe they would if it looked less intimidating and was easier to use. Is it still relevant? How is this data being used? Is it correct? How many columns are there? Can some of them be combined or removed? Are you adding new data points? Can you easily scan the data? Can you filter or manipulate the data in a way a user would need to? Have you witnessed a user interacting with this table? Maybe your users aren’t using your table at all. Look at each column of data in the table. Now it’s your worst UX design nightmare.Īll data tables aren’t created equally and you may not need every single feature recommended in your table. Somehow, this table grew into a monster- “we need to quickly add this, or that for stakeholders- done”. Data isn’t aligned, columns are not consistent in size, the various colored icons remind you of sprinkles on a cupcake and you’re not sure if there is a rhyme or reason to the information architecture. Your designer eye is telling you this is a mess, you need to determine what is practical with your development team and within a reasonable time frame. Possibly you’re looking at it wondering where to begin. Are you redesigning a data table for enterprise software? Suddenly you’re feeling overwhelmed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |