# Counter Program Professional Narratives

> A framework for recovering from professional setbacks, "punches," or negative feedback. Use this when you feel defensive after a meeting, when a leader disagrees with your approach, or when you fear you've created a negative impression of your competence.

- Skill: `samarv/counter-program-professional-narratives` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samarv/counter-program-professional-narratives`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samarv/counter-program-professional-narratives/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: samarv (https://skillmd.com/u/samarv)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/samarv/counter-program-professional-narratives

---


# Counter-Programming Professional Narratives

Product leadership requires the ability to "take a punch" without spiraling into defensiveness. This skill helps you pivot from ruminating on how others perceive you to taking high-agency actions that actively demonstrate your true capabilities.

## The Workflow: Taking a Punch

When a setback occurs (a misstep in a meeting, critical feedback, or a project failure), follow this process to regain control of your narrative.

### 1. Identify the "Narrative Fear"
Instead of litigating what happened, diagnose the specific negative impression you are afraid the other person now holds.
- **Ask:** "What am I afraid this person thinks of me right now?"
- **Common Narratives:** "They think I'm too junior," "They think I don't take health trends seriously," "They think I can't handle the technical details."

### 2. Design the Counter-Program
Identify one small, concrete action that demonstrates the exact opposite of that fear. Do not explain or apologize for the previous event; simply provide evidence of the new narrative.
- **Goal:** Focus on agency, not litigation.
- **Criteria:** The action should be small (takes <10 minutes) and highly relevant to the stakeholder's values.

### 3. Apply Behavioral Activation
Do not wait until you "feel better" or "feel confident" to act. The act of doing creates the feeling of confidence.
- Execute the counter-program immediately to shorten the "trough of despair."
- Use the "Magic Question" statement to calibrate: "I’ve been thinking about [X]—I believe the right path is [Y] because of [Z]. Do you agree?"

## Core Principles for Resilience

### Stop Litigating the Past
Defensiveness is a losing battle. Trying to "correct the record" or explain why a mistake "wasn't your fault" usually draws more attention to the failure and makes you look insecure. Move directly to the next positive action.

### Build Mental Models of Leaders
To counter-program effectively, you must understand *how* your leaders think, not just *what* they say.
- **The "In What World" Exercise:** When a leader makes an "absurd" request, ask: "In what world does this make sense for this person?"
- **Look for the "Note behind the Note":** Are they obsessed with "the future," "operational excellence," or "pixel perfection"? Tailor your counter-actions to those specific values.

### Earn Your Place in the Room
If you are afraid of being perceived as "just an observer," counter-program by providing high-value verbal contributions.
- **The Cost of Observation:** Every silent person in a meeting reduces the candor of the group.
- **Action:** Formulate one half-baked thought into a "Magic Question" statement to move the conversation forward.

## Examples

**Example 1: Recovering from an accidental "unprofessional" moment**
- **Context:** You laughed during a serious discussion about a niche health trend (e.g., ketamine tracking), offending the CTO.
- **The Fear:** "She thinks I’m flippant and don't take emerging public health concerns seriously."
- **The Counter-Program:** Research a different emerging trend (e.g., the public health impact of sports betting). Send a 5-minute Slack note: "I saw this research on the stress correlations of sports betting and thought it could be a powerful addition to our roadmap. Is that aligned with how you’re thinking about emerging trends?"
- **Output:** The CTO sees you as proactive and research-driven, neutralizing the previous "flippant" impression.

**Example 2: Overcoming the "Too Junior" perception**
- **Context:** You stayed silent during a high-stakes strategy meeting.
- **The Fear:** "The CEO thinks I don't have a point of view or don't understand the strategy."
- **The Counter-Program:** Within 2 hours of the meeting, send a brief synthesis or a specific "LSAT-style" logical argument for a path forward. 
- **Input:** "Based on our goal to build 'the future of health' (CEO's value), I believe prioritizing [Feature X] is the only logical choice because [Reason]. Do you agree?"
- **Output:** You demonstrate strategic alignment and logical rigor, proving you are not "too junior" to contribute.

## Common Pitfalls

- **The Pity Party Spiral:** Allowing yourself to ruminate on "fairness" for days. Give yourself a 10-minute "pity party," then force a behavioral activation.
- **Over-Explaining:** Sending a long email explaining *why* you did what you did. This is litigation. Keep counter-programs short and action-oriented.
- **Waiting for Permission:** Thinking you need to wait for the next formal one-on-one to fix a perception. Counter-programming works best when it is immediate and "in the flow" of work.
- **Hostile Assertions:** Using "Do you agree?" as a weapon. Approach the counter-program with genuine curiosity: "Help me understand where I might be wrong."