Good article on considering data set size in design

Interface Scalability — CMS Watch Interface bottlenecks typically result in creeping inefficiencies in editorial processes. Maybe it takes […]

Interface Scalability — CMS Watch

Interface bottlenecks typically result in creeping inefficiencies in editorial processes. Maybe it takes too long to find content because, while the system response time is fine, there’s simply too much stuff to wade through. Perhaps some operations you would like to make in bulk can only be conducted one at a time. Or maybe there isn’t an easy way to see who is working on what, so sorting out the week’s responsibilities takes editors several rounds of the kind of off-system emails and face-to-face meetings that the CMS was meant to obviate in the first place.

1 Comment

Add Yours
  1. 1
    Austin Govella

    For the record, PublicSquare does this really well. The Dashboard and coming soon list make finding the important stuff super easy.

    The article-based discussions remove the need for meetings. That’s great, especially since everyone lives somewhere else.

Comments are closed.