Anxiety for Highly Competent People — 14-day Protocol for Engineers Who Have Impostor Syndrome
You're good at your job but you're convinced everyone will realize you don't belong. Your anxiety isn't about being competent. It's about being seen as competent.
This 14-day draft is a kickstart: we instrument your threat model and catch the first false alarms in the act, so the very first wins are on the record before anything is "fixed".
normative summary: instrument → store evidence → diff anxiety against reality, weekly.
- Request for Comments
- 2026
- Category
- Experimental
- Vertical
- V5 · anxiety & calm
- Avatar
- A3 · engineers and PMs
- Program
- 14-Day
- Status
- DRAFT · kickstart
Three reproducible defects in the threat model. If any reproduce on your system, this document is addressed to you.
1 · Problem Statement
Your anxiety is not a character flaw. It is a monitoring system with its severity thresholds set catastrophically wrong — paging P1 for events that merge clean.
- 1.1P1IMPOSTOR-001
Every green build still reads as fragile
You ship working code and immediately think 'this is fragile, someone will find a critical flaw, they'll see I'm a fraud.' You can't internalize success. Each win feels temporary.
- 1.2P1IMPOSTOR-002
One bad signal escalates straight to “career over”
You catastrophize: one bad code review = they're about to fire you. A critical bug = your career is over. You know rationally these are overreactions but your nervous system is screaming danger.
- 1.3P2IMPOSTOR-003
Perfectionism, running as a denial-of-service on you
You're trying to be perfect to prove you belong. You work 60-hour weeks. You're exhausted, stressed, anxious. And still convinced it's not enough. The treadmill never stops.
Three normative moves. None of them are “think positive” — each one writes evidence to disk so the next spike has something to argue against.
2 · Specification
The key words MUST, SHALL, and SHOULD are to be interpreted as in a real spec: non-negotiable, required, and strongly recommended.
- §2.1MUSTsplit_signal
Separate performance anxiety from actual performance
We track: What did you actually accomplish? vs. What did anxiety tell you about it? These are usually wildly different. Your anxiety says 'you'll get fired.' Reality says 'solid Q2, on track for promotion.'
- §2.2SHALLevidence_store
Build an evidence system
Every time you complete a project, we document: scope, deadline, quality, impact. This becomes your personal evidence library. When anxiety says 'you're incompetent,' you point to 50 successful projects. Math beats anxiety.
- §2.3SHOULDweekly_retro
Friday retro: anxiety vs. reality
What did anxiety predict? What actually happened? How accurate was anxiety? Usually: anxiety is wrong 80%+ of the time. Your nervous system learns: 'False alarm, you're actually fine.'
The first patch. Across your 14-day draft you start landing changes like the one below — small, reviewable, reverted by your nervous system far less often than it used to.
3 · The Patch
the prediction
what anxiety swore would happen
the evidence
what the record actually shows
the anxiety tax
the gap, shrinking each release
Short and honest. Before the big release, the early builds already change the shape of the week.
4 · Changelog
- [v0.1.0]Day 6 · 43%Added
First instrumentation lands: anxiety swears the review means you are done — the review merges clean, zero changes requested. Logged as a false alarm.
- [v1.0.0]Day 14 · 100%Stabilized · first build
You start tagging catastrophes as they fire, before they spiral. Not gone — just no longer trusted on sight.
Three implementers, three incident histories, one spec. Names rotated; roles and deltas real.
5 · Conformance
I shipped clean for two years and still read every review as the one that exposes me. The evidence store was the first thing that argued back with data instead of vibes.
The Friday retro is the only ritual that survived a re-org and an on-call rotation. I diff what anxiety predicted against what happened. It is wrong almost every single time.
A prod incident no longer reads as “career over.” It reads as a ticket. Same brain, recalibrated thresholds. That is the whole product, and it shipped.
Conformance note: this is a self-directed protocol, not a substitute for diagnosis, therapy, or medication. If anxiety is severe — panic attacks, avoidance — add a clinician; the spec is designed to run alongside one.
All pre-cached. We will not pretend we have not fielded each of these a few hundred times in review.
A · Frequently Raised Objections
A.1Isn't impostor syndrome just part of being an engineer?+
It is common. But common doesn't mean healthy. High-performers often have it worse. The problem is when it blocks you from taking risks or accepting promotions. That's when we treat it.
A.2If I stop feeling anxious, will I stop trying hard?+
Opposite. You'll try smarter, not harder. Right now anxiety is making you work in panic mode. Calm allows actual strategic thinking and better code.
A.3What if my anxiety is telling me something true? What if I'm not actually good enough?+
Then your track record would show that. Pull up your code reviews, your projects, your impact. If they're strong, anxiety is lying. If they're weak, we address the actual skills gap, not the anxiety.
A.4Can I do this without therapy?+
This protocol works well for mild-moderate anxiety. If anxiety is severe (panic attacks, avoidance), therapy is worth adding. But many engineers respond really well to the evidence-based protocol alone.
Open the draft.
A 14-day kickstart that catches your threat model lying and logs the first false alarms as resolved. The quiz takes two minutes, maps the events your threat model over-fires on, and hands back a 14-day spec — no shame copy, no upsell mid-quiz, no credit card.
status: DRAFT · kickstart · ready to adopt
- A baseline read of your threat model, no devices required
- The daily reset — under two minutes per spike
- The evidence store + the weekly anxiety-vs-reality diff
- Money-back if your false-alarm rate hasn’t moved