{"id":105,"date":"2019-11-21T09:42:34","date_gmt":"2019-11-21T09:42:34","guid":{"rendered":"http:\/\/trends.memoq.com\/?page_id=105"},"modified":"2020-01-13T14:10:16","modified_gmt":"2020-01-13T14:10:16","slug":"convergence-connectivity","status":"publish","type":"page","link":"https:\/\/trends.memoq.com\/convergence-connectivity\/","title":{"rendered":"Convergence & connectivity"},"content":{"rendered":"\n

The way we do business is changing. We are in a race to provide faster time-to-market, and to speed up and streamline processes. It is inevitable that we will choose solutions that are comprehensive but not complex, that can deliver more but require less.<\/p>\n

 <\/p>\n

Convergence therefore is an obvious answer to the challenges that face us. But will convergence be something that we should watch out for this year? Some of our colleagues seem to think so.<\/p>\n

 <\/p>\n

Streamlining processes, making things happen faster, closing all gaps \u2013 just a few perks CMS-to-CAT connections can deliver. Connectors have been on the rise in the past couple of years and it seems that we cannot live without them. Or can we? Are connectors the right answer for everybody?<\/p>\n

\n\t\tConvergence: connecting systems in single environments\n\t<\/h3>\n\t\t\t\t\"Norbi-wb\"\n\t

Norbert Oroszi<\/strong><\/p>\n

CEO at memoQ<\/p>\n\t\t\t\t\"Gonzalo-wb\"\n\t

Gonzalo Fern\u00e1ndez<\/strong><\/p>\n

Digital Marketing Manager at memoQ<\/p>\n\t\t\t\t\"Lukasz-wb\"\n\t

\u0141ukasz Rejter<\/strong><\/p>\n

Account Executive at memoQ<\/p>\n\t

The intricate processes surrounding the translation\/localization workflow and the need for multiple input can be sources of distraction not only for professionals, but for their clients as well. Norbert Oroszi, CEO at memoQ; Gonzalo Fernandez, Digital Marketing Manager; and \u0141ukasz Rejter, Account Executive, were thinking of the same trend: these issues can be tackled by none other but convergence.<\/strong><\/p>\n

 <\/p>\n

As demand is getting more and more complex, systems managing various processes are offering more and more features, making things ever more complex for ordinary users. This is especially true for the translation\/localization industry: to serve customers better we need more and more supporting tools, features and procedures to be incorporated in the workflow.<\/p>\n

 <\/p>\n

Clients, however, see things differently. Business and content owners<\/strong> are pressed to achieve rapid time-to-market<\/strong> \u2013 and that represents a curious cognitive dissonance. How can you achieve cutting delivery times when ordering a service is getting ever more complicated? How can you shorten TTMs if complexity rules? Since short TTMs are key, it is understandable that client demand is essentially simple<\/strong>: translate! localize! \u2013 and do it effectively, efficiently and fast. From a client\u2019s perspective,<\/strong> ideally, ordering should be as easy as clicking a button<\/strong>.<\/p>\n\t

\n\t\t
” Clients, by default, do not really care about files, formats, structures, and workflow characteristics \u2013 they only deal with these because and when they absolutely must. From their perspective they have a text, a string, a file, an application or a site to be localized \u2013 and they expect it to happen.”<\/header>\n\t\t\t\t\t