Run Your Japan Sales Review on One Won Deal and One Lost Deal
The monthly Japan pipeline review runs on schedule. The slides are clean, everyone has seen the bookings and the stage counts, and the next month starts exactly like the last one.
The usual diagnosis is that the team is passive or the data is thin.
More often the meeting opens with the whole table, so nobody ever gets to the reasons. The fix is to open single deals instead.
But opening one sales deal in front of the team is heavier than opening one marketing asset, and the format has to account for that.
A table invites confirmation, not explanation
Put last month’s bookings, deal counts and stage totals on screen and everyone nods at the same figures. Agreement is easy at that level.
The reasons are not on the screen, though, so someone has to volunteer a hypothesis, and in a Japanese team that is often a senior person who would rather not guess in public. If no one does, the meeting runs out on confirmation.
Survey data on how review screens are used points the same way.
In a survey by Keywalker (fielded in October 2025, n=1,034 sales managers and field staff at Japanese companies that had adopted SFA, CRM or BI tools, online panel), 58.2% of managers used the dashboard to check figures in sales meetings, against 15.4% who used it to decide the next action. The sponsor sells BI implementation support, so read the percentages as orders of magnitude.
One case at a time gives the room something to talk about
We use this format ourselves, on our own monthly review of LinkedIn posts. Five minutes to scan all the figures, with no discussion. Ten minutes on one post that did well. Ten minutes on one that did poorly. Five minutes to decide what changes next month.
A single case is concrete. Nobody has an opinion on “the average moved”, but everyone has something to say about why one item worked. The reasons that were invisible in the table appear once one item is open.
A sales review is a different setting. Posts are numerous and no single post decides anyone’s evaluation. A won or lost deal is a rep’s result, by name.
Carry the format over unchanged and the won deal becomes a victory lap and the lost deal becomes a public trial. Three things need to change first.
Three changes before you run it on deals
1. Pick the case likely to recur, not the extreme
The largest win and the most painful loss are easy to pick and heavily shaped by chance. A change built on a one-off deal will not repeat next month, and when the figures drift back toward normal, the team will misread that as the change failing.
The selection rule is: how many deals of the same shape are still in the pipeline? A win whose industry, company size or source matches other open deals. A loss whose stopping point matches other stalled deals. Choose cases whose reasons can be applied to next month’s pipeline.
2. Examine the sequence, not the rep
Tell the rep the day before which deal will be opened. Naming someone cold in the meeting puts them on the defensive before they explain anything.
The question is not “what did you do?” but “at what point, and what happened on the buyer’s side?” Lay out the dates the CRM already holds, first meeting, proposal, quote, the buyer’s internal approval, and look together at where the deal moved and where it stopped.
Keep target pressure out of this meeting. Once it mixes in, nobody volunteers a lost deal again.
In a Japan team that reports to HQ, this matters more: the review should feel like analysis the team owns, not an audit HQ runs.
3. After the reason, always ask what happens next time
For the win: when did the buyer’s organisation start to move, and can that be created again? For the loss: where did it stop, and what will we do the next time the same signal appears? Reasons without the second question turn into commentary.
If every lost deal comes back as “price”, fix the loss reason options before fixing the meeting. That is covered in When Japan’s lost deals are all recorded as “price”.
Leave with one or two changes
The output is one or two changes, at the level of “after a first meeting without the decision maker, ask how the approval will be routed” or “send a case study from a company of the same size before the proposal”. More than two and nobody can tell next month which one worked.
Close with a read-back of the two deals, the reasons, and the change, and record the reasons on the deal records in the CRM, not only in the minutes. The next meeting opens by checking that change first.
For a Japan team reporting to HQ, this also gives the team a position it can defend. A change tied to one named pattern is easier to approve than a general promise to “improve conversion”.
Reasons that are written down can travel
Putting reasons into words is not only for the meeting’s own decision. Once reasons exist as words, they can be shared with other teams.
In the “BtoB Marketing Survey 2026” by Fast Marketing, Inc. (fielded May 2026, n=432 sales and marketing staff at B2B companies in Japan, online panel), one question asked how far the outcomes of leads handed from marketing to sales are shared back (Q18).
Companies that shared the reasons for wins and losses reported 82.1% attainment of their win target; companies that shared only whether the lead was followed up reported 54.3%.
Be precise about what this measures. It is about sharing lead outcomes across teams, not about how internal review meetings are run.
The report itself says the figures show correlation, not causation, and the publisher sells B2B marketing strategy support. Companies already doing well may simply have more room to discuss reasons.
What it does support is narrower: reasons can only be shared once someone has put them into words. A review that opens one won deal and one lost deal produces that material every month.
Applying it to your next Japan review
Do not open the table first. Before the meeting, pick one won deal and one lost deal by asking whether deals of the same shape are still open, and tell the reps.
Then check the end of the meeting: does it produce a named change for next month? A review that cannot name one has confirmed the numbers, which a document could have done without calling everyone in.
Do not review the Japan numbers as a table. Open one won deal and one lost deal, choose cases likely to recur rather than the extremes, examine the sequence of events rather than the rep, and end the meeting with one or two changes for next month.
Related reading
If the Japan team’s figures raise the question “is that good or bad?” in every meeting, the fix is to write the threshold first, as described in Before you add another Japan dashboard, write the threshold.
For closing a lost deal with a condition for reopening it, see Add a restart condition to lost deals in Japan.
Other notes on the same problem are collected under Revenue data.