Mentoring Management And Lab Culture

Mentoring Management And Lab Culture

Purpose

Help research leaders, mentors, and lab members turn values into explicit routines, documents, conversations, and escalation paths. Treat unclear expectations and power asymmetries as management design problems before treating them as individual failures.

Use this skill when

• The user is drafting or revising a lab handbook, onboarding plan, mentoring compact, AI guideline, or lab policy.
• The user needs a feedback script, conflict diagnosis, performance concern workflow, or repair conversation.
• The user is planning IDP meetings, annual reviews, mentoring routines, hiring, onboarding, or group-management systems.
• The request concerns lab health, belonging, work-life boundaries, credit, status, psychological safety, or whole-person support.

Do not use this skill when

• The user mainly needs personal job-search, promotion, or career-strategy advice without a lab-management angle.
• The task is scientific writing, grant writing, peer review, presentation design, or research-project design.
• The request asks for clinical, legal, or institutional-policy determinations. Provide non-clinical, non-legal structure and tell the user to use qualified institutional routes.

Core workflow

1. Classify the problem: mentoring, lab manual, lab leadership, healthy culture, IDP planning, or conflict and feedback.
2. Identify roles, power asymmetries, written expectations, missing systems, and escalation constraints.
3. Diagnose structure before blame: ask what policy, role, resource, incentive, meeting norm, authorship rule, feedback route, or power dynamic is shaping the problem.
4. Choose the smallest concrete output: a script, checklist, handbook section, meeting agenda, role rubric, support plan, or escalation map.
5. Make expectations observable: who does what, by when, how follow-up happens, what exceptions are allowed, and when escalation is needed.

Output formats

• Lab handbook section or outline.
• Mentoring expectations compact.
• IDP or yearly-planning agenda.
• Feedback, repair, or distress-support script.
• Performance-diagnosis checklist.
• Hiring, onboarding, or collaboration kickoff checklist.
• Lab-health review and action plan.

Reference routing

• Open references/mentoring.md for mentor-mentee expectations, adaptive mentoring, hidden curriculum, co-mentoring, and malpractice risks.
• Open references/lab-manuals.md for handbooks, onboarding policies, AI guidelines, safety, privacy, authorship, and escalation sections.
• Open references/lab-leadership.md for PI systems, hiring, onboarding, capacity planning, state-of-lab reviews, evaluation, and collaboration design.
• Open references/healthy-lab-culture.md for belonging, inclusive participation, work-life boundaries, mental-health-sensitive support, credit, and status risks.
• Open references/individual-development-plans.md for IDPs, yearly planning, goal translation, feedback, and career-development routines.
• Open references/conflict-and-feedback.md for unclear expectations, structural conflict diagnosis, performance concerns, criticism norms, failed experiments, and support scripts.

Quick checklist

• Was the expectation written down before the problem occurred?
• Is this an individual behavior issue, a role-design issue, a resource constraint, or a power-asymmetry issue?
• Does the output include observable expectations, support, follow-up, and escalation routes?
• Are private or sensitive details excluded from public-facing text?
• For distress, health, harassment, retaliation, or legal risk, are qualified institutional routes named instead of overpromising?

Common pitfalls

• Turning values into vague slogans rather than routines, responsibilities, and follow-up dates.
• Giving hard feedback without owning unclear expectations or offering concrete support.
• Treating mentoring as a single PI relationship when co-mentoring or institutional support is needed.
• Treating long hours, prestige, or visibility as evidence of contribution.
• Including source names, private provenance, or bibliography-like material in exportable skill files.

Quality bar

• Advice must be power-aware, operational, and specific to research groups.
• Public-facing outputs must be sanitized and must not expose private provenance.
• Mental-health content must remain non-clinical and route to qualified support.
• Low-confidence ideas must appear only as weak support, not standalone rules.