User Experience & SharePoint... Why Bother?
•
1 like•580 views
This deck is about User Experience and its benefits to SharePoint specifically.
Recommended
Recommended
More Related Content
Similar to User Experience & SharePoint... Why Bother?
Similar to User Experience & SharePoint... Why Bother? (20)
Recently uploaded
Recently uploaded (20)
User Experience & SharePoint... Why Bother?
- 1. SHAREPOINT & UX WHY BOTHER? www.sharepointalism.com
- 2. Thank you for being a part of the 3rd Annual SharePoint Saturday Houston! Please turn off all electronic devices or set them to vibrate. If you must take a phone call, please do so in the hall so as not to disturb others. Thanks to our Title Sponsor Thanks to our Platinum Sponsors www.sharepointalism.com
- 3. Hi. I’m Craig User Experience Consultant Dallas, Texas www.sharepointalism.com
- 4. SHAREPOINT & UX WHY BOTHER? www.sharepointalism.com
- 5. “ You keep using that word. I do not think it means what you think it means. ” -Inigo Montoya www.sharepointalism.com
- 6. “ A person's perceptions and responses that result from the use or anticipated use of a product, system or service. ” www.sharepointalism.com
- 8. So, why bother? www.sharepointalism.com
- 9. Out of the box is out www.sharepointalism.com
- 10. “ There are only two mantras... yum and yuk. -Tom Robbins ” www.sharepointalism.com
- 11. Yum www.sharepointalism.com
- 12. Yuk www.sharepointalism.com
- 13. Yum www.sharepointalism.com
- 14. Yuk www.sharepointalism.com
- 15. Yuk www.sharepointalism.com
- 16. Yum www.sharepointalism.com
- 17. Out of the box is out Contextual Inquiries Personas Focus Groups Surveys www.sharepointalism.com
- 18. Personas www.sharepointalism.com
- 19. Contextual Inquiry www.sharepointalism.com
- 20. Web parts are not whole www.sharepointalism.com
- 21. “ The difference between the right word and the almost right word is the difference between lightning ” and lightning bug. -Mark Twain www.sharepointalism.com
- 24. Can’t process the process www.sharepointalism.com
- 25. “ If we want users to like our software we should design it to behave like a likeable person: respectful, generous and helpful. ” -ALAN COOPER www.sharepointalism.com
- 26. THANKS AGAIN TO ALL OUR SPONSORS! www.sharepointalism.com
- 27. Thank You! craig@sharepointalism.com www.sharepointalism.com @sharepointalism www.sharepointalism.com
Editor's Notes
- I’m here to talk about SharePoint and User Experience
- I’m a UX consultant in Dallas for Slalom Consulting currentlyI’ve been designing web based software and websites for near 15 years.Specializing in SharePoint design for about 4 yearsTodays talk is on user experience and how it relates to SharePoint. Let’s get started and get some context.
- I’m here to talk about SharePoint and User Experience
- I feel like UX has reached buzzword status and I want to clarify a couple of things
- ISO 9241Begins outside the computerDoes not end with visual designDoes not begin with wireframes
- So the sweet spot we are looking for is the confluence of Desirability = (want) = DesignViability = (profit) = BusinessFeasibility = (reality) = IT
- Does not end with visual designDoes not begin with wireframes
- SharePoint is a total solution isn't it?If we have learned on thing from History please let it be that SharePoint is not a complete solution. I needs careful planning design, governance.So, in the context of making things delightful to use…
- First point id like to make is, out of the box is out.There has always been a understanding that SharePoint is ugly, but the real barrier to user adoption(desire) is the misunderstanding that once it is stood up the users have everything they need to do business. It usually ends badly.Spaghetti Document LibrariesUnintuitive page layoutsNavigation out of controlUsers are more savvy now and the expectation is higher. There is a merging of consumer experiences with enterprise. Users know what a good experience is with software and demand it.
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- "a person's perceptions and responses that result from the use or anticipated use of a product, system or service".
- To get there consider some things before you open the box…Who is going to use the site?What is the anticipated time to tasksWhat is the culture of the companyThese are the things that UX pros work on with the business and IT to create a delightful experience.
- To get there consider some things before you open the box…Who is going to use the site?What is important to see and what is less importantWhat is the anticipated time to tasksWhat is the culture of the companyThese are the things that UX pros work on with the business and IT to create a delightful experience.
- To get there consider some things before you open the box…Who is going to use the site?What is important to see and what is less importantWhat is the anticipated time to tasksWhat is the culture of the companyThe more clearly you identify your users to the team the better the experience
- Often the page consists of some things that the user wants to see in a very general sense. Web parts are a great way to bridge the gap between the UI and the business logic but if you throw them on the page with no consideration then you getCognitive overloadAll noise and no signalNo idea what is important on the pageCan not find what looking for
- Considerations before adding web parts…Different roles see web parts differently and we have to make that clear.Don’t miss the opportunity to be clear about it strengths and limitations.
- Use wireframes to map web parts to pagesUse wire frames to determine information hierarchy… If everything is important nothing isThink about not just the data displayed but also the poor soul who has to maintain it and define the interaction.
- Use wire frames to determine information hierarchy… If everything is important nothing isThink about not just the data displayed but also the poor soul who has to maintain it and define the interaction…
- From consuming to editing the OTB implementation by themselves are problematic and catastrophic if you combine them casually Make the entire thing more easy to digestHow do folks get added to the site?How does one update a list or file?What happens when it breaks?Are the error messages clear?Can folks find what they are looking for?Is taxonomy just the global navigation?Is there more than one taxonomy?Is the site going to be viewed on JUST a PC or is mobile/tablet a concern?
- How do folks get added to the site?How does one update a list or file?What happens when it breaks?Are the error messages clear?Can folks find what they are looking for?Is taxonomy just the global navigation?Is there more than one taxonomy?Is the site going to be viewed on JUST a PC or is mobile/tablet a concern?