1.Practical SharePoint Information ArchitectureRuven Gotz Director, Avanade

2. Its all about meRuven GotzToronto@ruvengspinsiders.com/ruvengruveng.gotz@avanade.comIntro - AnimatedLondon, UKJohannesburg, SASydney, AU 3. SHARE 2012 | 3Buy the Book (or Kindle):http://amzn.to/JnxlcC 4. Agenda for the day Mini-Keynote (30 min) Introduction (15 min) Preparing for successful outcomes & Requirements gathering (30 min) Coffee(15 min) Introduction to Mind Mapping (30 min) The Magic of Metadata (35 min) Lunch (60 min) @12:00 Catch-up (15 min) Card Sorting & Wireframing (30 min) Business process mapping (30 min) Coffee (15 min) Governance, Adoption & Training (30 min) Wicked Problems & Dialogue Mapping (30 min) Conclusion & wrap-up (15 min) 5. MINI-KEYNOTEFront matter 6. SHARE 2012 | 6Why areyouhere? 7. SHARE 2012 | 7Lost 8. SHARE 2012 | 8Notgoingso wellhttp://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Car_crash 9. SHARE 2012 | 9Show me 10. SHARE 2012 | 10Attendsessions 11. SHARE 2012 | 11I cando this 12. SHARE 2012 | 12Back to work 13. SHARE 2012 | 13Show others 14. SHARE 2012 | 14Getdown towork 15. SHARE 2012 | 15 16. SHARE 2012 | 16Can Ido this? 17. SHARE 2012 | 17Cant win the gameKnow how to move 18. SHARE 2012 | 18Wanted: 19. SHARE 2012 | 19Got: 20. SHARE 2012 | 20Why is this so hard? 21. SHARE 2012 | 21Reality ismessy(and chaotic) 22. SHARE 2012 | 22Dirty secret 23. SHARE 2012 | 23 24. SHARE 2012 | 24We know itstrue & wedont like iteither 25. SHARE 2012 | 25Id like mymoney back.Now! 26. SHARE 2012 | 26Do I havethe answer?NoDo you wantthe solution?(sorry) 27. SHARE 2012 | 27But, I canhelp withthe pain 28. SHARE 2012 | 28One Law 29. SHARE 2012 | 29Shared understanding 30. SHARE 2012 | 30Twomainstrategies 31. SHARE 2012 | 311. Simplicity 32. SHARE 2012 | 322. Flexibility 33. SHARE 2012 | 33Threemainstrategies 34. SHARE 2012 | 343. Focus 35. SHARE 2012 | 35Letsdivein 36. SHARE 2012 | 36One Law 37. SHARE 2012 | 37Shared understanding 38. SHARE 2012 | 38 39. SHARE 2012 | 39 40. SHARE 2012 | 40 41. SHARE 2012 | 41 42. SHARE 2012 | 42Yes!A bridge! 43. SHARE 2012 | 43Odds ofSuccess? 44. SHARE 2012 | 44Projectgoes? 45. SHARE 2012 | 45Samepage 46. SHARE 2012 | 46Wickedproblems 47. SHARE 2012 | 47Hard(but tame)Wicked 48. SHARE 2012 | 48Guess whatSharePoint is 49. SHARE 2012 |Usually a bunchof people who allhave a differentidea of whatsuccess looks like 50. SHARE 2012 | 50, wont talk to each other 51. SHARE 2012 | 51 52. SHARE 2012 | 52 53. SHARE 2012 | 53 54. SHARE 2012 | 54SHARE 2012 | 54Shared understanding 55. SHARE 2012 | 551. Simplicity 56. SHARE 2012 | 56Go Big orGo Home 57. SHARE 2012 | 57Photo: ultrarob.com 58. SHARE 2012 | 58Learn howthings workfirst 59. SHARE 2012 | 59 60. SHARE 2012 | 60Dontstink-upthe joint 61. SHARE 2012 | 61Barthedoors 62. SHARE 2012 | 62Yourgovernanceplan 63. SHARE 2012 | 63Simple &Consumable- Sue Hanley 64. SHARE 2012 | 64Yourmetadatastrategy 65. SHARE 2012 | 65Handcuffingyour users isnot a strategy 66. SHARE 2012 | 66Anger + confusion + frustration= Adoption failure 67. SHARE 2012 | 67A controversial idea 68. SHARE 2012 | 68Yourtrainingstrategywont work 69. SHARE 2012 | 693 days of trainingTraining fail 70. SHARE 2012 | 70You wont squeeze thejuice out of SharePoint 71. SHARE 2012 | 71You needa coach 72. 1. 2.SHARE 2012 | 72 73. SHARE 2012 | 73Follow theKISSprincipleAs simple as possible, but no simpler- Albert Einstein 74. SHARE 2012 | 742. Flexibility 75. SHARE 2012 | 75SteeringCommitteeIssues 76. SHARE 2012 | 76ThecowboyCIO 77. SHARE 2012 | 77Thesavior 78. SHARE 2012 | 78(nothing) 79. SHARE 2012 | 79Grassroots campaign 80. SHARE 2012 | 80Hit the road 81. SHARE 2012 | 81 82. SHARE 2012 | 82Flexibility 83. SHARE 2012 | 833. Focus 84. SHARE 2012 | 84Focuson theright things 85. SHARE 2012 | 85Projectfailure 86. SHARE 2012 | 86 87. SHARE 2012 | 87 88. SHARE 2012 | 88 89. SHARE 2012 | 89 90. SHARE 2012 | 90 91. SHARE 2012 | 91 92. SHARE 2012 | 92 93. SHARE 2012 | 93 94. SHARE 2012 | 94Is launch the goal? 95. SHARE 2012 | 95Why do weput all thefocus on alaunch date? 96. SHARE 2012 | 96If you are not planningfor change on day 1You are already behind 97. SHARE 2012 | 97This stuff isconfusing anddifficult 98. SHARE 2012 | 98Yoursuccessstrategy 99. SHARE 2012 | 99SHARE 2012 | 99One Law 100. SHARE 2012 | 100Three StrategiesSimplicity Flexibility Focus 101. SHARE 2012 | 101You cando this 102. INTRODUCTIONFront matter 103. SharePoint can be dangerous to your careerSHARE 2012 | 103 104. SHARE 2012 | 104Expectations are set very high 105. The waters can be rougher than expectedSHARE 2012 | 105 106. SHARE 2012 | 106but the results can make it worthwhile 107. My point of view 108. What is an Information Architect?http://www.flickr.com/photos/racingmix/274777460/ 109. SHARE 2012 | 109What is a Business Analyst? 110. In the SharePoint world, its a bit of a hybrid 111. Dealing with humans in tough circumstances 112. SHARE 2012 | 112You have got to get everyone onto the same page 113. SHARE 2012 | 113The key to sharedcommitment isShared Understanding 114. SHARE 2012 | 114Visual tools are a greatway to get to sharedunderstanding 115. PREPARING FORSUCCESSFUL OUTCOMESChapter 1.Everything should be made as simple aspossible, but no simpler.Attributed to Albert Einstein 116. SHARE 2012 | 116Soft skills 117. Machiavelli (not exactly )It must be considered that there is nothing moredifficult to carry out nor more doubtful of success normore dangerous to handle than to initiate a newSharePoint project; for the project team has enemies inall those who profit by the old portal, and onlylukewarm defenders in all those who would profit bythe new portal; this lukewarmness arising partly fromthe incredulity of mankind who does not truly believein anything new until they actually have experience ofit. 118. Dealing with humans in tough circumstances 119. Dealing with humans in tough circumstances 120. Building confidence 121. Listening 122. Humor 123. Brutal Honesty 124. Requirements gathering 125. Requirements 126. What makes something a requirement? 127. My three rules of SharePoint1. Simplicity2. Simplicity3. Simplicity 128. We can do that for $10 129. We can do that for $1,000,000 130. We require a jumbo solution to get to our destination 131. The SharePoint Hammer Problem 132. Is it really close by? 133. Is fast and light-weight the way to go? 134. Is a pre-built solution the best course? 135. Do you need a specialized solution? 136. Do you need to think outside the box? 137. Sometimes you need the jumbo solution 138. Its the destination that matters 139. The environment will change 140. The unexpected will happen 141. A lot of required features never get used 142. DONT demo SharePoint 143. Initial discovery workshops 144. SharePoint Workshop 145. Agenda About the Project , Our Team & Goals SharePoint Overview Department and Role Document Collaboration Document Storage and Search Compliance, Records Management & Off-line Questions 146. About the Project, Our Team & GoalsAbout this Project Determine the requirements and scope for a SharePointimplementation at ABC Corp.Our Team Alison Andrews Project Manager Bob Baker Technical Architect Carol Conrad SharePoint Analyst Don Drummond Infrastructure AnalystWorkshop Goals Set expectations Gather your input Keep it to an hour (+ optional half-hour for further questions) 147. SharePoint 2007 OverviewCollaborationPortalSearchEnterpriseContentManagementBusinessProcessandFormsBusinessIntelligenceDocuments/tasks/calendars, blogs,wikis, e-mail integration, projectmanagement lite, Outlookintegration, offline documents/listsVirtual Teams/Global TeamsEnterprise Portaltemplate, SiteDirectory, MySites, socialnetworking, privacycontrolEnterprisescalability, contextualrelevance, rich search forpeople and business dataIntegrated documentmanagement, recordsmanagement, and Webcontent management withpolicies and workflowOOB workflows,WF integration,rich and Web formsbasedfront-ends, LOBactions, pluggable SSOServer-based Microsoft OfficeExcel spreadsheets and datavisualization, Report Center,business intelligence WebParts, KPIs/DashboardsPlatformServicesWorkspaces, Mgmt,Security, Storage,Topology, Site Model 148. SharePoint 2010 Overview Ribbon UISharePoint WorkspaceSharePoint MobileOffice Client and Office Web App IntegrationStandards SupportIntranet, Extranet, Team CollaborationTagging, Tag Cloud, RatingsSocial BookmarkingBlogs and WikisMy SitesActivity FeedsProfiles and ExpertiseOrg BrowserEnterprise Content TypesMetadata and NavigationDocument SetsMulti-stage DispositionAudio and Video Content TypesRemote Blob StorageList EnhancementsOrganizing InformationSocial RelevancePhonetic SearchNavigationFAST IntegrationEnhanced PipelineSearchPerformancePoint ServicesExcel ServicesChart Web PartVisio ServicesWeb AnalyticsSQL Server IntegrationPowerPivotBusiness IntelligenceBusiness Connectivity ServicesInfoPath Form ServicesExternal ListsWorkflowSharePoint DesignerVisual StudioAPI EnhancementsREST/ATOM/RSSBuilding complex solutionson top of SharePoint 149. Department and RolePlease introduce yourself: Name Department What is your role within your department? How do you interact with technology to do your job? How does the current technology help you (or hinderyou) from doing your job? 150. Document Collaboration Do you work on documents with others? How do you collaborate (e-mail, shared drive) ? What document types do you create? Which programs do you use? Do your documents require multiple reviews and edits? Isapproval required? How do you implement the required workflow? How do you get the final information out to the audiencethat needs it? Do you publish PDFs? How are they distributed/posted? 151. Document Storage and Search Can you find the documents that you need, when you needthem? Does your shared drive folder hierarchy work well? How long does it take to find a document? At what point do yougive up? When you create a document, do you know where it shouldbe saved? Are documents saved in more than one location to easeretrieval? Does search work well? What features would you like to see in search that would makeit better for you and your team. 152. Compliance, Records Management & Off-line Do you have any regulatory requirements that you need tomeet? ISO 9000 Sarbanes-Oxley Bill 198 How are records management policies implemented? Are there specific policies for document retention anddestruction. Do you have a need for off-line access? Do you travel off-site for your work Do you need to work when you are disconnected from thenetwork. 153. Questions 154. NOW its ok to demo SharePoint 155. Roadmapping 156. The Simplest Prioritization Formula EverEstimated ValueEstimated Difficulty 157. Prioritization Example I have a difficult solution. Its an 8 in difficulty (out of 10). I have an easy solution. Its a 2 in difficulty (out of 10). The expected value of the difficult solution is 4 (out of 10). The expected value of the easy solution is 6 (out of 10).Estimated ValueEstimated Difficulty 158. CentralizeKnowledge andResourcesEnhanceCollaborationAutomate andImprove BusinessProcessesEnhanceGovernanceModelReduceRedundancy andImprove EfficiencyCentralizeKnowledge andResourcesCentralize Centralize Centralize CentralizeEnhanceCollaboration Improve BP Governance RedundancyAutomate andImprove BusinessProcessesGovernance RedundancyEnhanceGovernanceModelRedundancyReduceRedundancy andImprove EfficiencyPaired Comparison MatrixObjective WeightCentralize 4Collaboration 0Improve BP 1Governance 2Redundancy 3 159. The Power Of Zero $$ Change Orders 160. Morning Coffee (15 min) 161. INTRODUCTION TO MIND MAPPINGChapter 2What do you call what we just did there? That wasamazing!More than a few of my clients on morethan a few occasions after a workshopwhere I used mind mapping 162. Mapping for Navigation 163. Mapping for Prioritization 164. Mapping for Scoping 165. THE MAGIC OF METADATAChapter 3If it walks like a duck, quacks like a duck, looks like aduck, it must be a duck.Proverb 166. This is a Meta-Presentation Two Goals and a Meta Goal: Understand metadata How it applies to taxonomy How it applies to content types Understand why it matters in SharePoint Meta Goal Educate you Give you tools to educate YOUR stakeholders 167. The BIG questionWhat isMetadata? 168. Data about data 169. Questions 170. The BIG questionWhat isMetadata?I thinkI get itOh!Now I see(Mostly)What is Metadata?I think I get it 171. To understand what are 172. Well use a 173. What does a cow say? 174. What does a chicken say? 175. What does a duck say? 176. Whats the difference? 177. What is the content?What are some attributes? Artist: Prince Genre: Pop/Rock Year: 1984Example from Yoav Lurie 178. Organizing Content 179. Another metaphorAdapted from the peasoup story by SergeTremblay 180. Labels can help 181. Food taxonomy nirvanahttp://caseyxrobertson.deviantart.com/art/Grocery-Store-2-191196289 182. So, what is metadata? 183. or thisNot this!What is taxonomy? 184. Its this 185. Carl Linnaeus (1751) 186. TaxonomyAnimalKingdomInvertebrates VertebratesMammalsPredators Primates Whales RodentsSquirrels MiceMice & RatsHamsters andVolesPorcupines Guinea PigsFish Amphibians Reptiles BirdsSuperclassClassOrderSuborderFamilyKingdom 187. The bottom of this tree AnimalKingdomInvertebrates VertebratesMammalsPredators Primates Whales RodentsSquirrels MiceMice & RatsHamsters andVolesReal HamstersShort-taileddwarf hamstersDjungariandwarfhampstersRoborovskiHamsterLong-taileddwarf hamstersVoles GerbilsPorcupines Guinea PigsFish Amphibians Reptiles Birds 188. Taxonomy X:ProductionSales &MarketingMarketingCommercial Industrial Government HealthcareLabs HospitalsPrivate PublicLargeUrbanNotAssociatedUniversityRuralMedium SmallClinics MobileSales Web Design Newsletter SocialShared drive zoo 189. Taxonomy X:ProductionSales &MarketingMarketingCommercial Industrial Government HealthcareLabs HospitalsPrivate PublicLargeUrbanNotAssociatedUniversityRuralMedium SmallClinics MobileSales Web Design Newsletter Social 190. Weve all seen how well this works out 191. Taxonomy X:ProductionSales &MarketingMarketingMajorHospitalsCommercial Industrial Government HealthcareLabs HospitalsPrivate PublicLargeUrbanNotAssociatedUniversityRuralMedium SmallClinics Mobile CollegesBig SmallSales Web Design Newsletter SocialShared drive zoo 192. Moving this mess to SharePoint only makes it worse 193. SharePoint Sux!SharePoint is confusing! Why? 194. What is our base metaphor for files? 195. Folders on the Mac 196. What if we saw this? 197. Better 198. Solve it with folders! 199. Now, you hire an intern to add documents 200. Finding vs. Saving 201. Findability 202. Putability 203. The #1 rule of SharePointNever usefoldersExcept when it makes sense todo soever 204. When it makes sensePermissions assignedper folder 205. SharePoint Taxonomy 206. SharePoint Taxonomy (Metadata)Customer Type Lab Hospital Clinic MobileSector Private PublicSize Large Medium SmallLocation Urban RuralUniversity Yes No 207. Adding metadata (when uploading) 208. A SharePoint Simulation 209. Inventory worksheet 210. What is metadata? 211. What is taxonomy? 212. What are content types? 213. Name _________Emp. # _________Date _________Dates Requested:From __________To: __________Manager ____Approved Y/NName _________Emp. # _________Date _________Drug Used:Name __________Cost: $ _________Manager ____Approved Y/NVacation RequestDrugReimbursement 214. Both content types in one list 215. Content types for: Workflow, Policy, Security 216. InventoryWorksheet 217. Mind Mapfrom InventoryWorksheet 218. Key Points to Take Home Metadata takes a while to understand Use of metaphors can help Use of visual tools can help a LOT Much more than technology, its governance that makes thedifference Folders are bad, except when theyre not 219. Lunch (60 min) 220. Morning Recap (15 min) 221. This is tough, but the results can be worthwhile 222. Differences between BA and IA 223. Getting to Shared Understanding is crucial; visual tools can help 224. Soft Skills need to be developed:Confidence, Listening, Humour & Honesty 225. Gather requirements Focus on business outcomesRequirements 226. Run the discovery workshops and build the roadmap 227. The magic of metadata 228. CARD SORTINGChapter 4 229. What is Card Sorting? 230. Card sorting is a great, reliable,inexpensive method for findingpatterns in how users would expectto find content or functionality.- Donna Spencerhttp://www.amazon.com/Card-Sorting-ebook/dp/B004VFUOL0 231. What are the types of card sort?Open & Closed 232. Open card sorting processGerbil 233. ResultsGerbil 234. But not always what you expectFordGerbil 235. But not always what you expect (2)FordGerbil 236. Analysishttp://www.boxesandarrows.com/view/analyzing_card_sort_results_with_a_spreadsheet_template 237. WIREFRAMINGChapter 5You cant do sketches enough. Sketch everythingand keep your curiosity fresh.John Singer Sargent 238. I used to hate wireframing! 239. A useless wireframe 240. Way too much workErik Swenson 241. Balsamiq: Just right 242. BUSINESS PROCESS MAPPINGChapter 7If you cant describe what you are doing as a process,you dont know what youre doing.W. Edwards Deming 243. Information doesnt just pop into existence 244. Afternoon Coffee (15 min) 245. GOVERNANCE, ADOPTION & TRAININGChapter 7Mary, Mary quite contrary, how does your garden grow? Withsilver bells and cockleshells and pretty maids all in a row.Nursery Rhyme 246. Done?SHARE 2012 | 267 247. You need to tend the gardenSHARE 2012 | 268 248. Final gardening metaphor SHARE 2012 | 269 249. Above the line vs. Below the lineSHARE 2012 | 270 250. Marcy Kellars Publishing Cheat SheetSHARE 2012 | 271http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoint/comment-page-1/P 86 251. The modified pyramidSHARE 2012 | 272 252. SHARE 2012 | 273 253. What is governanceSHARE 2012 | 274 254. An outcome based concept (Paul Culmsee)SHARE 2012 | 275 255. A definition from outside SharePointSHARE 2012 | 276 256. SHARE 2012 | 277 257. Steering committeeSHARE 2012 | 278The job of the steering committee includes: Establishing vision and strategy, Creating and managing the portal roadmap, Synchronizing the vision across businessunits, Acting as champions within individualbusiness units as well as enterprise wide, Defining success factors and keyperformance indicators and measuring results, Procuring and allocating the intranet budget, Reviewing and tracking intranet projectbudgets, Providing operations team oversight. 258. Operations TeamSHARE 2012 | 279The operations team is a partnership betweenIT and business owners of the portal. Its job isto communicate and cooperate to ensure thatthe portal runs smoothly and efficiently. Theteam members have to work together tobalance the needs of IT for control andmanageability and the needs of the businessforresponsiveness, reliability, performance, andflexibility. The team as a group doesnthave specific roles and responsibilities; thoseare dictated by their individual roles furtherdown in thehierarchy. 259. IT ManagerSHARE 2012 | 280The IT manager is responsible for the physicalinfrastructure as well as operational aspects ofthe SharePoint service, including: Hardware service and upgrades, System assurance (uptime, performance,availability, security, disaster recovery,system updates and upgrades, monitoring), Development or procurement andsubsequent deployment of new features, Help desk, second-level support, Training and coaching (Optional: In manyorganizations, this is owned by other groups), Key member of the operations team and thegovernance committee. 260. Editor in ChiefSHARE 2012 | 281The editor in chief (sometimes called the portalowner) is the person responsible for thecontent that appears on the site. His or herresponsibilities include: Approving overall content on the site,ensuring consistency of look, feel, tone,style (words and pictures), and overall sitequality, Taking ownership of the home page,including approving content that appearsthere, ensuring it is fresh and accurate, Nurturing and supporting the internalSharePoint community, Leading communications efforts (letting thecompany know of new features orchanges to the portal), Being a key member of the operations teamand governance committee. 261. Site Owner/Section OwnerSHARE 2012 | 282The responsibilities of these owners include: Maintaining quality for the content in thissection or site, Ensuring that high-risk(confidential/inappropriate) material is notexposed on the portal, Ensuring that existing content is updated asrequired, Ensuring that content is removed from thesite if it is out of date, expired, orotherwise no longer relevant (while adheringto the records management policy), Remaining aware of content in other areas toensure consistency and to ensurethat duplicate content does not existelsewhere, Ensuring that published content adheres tostyle policies. 262. Site Owners/Section OwnersSHARE 2012 | 283 263. Content ApproverSHARE 2012 | 284This role is not usually assigned to a separateperson; the section owner may be theapprover of content for the sites containedwithin that section. Or a site owner may be theapprover for subsites. In some cases, wherethere are legal or other high-risk issues, theremay be approvers assigned from the legal orother departments. The responsibilities of theapprover include: Checking that content is factually correct, Providing oversight to ensure that high-risk(confidential/inappropriate) materialis not exposed on the portal, Ensuring that content follows corporate policies forstyle and content, Being responsible for timely approval (not being abottleneck), Ensuring that metadata has been properly entered, Ensuring content is posted to the correct location. 264. Content OwnerSHARE 2012 | 285The content owner may be the same person asthe site owner, or that person may just beresponsible for a subset of content within aparticular area of a site.There is a lot of overlapping responsibility hereThat is because at every level, people have anabsolute responsibility to ensure the qualityand impact (safety and risk) of the contenton the site. As we move up the responsibilityhierarchy, each level can catch issues missedby the layer below.See P 195 for details here 265. Content AuthorSHARE 2012 | 286The next layer is where the actual work getsdone: authoring. Content authors areresponsible for: Creating content, Ensuring content adheres to corporatepolicies, Ensuring that high-risk(confidential/inappropriate) material is notexposed on the portal, Ensuring that appropriate metadata areproperly and completely entered, Ensuring that the content is placed in thecorrect location within the site. 266. Visitors/ReadersSHARE 2012 | 287Finally, we get to the layer of those who haveno hand in the creation, approval, ormanagement of content: the readers. And yet,within an organization, you must putresponsibility into the hands of readers tonotice and point out material that isinaccurate, out of date, or that could put theorganization at risk. You have to enable thereaders to report issues by making it easy forthem to do so. There should be a link on eachpage to report issues or at least to contact thepage owner (every page must displaywho the owner of that page is). 267. Adoption in the real worldSHARE 2012 | 288 268. Disengaged leadershipSHARE 2012 | 289 269. The power of leadershipSHARE 2012 | 290 270. Build a communitySHARE 2012 | 291 271. Classroom TrainingSHARE 2012 | 292SUX 272. Video TrainingSHARE 2012 | 293SUX 273. No TrainingSHARE 2012 | 294SUX 274. CoachingSHARE 2012 | 295 275. Your end-users DO need trainingSHARE 2012 | 296 Classroom Video Lunch and learn Community 276. A new worldSHARE 2012 | 297 277. COMPLEXITY, WICKEDNESS ANDDIALOGUE MAPPINGChapter 6Something wicked this way comesRay Bradbury 278. Two books you must read 279. What are wicked problems? You dont really understand the problem until youvedeveloped the solution You dont know when youve accomplished your goal Solutions are not right or wrong, they are just better orworse Every wicked problem is unique Every solution to a wicked problem is a one-shotoperation You are dealing with social complexity 280. Tools that can help 281. IBIS Notation 282. I use Mind Manager to express the same notation 283. Dialog mapping to capture argumentation 284. Dialog mapping to capture argumentation 285. Dialog mapping to capture argumentation 286. Dialog mapping to capture argumentation 287. Dialog mapping to capture argumentation 288. Dialog mapping to capture argumentation 289. Dialogue Mapping for scoping 290. CONCLUSION & WRAP UPChapter 7Things done well and with a care, exempt themselvesfrom fear.William Shakespeare 291. Practice or Practitioner 292. Kick-off Identify the players 293. Nail down the vision 294. Roles & Personas 295. Assess Current Maturity http://www.sharepointmaturity.com/home.aspx 296. Run your discoveryworkshops 297. Managing Content Inventory content and identify content owners Writing for the web learn to do it properly Create and approve content as early as possible 298. Navigation Workshops 299. Collaboration strategy 300. Infrastructure 301. Search strategy 302. Wireframing & Branding 303. Communication Planning and Community Building 304. Training, Adoption& Governance 305. Summary 306. This presentation will be available on the TorontoSharePoint Summit web site a few days after the event.Thank you 307. Please rate this session!Fill out the survey and get a chance to win a Surface 308. www.sharepointsummit.orgRuven Gotz@ruvengspinsiders.com/ruvengruveng.gotz@avanade.comIntro - Animated 309. Summary 310. SharePoint Containment HierarchyDocuments, Items andPagesFolders and DocumentSetsLibraries and ListsSitesSite CollectionsDatabasesWeb ApplicationsServersFarmWhat we care about from aninformation architectureperspective. 311. SharePoint Containment HierarchyMetadataItemDocuments, Events, Pages, Custom Item, Image, etc.Folders and Document SetsListsDoc Libraries, Pages, Calendars, Discussions, Surveys, etc.SitesTeam Sites, Publishing Sites, Meeting Workspaces, etc.Site Collections 312. Site Collection or Site (Subsite)?OR 313. Site Collection 314. Site Collection 315. When To Use A Site Collection 316. When To Use A Site Collection 317. When To Use A Site Collection 318. When To Use A Site Collection 319. When To Use A Site Collection 320. When To Use A Site Collection 321. When To Use A Site CollectionSite Collection 1 Site Collection 2Webparts &AggregationWebparts &AggregationMasterpages& Page LayoutsMasterpages& Page LayoutsSearch Across Site Collection BoundariesNavigation Navigation 322. When To Use A Site CollectionGroup AGroup BGroup CCollection Admin ACollection Admin BGroup YGroup ZCollection Admin YCollection Admin ZSite Collection 1 Site Collection 2