Agreed, it’s just an information density and layout issue. More layout and data display precision = less noise + lower cognitive load/easier processing = faster + more accurate decision making = less user stress (lovable product) and better business outcomes. Small effects at the level of this discussion for sure, but they accumulate over time, and the principle of it is a good one I think 
.
To be more specific, as far as layout goes, any healthy degree of complexity + decently high stakes (which we have in spades) means we need to see enough info that having the ‘full’ card layout just takes up too much space, plus it’s too verbose. Creates a lot of visual processing noise. Plus there’s usecase differences (potentially very large depending on the size of company) between what is effectively backend data mgmt and frontend user+use context. Specifically, well enough cases where the db field name will be different than the unit label.
This also relates I think to the other topic about customizable cards (which of course is a lot more work) https://community.fibery.io/t/card-customization-in-board-timeline-cal/3521
Even though as a company we’re still getting familiar with and migrating some stuff to Fibery (and things are looking good for it 
) I’m finding that I rarely use the Full card layout - mostly b/c it just stacks everything in a single vertical column. Just takes up so much space. Compact layout seems the most effective - but runs into the field context problem.