In these few short years, we have already crossed the software requirement, experimenting not just with services that so democratize and lower the barrier of entry to websites that often look indistinguishable from many custom jobs, but we are also toying with AI in such a way that websites lay themselves out best suited for their content.
Libraries are so concerned with being help-desk level professionals that they are ignoring the in-house opportunity for design and development expertise and unable to comprehend the role that plays in libraries’ independence.
“It’s a move away from using native applications to something else.”
Nobody can quite agree on just what user experience audits do. It’s an ambiguity that extends across the table. As a term, it fails to describe its value to client stakeholders. Let me suggest an alternative.
Be careful about reading too much into this. There really is only one takeaway: you’re not Facebook, Amazon, Netflix, or Google.
You sell it as part of your design process, but you only bust this out if it appears the organization is dysfunctional.
The value of such community can’t be understated. It sustains a virtuous cycle that if Springshare could model would position them to outlast even the most dug-in integrated library systems.
We’re not talking about UI, here. Elsevier has positioned itself to rely less on libraries. It’s smart, but libraries should pay attention.
This is an every-industry kind of a problem, because there’s just not a lot of good advice about how to shop for web work.
This is not just a sign of the times but a trend carried by the momentum of aggregation theory, which describes how the user experience has become such a dominant force shaping the success of businesses.