Experiences with two AsiaPacific-wide SharePoint Deployments - SharePoint Conference Southeast Asia


Published on

A SharePoint implementation with a scope targeting multiple countries comes with several challenges. Various cultural differences and technological barriers have to be considered for a successful rollout. These include factors like different management styles and working cultures, multiple languages (“can my SharePoint be in Chinese?”), distributed locations (“can we have a local server here?”), varying connection speeds (“our SharePoint is too slow!”), and others.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Opening slide please include
  • Shaking head -> India/Europe
    different thinking -> different ways to do things (e.g. Gerard's flight to Beijing story)
    working culture (e.g. office hours -> Japan vs. Zhuhai office)
  • Individualism/Collectivism relates to the relative emphasis that members of a society place on their self-interests vs. those of the group. People from a collectivist culture tend to define themselves in terms of their relationships with others, and they are more inclined to give up their individual needs when there is a conflict between their needs and group needs (Triandis 1995). Studies also have shown that people from collectivist cultures display a greater tendency to cooperate (e.g., Cox et al. 1991; wagner 1995). In contrast, members of an individualist culture tend to define themselves as autonomous entities independent of groups (Markus and Kitayama 1991). They are more likely to emphasize their individual needs over group needs and tend to be more competitive (Redding 1993; wagner 1995).

  • Might need translator
     Slower understanding
     Different way of communication (direct vs indirect)
  • Experiences with two AsiaPacific-wide SharePoint Deployments - SharePoint Conference Southeast Asia

    1. 1. Platinum Sponsor Gold Sponsors
    3. 3. ABOUT ME • Working with SharePoint since 2007 • Currently doing second regional SharePoint deployment • Responsible for presentation of SharePoint to management teams, requirements gathering, solution implementation, training of users, evaluation of third-party software, site maintenance, … Rene Modery www.modery.net
    4. 4. SESSION OBJECTIVES • Understand the challenges that a regional implementation poses • Hear about available solution options • Learn some best practices
    5. 5. • “one of the leading solution providers for the print media industry” • 11 subsidiaries in 12 countries BACKGROUND INFO:
    6. 6. BACKGROUND INFO: • “world's leader in smart metering, energy management solutions, and related services” • Australia/New Zealand, China, India, Southeast Asia
    7. 7. CHALLENGES OF REGIONAL DEPLOYMENTS They speak different languages 我爱 Share Point 私はシェ アポイン トが大好 きです Different connection speeds Users are everywhere Their (work) cultures are different
    8. 8. DIFFERENT (WORK) CULTURES The way we do things varies • Our behaviour can be misinterpreted by others • Decision making process • Formal vs Informal procedures
    9. 9. “Culture of Sharing” can differ • Individualism vs Collectivism • Security issues in different countries • “We want to share our information, but can we prevent people from printing and saving it?” DIFFERENT (WORK) CULTURES
    10. 10. BEST PRACTICES – (WORK) CULTURE • Prepare for differences beforehand by gathering information about the various cultures • Don’t do things your way, get feedback from “locals” on how they suggest to proceed • Provide information about security possibilities and their impact (cost, effort, …) if required
    11. 11. DIFFERENT LANGUAGES “Can our SharePoint be in Chinese?” Your users speak different languages which affects • Interactions • Site languages • Content 你好 こ ん に ち は Kumusta G’day mate नमस्ते สวัสดี 안녕하세요
    12. 12. DIFFERENT LANGUAGES - INTERACTIONS Language can be a barrier in • Requirements Gathering • Training • Communications • Support due to • different ways of expressing oneself • lack of knowledge & misunderstanding SharePoint End User TrainingOutline of today’s session:
    13. 13. DIFFERENT LANGUAGES - SITES Which language should “SharePoint items” be in? • What languages do users accessing a site use • Simplify access for users by providing multiple languages (improved in SP2010)
    14. 14. Should content be in English or local language? • Content targeted at local users only Local Language • Content for users speaking different languages English only Multiple Languages (more difficult to maintain) DIFFERENT LANGUAGES - CONTENT
    15. 15. BEST PRACTICES - LANGUAGES • Local power user(s) & a key contact • Specific content in target specific language • Provide clear guidelines which language to use in which situation • Provide training and support options in different languages
    16. 16. Single server location • Different offices have different connection speeds to it • Problem: • User Experience is not the same for all! •  “SharePoint is too slow!” •  “Can we have a local server?” DIFFERENT CONNECTION SPEEDS
    17. 17. Option #1 – multiple servers • Offers greatest flexibility • Administration becomes more difficult • May only make sense for a few locations DIFFERENT CONNECTION SPEEDS - SERVERS - + Flexibility User Experience Effort Cost
    18. 18. DIFFERENT CONNECTION SPEEDS - NETWORK Option #2 – Improve Network • More bandwidth (latency still an issue) • WAN optimization (e.g. caching) • Server improvement (Windows Server 2008) Cost might still be much higher than benefits!
    19. 19. DIFFERENT CONNECTION SPEEDS - APPROACH Option #3 – Different Implementation Approaches • “SharePoint light” for low-bandwidth countries • Less documents • Focus on simple pages, forms, and other “smaller” content Clear policies required - what to use when Risk: “Country X’s SharePoint is better than ours!”
    20. 20. BEST PRACTICES – CONNECTION SPEEDS • Think global, consider local • Get local input beforehand on requirements and possible performance • Do performance tests in different locations • Define clear governance
    21. 21. Q&A