Change management
Rollout in Japan is usually treated as a training problem, so it gets a manual, a kickoff session, and a support address. Three months later usage has settled at whatever the weekly meeting actually requires.
This category covers what moves that number: changing the meeting rather than the manual, choosing an owner by authority rather than product knowledge, measuring adoption with something other than logins, and the follow-up that decides the outcome in the first fortnight.
9 articles
Your review cadence sets how long Japan waits for answers
Adoption in the Japan entity stalls, so HQ adds an executive sponsor and puts Japan on the monthly regional review. Nothing moves. The backlog in Japan is not work, it is decisions a local manager cannot make alone and that do not qualify for a formal approval route. Japanese survey data (n=1,034, n=312) and how to set the cadence.
When your Japan team asks to go back to the spreadsheet, answer with a date
A month after the global rollout, the Japan entity asks to go back to its old spreadsheet. HQ hears resistance, or a local exception request, and answers yes or no. Neither answer makes the request go away. It moves to a file HQ never sees, while the Japan adoption dashboard stays green. Japanese survey data (n=101, n=1,034) and what the request is actually reporting.
Bring your Japan team in while one decision is still open
HQ finalises the global rollout, then runs a feedback session with the Japan entity. Nobody objects, so HQ records agreement, and three weeks after go-live the adoption numbers say otherwise. Silence in that room is not consent. It is what happens when a team is invited to comment on something they cannot change. Japanese survey data (n=101, n=1,034, n=312) and the three decisions worth handing over.
Japan's parallel run has an end date but no end condition
HQ rolls the global CRM out to the Japan entity and grants a three-month parallel run with the local spreadsheet. Three months later the request is for an extension, and a year later Japan's number still arrives by email. The parallel run does not end because nobody wrote down what would end it. Japanese survey data (n=1,545, n=305) and the four steps that actually close a legacy system in a Japan entity.
Silence after your Japan go-live is not adoption. It is the first warning
HQ ships the CRM to the Japan team, the project closes at go-live, and no support tickets come in. A quarter later the Japan pipeline data is empty. In Japan, zero questions rarely means success. What to do in the first two weeks after go-live instead of waiting for tickets.
Who should own your Japan CRM rollout (not the power user)
HQ asks the Japan entity to nominate a local CRM owner, and the nomination goes to whoever is most comfortable with the system. Six months later Japan has the worst data of any region. The constraint is not skill. It is that the ops function HQ assumes exists does not exist locally, and admin rights are not the lever in a Japan entity.
Your Japan adoption number is green because it counts logins, not decisions
HQ sees Japan at 90%+ weekly active users and calls the rollout a success, while the regional forecast still has to be collected verbally. Login and active-user metrics count the screen being opened, not what was decided from it. Here is what to measure instead in a Japan entity.
Your Japan team will not read the guide. Change the weekly meeting
When the Japan team stops updating the CRM, HQ ships a localised guide and another training session. Adoption does not move, because nothing in the local week depends on the record. Here is the change that does work: rebuild the agenda of the meetings that already exist so they can only be built from the CRM.
Why your Japan team won't log data: the CRM design returns nothing to them
Global SaaS teams often blame low adoption in Japan on discipline or training. The real reason your Japan reps don't log data is that the CRM returns nothing to the person entering it. Fix the return first, not the friction.
Frequently asked
- Can we appoint a dedicated Japan owner for the rollout?
- Usually not, so design for that from the start. IPA's DX White Paper 2023, a public-sector study run to the same design in Japan and the US, found that only 10.9% of Japanese companies considered their digital transformation staffing sufficient, against 73.4% in the US. The real question is which existing person takes it on alongside their job, and whether that person can set the agenda of the meeting where the data is used.
- Is login rate a reasonable adoption metric?
- No. Logins measure compliance with a reminder. Measure the records that a decision was actually made from, which is the only definition that fails loudly when adoption slips.
- Should we involve the sceptics on the Japan team early?
- Timing is the wrong variable. Invite them while at least one decision is still theirs to make, such as two of the mandatory fields, when data gets entered, or which meeting the numbers appear in. Asked to comment on a design that is visibly already approved, a Japanese team will usually go quiet rather than object, and HQ will record that silence as alignment until the adoption numbers say otherwise.
- Our Japan team says they prefer the old process. Is that cultural resistance?
- Rarely. It is usually a correct observation that the new process costs them time and returns nothing they can use. Treat it as design feedback and find out which meeting still runs on the old artefact, because that meeting is what keeps the old process alive.