INSIGHTS FOR REVENUE LEADERSPublished by Consilegy ↗

Organization & adoption

Why Your Japan Team Ignores KPIs: Translate Them to Actions

Why Your Japan Team Ignores KPIs: Translate Them to Actions

HQ sends the Japan team a KPI sheet, asks them to review it every week, and sees no change in behaviour. The usual reading is a motivation problem.

More often it is a translation problem: the team looks at the number and cannot say what they would do differently tomorrow.

Typical signs: the monthly attainment figure is first opened the day before the report is due, a hit target cannot be explained by anyone, and the next month starts without a decision on what to do next.

A number with no next action gives people no reason to open it

Survey data on how dashboards are actually used points the same way.

In a survey by Keywalker (fielded 8 to 10 October 2025, n=1,034 sales managers and field staff at Japanese companies that had adopted SFA, CRM or BI tools, run as an online panel survey), 58.2% of managers said they use the dashboard to check figures in sales meetings, and 15.4% said they use it to decide the next action.

Among field staff the split was 48.6% and 20.7%. In the same survey, the top motivator for entering data was “the purpose and use of the data is clear”, at 54.8%.

The sponsor sells BI implementation support, so read the percentages as orders of magnitude.

A dashboard is opened to confirm, and rarely to decide. If your Japan KPI list is built the same way, it will be reviewed and not acted on.

What HQ wants to observe is not what the field can move

Monthly revenue attainment is a number for observing the business. A Japanese sales rep who opens it learns nothing about tomorrow.

Translate it into “new first meetings booked this week” or “follow-up sent within three days of a proposal”, and the rep can answer the question without being coached.

One caution. “New first meetings booked this week” comes out of a standard report in most CRMs.

“Follow-up within three days of a proposal” does not, unless the system can compute the gap between the date a deal reached the proposal stage and the date of the next activity. Whether that needs extra date fields or an automation depends on your CRM and its configuration.

If the CRM cannot produce the translated number, either rephrase it into one it can, or build the mechanism first. A number someone has to count by hand every week does not survive long.

One question to run over the whole list

Pick one KPI and ask: “If the Japan manager looks at this, can they say what the team should do tomorrow?” If not, it is an observation metric. HQ may need it, but it should not be on the field’s list.

Check the cause-and-effect with the Japan team, not for them

Once a metric is translated, the logic behind it has to be shared. If the manager alone decides that faster follow-up moves deals, and the team does not believe it, the number becomes another reporting item. Working through the link together is what builds trust in the metric.

This does not need a new meeting. In the weekly sales meeting where the metric is chosen, state in one line which outcome number should move if the team does this.

A few weeks later, in the same meeting, put the action number and the outcome number side by side. If the action went up and the outcome did not, the translation was wrong, so translate again.

The trap to watch for: an action metric loses its substance once it becomes a target. Chase “follow-up within three days” and the number fills with empty check-in emails.

Keeping it next to the outcome number is how you notice. An action metric works as a signal only while you keep checking its link to the result.

A metric with no owner and no review date comes back even after you cut it

Last, name who looks at each remaining number, and when, and what they decide from it. A metric without that is formalised and then ignored, however carefully it was designed. “Someone will look” means no one will.

Keep only the metrics that pass all three tests: translatable into tomorrow’s action, agreed with the team, and owned with a review date. Retire the rest, and say where each retired metric goes, otherwise it returns to the agenda at quarter end.

Cutting is harder than adding. But a short list is what turns KPIs from a report HQ reads into a compass the Japan team uses.

Open your current list and run the question over it. The first number that stumps you is where to start.

The wider view is in Japan Market GTM and Messaging.

If cutting the list raises the question of where the dropped metrics should go, see assign owners to the metrics you drop.

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