Receive
the Free CMSWire NewsletterJesse James Garrett quietly published the second edition of his requisite “The Elements of User Experience” last year, almost ten years after the first volume issued. Reading his book in light of today’s SharePoint governance plans is a fascinating hindsight exercise.
Mr. Garrett’s work is essentially a forerunner to them. The second edition is as relevant as the first: if you’re a classically trained Records person, chances are you could use some summary advice. I recommend incorporating his guidelines into your SharePoint 2010 Records Governance Plan if you’re producing one for your organization.
Elements of User Experience, from Jesse James Garrett
Mr. Garrett encourages us to review our SharePoint 2010 implementation for the corporate intranet from two perspectives: product as functionality or product as information (we’re interested in both). Furthermore, he disassembles the two views into five panes, from base layer to top:
Strategy, or
- user needs: what users will want from the site; and,
- product objectives: business goals or business drivers.
Scope, or
- functional specifications: detailed description of the "feature set" of the product; and,
- content requirements: description of the various content elements that will be required.
Structure
- interaction design: define how the system behaves in response to the user; and,
- information architecture: the arrangement of content elements to facilitate human understanding.
Skeleton
- interface design: the presentation of information in a way that facilitates understanding;
- navigation design: the set of screen elements that allow the user to move through the information architecture; and,
- information design: set of screen elements that allow the user to move through the information architecture.
Surface, or sensory design: created by the finished product.
Mr. Garrett states simply that content is king and technology is as important as content in creating a successful user experience. A successful user experience is all that matters in a SharePoint 2010 Records Management environment.
Strategy Pane
If you’re writing your SharePoint 2010 Records Management Governance Plan within Mr. Garrett’s framework, the absolute first step is to define your organization’s strategy.
Ask your matrix committee of assembled stakeholders and power users two questions: 1. What do we want to get out of this product (product and corporate objectives)? 2. What do our users want to get out of it (user needs)? Consider records management governance against task analysis, a concept in which every user’s interaction with SharePoint 2010 takes place in the context of some task that the user is performing.
Your scope strategy section will contain not only a list of corporate objectives, but also an analysis of the relationships among the various objectives and of how those objectives fit into the larger context of your organization — objectives which should be supported by direct quotes from stakeholders and users inside the document. How would you measure successful interaction? With indicators that will track achievements after the product has been launched to see whether it is meeting both corporate objectives and user needs.
Scope Pane
Scope defines requirements. We want to know what we’re building and what we’re not building. Never mind the “why,” advises Mr. Garrett. Ask instead, “What are we going to make?”
The debate between SharePoint 2010 features as vehicles for functionality and the corporate intranet site as an information medium begins on the scope plane. Recall the difference between requirements and specifications: requirements are stated in the beginning of the project to describe what the system should do while specifications are written at the end to describe what it actually does.
Some defined requirements will apply to SharePoint 2010 as a whole while others are mapped to a specific feature. Users are the most productive source — ask them. Capture functional specifications. Be positive and be specific. Avoid subjective language. Describe what the product will do to prevent bad things from happening. Leave as little as possible to interpretation.
Continue reading this article:
Email It
RSS
We take your privacy seriously