Product Manager
Cross-Team Alignment (CN-only)#alignment#sync#cross-functionalCross-Team Alignment Sync Notes · CN-context
CN-only · After a cross-team sync, get a clean 'who-owns-what + consensus + open items + next-step' doc in 5 minutes — designed to be sealed in a Feishu/WeChat group with a 24h thumbs-up rule.
Pain addressed · PM = team glue. 'Just synced design / eng / ops separately — four people, four understandings — skip the notes and we redo it tomorrow, write the notes and lose 30 minutes.'
Cross-Team Alignment Sync Notes · CN-context
CN-only prompt. See prompt_zh.
This scenario (kuabumenlaqi · cross-team alignment as an informal sync ritual before formal meetings) is unique to Chinese tech / internet workplace culture. The closest English-language equivalent is captured in the product-manager-meeting-notes prompt — but lacks the 24h-thumbs-up sealing convention and the 1-sentence PM commitment that Chinese 'glue PM' culture treats as the deliverable.Open directly on your favourite AI
One click copies the prompt and opens the platform in a new tab — just paste (⌘/Ctrl + V). Recommended platforms are ordered by content fit.
Workflow · 6 steps
- 1
This is a Chinese-workplace ritual; the closest Western analogue is the 'decisions doc' from product-manager-meeting-notes. Use that prompt instead if you're outside CN.
- 2
If you're writing one anyway: immediately after the sync, dump quotes and key statements into one block, tagging [Who][Said what].
- 3
Run the prompt in Kimi or Doubao (best Chinese tone). Replace {paste_meeting_notes}.
- 4
On the first draft, edit three things: verify the consensus block is REAL consensus (don't include items where someone stayed quiet), make sure every open item is documented, and confirm every next step has an owner + deadline.
- 5
Run the checklist and remove vague language.
- 6
Post to the team channel with @-mentions and the '24h thumbs-up or comment' rule — silence = consent.
Verify before you ship
AI's "almost right" is the #1 pain. Tick these off so reviewers can't find the obvious holes. (Checkbox state stays local — we don't track it.)
Why this prompt works
This prompt isn't a generic “write me a Cross-Team Alignment (CN-only)”. It folds in the concrete context a Product Manager actually faces (target reader, info density, deliverable format). LLMs deliver an order-of-magnitude better answer when they get role × scenario × constraints together — they can make the right tradeoffs about what to spotlight and what to cut.
When to use
Best moment: you know roughly that you need to do a Cross-Team Alignment (CN-only), but you're stuck on “how do I even ask the AI?” Muscle memory has no template. Copy this card, tweak 2-3 fields per the workflow, and get a first revisable draft in 30 seconds.
Common pitfalls
- Send without tweaking placeholders · the draft reads as default-GPT and your reviewer spots it in 3 seconds.
- Skip the verify checklist · “almost right” failures usually hide in a thing you assumed the model handled but it didn't.
- Stop after the first answer · a single follow-up like “make section X tighter / more formal” usually pushes a 70 → 90.
Variants & extensions
Want to use this card more aggressively? Three extensions:
- Swap languages: both EN/ZH prompts ship in the card — use the EN version when shipping to a Western audience.
- Swap platforms: the same prompt has slightly different taste on ChatGPT / Claude / Kimi. The recommended-platform pill marks the best fit.
- Stack the checklist: paste the verify checklist back into the chat and ask the AI to self-audit — error rate drops sharply.
Want 25 more prompts like this one?
Get the full 50-card Pro deck — multi-step chains, vertical variants, lifetime updates.
- 50 prompts · 25 free + 25 advanced multi-step chains
- PDF printable + Notion template
- Lifetime updates · ~5 new prompts a month, auto-synced
- Dual-language · EN/CN + 5 China-exclusive scenarios
