102 · Representative Documents: Outreach and Assessment Guides
UNIVERSITY OF MICHIGAN
U-M Library Public Web Presence Guiding Principles
What this means:
Redesign efforts take precedence over other new efforts. In order to stay focused on improving for
the future, all new content or development efforts will need to be discussed and prioritized alongside
redesign efforts.
Prioritize content efforts. Favor putting effort towards “core” areas that have potential for high user
impact over niche, or “just in case” content.
Prioritize development efforts. Focus on “core” areas that have potential for high user impact and
avoid niche features and tools.
Focus on things only the library can offer and avoid developing tools already offered elsewhere or
creating content readily available on the open web.
3) Keep it simple
Less is more. Making something look simple is easy; making something simple to use is much
harder especially when the underlying systems are complex. This will help keep the whole
system: sustainable, upgradable, scalable, cross­browser compatible; have a consistent look
and feel; consistent branding; quality content; and a user­friendly interface.
What this means:
Quantity and quality of content matters. The website is not a filing cabinet or archive. Users are
often better served by fewer pages that contain more succinct and useful content. We should err on
the side of being strategic over being exhaustive. Remember, everything that is created must
continue to be managed.
Use time­ and cost­effective user research methods that require fewer resources yet still yield
quality results.
Use simple design aesthetics to make it easier to apply the styles consistently and broadly. Use
design to simplify and improve interactions.
When considering add­on, third­party applications, mobile app platforms, custom, or advanced
technology, make sure the user need justifies the use.
Be mindful of archival responsibilities, long­term maintenance, and development overhead needed to
develop and manage.
4) Take a holistic “one library” view
We are a large and complex organization but users shouldn’t have to know anything about how
our organization is structured to find the information they need.
What this means:
Just because different back­end technologies are being used or different groups have managed the
programming doesn’t mean we can’t present those systems as a unified whole. Sites and tools
should be built within existing library website management tools, interface frameworks, and use
consistent visual design and branding.
Content should be created and organized for the context of the whole library. Unit­specific content
should not duplicate content applicable to everyone (or available elsewhere already). Services and
collaborative initiatives that apply broadly should be presented as U­M Library services or initiatives,
Previous Page Next Page