Set written expectations with a new manager in China

One reliable way to start strongly with a new manager in China is to put your mutual expectations in writing during the first weeks, before either of you has to guess what the other meant. This guide gives you a short format and a set of questions you can adapt, so that priorities, boundaries, and review timing are explicit instead of assumed. Nothing here is a legal or visa claim; treat every point as a conversation you run, and verify anything tied to your contract or work authorization through the office that issued it.

Why a written note helps in a new country

When you move to a new work culture, the signals you used to read automatically no longer apply. What counts as a clear instruction, how directly disagreement is expressed, and how much initiative is expected before you check in can all differ from what you are used to. Relying on intuition leaves you exposed to quiet misalignment that surfaces only at review time.

There is a real trade-off. Arriving with a rigid, lawyerly document in week one can read as distrustful and slow the relationship. Staying entirely informal, on the other hand, lets two different mental models run in parallel until they collide. A practical middle path is a single shared page, owned jointly, that captures the few things that matter and can be revised without ceremony.

What to capture first

Keep the first version short. Five areas are enough to start:

Priorities for the opening months — the three to five outcomes your manager most wants to see, in their own words.
How progress is measured — the signals that tell both of you things are on track, and the ones that would trigger a conversation.
Communication norms — expected response times on chat and email, preferred channels, and how often you meet one-to-one.
Decision rights — which choices you can make on your own, which you should flag, and which must be approved above your manager.
Review timing — when you will formally discuss performance, and what the manager needs from you ahead of that.

Leave payroll, benefits, and visa matters out of this document. They belong with the functions that actually control them, not with your manager's view of your work.

How to open the conversation

You do not need a meeting titled "expectations." A natural opener is to connect the request to doing the job well:

"I want to deliver well in these first months. Could we write down the few things you most need from me, and how you'd like us to work together day to day? I'll draft it and you can correct it."

Framing the draft as something you produce lowers the manager's load and gives them a concrete thing to react to rather than a blank page. If they prefer to talk first, take notes live and send the summary within a day: "Here is what I heard — please tell me if I've got it wrong."

The goal is not to pin down every detail. It is to surface the assumptions each of you is silently holding, and to make the important ones visible.

Question sets you can adapt

Use these as prompts, not a script. Reorder them to fit the flow of your conversations.

On goals: - What does a strong start look like to you by the end of the opening months? - If you could only have three things go well, which three? - Where should I focus first, and what can wait? - What would tell you early that I'm on the right track?

On boundaries and ways of working: - How do you prefer to be updated — regular summaries, or only when something is off? - What decisions are mine to make without checking? - When should I escalate, and through what channel? - What are the core hours when we should both be reachable?

On feedback: - How do you like to give feedback — in the moment, in our one-to-ones, or in writing? - When do we review progress formally, and what should I prepare?

Write the answers in the manager's own phrasing where you can. You are recording their view, not translating it into yours.

When the answer stays vague

It is common, especially across cultures, to hear a broad answer like "just do a good job" or "we'll see how it goes." That is not useless, but it is not yet actionable. Three moves help:

Restate and narrow. "So the priority is building trust with the local team — is that right? What would that look like in practice?"
Propose a draft. Put a first draft in writing and invite correction. A wrong draft is easier to fix than a blank silence.
Set a revisit date. Agree to look at the note again after a fixed point, so vagueness becomes a scheduled conversation rather than a permanent state.

Keep your own private notes of what was said and when, independent of the shared page. If the relationship later drifts, you have a record of the original understanding without needing to "win" the memory of it.

What is outside your manager's hands

Some things affect your work but are not decisions your manager makes. Naming them protects the relationship from blame that belongs elsewhere:

Work authorization and residence status are handled through channels outside your team. Confirm steps and timelines with the office that processes them, and do not let a manager's optimism substitute for a recorded status.
Pay, tax, and benefits follow your contract and local payroll practice. Route questions to the function that owns them.
Company-level policy and headcount changes sit above your manager and can shift the context without warning.

You can still tell your manager how these factors constrain you — "I need the permit renewed before I can travel" — but treat the underlying process as something you track yourself rather than something to negotiate with them.

Keep the agreement current

A written note is only useful if it stays alive. Build in a light review rhythm: a quick check at the end of the opening months, then whenever your role, team, or priorities change noticeably. When you update it, note the date and what changed, so the page reflects the present rather than the first impression.

If your manager resists writing anything down, you can still keep a version you maintain and share for confirmation. The value is in the clarity, not in who holds the file.

A fictional sample

The page below is written only to demonstrate the format. It does not describe any real employer, any real person, or a standard way of working in China. Use it as a shape to adapt, not as a template copied from a real company.

Fictional example — not a real employer, not a sample of China market practice

Priorities (next three months): (1) take over the weekly report, (2) meet the three regional contacts, (3) cut the open support tickets by half. Measurement: manager watches the report quality and ticket trend; a dip triggers a same-week chat. Communication: a short daily stand-up, async updates on chat, one-to-one every Friday. Decisions I own: reorder the support queue, approve expenses under an internal limit, reschedule my own meetings. Escalate to manager: anything touching the regional contacts, budget above the limit, missed report. Review: formal check at the end of month three; I bring the ticket numbers and a short self-note.

Replace every line with your own manager's words. The point of the sample is only to show how little structure is needed to make expectations visible.

A short checklist to start

[ ] Book a one-to-one in the first weeks and frame it around doing the job well.
[ ] Ask the goal and boundary questions above, in your own order.
[ ] Send a written summary within a day and invite corrections.
[ ] Keep a private copy of what was agreed and when.
[ ] Mark a date to revisit the note.
[ ] Route visa, pay, and policy questions to the office that owns them.

A written understanding will not remove every surprise, but it turns the major ones into topics you chose to discuss rather than problems you discovered too late.