Curated for content, computing, and digital experience professionals


Aging: Web Years Are Worse Than Dog Years

This was one of my favorite quotes from Sun’s April 10th presentation at Gilbane San Francisco, titled Managing Content Globally: What Works, What Doesn’t. Given by Jed Michnowicz, Engineering Lead, and Youngmin Radochonski, Globalization Program Manager, the presentation opened the LISA Forum on Day 1 of the conference.

Jed and Youngmin nailed it when they defined three key components of a global content platform: content management, translation, and delivery. As they outlined the struggles of legacy challenges in all three areas, a pattern of checklist items for the audience quickly surfaced. Lack of metadata. “Siloed” mindsets, workflow, and content repositories. Static Web server content delivery. Inconsistent messaging. Slow time to market. Cost overruns. As moderator, it is always interesting to scan the faces in the crowd for reactions. During this part of the presentation the response was palpable: “got that, got that, and yes, definitely got that.”

They also nailed it when they moved to the “here’s the good news” part of the presentation. Global awareness throughout the organization. Process alignment and consistency. Separation of content from presentation. Translation memory management and sharing. Integrated content and translation workflows. Automated, Web services-based content distribution. They described what is most definitely a “Level 2+” integration from a technology perspective. At this point, the audience response was equally palpable: “want that, want that, and yes, definitely want that.”

Wrapping up the success story with lessons learned (according to people, process, and technology categories; be still my heart!) Jed and Youngmin also noted that Sun, like most organizations, is still learning. Some of the questions they posed — which we will continue to explore on this blog — included:

  • What takes precedence when solving for people, process and technology?
  • What is the proper globalization strategy and who defines it?
  • Can a single solution work for everyone?

On behalf of The Gilbane Group and LISA, we thank these excellent presenters for a job well done. This presentation will be available here this week; check out one of my other favorite quotes emblazoned on the t-shirt on the last slide.

Going to Beijing?

If so…

The LISA Forum Asia in Beijing on March 12-15 will focus on buyers/end-users of globalization services. Entitled “The Globalization of China 2.0,” the program features some of China’s international expansion leaders alongside high-tech multinationals such as Microsoft, Huawei, Cisco Systems, Nokia, Adobe Systems, TIBCO Software and IBM.

The program includes sessions such as “The Basics of Going Global: Understanding Globalization, Internationalization, Localization and Translation,” “Buying and Implementing Content Management and Global Translation Management Systems,” and “How to Run a Globalization Audit of Your Business Processes.” Register here.

For those of you not going to Beijing, note that the LISA Forum’s highly-popular globalization audit session will also run at Gilbane San Francisco on Tuesday April 10th during pre-conference tutorials.

Lots of Globalization and localization activity this week

Underscoring the increasing interest in globalization and localization among our audience of content and web professionals are three items this week. Today we announced that the the LISA (Localization Industry Standards Association) Forum will co-locate with the Gilbane conferences starting with Gilbane San Francisco April 10- 12, 2007. Last Friday, Kaija Poysti, introduced herself as our new guest blogger covering translation and localization issues (in her post, she doesn’t actually propose it, but she does point us to some reasons why we should just all speak Finnish). And, this coming Wednesday, we co-host a case-study webinar on how Sun has built a a global customer experience with their online content and branding.

© 2020 The Gilbane Advisor

Theme by Anders NorenUp ↑