How Information Architecture can improve in SharePoint 2013

Transcription

1 How Information Architecture can improve in SharePoint 2013 Virgil Carroll President High Monkey Consulting

2 About Me From the great State of Alaska Certified Athletic Trainer Masters in Instructional Design (from UAB) User Experience Aficionado Taking care of user needs since 1998 Blog:

3 About High Monkey Been around since 1998 (HMC name since 2004) Offices in Minnesota and Michigan Clients throughout the US and Canada Core Competencies Web and interface design SharePoint / CMS consulting User Experience

4 SharePoint 2010 vs Performed a heuristic usability test on both SharePoint 2010 and 2013 team site OOTB template Both end user and administrative tasks Shows usability issues and challenges

5 101 SharePoint Usability Tips For more usability tips, check out my blog series 101 usability tips recorded over 101 days around SharePoint 2010 Covering design/layout, navigation, content management, forms and more! Mobile:

6 SETTING THE EXPECTATIONS IA rules to live by

7 REMEMBER Information architecture is a practice not a step-by by-step, one size fits all plan.which MEANS

8 IN INFORMATION ARCHITECTURE There is no single right answer

9 GOOD INFORMATION ARCHITECTURE has NOTHING to do with SharePoint

10 UNDERSTANDING THE CONCEPT Knowledge of why should affect the how

11 WHAT IS INFORMATION ARCHITECTURE 4 basic IA concepts Information Structuring, organizing, and labeling Finding and managing Art and science

12 WHY DO WE CARE? Because we want to be SMART Because we understand users are important Because we don t want yet another IT project to suck

13 IA BREAKDOWN Business goals, funding, politics, culture, technology, resources and constraints Document / data types, content objects, volume, existing structure Content Context Users Audience, tasks, needs, information seeking behavior, experience

14 CONTEXT Context All web sites and intranets exist within a particular business or organizational context Each organization has a mission, goals, strategy, staff, processes and procedures, physical and technology infrastructure, budget, and culture the key to success is understanding and alignment Content Users

15 CONTENT Context Includes documents, applications, services, schema, and metadata that people need to use or find on your site How much content do you have? What are the formats your content is in? Who owns your content? Content Users

16 USERS Context Every user has different experiences and abilities to draw from Every user has different needs and wants Do you know how your users use your site now? Content Users

17 FINDABILITY VS. PUTABILITY To give or to receive, that is the answer

18 REALIZE HOW USERS THINK The too-easy information seeking model User asks question MAGIC HAPPENS User received answer

19 WHAT IS PUTABILITY How we store information Successful more with complex structures People don t want to make too many decisions

20 WHY DO WE CARE? Because people finding stuff is the MOST important, but we still have to have storage Because organization is key to successful finding People can t find stuff that isn t there

21 WHAT IS FINDABILITY How we look for stuff Complex structures tend to fail People want to find things their way People DON T UNDERSTAND HOW TO FIND STUFF

22 IA KEY TRADE OFF Discipline vs. Structure

23 How 2013 is different Think.then be different!

24 WHAT S NEW IN SHAREPOINT 2013 Information? Nothing Structurally? Not much Navigation and labeling Quite a bit Finding and managing GAME CHANGER

25 STRUCTURALLY Some new templates of significance Community Site / Portal ediscovery Center Some new structure changes of significance HTML instead of XSLT Design Manager Display templates

26 NAVIGATION AND LABELING Managed Navigation By term set (can be dedicated or combined) Will take careful planning and understanding Faceted Navigation Used to filter search results Inline navigation editing

27 NAVIGATION AND LABELING URL Rewriting MMS has some new features Custom Sort Order Custom Properties Pinning of Terms

28 FINDING AND MANAGING 2013 makes it easier to change the look-n-feel HTML throughout Better mobile support Managing information Document Sets Create a folder inside Support for OneNote Workflow Better move information

29 FINDING AND MANAGING Its all about search! FAST Search Integration Better results Cooler refiners

30 FINDING AND MANAGING Search Results Search query history Search Refiners Determine specifically what refiners to show Enter your own value Graphical histograms Query Rules Group specific search results Tie to specific search terms or patterns

31 FINDING AND MANAGING Cross Site Collection Publishing Use search to surface content throughout the organization without boundary concerns Content must be in a Catalog Enable continuous search crawl for 2 minute content refresh Requires publishing features

32 FINDING AND MANAGING Content Search Web Part Same content, different display Build complex queries based of metadata and query rules Query builder tool Create custom refiners

33 Breakin down the Monkey Madness, 2013 style Bringin in the cool

34 WHAT IS MONKEY MADNESS A Website built in SharePoint 2013 Includes: Solid content management practices Separation of content and presentation Creative design elements Managed Navigation Content Search Web Parts galore!! MOST IMPORTANTLY NOT A LOT OF TIME AND EFFORT

35 WHAT USERS SEE

36 WHAT INFORMATION ARCHITECTS IMAGINE

37 WHAT CONTENT CREATORS USE

38 WHAT SITE ADMINS BUILD

39 SITE COMPONENTS: MASTER PAGE Can be applied to entire site or sub-sections Link global CSS & Script files Significantly different from previous User HTML-based file (never touch.master page) Use Snippet Gallery to quickly add standard web parts and components Can open in 3 rd party products, upload and SharePoint builds master page Has commented components and language that must be understood

40 SITE COMPONENTS: PAGE LAYOUT The insides of an overall page Designers can create multiple, content creators can pick-n-choose

41 SITE COMPONENTS: DISPLAY TEMPLATE Represents the container of a search web part rendering Add HTML, CSS, JavaScript code directly into the control

42 SITE COMPONENTS: ITEM TEMPLATE Controls the rendering of each item in a Display Template Can access results fields and other advanced Client OM functions

43 QUESTIONS?? Virgil Carroll, President High Monkey Consulting Blog: