SharePoint Information Architecture & Usability - SharePoint Saturday The Conference

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

2. 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:

3. Who am I?
I

4. 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

6. Information Architecture is a Practice not a Strategy

7. In IA, there is no single right answer.

8. Proven Success

9. Take Away: Confidence

10. Take Away: Improved Communication

11. Take Away: Knowledge YouCan Use

12. Our Goal Today
From Here To Here

13. 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

14. What We Wont 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

15. Why SharePoint Information Systems Fail
Visualizing and Communicating IA Concepts

16. Why SharePointIA Fails

17. #1
NO PLAN
(or it was small)

18. It started out simple

19. Then it grew

20. Then it got TOTALLY out of control!!

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

22. SharePoint will be

Utilized by Business Users to develop and implement business solutions that use technology without ITs direct involvement.

23. Our primary unified application delivery platform.

24. Our primary workflow/business process automation platform.

25. Our intranet and communication center for internal corporate communications.

26.

SharePoint will not be

Our (external) web content management platform.

27. Our primary document management platform.

28. Our contact management platform.

29.

#2
BUSINESS DOES NOT WORK THE WAY WE THOUGHT

31. Opportunistic Driven Learning
Image from Paul Culmsee

32. #3
WE THOUGHT
ORG CHART = SITE MAP

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

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

35. #6
NO REVIEWS
(or analysis of usage)

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

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

Why SharePoint Information Systems Fail

39. What MakesAn IA StrategyREALLYwork

40. With a good IA

41. You can take this

42. and make it into this

43. This

44. into this

45. 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.

46. What is information architecture?
4 basic IA concepts
Information
Undergoes Structuring, organizing, and labeling
To improve Finding and managing
ThroughArt and science

47. 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 cant understand it something if you dont organize it!

48. 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

49. 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

50. Content
Context
Includes documents, applications, services, schema, and metadata that people need to use or find onyour site.

How much content do you have?

51. What are the formats your content is in?

52. Who owns your content?

Content
Users

53. 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

54. What does IA support?

55. 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

56. A good IA
increases our chances of finding the right stuff

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

58. Why doesnt this model work?

Most users dont know what their looking for

59. Most users dont know how to search

60. Most users dont have the patience for complicated systems

Find-ability
Models

61. Sometimes youre just looking for one answer (known-item)

62. Sometimes you want to investigate(exploratory)

63. Sometimes you want to find everything(Dont know what you need)

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

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

66. Dont Forget Put-ability
Search isnt a silver bullet.

67. A good IA
helps us work effectively

68. Lets look back

69. A good IA
supports user experience

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

71. Incorporate Feedback Planning
Couldnt 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 dont 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

72. Plan IA Review Processes

73. 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

76. Visualizing and CommunicatingIA Concepts

77. Taxonomy and Metadata

78. Taxonomy and Metadata

79. What is Taxonomy?
or this
Not this!

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

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

82. 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!

83. Arrangement and Context
Taskonomy?
Department Store
Wholesale Warehouse

84. 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

85. 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?

86. What is Metadata?
The BIG Question

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

88. Adapted from the pea soup story by Serge Tremblay

91. What is our Base Metaphorfor files?

93. What if we saw this?

94. Better

95. Solve with folders

96. Hire an intern

97. This is metadata!

98. As weve already seen: This always works out great
This is a common result

99. Shared Drive Zoo

100. Moving this mess to SharePoint
makes it worse

101. SharePoint Sux

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

103. 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!

104. Metadata
I like it!

105. Adding Metadata (when uploading)

106. A SharePoint Simulation

107. What are content types?

108. 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

109. Both Content Types in One Library

110. Content Types for:
Security
Workflow,
Policy,

111. CREATE LABELING SUPPORT
(metadata)

112. 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.

113. Creating your labels
Start small, grow organically
Dont be afraid of natural language
Always label
Train your usersright now!
Its not a relational database
Use Content Type Syndication

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

115. 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

116. 2010 takes labeling serious!

117. 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.

119. Tools For The Information Architect

120. Same Page

121. Abstract

122. Concrete

123. Mind Mapping Demonstration

124. Navigation
workshops

125. Navigational Map

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

130. 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.

131. 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

132. 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?

133. 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.

134. What are the types of card sort?
Open
& Closed

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

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

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

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

139. BIG MONKEY
Card Sort

141. Card Sort Results

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

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

144. Wireframing Workshops

145. Balsamiq

146. CommonIntranet Components

147. Balsamiq DEMO

148. Wireframing Tip!

149. Dont Forget Consistency
Consistency Across User Environments
Modify Provisioned Site (or Templates) Based on Need
Each Page Design Should Be Consistent

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

151. Usabilitys 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?

152. Why do we need it?

153. Why do we need it
When an interface doesnt make sense
PEOPLE DONT USE THEM

154. Usability Testing

155. Setting up your Usability Plan
Determine what you are trying to find out
Establish your purpose

why are you testing?

156. what worries you with your system?

What do you really need to test?

Design your Test
Identify the users youll test

test at least 5 people

158. set-up use cases

159. get permission to use data

160. get users from different levels of competency

Setting up your Usability Plan
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

164. Complete a process

165. Find a specific piece of content

166. Create something

Lets look at a
sample usability test

Run your Test
Re-assure your User

go over expectations

169. make sure the user understands the INTERFACE is being tested, not THEM

170. 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

174. FIGURE OUT YOUR CONTENT

175. Document Inventory Workshops

176. 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?

177. An Inventory Worksheet

178. Build Mind Map (based on an inventory worksheet)

179. 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?

180. 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

181. 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

182. ORGANIZE WHAT YOU FIND

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

184. 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!!!

185. No Single Approach
Projects
Communities
Tasks
Practices

186. Business Process Workshops

187. Visio 2010 Demo

188. Common Intranet Processes

Absence Reporting and Vacation Scheduling

189. Expense Reimbursement

190. Equipment and Room Reservation and Management

191. Meeting Planning and Management

192. Policy Review and Approval

193. Booking Travel

194. Interview Management and Hiring Processes

195. Training Sign Up and Management

196. Event Planning

197. Change Request Management

198. Timecard/Time Tracking

199. Product Planning

200. Help Desk Ticket Management

201. Compliance Support

202. Contacts Management

203. Inventory Tracking

204. Lending Tracking

205. Sales Lead Pipeline

Roadmap

206. 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.

209. Making
Information Architecture Decisions

210. The Importance of Making Good Information Architecture Decisions

211. What is the ultimate IA structure?
There isnt one!

212. You need to
Un-enterprise your architecture

213. Why Enterprise IA doesnt work
One IA doesnt 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 doesnt necessarily mean better (how many people really need to search everything)
Do not fret, there are models that do work.

214. Information Architecture and Governance Areas
Permanent central portal
- Few authors/Many readers
Communication Portal

Central navigation

215. Central taxonomy

216. Divisional stakeholders

217. Enterprise search

CentralPortal
Departmental sites

Departments

218. Resources

219. Business Processes

- Few authors/Many readers
Increasing Strictness of Governance
Collaboration

Local taxonomies

220. Local search

Semi Structured
Team sites
- Multiple authors
Blogs, bios,
Social
Personal
Above The Line versus Below The Line

221. Recommended Approach
Bob Mixon on SharePoint 2007 Site Collections

222. 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

223. Enterprise Publishing

224. 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

225. And for the rest of us?

226. 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

227. How can SharePoint help?

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

229. SharePoint Containment Hierarchy

230. Site Collection or Site (Subsite)?
OR

231. Site Collection

232. Site Collection

233. 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

241. SharePoint Permissions

242. Purpose of a List?

To Replace Excel Spreadsheets

243. To Track Complex Input From Multiple People

244. To Centralize Storage and Retrieval of Content

245. To Provide Validation, Easy To Use Online Forms

246. To Reduce Duplication of Effort

One List or Multiple Lists?
OR

247. 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).

248. You want to search for items in the same location.(When dispersed across many lists it requires additional effort to configure search scopes).

249. You want to easily apply consistent versioning, approval, metadata or form settings.

250. You want to receive consolidated updates on the collection of items (alerts or RSS).

When To Use Multiple Lists

You dont expect people to need summaries of the items together.(When dispersed across many lists it requires additional effort to aggregate the lists).

251. You need to apply different versioning, approval, metadata, or form settings.

252. You want to distribute management of versioning, metadata, workflows or form settings.

253. You do not need to receive consolidated updates (alerts or RSS).

Advanced Uses Of Lists

254. One Library or Multiple Libraries?
OR

255. 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).

256. You want to search for documents in the same location.(When dispersed across many libraries it requires additional effort to configure search scopes).

257. You want to easily apply consistent versioning, approval, metadata or form settings.

258. You want to receive consolidated updates on the collection of documents (alerts or RSS).

When To Use Multiple Libraries

You dont expect people to need summaries of the documents together.(When dispersed across many libraries it requires additional effort to aggregate the libraries).

259. You need to apply different versioning, approval, metadata, or form settings.

260. You want to distribute management of versioning, metadata, workflows or form settings.

261. You do not need to receive consolidated updates (alerts or RSS).

List and Content Type Tip!

262. Default Content Types and Metadata Values

263. Navigating with MetadataTip!

264. Navigating with Metadata, not Folders

265. Set up with Library Settings

266. Configure Setttings

267. Filters the list

268. Document Routing Tip!

269. Content Organizer and Routing

270. Configure the router

272. Configure settings

273. Create Rules

274. Create/Modify Rules

276. Use the Drop-off Library

277. Add a document

278. Enter Metadata

279. Detour: 2010 Metadata

281. Back to Drop-off library

282. Your document was moved

283. Rules dont apply

284. it doesnt get moved

285. Folder or Metadata?
OR

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

287. Whats 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

288. Whats the alternative?
metadata

289. Whats the alternative?

290. Metadata = No more folders
Filtering
Views

291. 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?

292. 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

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

294. Folders and Default Values

296. The Sales document library

297. Drill down into Military folder

298. Drill down into Air-to-Ground

299. Add a new document here

300. Note: Some metadata prefilled

301. How did we do that?
Library tab
Library settings

302. Column default value settings

303. Select a folder and set defaults
Note folder inheritance

304. Set the default value

305. 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

306. Working With Managed Metadata

307. Term Store Management

308. Adding Terms

309. Turn off Available for Tagging
Add sub elements: Proposal, Quote, Invoice
Leave Available for Tagging checked

310. 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)

312. CSV file for Import to Term Store

313. 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

314. Folder or Document Set?
OR

315. Folders vs. Document Sets
Document Sets vs Folders

316. Document Sets

317. Folders and Default Values

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

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

325. 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.

328. Putting it all Together
(a case study approach)

329. Introducing multiMEGA Industries
The worlds leading supplier of Missiles, Produce and Soap

330. They Want A SharePoint Intranet!

331. Find and Involve Stakeholders

332. Educate Stakeholders

333. Roadmap
Plan Their Roadmap

334. Inventory and Plan for Documents

335. Analyze Content Usage

336. Map Business Processes

337. Determine Navigation

338. Perform Card Sorting

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

340. Wireframing Workshops

341. CommonIntranet Components

342. Identify Key Pages

343. Mockup Key Pages

344. Improve Usability

345. Improve Governance

346. 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.

348. AND FINALLY
PAY ATTENTION!!

350. Information Architecture Tips and Tricks

351. MAKE IT FINDABLE

352. Search Reality
Most users dont know how to perform searches well

353. 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 users input
Refiners
query expansion, synonyms, suggestions
Build the results page around the users needs
show relevance
Best bets
Conditional content Best bets better

354. 2010 refiners can get users to content quickly

355. TRAIN YOUR PEEPS!

356. 2010 can make training ainteractive process

357. Productivity Hub

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

359. Make it easier to work with

Powerful Columns You Probably Didnt Know About

Why Leveraging SharePoint Blog Features for News is a Great Idea

362. AD Groups or SharePoint Groups?
OR

363. SharePoint Groups vsAD Groups

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

365. Item Level Permissions

366. Web Level Permissions

367. Targeted Code
New in SharePoint 2010 SPRoleAssignmentCollection.AddToCurrentScopeOnly

368. 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.

370. 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

371. Full Name
Email Address
Allow Us To Keep In Touch And Send You SharePoint Information Architecture Resources
Role(s)
IT Pro DeveloperEnd UserArchitectBiz 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?

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

373. 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

375. Thank You Organizers, Sponsors andYoufor Making this Possible.
Questions? Ideas? Feedback? Contact us:

Twitter:@VCMonkey & @rharbridge

376. Blogs: monkeyblog.highmonkey.com & rharbridge.com

377. Email us: [email protected]& [email protected]

378. Resources: http://www.PracticalIntranet.com

Technology

SharePoint Information Architecture & Usability - SharePoint Saturday The Conference