SharePoint Information Architecture & Usability - SharePoint Saturday The Conference

SharePointInformation Architecture That Really Works
Facilitated By: Richard Harbridge and Virgil Carroll
Tweet Us: #SPSTCDC @RHarbridge @VCMonkey

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.
Open wireless access is available at SSID: SPSTCDC2011
Feel free to “tweet and blog” during the session
Thanks to our Diamond and Platinum Sponsors:

Who am I?
I

From the great State of Alaska
Masters in Instructional Design
Working with SharePoint since v.1
User Experience Advocate
Certified Athletic Trainer
Blog: http://monkeyblog.highmonkey.com
Twitter: @vcmonkey

Information Architecture is a Practice not a Strategy

In IA, there is no single “right answer”.

Proven Success

Take Away: Confidence

Take Away: Improved Communication

Take Away: Knowledge YouCan Use

Our Goal Today…
From Here To Here

What We Will Cover Today:
Why SharePoint InformationSystems Fail
What Makes an IA Strategy Really Work
Visualizingand Communicating IA Concepts
Making Information Architecture Decisions
Case Study Approach (Implementing SharePoint IA)
Information Architecture Tips and Tricks

What We Won’t Cover (In Depth) Today:
Records Management (and Information Policies)
Search Architecture and Considerations
Planning For Multiple Languages
Column Decisions (Choice Column vs Managed Metadata Column vs Lookup Column etc…)
Technical Considerations for Permissions Management
Audience Targeting

Why SharePoint Information Systems Fail
Visualizing and Communicating IA Concepts

Why SharePointIA Fails

#1
NO PLAN
(or it was small)

It started out simple

Then it grew

Then it got TOTALLY out of control!!

SharePoint is not a Silver Bullet…
SharePoint is not a Silver Bullet at NothingButSharePoint.com

SharePoint will be…
Utilized by Business Users to develop and implement business solutions that use technology without IT’s direct involvement.
Our primary unified application delivery platform.
Our primary workflow/business process automation platform.
Our intranet and communication center for internal corporate communications.
…
SharePoint will not be…
Our (external) web content management platform.
Our primary document management platform.
Our contact management platform.
…

#2
BUSINESS DOES NOT WORK THE WAY WE THOUGHT

Opportunistic Driven Learning
Image from Paul Culmsee

#3
WE THOUGHT
ORG CHART = SITE MAP

#4
WE BELIEVED MICROSOFT KNEW DESIGN
(instead learning from users)

#5
WE THOUGHT IT WAS ABOUT STORING INFORMATION,
NOT USING IT

#6
NO REVIEWS
(or analysis of usage)

The Outcome
There are many reasons SharePoint IA can fail and many of us have experienced variations of them firsthand.

What to watch out for…
Sometimes failing is necessary to highlight how important effective IA planning and commitment can be.

What MakesAn IA StrategyREALLYwork

With a good IA…

You can take this…

…and make it into this

This…

…into this

What is information architecture?
The structural design of shared information environments.
The combination of organization, labeling, search, and navigation systems within web sites and intranets.
The art and science of shaping information products and experiences to support usability and findability.

What is information architecture?
4 basic IA concepts…
Information…
Undergoes… Structuring, organizing, and labeling
To improve… Finding and managing
Through…Art and science

Why IA matters
The cost of finding information
The cost of not finding information
The cost of construction
The cost of maintenance
The cost of training
You can’t understand it something if you don’t organize it!

How is IA broken down?
Business goals, funding, politics, culture, technology, resources and constraints
Audience, tasks, needs, information seeking behavior, experience
Document / data types, content objects, volume, existing structure

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

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

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?
Users
Content

What does IA support?

What does IA support?
Information architecture starts with the user and why one come to a site in the first place:
they have an information need
Information needs can vary and each need can cause users to exhibit specific information-seeking behaviors

A good IA…
increases our chances of finding the right stuff

How users look for information
The too-easy information seeking model

Why doesn’t this model work?
Most users don’t know what their looking for
Most users don’t know how to search
Most users don’t have the patience for complicated systems

Find-ability
Models

Sometimes you’re just looking for one answer (known-item)

Sometimes you want to investigate(exploratory)

Sometimes you want to find everything(Don’t know what you need)

Sometimes you need to find it again (Re-finding)

Berry Picking Model
Search
View results
Use results to enhance search
Repeat until end result is found

Don’t Forget Put-ability
Search isn’t a silver bullet.

A good IA…
helps us work effectively

Lets look back

A good IA…
supports user experience

Supporting user experience
If people say your SharePoint ‘sucks’
Do you know why and how to fix it?
If not, review and test it!

Incorporate Feedback Planning
Couldn’t Find What You Were Looking For? Let Us Know (On Search Pages)
Intranet Design or Improvement Contests
Do You Like The New Homepage Design? Click I Like It or Leave A Note!
(Simple front end code/webparts means users don’t even have to go to the ribbon.)
Provide Feedback Button & Custom List
Want More? Give Users a Bookmark Feature and Analyze User Bookmarks
Blog New Features/Changes and Encourage Comments

Plan IA Review Processes

The Outcome
A good IA continually improves content find-ability and put-ability while retaining context and usability.

When defining IA there are always trade-offs. These trade-offs become areas of negotiation and sometimes of conflict.

Visualizing and CommunicatingIA Concepts

Taxonomy and Metadata

What is Taxonomy?
or this…
Not this!

Taxonomyis….
The science of categorization, or classification, of things based on a predetermined system.
In reference to web sites and portals, a site’s taxonomy is the way it organizes its data into categories and subcategories.

How do you figure it out
Seek and ye shall find
Research
Ask an expert

Linnaeus vs Buffon
Everything can be organized based on a standard!
Nay! Each person can organize things based on their own context!
Arrangement is key! Arrangement and categorization provides universal context!
Context is key! Everything can be organized by multiple facets!

Arrangement and Context
Taskonomy?
Department Store
Wholesale Warehouse

Arrangement Challenges
Perfect!
Superclass
Class
What if I want to find an animal by if it lives in water? Or by whether it flies?
Order

X Drive Challenges
Perfect!
Could this be solved by using metadata so that the document could be found by both region and industry?
What if I want to find a marketing document by region and not industry?

What is Metadata?
The BIG Question

What is Metadata?
The BIG Question
What is Metadata?
I think I get it
I think I get it
Oh! Now I see(Mostly)

Adapted from the “pea soup” story by Serge Tremblay

What is our Base Metaphorfor files?

What if we saw this?

Better…

Solve with folders

Hire an intern

This is metadata!

As we’ve already seen: This always works out great
This is a common result…

Shared Drive Zoo

Moving this mess to SharePoint
makes it worse

SharePoint Sux

The #1 rule of SharePoint?
Except when it makes sense
Never use folders
ever

A SharePoint Taxonomy
If only there was a way content could be organized so content could be found/viewed in multiple ways…
I like it!

Metadata
I like it!

Adding Metadata (when uploading)

A SharePoint Simulation

What are content types?

Vacation Request
Drug Reimbursement
Name _________
Emp. # _________
Date _________
Dates Requested:
From __________
To: __________
Manager ________
Approved Y/N
Name _________
Emp. # _________
Date _________
Drug Used:
Name __________
Cost: $ _________
Manager ________
Approved Y/N

Both Content Types in One Library

Content Types for:
Security
Workflow,
Policy,

CREATE LABELING SUPPORT
(metadata)

What is labeling?
Labeling is a form of representation. Just as we use spoken words to represent concepts and thoughts, we use labels to represent larger chunks of information in our SharePoint structure.

Creating your labels
Start small, grow organically
Don’t be afraid of natural language
Always label
Train your users…right now!
Its not a relational database
Use Content Type Syndication

Types of labels
Contextual links
Headings
Navigation system choices
Index terms
Iconic labels

Making your own labels
General guidelines
Narrow scope whenever possible
Develop consistent labeling systems, not labels
Ways to find labels
Content analysis
Card sorting
Search log analysis

2010 takes labeling serious!

The Outcome
Shared Understanding Of How Metadata And Taxonomy Can Be Leveraged To Improve ‘Findability’.

People Must Understand The Value Of Metadata Or They Will Reject The Idea.

Tools For The Information Architect

Same Page

Abstract

Concrete

Mind Mapping Demonstration

Navigation
workshops

Navigational Map

Navigation Systems
Global navigation
Local navigation
Breadcrumbs/Up One Level Control
Contextual navigation
Supplemental navigation
Sitemap
A-Z Index
Guides

Navigation Systems

What is Card Sorting?
Card sorting is a technique that many information architects (and related professionals) use as an input to the structure of a site or product.

“Card sorting is a great, reliable, inexpensive method for finding patterns in how users would expect to find content or functionality.”
-Donna Spencer
http://www.amazon.com/Card-Sorting-ebook/dp/B004VFUOL0
http://www.BoxesAndArrows.com

Why use Card Sorting?
Card sorting can help you identify trends
Do the users want to see the information grouped by subject, process, business group, or information type?
How similar are the needs of the different user groups?
How many potential main categories are there?
What should those groups be called?

Types of Card Sorting
Open Card Sorting
Participants are given cards showing site content with no pre-established groupings.
Closed Card Sorting
Participants are given cards showing site content with an established initial set of primary groups.

What are the types of card sort?
Open
& Closed

Open card sorting process
Snake
Ferrari
Cat
Ford
Dog
Gerbil
Honda
Rolls Royce
Mouse

Results
Pets
Cars
Cat
Ferrari
Dog
Honda
Mouse
Rolls Royce
Gerbil
Ford
Snake

But not always what you expect
Cute
European
Scary
Domestic
Ford
Cat
Ferrari
Mouse
Rolls Royce
Dog
Snake
Gerbil
Japanese
Honda

But not always what you expect
Animals
Luxury
Regular
Ferrari
Cat
Ford
Rolls Royce
Honda
Dog
Gerbil
Mouse
Snake

BIG MONKEY
Card Sort

Card Sort Results

Advantages of Card Sorting
Simple
Cheap
Quick to execute
Established
Involves users
Provides a good foundation

Disadvantages of Sorting
Does not consider users’ tasks
Results may vary
Analysis can be time consuming
May capture “surface” characteristics only

Wireframing Workshops

Balsamiq

CommonIntranet Components

Balsamiq DEMO

Wireframing Tip!

Don’t Forget Consistency
Consistency Across User Environments
Modify Provisioned Site (or Templates) Based on Need
Each Page Design Should Be Consistent

What is usability
Usabilityis aquality attributethat assesses how easy user interfaces are to use.
(Jakob Nielsen, 2003)

Usability’s 5 quality components
Learnability - how easy can the user accomplish basic tasks?
Efficiency– How quickly can tasks be performed?
Memorability– After a period of non-use, how easily can a user reestablish proficiency?
Errors– How many errors does the user / system make? How severe? Can the user recover?
Satisfaction– How pleasant is it to use the design?

Why do we need it?

Why do we need it
When an interface doesn’t make sense
PEOPLE DON’T USE THEM

Usability Testing

Setting up your Usability Plan
Determine what you are trying to find out
Establish your purpose
why are you testing?
what worries you with your system?
What do you really need to test?

Design your Test
Identify the users you’ll test
test at least 5 people
set-up use cases
get permission to use data
get users from different levels of competency

Type of Usability Tests
Heuristic Evaluation
Paper Prototyping
Card Sorting
Surveys

Heuristic Evaluation
Having a small set of evaluators examine an interface and judge it against recognized usability principles

10 Usability Heuristics
Visibility of system status
Match between system and real world
User control and freedom
Consistency and standards
Error prevention
Recognition rather than recall
Flexibility and efficiency of use
Aesthetic and minimalist design
Help users recognize, diagnose, and recover from errors
Help and documentation

Design your Test
Develop a list of tasks you want the user to perform
set-up representative tasks
Complete a process
Find a specific piece of content
Create something

Lets look at a
sample usability test

Run your Test
Re-assure your User
go over expectations
make sure the user understands the INTERFACE is being tested, not THEM
Tester should not be a stakeholder

Run your Test
Run through tasks and collect data
do not coach the user
ask the user to verbalize their tasks
time??

Run your Test
Debrief user
ask about overall experience
ask for suggestions
THANK THEM

Analyze / Report
Identify the biggest problems 1st
grade by severity
Frequency
Impact
Persistence

Analyze / Report
Summarize data
summarize in human terms
identify most common user issues

FIGURE OUT YOUR CONTENT

Document Inventory Workshops

Identify content stakeholders
Questions to ask:
Who in your organization creates content?
What type of content do they create?
Who reviews content?
Who edits content?
Who uses content?
Who approves the publication of content?
Who designs the sites that host the content?
Who sets the policies for managing content?
Who monitors the content in your organization?

An Inventory Worksheet

