Presented at 3|SHARE's EVOLVE'14 - The Adobe Experience Manager Community Summit on Wednesday November 19th, 2014 at the Hard Rock Hotel in San Diego, CA. evolve14.com

1. Staying on the multilingual rails
42
2,300,000,000
60

2. Staying on the multilingual rails
42 Ave # of langs a global firm translates into
2,300,000,000
60

3. Staying on the multilingual rails
42 Ave # of langs a global firm translates into
2,300,000,000
# of Internet users who don’t speak English as their
decision making language
60

4. Staying on the multilingual rails
42 Ave # of langs a global firm translates into
2,300,000,000
# of Internet users who don’t speak English as their
decision making language
60% of IT project fail to meet their objectives

5. Staying on the multilingual rails
Three cautionary Tales…
• Global Banking Institution
• Global Hotel Chain
• Global Online Entertainment Firm

6. Wreck # 1: Global Financial Institution
Had AEM installed and in production

7. Wreck # 1: Global Financial Institution
Had AEM installed and in production
Needed automated translation transmission

8. Wreck # 1: Global Financial Institution
Had AEM installed and in production
Needed automated translation transmission
Existing workflow didn’t respect translation, site not built for n-langs

9. Wreck # 1: Global Financial Institution
Had AEM installed and in production
Needed automated translation transmission
Existing workflow didn’t respect translation, site not built for n-langs
Custom workflow created and added, let’s just call it a hack

10. Wreck # 1: Global Financial Institution
Had AEM installed and in production
Needed automated translation transmission
Existing workflow didn’t respect translation, site not built for n-langs
Custom workflow created and added
Had to spend $$ on custom development at last minute, project
launch date missed

11. Key Take-aways (don’t leave ‘em here!)
Repeat Retrofitting
Plan for Languages FIRST
Consider workflow
Survey your systems for
language support
Avoid
Workflow w/o Language
Leaving your tech folks out
of the loop
Leaving language till the end

12. Wreck # 2 Global Hotel Chain
Greenfield AEM installation

13. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components

14. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components
Wanted to federate content and loc control to regional properties

15. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components
Wanted to federate content and loc control to regional properties
Reduced the AEM Multilingual implementation budget

16. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components
Wanted to federate content and loc control to regional properties
Reduced the AEM Multilingual implementation budget
Budget cuts meant NO mapping of components for translation, no federation

17. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components
Wanted to federate content and loc control to regional properties
Reduced the AEM Multilingual implementation budget
Budget cuts meant NO mapping of components for translation, no federation
ALL content sent for translation, split-focus of resources, delays, translation cost increases

18. Wreck # 2 Global Hotel Chain
Greenfield AEM installation
Working with multiple translation providers, lots of complex components
Wanted to federate content and loc control to regional properties
Reduced the AEM Multilingual implementation budget
Budget cuts meant NO mapping of components for translation, no federation
ALL content sent for translation, split-focus of resources, delays, translation cost increases
Totally TCO is actually now HIGHER due to cost-saving attempts

19. Key Take-aways
Repeat Retrofitting
BUDGET for Localization
Assign funding for Loc
Ensure $$ for translation
Avoid
Split focus resources
Underfunding Loc
Cutting corners on
efficiency efforts

20. Why are we doing this again?
To avoid this…

21. Wreck # 3: Global Online Gaming Firm
Greenfield AEM implementation

22. Wreck # 3: Global Online Gaming Firm
Greenfield AEM implementation
Tight timeline and needed data encryption

23. Wreck # 3: Global Online Gaming Firm
Greenfield AEM implementation
Tight timeline and needed data encryption
Encryption requirement cropped up mid-project

24. Wreck # 3: Global Online Gaming Firm
Greenfield AEM implementation
Tight timeline and needed data encryption
Encryption requirement cropped up mid-project
Business and Technology sides not aligned

25. Wreck # 3: Global Online Gaming Firm
Greenfield AEM implementation
Tight timeline and needed data encryption
Encryption requirement cropped up mid-project
Business and Technology sides not aligned
Project was delayed by four months

26. Key Take-aways
Repeat Retrofitting
Build in “surprise” time
Align Biz and Tech
Small not always good
Avoid
Surprises
Not including all groups
Leaving “paperwork” till late

27. Staying on the multilingual rails
Grabber

28. I’m awake – what’d he say?
Plan with Loc in mind

29. I’m awake – what’d he say?
Plan with Loc in mind
Put $$ behind it

30. I’m awake – what’d he say?
Plan with Loc in mind
Put $$ behind it
Align Biz and Tech

31. What?
Questions

32. rkelly@clay-tablet.com
@claytablet
clay-tablet.com
Contacts