I have a screen with CRUDs

For example:

I will register a department and identify all job positions, equipment and employees

Solution A: Display everything on a scrollable page

enter image description here

Solution B: Display in column

enter image description here

Solution C: Display in Tab (top in the example or left)

enter image description here

What are your thoughts?

What better way to work? My forms open in a modal.

  • 4
    Hi Marcelo, thanks for your contribution to UXSE. What option were you thinking of going with and why? I think it is a little bit difficult to decide based on the information provided because they can all potentially work. Maybe think of some of the edge cases or the most common use case and see which option definitely would not work?
    – Michael Lai
    Feb 19, 2019 at 22:21

2 Answers 2


I would do C (tabs), considering the width of the tabs (good if limited to tabs you have). Also considering whether the departments will have a long list of records that would cause the other categories to get lost way at the bottom of the page. If the add button is there to add more records, I would consider repositioning that button and making the call to action more clear. I got a bit confused with what we are adding (add more tabs...add department...add equipment). You may not have to make call to action more specific if positioned well and possibly contained with your records. It's all about positioning, proximity to what you are adding and specificity in labeling (if still needed).

Hope that helps.


My answer would be: it depends.

I don't see an obvious choice between the three. It depends on what your users do and how they do it. So the simple answer is: have your users try it and see what works better! In other words, it's work.

Now let's think about constraints and tradeoffs here:

  • A has three tables visible. The page might be longer.
  • B cuts down on length, but trades it off for table width. Depends on what your table contains.
  • C has a short page and full-width table, but you can only see one at a time. This means one might need to remember information from an inactive tab.

Some questions:

  • Are your entities all independent? Is an employee linked to a job description for instance? To an equipment? That will change the workflow.
  • If they're not, how important are the links between them? How does that factor in the UI?
  • What task(s) does your user do more/less frequently?
  • What needs to be fast/efficient? What doesn't, if there's a tradeoff to be made?

Those will influence what interface will work better. Otherwise, listen to/watch your users, and think through their workflows!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.