Stop us if this sounds familiar: The localization workflow you built around Google Sheets felt smooth at first, but as your projects scaled and the demands on your pipeline intensified, it soon became apparent that something wasn’t right. Should you try and improve Google Sheets with one workaround after the next or swap to a better solution? Follow along with Denis as he details his team’s challenges while working with Google Sheets and why they chose Gridly as a better way to localize.

1. HOW WE HALVED
THE TIME FOR LQA
AND DIDN'T
BREAK ANYTHING
Denis Ivanov
Lead Localization Manager

2. Top-20 grossing
company in EU
acc. to data.ai
2023
Top-20 company by
revenues in EMEA
acc. to data.ai
2021
Solitaire Cruise -
#3 grossing
solitaire, WW
2020
2010
Partnership with
AppLovin
In 2010, two guys
released their
first game
December,
2014
The mobile version
of Clockmaker
is released
Belka Games Today
● full cycle: from prototyping to development
● operations, LiveOps, marketing and analytics
● Clockmaker, Bermuda Adventures, Solitaire Cruise
● 2 more projects in tech launch

3. Is there anything better?

4. If it ain't broke, don't fix it?

5. 4 more reasons why
● you have to constantly duplicate repetitive
phrases by hand
● you have to check the consistency of the
translation
● you have to check history so as not to miss
edits in the source
● you have to check compliance with the
source

6. Consistency is a key
clothes
apparel
garments
turtleneck sweater
sweater
top

7. Who are we? What do we want?
● automation tools
● better access controls
● a custom UI
● a more straightforward way of tracking changes
● translation memory
● built-in glossary
● machine translation
● automatic QA and LQA checks

8. Two months of research…

9. Finally, the one — to localize them all

10. Let’s do some experiments

11. Twenty minutes adventure

12. Gridly’s API integration

13. Planning the flow

14. Pay special attention to training — or meet the consequences

15. Smorgasbord of features
● Branch creation
● Customizable Views in the Grid system
● Screenshots
● A built-in translation memory and
glossary

16. The flow: before and after

17. pros cons
● not quite as fast
● as spreadsheets
● a third-party service
➢ keep the developers out of
the localization process
➢ add in some missing
features from spreadsheets
➢ make the transition as
smooth as possible
➢ reduce the time for LQA
➢ great customer service

18. What exactly helped us to halve the time for LQA
● automatic QA and LQA checks
● customizable views
● screenshots → game story evaluation
● CAT tool integration
● built-in glossary
● translation memory
● less human errors
● less specialists involved

19. Switching to Gridly: in progress

20. Grid

21. Narrative Designer → Localization Manager

22. Localization Manager → Vendor

23. Vendor → Localization Manager

24. Localization Manager → Developer

25. Developer → Localization Manager → Vendor (LQA)

26. Screenshot enlarged
screenshot from the dev build

27. Localization Manager → QA

28. THANK YOU FOR YOUR
ATTENTION!
Denis Ivanov
Lead Localization Manager