- Home
- Skills
- Menkesu
- Awesome Pm Skills
- Workplace Navigation
workplace-navigation_skill
166
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill menkesu/awesome-pm-skills --skill workplace-navigation- SKILL.md2.2 KB
Overview
This skill helps product managers and individual contributors navigate difficult colleagues, resolve team conflicts, and maintain productive relationships under stress. It distills frameworks from Anneka Gupta and workplace dynamics research into a practical, repeatable approach. Use it to diagnose behavior, run constructive conversations, and decide when to escalate.
How this skill works
The skill inspects behaviors, frequency, and impact to generate a root-cause hypothesis (fear, misalignment, ego, or style differences). It then recommends a staged conflict-resolution pattern: one-on-one understanding, finding shared goals, setting boundaries, and a clear escalation path. Templates and a quick checklist guide wording, evidence collection, and next steps.
When to use it
- A colleague repeatedly blocks progress on a project
- You encounter persistent toxic dynamics affecting team morale
- Communication style mismatches create frequent misunderstandings
- You need to preserve a working relationship while addressing harmful behavior
- Before escalating issues to a manager or HR
Best practices
- Start with a hypothesis about root cause, not judgment — ask questions to confirm
- Prepare a non-confrontational opening and listen actively to gather facts
- Focus feedback on specific behaviors and impacts, not character or intent
- Define acceptable boundaries and agreed consequences before escalating
- Document interactions and attempts to resolve before involving managers or HR
Example use cases
- Run a one-on-one template when a stakeholder regularly changes priorities and blocks delivery
- Use the quick navigation checklist before confronting someone to ensure calm, evidence-based conversation
- Apply the root-cause framework if a teammate’s defensiveness appears driven by fear of job security
- Set an escalation path after documenting repeated breaches of agreed boundaries affecting your work
FAQ
Document the refusal, continue to focus on observable impacts in shared work, and escalate with evidence to your manager or HR after a defined number of attempts.
How long should I try informal resolution before escalating?
Attempt 2–3 structured one-on-ones over a few weeks, unless the behavior is severe; use that window to document examples and set clear expectations before escalation.
How do I protect my own work while resolving conflict?
Set concrete boundaries, keep written records of decisions and approvals, copy relevant stakeholders on key communications, and avoid making unilateral changes that increase risk.