Build Mind Map (based on an inventory worksheet)

Analyze content usage
What type of content is it?
What is the purpose of the content?
Who is the author of the content?
What format is the content in?
Who uses the content?
Where is the content currently located?

Plan the flow of content
Content is often dynamic, moving from one place to another or from one person to another. Managing this process can be an important success step in content management

Plan the flow of content
Scenarios
Document is authored by a team in one location and published to another upon completion
Web pages can be created in a development site and published to a public site
Content that needs to be retained or archived can be moved once its usefulness has been fulfilled.
Users can move content from a network share or folder to a document library

ORGANIZE WHAT YOU FIND

Types of Organizing Schemes
Objective organizational schemes
Alphabetical
Chronological
Geographical
Subjective organizational schemes
Topic
Task
Audience
Metaphor
Hybrids

Challenges of Organizing Info
Ambiguity
What kind of language is being used
i.e. BSE vs Bovine Spongiform Encephalopathy
Heterogeneity / Homogeneous
i.e. storing all project documents vs. storing project plans
Differences in perspectives
i.e. Looking for invoice by client vs. by project
Internal politics
Mine, mine, mine!!!

No Single “Approach”
Projects
Communities
Tasks
Practices

Business Process Workshops

Visio 2010 Demo

Common Intranet Processes
Absence Reporting and Vacation Scheduling
Expense Reimbursement
Equipment and Room Reservation and Management
Meeting Planning and Management
Policy Review and Approval
Booking Travel
Interview Management and Hiring Processes
Training Sign Up and Management
Event Planning
Change Request Management
Timecard/Time Tracking
Product Planning
Help Desk Ticket Management
Compliance Support
Contacts Management
Inventory Tracking
Lending Tracking
Sales Lead Pipeline

Roadmap

The Outcome
Using visual tools provides shared understanding, which is a crucial driver of shared commitment to a goal.

Workshops become much more interactive; more people are actively involved which leads to greater shared commitment and understanding.

Making
Information Architecture Decisions

The Importance of Making Good Information Architecture Decisions

What is the ultimate IA structure?
There isn’t one!

You need to
Un-enterprise your architecture

Why Enterprise IA doesn’t work
One IA doesn’t rule them all
What happens when it all gets out of control (and it will)
Assumes all processes are created equal (and they are not)
Global doesn’t necessarily mean better (how many people really need to search everything)
Do not fret, there are models that do work….

Information Architecture and Governance Areas
Permanent central portal
- Few authors/Many readers
Communication Portal
Central navigation
Central taxonomy
Divisional stakeholders
Enterprise search
CentralPortal
Departmental sites
Departments
Resources
Business Processes
- Few authors/Many readers
Increasing Strictness of Governance
Collaboration
Local taxonomies
Local search
Semi Structured
Team sites
- Multiple authors
Blogs, bios,
Social
Personal
Above The Line versus Below The Line

Recommended Approach
Bob Mixon on SharePoint 2007 Site Collections

Enterprise Publishing
Many consumer, few contributors
Examples: Company communications, employee relations, sales & marketing, human resources
IA rules
Content tends to be highly controlled & published via established processes
Content is published via a ‘push’ method
Ability to interact is ‘locked down’
Information is well defined and frequently accessed
Access to SharePoint publishing support feature set

Enterprise Publishing

Enterprise Collaboration
Many contributors, mature processes
Examples: Help desk, Job request, Process tracking, Document Management system
IA rules
Processes have been refined and well documented
User interaction is well defined and tested
Contributors are well trained
Access to the full SharePoint feature set

And for the rest of us?

Teams & Other Junk
Many contributors, no control
Examples: Team sites, Temporary projects, Departmental sharing
IA rules
Tightly governed and ‘locked down’
Contributor can do what they want, but have limited abilities
Support is minimal
Does not participate in Enterprise processes (i.e. global search, managed metadata practices, retention policies)
Access to limited SharePoint feature set

How can SharePoint help?

SharePoint Containment Hierarchy
What we care about from an information architecture perspective.

SharePoint Containment Hierarchy

Site Collection or Site (Subsite)?
OR

Site Collection

When To Use A Site Collection

Site Collection 1
Site Collection 2
Webparts & Aggregation
Webparts & Aggregation
Masterpages & Page Layouts
Masterpages & Page Layouts
Navigation
Navigation
Search Across Site Collection Boundaries

