evolve'14 | maximize | robinson kelly | multilingual localization

42

2,300,000,000

60

Staying on the multilingual rails

42 Ave # of langs a global firm translates into

2,300,000,000

60



2,300,000,000# of Internet users who don’t speak English as their decision making language

60



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


Three cautionary Tales…

• Global Banking Institution

• Global Hotel Chain

• Global Online Entertainment Firm


Had AEM installed and in production

Wreck # 1: Global Financial Institution


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





Custom workflow created and added

Had to spend $$ on custom development at last minute, project launch date missed


Key Take-aways (don’t leave ‘em here!)

Plan for Languages FIRST

Consider workflow

Survey your systems for language support

Repeat Retrofitting

Workflow w/o Language

Leaving your tech folks out of the loop

Leaving language till the end

Avoid

Greenfield AEM installation

Wreck # 2 Global Hotel Chain


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







ALL content sent for translation, split-focus of resources, delays, translation cost increases

Totally TCO is actually now HIGHER due to cost-saving attempts


Key Take-aways

BUDGET for Localization

Assign funding for Loc

Ensure $$ for translation

Repeat Retrofitting

Split focus resources

Underfunding Loc

Cutting corners on efficiency efforts

Avoid

To avoid this…

Why are we doing this again?

Greenfield AEM implementation

Wreck # 3: Global Online Gaming Firm


Tight timeline and needed data encryption




Encryption requirement cropped up mid-project





Business and Technology sides not aligned





Business and Technology sides not aligned

Project was delayed by four months


Key Take-aways

Build in “surprise” time

Align Biz and Tech

Small not always good

Repeat Retrofitting

Surprises

Not including all groups

Leaving “paperwork” till late

Avoid

Grabber


Plan with Loc in mind

I’m awake – what’d he say?


Put $$ behind it



Put $$ behind it

Align Biz and Tech


What?

Questions

[email protected]

@claytablet

clay-tablet.com

Contacts