When leaders push back on localization time, resources, or AI, the strongest answer is not to defend every step of the process. It is to reframe the conversation around risk.
In this post, I explore why explaining Localization from a quality perspective, with too many process details, may not always be the best strategy when speaking with senior stakeholders.
This post explores the key differences between working on the buyer versus the provider side of the localization industry. While there are some tasks common to both, others vary significantly in areas such as people management, operations, strategy, and metrics. The article breaks these tasks into four categories, providing examples for each to highlight these distinctions
LLMs don’t learn your brand style just because you use them more. They improve when someone guides them, feeds them with examples, corrects them, and owns the outcome. In this blog post I reflect on how we can create a strategy to do that
Several factors affect the duration of localization for a digital product, including translators' availability and the technology setup level. This blog post explores the various elements that impact the amount of time needed for product localization.
In some RFPs today, it is no longer so clear what buyers really value from LSPs. This post explores why. Based on my experience on the buyer side, I share why the real need may be shifting from pure execution toward something harder to explain, but often more useful in practice.
What do you do when someone asks for the ROI of localization and you know the question is too narrow from the start? In this post, I reflect on why I stopped trying to prove isolated ownership and started talking more honestly about contribution.
Reading The Myths of Happiness reminded me of the arrival fallacy: the belief that once we reach a certain goal, everything will finally feel solved. In localization, that can look like waiting for the day when people will finally understand what we do. But organizations keep changing, so that moment may never fully come. And maybe accepting that is exactly what helps us stay grounded, avoid frustration, and keep moving forward.
In many companies, the localization budget does not sit with the localization team. At first, that may seem like a small detail. But over time, it changes how localization influences strategy
Defining localization metrics is relatively easy. In many cases, a team can write a reasonable list during a workshop, like the ones I mentioned above, or during a strategy session. The conceptual part of what to track and why rarely takes long. The real difficulty appears later: HOW you actually obtain those metrics.
“Welcome to my blog. The space where I document my passion about Localization, Project Management and Leadership”
Making your way as a localization professional in the video game industry might be tricky at the beginning. But it's obviously not impossible! In this post, I share 7 ideas so that all those who want to work localizing, testing, or managing video games will know where to start.
Is there anything more human than language?
Is there anything more user-centric than giving the user the product in their native language?
There is a better way to approach it, and that way is to understand that Localization is User Experience.
And in this post, I explain why (and how to do it!)
Can generic MT engines be used for business?
MT has come a long way in the last few years, but there is still a long way to go for stakeholders who are not very familiar with this technology to understand if the valid option for their global expansion is to use a generic MT engine or if a custom mt is what is needed.
In the second part of the LQA design post, I explain to you how to make LQA part of the design process
Building a digital product is an iterative process that includes several phases. Different localization activities to a greater or lesser extent are carried out throughout the different phases. One of these activities is Localization QA (LQA). LQA is traditionally done in the deployment phase; however, it is too late in most cases.
Much has been written and talked about the ROI of Localization and the reality is that localization activities by themselves do not generate a profit.
In this post, I analyze the different phases necessary to develop software. At the top, we can find a summary of the typical tasks/deliverables that the Product Development team performs. In the bottom part, we can find the different Globalization activities needed to create a digital product Global ready from the beginning. They are executed in parallel. Working side by side. Not as an afterthought
The role of the Internationalization engineer is one of the most unknown and complicated jobs in the #localization industry, and yet it is one of the most important because thanks to their work, they contribute to making the localization phase more accessible.
For those of you who like programming, technology and are interested in languages, specializing in this area can be an excellent option to build a promising future, as it is a role in high demand.
Culture Fit can lead to misunderstandings if it is not explained well because it can be interpreted as only hiring similar people. That's why I believe that better than Culture Fit is to embrace a Culture Sum mindset.
Culture Sum is all about understanding that people who are different can achieve great things together by relying on shared values.
Localization ROI has never seemed to me a good metric to measure the impact of a Localization team. However, Sentiment Analysis feedback can give more clues about how the work of a Globalization professional contributes to the success of your product.
A big part of the customer-centric experience is related to the language, culture, the localized price per market, and payment methods
A company that really wants to reach a diverse audience has a potent weapon through hyper localization.
Some tips to create Global content ready when creating content
What skills should we develop as a localization/globalization professional if we want to go further?
Have you ever wondered how someone fills their time when they work in a Localization team but don't translate anything?
Here is a braindump of factors that I can think of that affect the perception that a localization project is cheap or expensive!
Why do we translate into some languages and not others, and who decides this? This is a question for which we must have a ready answer. This post explores possible answers to this question.
Nowadays, the software has reached a very high level of complexity and it is necessary to have localization tools that allow us to keep up with it.
Without the right tool, without the right connectors, your localization strategy will remain stagnant, and the perception that has accompanied the localization industry since time immemorial as a "painful and slow" process will not be mitigated. A good TMS may be the component you need to give the visibility your localization team deserves.A good TMS may enable you to offer an end-to-end solution
One of the main obstacles that localization industry professionals often face is the lack of internal visibility of our work or the impact on its bottom line. and the truth is that QBRs is an excellent tool to add to your arsenal of Localization tools/processes that can help you to Strengthen the partnership, Foster relationships and Highlight localization team's impact across your organization
Content is an exciting topic since content drives the customer journey, and good localized content drives the Global customer journey! In this post, I delve into the different phases and the strategy required to design a Globalization content customer journey.
Involving Localization team in Playtest might be a great idea! Find out here why ☺️
AI promises faster localization, and that message is attractive. But in many teams, the real issue is not speed. The work gets delivered. The harder question is how much hidden coordination, unclear ownership, and workflow complexity it takes to get there.