Who should own your Japan CRM rollout (not the power user)

HQ ships the global CRM to the new Japan entity and asks the country manager to nominate a local owner.

The nomination goes to whoever is most comfortable with the system. Usually the youngest account executive, or a contractor who set up the sandbox.

Two quarters later, Japan has the worst data of any region, and the review deck for Japan is still built in a spreadsheet. This is not a skill problem, and a second round of training will not change it.

The ops function you are assuming does not exist locally

HQ’s mental model is a US or EMEA org where a revenue operations hire is available, because that is how the function was staffed at home.

IPA, Japan’s Information-technology Promotion Agency, ran the same questionnaire in both countries for its DX White Paper 2023 (fielded June to July 2022, 543 valid responses in Japan and 386 in the United States, a public-sector survey rather than a vendor one).

Companies answering that they had enough people to drive digital transformation: 10.9% in Japan against 73.4% in the United States.

Read that as a labour-market fact rather than a maturity judgment. The role HQ wants to appoint into is one that most Japanese companies have not been able to staff either, so there is no pool to hire from and no internal precedent to copy.

That changes what the nomination actually is. It is not a nomination. It is a reallocation, and someone has to stop doing something.

Where the function actually sits in Japan

Virtualex Consulting’s domestic RevOps survey (fielded 24 to 26 March 2023, n=9,798, executives and full-time employees aged 20 and over across Japan; the firm sells RevOps services, so treat it as a vendor study) found that in Japan the work is more often carried inside corporate planning or marketing than inside a dedicated revenue-operations team.

Corporate planning, keiei kikaku, is the department that builds the numbers the management meeting reads. Most foreign-owned entities in their first year do not have one, and HQ has no direct equivalent to map it to.

So the closest local analogue to the person HQ is looking for is a function HQ does not recognise and the entity has not hired.

Two things the local owner needs, and one they do not

Agenda ownership of the Japan review. In a Japan entity the monthly review deck is a circulated document. People who never open the CRM read it, and it is where a number becomes real.

Whoever builds that deck decides what data has to exist.

HQ routinely grants admin rights to one person and leaves the agenda with the country manager, which leaves data entry and the meeting agenda under different owners. Agree how those owners will resolve changes.

Written authority to retire fields for the Japan entity. A local owner without written authority will not delete a field that a global team asked for. They will keep it and fill it, and the values will be technically present and analytically worthless.

HQ then reads Japan as low-quality data when Japan is being compliant. The authority has to come from HQ in writing, because the local owner cannot grant it to themselves.

What they do not need is deeper product knowledge. Configuration skill can be supplied from the side, by the system administrator or an implementation partner. Authority cannot be supplied by anyone else, and six months spent with the wrong person costs a large part of the ramp year.

What to do before the next quarter

Name what the person stops doing, in the entity’s plan, by task and by who picks it up. An allocation of twenty percent is not a decision.

Give the same person the agenda of the Japan review, not only the admin seat.

Grant field-retirement rights for the Japan instance in writing, with a quarterly note back to the global CRM owner.

Separate the decision from the deletion: the local owner decides, and the system administrator checks what references the field (reports, workflows, validation rules, integrations with ERP or marketing automation) before removing it. User provisioning and permissions can stay with the administrator.

If your global change process runs on a six-week cycle, exempt the Japan entity for its first four quarters. The entire ramp is four quarters long, and a six-week queue consumes it.

Give the local CRM owner clear authority over the review agenda and operating rules. Separate those responsibilities from administration, and agree how global field changes are approved.

Designing the local operating model, rather than shipping the global one and appointing someone to maintain it, is covered in Japan Market GTM and Messaging.

Related reading

Once the right person owns it, the first thing to change is the meeting rather than the documentation, which is where agenda ownership pays off. That is covered in your Japan team will not read the guide, change the weekly meeting.

Other notes on the same problem are collected under Change management.