Team achievements on a Japanese work history: separate the result from your contribution

Most meaningful work is collaborative. Removing every shared outcome would make the document less accurate. The problem is not using a team result; it is writing the result so the reader cannot tell what you did.

The Japanese Job Card asks candidates to record both their role and contribution. Treat those as separate fields. The team line establishes scale and outcome. The contribution line shows the evidence a future employer can expect you to reproduce.

For each project, record six items: team goal, team result, your formal role, the decision or deliverable you owned, people you depended on, and evidence connected to your work. Evidence may be a shipped component, accepted proposal, reduced error class, faster handoff, or a measured operating change.

Use "we" in your notes for the shared result and "I" for your action. The final Japanese document may omit pronouns, so explicit labels such as "team result" and "responsibility" prevent the grammar from hiding attribution.

Line 1, goal: "Seven-person team rebuilt the order workflow before a regulatory deadline." Line 2, ownership: "Owned the validation service and the cutover checklist." Line 3, collaboration: "Agreed field rules with operations and coordinated contract tests with two upstream teams." Line 4, result: "Team launched on schedule; validation-related manual corrections fell from the measured baseline of 120 to 35 per week."

This structure does not diminish the candidate. It makes the personal signal easier to find: boundary ownership, cross-team coordination, and a result linked to that boundary.

Ask: if your work had been removed, which part of the result would probably have changed? Use that counterfactual only as a thinking tool, not as a made-up percentage. It helps distinguish direct output, enabling work, and general participation.

Revenue, company growth, or a large launch may be too distant from one person's work to claim directly. In that case, state the business outcome for context and use a nearer measure for your contribution: adoption of your workflow, defects in your component, decision time, test coverage, or delivery predictability.

Before: "Led a team that increased conversion by 20%." It does not show team size, leadership scope, experiment ownership, or whether the conversion change can be attributed to the candidate.

After: "In a five-person product team, owned checkout instrumentation and the experiment-readout process. Worked with design and analytics to define guardrails and reject two inconclusive variants. The team's final release coincided with a 20% relative conversion increase during the stated test window; my direct deliverables were the event model, analysis checks, and rollout decision record." Use only a causal claim that the evidence supports.

For an individual-contributor role, foreground technical or functional ownership. For a manager role, include staffing, delegation, decision quality, and how the team operated without turning every output into the manager's personal achievement. For a cross-functional role, name the interfaces and the disagreement you helped resolve.

Keep the same factual core in the 職務経歴書, self-promotion section, and interview answer. Change the length, not the ownership story. A final resume-match review should confirm that the evidence answers the target requirement rather than merely sounding large. Read the finished bullet once as a hiring manager: the shared result, your work, and the boundary of your claim should be easy to distinguish.