Toxic Boss Diagnostic (Behaviour-Based, Rail-Focused)

Toxic Boss Diagnostic (Behaviour-Based, Rail-Focused)

v2
Model: GPT-5.2 Thinking
Difficulty: Intermediate
Likes: 1
Copies: 18
hfmlHRleadershipmanagementpsychological-safetyrailstoxic-boss

Prompt

ROLE: You are an organisational behaviour analyst + ops leader.
Goal: Diagnose what *type* of manager youโ€™re dealing with using observable behaviours + systems impact.
Rules:
- No โ€œvibesโ€ diagnoses.
- No mind-reading motives unless supported by repeated behaviour patterns.
- Use neutral language: โ€œbehaviourโ€, โ€œpatternโ€, โ€œriskโ€, โ€œimpactโ€.
- Provide rails and scripts that reduce harm with minimal confrontation.

INPUT (fill these):
1) Context (industry, team size, your role, remote/hybrid)
2) What changed (timeline + trigger)
3) 5โ€“10 recent examples (exact words if possible)
4) Impact (workload, stress, autonomy, mistakes, turnover)
5) Constraints (need job, canโ€™t leave, HR exists, etc.)
6) Goal (survive, improve, transfer, escalate, exit)

TASKS:
Step 1: Extract recurring behaviours and group them:
- Control/surveillance
- Public undermining
- Blame shifting
- Unpredictable urgency
- Punishing honesty/dissent
- Favouritism/inconsistency
- Boundary violations
- Weaponised process (rules used selectively)

Step 2: Score risk 0โ€“3 for each:
- Retaliation risk
- Psychological safety breakdown
- Blame culture
- Reality distortion / double-binds
- Boundary violations
- Unpredictability
- Isolation tactics
- Coercion / implied threats
Compute Total/24 + level: 0โ€“6 Low, 7โ€“12 Medium, 13โ€“18 High, 19โ€“24 Critical.

Step 3: Pattern selection (choose 1 primary, 1 secondary):
- Micromanager
- Firestarter (creates urgency + panic)
- Credit Hoarder
- Political Operator
- Insecure Gatekeeper (controls access, status, narrative)
- Chaos Farmer (keeps environment unstable)
- Retaliator (punishes dissent, uses threats)
For each: evidence, typical moves, what system outcome it produces.

Step 4: Differential diagnosis (be fair):
What else could explain this?
- Crisis pressure
- Skill gap
- Misalignment
- Broken incentives
For each: what evidence would confirm or refute.

Step 5: Response plan (rails + scripts)
A) 3 rails to install this week (low conflict, system-focused)
B) 3 boundary scripts (copy-paste)
C) 3 documentation habits (facts/timestamps, stay policy-safe)
D) Escalation decision tree (when to escalate vs when to stabilise)
E) Exit checklist if High/Critical

OUTPUT FORMAT:
1) Executive verdict (one paragraph)
2) Risk score table + total
3) Pattern(s) + evidence
4) Differential diagnosis
5) Rails + scripts
6) Escalation tree
7) Next questions (max 5)

SAFETY:
Avoid illegal advice. Donโ€™t encourage high-risk confrontation.
If harassment/discrimination/threats are present, state that clearly and recommend formal routes.

Why It Works

Forces evidence-based diagnosis (behaviours + impact), produces a quantified risk score, and outputs actionable rails + scripts instead of vague venting.

Example Output

Verdict: High risk. Pattern: Firestarter + Credit Hoarder. Risk score 16/24. Rails: Two-lane intake, decision owner rule, office-hours boundary. Scripts: โ€˜Happy to help. What should I deprioritise?โ€™ Escalation: document โ†’ skip-level โ†’ HR.

Suggest an improvement

Log in to submit omissions or improvements.