The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
*Japanese version follows English below. / 日本語は英語の後に続きます。
Why do Japanese companies struggle with true digital transformation despite importing global best practices for 30+ years?
As an industrial translator with 35 years of experience in IT localization, here is my insight, inspired by economic analyst Keiichi Kaya's recent perspective.
Over the past three decades, translators have localized countless global software solutions and ERP (Enterprise Resource Planning) systems into Japanese. However, Japanese industry has struggled to reap the full benefits of Business Process Reengineering (BPR).
Why? Because of an obsession with "Hardware Mindset."
As Keiichi Kaya points out in his book: ・Hardware Approach: Trying to fix every flaw physically through precision manufacturing leads to astronomical complexity and costs. ・Software Approach: Accepting physical variance and absorbing/correcting it flexibly via software algorithms allows for lower costs and rapid adaptability.
Japan excels at perfecting physical hardware. However, when adopting global software, companies forced the software to bend to their legacy, hardware-oriented workflows through excessive customization. They tried to run a modern, software-driven architecture with an old "craftsmanship/zero-defect" mindset.
True transformation requires shifting from "over-engineering hardware" to "embracing software flexibility." Language is no longer the barrier—the real challenge lies in updating our organizational mindset.
What are your thoughts on shifting from a hardware-centric culture to software-driven agility?
【日本語版】
なぜ日本企業は、30年以上もグローバルのベストプラクティスを輸入し続けているにもかかわらず、真のDX（デジタルトランスフォーメーション）に苦戦しているのでしょうか？
ITローカリゼーションに36年間携わってきた産業翻訳者の視点と、経済評論家・加谷珪一氏の提示する知見を交えて考察します。
この30年間、私たち翻訳者は膨大なグローバル・ソフトウェアやERP（企業資源計画）を日本語化してきました。しかし、日本の産業界はBPR（業務プロセス再構築）の恩恵を十分に享受できていません。
その根底にあるのが「ハードウェア（Hardware）至上主義マインド」の壁です。
加谷珪一氏も著書で指摘している通り：
・ハードウェア的アプローチ： 部品同士の精密な噛み合わせや極限の品質調整で対応しようとすると、膨大なコストと複雑化が生じる。
・ソフトウェア的アプローチ： 物理的な誤差やゆらぎを前提とし、それをソフトウェアの制御で柔軟に補正することで、低コストで迅速に対応する。
日本は「完璧なハード（物理製品）をつくり込む」ことに長けています。しかし、グローバルなソフトウェアを導入する際にも、その「完璧主義・従来の現場のやり方」にこだわり、ソフトウェア側を過剰にカスタマイズして元に戻してしまいました。
真の変革には、「ハード至上主義・減点回避マインド」から「ソフトウェア主導の柔軟性・標準化」へのパラダイムシフトが不可欠です。もはや言語の壁はありません。真の課題は、組織マインドセットの更新にあります。
ハード中心の文化からソフトウェア主導のアプローチへ脱却することについて、皆様はどうお考えになりますでしょうか？
※本考察におけるハード／ソフトのアプローチ比較や日本のITD（Information Technology Deficit／情報技術赤字）の背景については、加谷珪一氏の著書『縮小ニッポンの再興戦略』（マガジンハウス新書）における分析を参考にしています。
#Localization #Translation #ERP #SAP #BPR #BestPractice #DigitalTransformation #ITLocalization #産業翻訳 #ローカリゼーション
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
A year ago, I moved from our i18n team at Canva, where I led and supported template campaigns built around cultural insights, local context, and the nuances of how people celebrate, communicate, and create across different locales.
Now, on Growth, my design team's starting point looks different. We work mainly from SEO data, search behavior, and signals around what people are actively looking for 👀
Different insight. Different source. Same creative process: find the signal, ground it in real-world research, understand the person behind it, and turn that understanding into something useful, relevant, and worth creating.
It’s honestly been interesting to see how changing the input can change the output, while the fundamentals of good design stay surprisingly the same.
Here’s a look at what my team has been making so far this year! ✨
________________________
Disclaimer: Performance metrics shown are illustrative and for presentation purposes only
The construction of a water treatment plant in Bogotá, Colombia, was one of my proudest moments. I had the privilege of working with a multicultural team of engineers, India, Colombia, and the USA. Clear and concise communication between the engineers, the construction crew of 55 workers, and the general manager of the factory was a must. I confronted a few challenges and hurdles, but I was able to overcome them and complete the job of helping to build a water treatment plant and bring it online.
I was part of the team responsible for the construction and implementation of the water treatment plant. My role went beyond translation. I served as the communication and documentation bridge between the engineers, supervisors, and field workers, translating technical instructions, documenting processes, transcribing information, and helping ensure that the engineering decisions made at the technical level were correctly understood and implemented in the field.
I was involved throughout the project, from the initial ground work and construction stages through installation, testing, commissioning, and bringing the plant into operation.
My Role and How I Worked
Because the project involved professionals with different technical backgrounds, languages, and ways of communicating, one of my most important responsibilities was making sure that information moved accurately between the engineering team and the construction crew.
I translated technical instructions and conversations between English and Spanish, while also helping communicate decisions from the engineers to the workers in a clear and practical way. I documented and transcribed important information throughout the process so that decisions, changes, instructions, and progress could be tracked.
My approach was to make complex technical information understandable without losing its meaning. I learned to identify when a direct translation was not enough and when an engineering concept needed to be explained in practical terms so that the field team could execute it correctly.
I also paid close attention to communication between the three engineers. When differences in interpretation or technical approach appeared, I helped clarify the information and ensure that everyone was working from the same understanding.
The Process
The project required continuous coordination between engineering decisions and field execution.
I participated in the communication and documentation process from the early stages of construction, including:
Initial ground and site work
Communication of engineering instructions to the construction crew
Documentation and transcription of technical information
Coordination between the Colombian, Indian, and U.S. engineering teams
Translation of technical discussions and field instructions
Communication of changes and decisions during construction
Support during equipment installation and system implementation
Testing and troubleshooting.
Final preparation and commissioning of the treatment plant
Supporting the transition from construction to an operational system
Throughout the project, I worked to make sure that information was not lost between the people designing the system and the people physically building it.
Challenges
One of the greatest challenges was working across different languages, cultures, technical backgrounds, and communication styles.
The engineering team came from three different countries, while the majority of the construction workforce was Colombian. Technical terminology could sometimes create misunderstandings, particularly when an engineer explained a concept in English and the field crew needed to understand exactly how that concept should be applied in practice.
Another challenge was that construction rarely follows a perfectly predictable path. Unexpected problems, changes in decisions, adjustments to procedures, and field conditions required the team to adapt quickly.
My response was to remain organized, ask questions when something was unclear, verify information before communicating it to the crew, and document important decisions. Rather than simply translating words, I focused on translating the meaning, intention, and technical requirements behind those words.
What I Learned
This project taught me that successful engineering projects depend not only on technical knowledge, but also on communication, documentation, adaptability, and teamwork.
I developed a deeper understanding of how engineering decisions become physical systems and how important it is to maintain a clear connection between design, instruction, construction, and operation.
I also learned how to work under pressure, manage information from multiple sources, communicate with people at very different levels of technical expertise, and adapt my communication style to different cultures and professional environments.
Successes
One of my greatest achievements was helping create a reliable communication process between three international engineers and a 55-person Colombian workforce.
By maintaining clear communication and documentation, I helped reduce misunderstandings and ensured that important instructions and decisions could be communicated effectively throughout the construction process.
The most rewarding part of the project was seeing the process move from plans, conversations, and technical decisions into a functioning water treatment plant.
I was able to contribute from the ground up—not only as a translator, but as a communicator, documenter, coordinator, and link between the technical and operational sides of the project.
Professional Reflection
This experience changed the way I understand my own role in a technical project. I discovered that translation can be much more than converting one language into another. In a complex international project, effective translation requires understanding people, processes, technical concepts, priorities, and the consequences of a misunderstanding.
My contribution was to help turn technical knowledge into clear action and to make sure that communication continued flowing between the people who designed the system and the people who built it.
The water treatment plant became the physical result of that collaboration. My role was to help make the collaboration possible.
𝗜 𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗘𝗻𝗷𝗼𝘆 𝘁𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝗡𝗼𝗯𝗼𝗱𝘆 𝗪𝗮𝗻𝘁𝘀 𝘁𝗼 𝗧𝗼𝘂𝗰𝗵.
Broken forms.
Strange mobile layouts.
Plugin conflicts.
A website that suddenly stopped working.
A page that looks perfect on one device and terrible on another.
A third-party integration that refuses to cooperate.
These aren't necessarily the glamorous parts of web development.
But they're some of the problems I enjoy solving most.
Because there's usually a moment when everything feels confusing.
Then you start isolating the variables.
Check the code.
Check the browser.
Check the plugin.
Check the console.
Check the settings.
Test again.
And eventually...
You find it.
That moment is addictive.
It's one of the reasons I enjoy development beyond simply designing pages.
I like figuring out why something isn't working.
Then making it work properly.
What is one frustrating technical problem you've spent way too long trying to solve?
Contra's own post editor got me with this once: it swallowed the first keystroke after I clicked into it, and nothing failed loudly. Now I type one word, read the field back, then add the rest.