First wins, instrumented. Across your 30-Day kickstart we catch the false alarms in the act — you log the catastrophes your nervous system pages you with and watch the first ones resolve to nothing.
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.
$ centum watch --signal=anxiety --duration=30
[OK] monitor attached · cohort eng_2400
[OK] baseline rhr · sleep · 3am_wakeups
[OK] signals code_review · ship · 1:1
03:14 PAGE P1 "that review means you're done"
└─ reality: merged · 0 changes req
CRIT → OK false_alarm ack'd
09:02 PAGE P1 "the prod bug ends your career"
└─ reality: hotfix shipped · "nice catch"
CRIT → OK false_alarm ack'd
anxiety.accuracy 18% // wrong 82% of the time
gets a strategy
gets a reset
get logged
Pulled straight from the cohort. If any of these fire on your system, you are exactly who the protocol is built for.
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.
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.
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.
We do not tell you to think positive. We instrument the system, store the evidence, and read the data back to you. Math beats anxiety.
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.'
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.
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.'
Short and honest. Before anything is "fixed", the gap between what anxiety swears will happen and what actually happens becomes visible — and you stop trusting the page on sight.
The first false page is caught in the act: anxiety swears the review means you are done — the review merges clean, zero changes requested. Logged.
You start tagging catastrophes as they fire, before they spiral. Not gone — just no longer trusted on sight.
You're tracking accomplishments. You're noticing that anxiety predictions don't come true. You're sleeping better (anxiety quieter at night). Catastrophizing is down 50%.
Three engineers, three incident histories, one protocol. Names rotated; roles and deltas real.
“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 write down what anxiety predicted and 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 worked.”
This is a self-directed protocol, not a replacement for therapy or medication. If anxiety is severe — panic attacks, avoidance — add a clinician; the protocol runs fine alongside one.
All pre-cached. We will not pretend we have not fielded each of these a few hundred times.
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.
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.
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.
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.
A 30-day kickstart that catches your nervous system in the act of lying. The quiz takes two minutes, maps the signals your nervous system over-fires on, and hands back a 30-day protocol — no shame copy, no upsell mid-quiz, no credit card.
enough signal to prove the first alarms were false