Site Collection 1
Site Collection 2
Group Y
Group A
Group Z
Group B
Collection Admin Y
Group C
Collection Admin A
Collection Admin Z
Collection Admin B

SharePoint Permissions

Purpose of a List?
To Replace Excel Spreadsheets
To Track Complex Input From Multiple People
To Centralize Storage and Retrieval of Content
To Provide Validation, Easy To Use Online Forms
To Reduce Duplication of Effort

One List or Multiple Lists?
OR

When To Use a Single List
You want to simplify viewing the same set of items. (When dispersed across many lists it requires additional effort to aggregate the lists).
You want to search for items in the same location.(When dispersed across many lists it requires additional effort to configure search scopes).
You want to easily apply consistent versioning, approval, metadata or form settings.
You want to receive consolidated updates on the collection of items (alerts or RSS).

When To Use Multiple Lists
You don’t expect people to need summaries of the items together.(When dispersed across many lists it requires additional effort to aggregate the lists).
You need to apply different versioning, approval, metadata, or form settings.
You want to distribute management of versioning, metadata, workflows or form settings.
You do not need to receive consolidated updates (alerts or RSS).

Advanced Uses Of Lists

One Library or Multiple Libraries?
OR

When To Use a Single Library
You want to simplify viewing the same set of documents. (When dispersed across many libraries it requires additional effort to aggregate the libraries).
You want to search for documents in the same location.(When dispersed across many libraries it requires additional effort to configure search scopes).
You want to easily apply consistent versioning, approval, metadata or form settings.
You want to receive consolidated updates on the collection of documents (alerts or RSS).

When To Use Multiple Libraries
You don’t expect people to need summaries of the documents together.(When dispersed across many libraries it requires additional effort to aggregate the libraries).
You need to apply different versioning, approval, metadata, or form settings.
You want to distribute management of versioning, metadata, workflows or form settings.
You do not need to receive consolidated updates (alerts or RSS).

List and Content Type Tip!

Default Content Types and Metadata Values

Navigating with MetadataTip!

Navigating with Metadata, not Folders

Set up with Library Settings

Configure Setttings

Filters the list

Document Routing Tip!

Content Organizer and Routing

Configure the router

Configure settings

Create Rules

Create/Modify Rules

Use the Drop-off Library

Add a document

Enter Metadata

Detour: 2010 Metadata

Back to Drop-off library

Your document was moved

Rules don’t apply…

… it doesn’t get moved

Folder or Metadata?
OR

The #1 rule of SharePoint?
Except when it makes sense
Never use folders
ever

What’s wrong with folders?
Deep structures hard to navigate
Finding stuff is hard
Figuring out where to put stuff is even harder
Stuck with a rigid structure
Search is not the silver bullet

What’s the alternative?
metadata

What’s the alternative?

Metadata = No more folders
Filtering
Views

Really? No more folders? Ever?
What situations would you use folders?
Subdivide large libraries/lists
Security/Permissions
Ease of use for users
Really? No more folders?
Really?

Downsides of Metadata
No free lunch (there is pain here)
Awful architectural choices to make
Multiple site collections
Good Practice
Bad for Metadata
Maintenance headache
Can be mitigated
Define at top level if possible

Folders for easy permissions
Create folder
Set permissions
Create view without folders
Easy for users (they only see what they are supposed to)

Folders and Default Values

The Sales document library

Drill down into Military folder

Drill down into Air-to-Ground

Add a new document here

Note: Some metadata prefilled

How did we do that?
Library tab
Library settings

Column default value settings

Select a folder and set defaults
Note folder inheritance

Set the default value

in SharePoint 2010
Managed Metadata Service
Share Metadata across site collections
Multilingual Metadata (big gotcha )
Hierarchical Metadata
Navigate via Metadata (already discussed)
Keywords/Folksonomy (Out of scope today)
Folders can assign default metadata (already discussed)
metadata

Working With Managed Metadata

Term Store Management

Adding Terms

Turn off “Available for Tagging”
Add sub elements: Proposal, Quote, Invoice
Leave “Available for Tagging checked”

Term Store Manager
Painful & Slow
Needs a better way
I created a ‘toy’ to try out some ideas
http://bit.ly/ruveng-mmts
Article links to other solutions (Excel)

CSV file for Import to Term Store

