Find your next skill gap in the role's real requirements, not the generic advice

Start with a real role, not a generic checklist

The most common reason a learning plan fails is that it was never aimed at anything specific. You read that "data literacy" or "cross-cultural leadership" is in demand, you sign up for a course, and two months later you cannot point to a single responsibility you can now handle that you could not before. The problem is not your discipline. The problem is that a generic list describes a hypothetical average role that does not exist at your company or in your target team.

A real role is concrete. It has a name, a team, a set of deliverables, and a manager who will judge whether you can do the work. When you derive your next skill from a real role, you are not guessing what the market might want in the abstract. You are answering a narrower, answerable question: against the things this specific role actually requires, where exactly do I fall short? That question produces a short list you can act on, instead of a long list that makes you feel busy.

This matters especially in China, where role expectations often carry context that generic global advice misses: local regulatory framing, the way a China-based team coordinates with headquarters, or the specific tools a regional function has standardized on. Reading the real requirements is how you surface those specifics instead of importing advice written for a different labour market.

Turn the job description into a capability list

A job description is not yet a skill list. It is prose, usually written by someone who was not thinking about your development. Your first job is to convert it into a flat list of capabilities, each stated as something a person in the role must be able to do.

Start by extracting the verb phrases. "Responsible for preparing monthly reports" becomes "prepare recurring performance reports." "Works with the local legal team on compliance reviews" becomes "coordinate compliance reviews with the local legal function." Keep the object of the verb, because the object is where the China-specific detail usually lives.

Then group the extracted phrases. Several sentences about running campaigns, measuring them, and reporting on them can collapse into one capability: "plan, execute, and report on local marketing campaigns." Grouping stops the same gap from appearing five times under five wording styles.

Next, mark the level each line implies. "Familiarity with" is not "expert in." "Experience managing a team" is not "can build a team from scratch." The level is part of the requirement; if you score yourself against the wrong level, the gap is fake.

Separate must-have from nice-to-have explicitly. Most descriptions blur these. A line that says "knowledge of Python a plus" is a different category from "required: SQL for daily reporting." Treating a plus as required invents a gap you do not actually have.

Finally, tag each capability with the context that makes it China-specific, if any. A requirement to "manage relationships with government affairs contacts" is not the same as "manage vendor relationships" in a market where no such function exists. The tag tells you later whether a generic course will actually close the gap or whether you need a locally grounded resource.

Fictional example: a posting for "Regional Operations Coordinator, Shanghai" lists "liaise with headquarters on inventory planning," "maintain local supplier records," and "support quarterly compliance filings." Read literally, that is three capabilities, not a vague "operations skills" bucket. The third one is China-specific in practice even if the words look generic, because compliance filings refer to a local procedure the headquarters role never touches.

Score yourself honestly against each line

With a flat list in front of you, score each capability on a simple three-point scale: can do it at the required level today; can do part of it but not reliably or not at the required level; cannot do it. Resist the temptation to use a ten-point scale. Fine gradations invite you to argue with yourself and produce a ranking that feels precise but is not.

The discipline here is honesty about evidence. "Can do it" should mean you have done it recently and can point to the output. "Partly" means you have touched it but the result depended on help, or you have not done it at the scale or standard the role demands. "Cannot" means you have no direct experience and would need to learn from scratch.

One trap is scoring the capability you wish the role had, not the one written. If the description says "maintain local supplier records" and you have only managed a global supplier database, your score for the local task should reflect the local task. Another trap is inflating because the capability sounds like something you are generally good at. General competence does not transfer automatically to a specific, context-bound requirement.

When you finish, you have a short table: capability, required level, your score. The gaps are simply the rows marked "cannot" or "partly" where the role says the line is required. Everything else is either a strength to keep sharp or a nice-to-have you can ignore for now.

Separate a true gap from a preference

Not every item you scored low is a gap you must close. A true gap is a required capability you cannot perform at the level the role demands. A preference is something you would enjoy learning, or something that would make you more comfortable, but that the role does not actually require at that level.

The test is simple: if you closed this gap, would a specific requirement in the role be met that is not met today? If yes, it is a gap. If the honest answer is "it would be nice but the role functions without it," it is a preference. Preferences are fine to pursue on your own time, but they should not crowd out a real gap in your plan.

A related confusion is the "keeping up" gap. You may feel behind because peers mention a tool you have not used. Check the role description. If the role does not require that tool, the feeling is social, not a requirement-driven gap. This is exactly where generic advice misleads: it turns other people's preferences into your emergencies.

Be equally careful in the other direction. Some gaps are hidden because the description understates them. If you know the team relies on a capability the posting only hints at, treat the hint as a required line and score it. The description is a starting point, not the full truth of the job.

Pick one gap to close

You will usually end up with several real gaps. Trying to close all of them at once is how plans collapse. Choose one, using four filters.

Leverage first. Which gap, if closed, unlocks the most required lines at once? A capability that the role mentions in three places beats one mentioned once. Learn the multiplying gap before the single-mention one.

Learnability second. Can you realistically close it in a defined window with resources you can access? A gap that needs a two-year degree when you have three months is a project, not a next step. Pick a gap with a finish line you can see.

Verifiability third. Can you prove to yourself, and later to a manager, that the gap is closed? A gap you can demonstrate with a small delivered piece of work is better than one whose completion is a feeling.

Alignment fourth. Does closing it move you toward the role you actually want, not just the role on the page? If the posting is a stepping stone, weight gaps that also serve the next role.

Write the chosen gap as a single sentence: "I will be able to [capability] at the level [required level] for [role], evidenced by [proof]." That sentence is the contract with yourself.

Build a short, honest learning plan with proof of progress

A learning plan is short if it has an end. Take the one gap sentence and break it into three or four small steps, each with a check you can perform.

Define the end state in observable terms. "Understand local compliance filings" is not observable. "Complete one filing draft and have it reviewed by the local function without major correction" is.

Choose resources deliberately. For a China-specific capability, a generic global course may miss the local procedure; look for material or a person grounded in the actual local context. For a general capability, any solid resource will do.

Set one early milestone within the first weeks, something too small to fail: read the relevant internal template, shadow one cycle, draft one section. Early proof keeps momentum and tells you whether your self-score was honest.

Show progress as you go. Keep the draft, the review notes, the before-and-after. Progress is not "I studied for ten hours"; it is "I can now produce the output the role requires, reviewed and accepted." When the proof exists, the gap is closed and you can return to your list and pick the next one.

One place to verify a credential is actually recognised

Sometimes the gap looks like a missing qualification when it may not be. Before you spend months studying for a credential you assume is required or unrecognised, check whether a qualification you already hold is accepted. Shanghai provides practical career-guidance services for foreign professionals, and its hub includes the Shanghai List of Recognized Overseas Occupational Qualifications, which you can use as a concrete check rather than assuming a certificate is or is not recognised: Shanghai career-guidance services for foreign professionals (incl. Shanghai List of Recognized Overseas Occupational Qualifications). Treat this as a Shanghai-specific pointer, not a national rule, and confirm against the official channel for the latest information before acting on any named qualification.