4:52 PM. Congress week. Your Outlook pings.

"Emergency call. 5:15."

Nobody tells you why. You ask around. Someone finally says it: a competitor dropped an abstract head-to-head against your product. The headline slide does not look good.

You have twenty-three minutes.

You find the abstract. Read it twice. Scenario-plan in the hallway between the poster session and a coffee that's gone cold in your hand. Walk into that room with a point of view and a plan.

Nobody asks if you had time to prepare. Nobody knows if you actually read the methods section or just skimmed the forest plot and bluffed the rest. They don't care. They care that someone showed up with an answer. That someone will own it, brief the field team, write the objection-handling deck, and tell the room it's going to be okay.

That's not a scientist's job. That's a therapist's job.

Congratulations. You are now a therapist. Nobody told you. Nobody trained you. The couch is a conference room. The clients are your entire cross-functional team, and on a bad day, all of them are a little bit afraid at the same time.

—

I've started keeping a private diagnosis for this. Working title: Occupational Reassurance Disorder — provisional, HEOR-specific, chronic.

Symptoms present in at least three of the following domains:

Launch. You're under-resourced and everyone knows it. Unmet needs evidence, JCA dossier, launch model, pricing inputs, regional HTA adaptation — yours, plus the four things that got added last week. PDUFA, field training, contract negotiations, P&T dates, payer testimony, market shaping already in motion. Every other function has an agency of record and a project manager tracking their timeline. You have neither, the tightest budget in the room, and the least runway. This is a Kobayashi Maru with a Gantt chart. Your job: show up, smile, and tell the team it will be done. Then go deliver it anyway.

Congress. See above. Someone else's abstract just became your emergency.

Pipeline governance. You show up with forecast inputs, a reimbursable trial design, outcome assessments across three development scenarios, price corridors, PICOs, a JCA plan, and a tidy explanation of "the cost of doing nothing" — for a program the company may or may not actually fund. You are expected to be fully prepared for a decision you don't get to make, in front of people who have never once had to explain to a payer why their asking price is reasonable.

—

I have justified a global cost-effectiveness model as "needed" to a room that had already decided it wasn't.

I have explained the ROI of a multi-million-dollar RWE investment without the authorization to actually tie the evidence to dollars.

I have prepped a product lead to go fight for my budget in an executive committee meeting I wasn't allowed into.

Every time, my actual job was the same: walk in calm, leave everyone else calmer than they found me, and quietly go build the thing in the background.

—

Nobody teaches this in school. There is no course called "Reassuring People While Doing Actual Science Under a Deadline Set By Someone Who Has Never Met You." There should be. Until then, you learn it live, on the job, usually during the worst possible week to be learning anything.

The good news: once you notice the pattern, you can't unsee it. And once you can't unsee it, you can start doing it on purpose instead of by accident.

That's the whole series. More scenes to come.

— Sanket

P.S. If you've got your own "and then I had to be the calm one" story — hit reply. Best one gets featured, no names attached unless you want them.