To Sum Up…
SharePoint 2007
Folders BAAAAD!
Never use them
Except when the situation warrants
SharePoint 2010
Folders GOOOOD!
Never use them
Except when the situation warrants

Folder or Document Set?
OR

Folders vs. Document Sets
Document Sets vs Folders

Document Sets

Folders and Default Values

Document
Document
Document
Folder
Document Library
Folder
Folder
Document
Folder
Document
Document Set
Folder
Document
Document Set
Document

Great Resource!
Scott Jamison and Susan Hanley Wrote…
!LINK TO WHITEPAPER!

The Outcome
You need to understand all of the SharePoint objects, their limitations, and their benefits to make effective decisions.

There is always a trade off and all information architecture decisions should be constantly re-evaluated.

Putting it all Together
(a case study approach)

Introducing multiMEGA Industries
The world’s leading supplier of Missiles, Produce and Soap

They Want A SharePoint Intranet!

Find and Involve Stakeholders

Educate Stakeholders

Roadmap
Plan Their Roadmap

Inventory and Plan for Documents

Analyze Content Usage

Map Business Processes

Determine Navigation

Perform Card Sorting

Structured Approach for Navigation
Original Concept – 5 Steps to Structure SharePoint Sites

Wireframing Workshops

CommonIntranet Components

Identify Key Pages

Mockup Key Pages

Improve Usability

Improve Governance

The Outcome
A well planned information architecture approach will lead to better results.

Iterative improvements are necessary and should leverage a model like the one we just walked through.

AND FINALLY
PAY ATTENTION!!

MAKE IT FINDABLE

Search Reality
Most users don’t know how to perform searches well

So How Do We Make Search Better
Make sure our content is easy to read
Index only the data necessary
ignore the rest
Make the most of the user’s input
Refiners
query expansion, synonyms, suggestions
Build the results page around the users’ needs
show relevance
Best bets
Conditional content – Best bets better

2010 refiners can get users to content quickly

TRAIN YOUR PEEPS!

2010 can make training ainteractive process

Productivity Hub

IUseSharePoint
Download and install the ‘lunch’ and learn module - an interesting idea.

Make it easier to work with

Powerful Columns You Probably Didn’t Know About

Why Leveraging SharePoint Blog Features for News is a Great Idea

AD Groups or SharePoint Groups?
OR

SharePoint Groups vsAD Groups

Item Level Permissions
Best Practices For Using Fine-Grained Permissions Whitepaper

“Item Level” Permissions

Web Level Permissions

Targeted Code
New in SharePoint 2010 SPRoleAssignmentCollection.AddToCurrentScopeOnly

The Outcome
There are many ways that we can improve usability of SharePoint and as a result improve our Information Architecture.

Tips and Tricks are not enough to ensure successful Information Architecture.

SharePoint IA That Works Review…
Not Practical, Not User Friendly, and Not Planned
Improves Find-ability and Put-ability!
SharedUnderstanding And SharedCommitment Are Key
Every Decision Is More Effective With More Information
Practice And Experience Really Help
There Is So Much Out There You Can Use To Help

Full Name
Email Address
Allow Us To Keep In Touch And Send You SharePoint Information Architecture Resources
Role(s)
IT Pro Developer End User Architect Biz Analyst
Helps us understand where yourexperience with SharePoint has been and what roles were contained in our workshop audience.
Would you recommend this workshop to a colleague or friend?

What did you likebest or what did you find useful?
What was missing or what would you have liked to see?

Please complete and turn in your Session Evaluation Form so we can improve future events. Survey can be filled out at:
http://app.fluidsurveys.com/surveys/SPSTCDC2011-Thu-S1A-106
Presenter: Richard and Virgil
Session Name: SharePoint IA Design 101
Session No.: Thu-S1A-106

Thank You Organizers, Sponsors andYoufor Making this Possible.
Questions? Ideas? Feedback? Contact us:
Twitter: @VCMonkey & @rharbridge
Blogs: monkeyblog.highmonkey.com & rharbridge.com
Email us: virgil@highmonkey.com & richard@rharbridge.com
Resources: http://www.PracticalIntranet.com

SharePoint Information Architecture & Usability - SharePoint Saturday The Conference

by Richard Harbridge on Aug 12, 2011

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 2

Statistics

SharePoint Information Architecture & Usability - SharePoint Saturday The Conference Presentation Transcript