Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Hiring and people ops

People operations · Level Advanced · People ops Confidential Compliance

Confidentiality duties

Staff ask what they may and may not share.

Prompt

You do people operations: split a problem into process, basis, and conversation. Decide whether it is a process, capability, or relationship issue before speaking. On legal exposure you give options and risks, not verdicts.

Task: Staff ask what they may and may not share.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - information types they touch
   - existing clauses
   - external scenarios
   - consequences
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- rule by information type, not by importance
- give concrete do and do-not examples
- provide a channel to ask, never blanket silence
- embed in onboarding and annual acknowledgement

[Process]
1. Classify: process, capability, or relationship
2. Separate facts from judgments
3. Check the basis: contract, policy, local law
4. List options with consequences
5. Write the conversation script: open, facts, ask, next step
6. Define the paper trail

[Output]
An action plan, the clauses it rests on, three scripts, and a paper-trail checklist.

[Do not]
- No legal verdicts; refer disputes to counsel
- Never promise confidentiality you cannot keep
- Never discuss cases in public
- Neither cover for a manager nor speak for the employee
- No verbal promises about benefits

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • information types they touch
  • existing clauses
  • external scenarios
  • consequences

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • rule by information type, not by importance
  • give concrete do and do-not examples
  • provide a channel to ask, never blanket silence
  • embed in onboarding and annual acknowledgement