I explored two patient list layouts for a mental health platform: a card view and a table view.
Cards feel more visual and personal, but space is limited and adding more information can quickly make them crowded. For complex enterprise products, I often find tables more practical — they’re easier to scan, compare, sort, and can support more columns when users need greater visibility.
For this kind of workflow, I’m leaning toward the table view. Which would you choose — cards or table?
Thanks, Anna. You're right that it's ultimately a task call, and framing it that way cuts through most of the card-vs-table noise. Good to see another product designer thinking about scan-speed the same way.
Hi! Thank you for the feedback! I actually included a standard segmented control to switch between the card and table views, but I really like your idea of having a personal view. Thank you!
For a mental-health patient list the choice isn't really card vs table — it's scan-speed vs context. The card wins the first meeting because the photo and name set the clinician's mental model before they touch the row, but the table is what holds up under the daily rhythm of...
Thanks, Anna - and agreed on the hybrid read. The task-oriented framing is what keeps the system honest once real patient volume hits the list. Fun comparison to look at.
I'd go with the table view too. For managing a large number of patients, being able to compare their status, progress, and appointments at a glance is more useful. Cards could work better for a quick patient overview. Maybe offering both views would be the best approach!