Media training has a bad reputation among founders, mostly because the version sold by large agencies produces executives who sound like hostage videos. That's a failure of execution, not of the idea. The useful core is small: know what you're trying to say, know the rules of the conversation, and know how to handle the two or three questions you're dreading.
You can learn that in an afternoon. Here's the afternoon.
Message discipline: three things, actually
Before any interview, write down three messages you want in the story. Three, not seven. Each one should be a complete sentence a reader could repeat, not a theme.
Bad: "innovation," "customer focus," "our growth."
Better: "Clinics using our tool cut prior-authorization turnaround from six days to under two." "The bottleneck was never staffing, it was payers publishing schemas." "We're profitable on a 22-person team."
Two tests. Could a competitor say it? If yes, it's a category description, not a message. Does it contain a number, a name, or a mechanism? Vague claims don't survive editing. Specific ones become the pull quote.
Then accept the ratio: in a thirty-minute interview you'll say thousands of words and maybe forty appear in print. You don't control which forty. Message discipline isn't about forcing your lines in. It's about making sure that whichever forty they pick, you're happy to see them.
Bridging, without sounding like a politician
Bridging means acknowledging a question and moving to something you can speak to usefully. It is a legitimate technique when the question genuinely isn't answerable and an obvious dodge when it is. The difference is whether you actually answered first.
The honest form has three beats: answer what you can, name the limit, then bridge.
"I can't discuss revenue. We're private and we don't disclose it. What I can tell you is we're profitable and have been for five quarters, and the reason is that our cost to serve a clinic dropped by two-thirds when we automated onboarding."
That's a real answer, a stated boundary, and useful material. Compare the version everyone hates: "What's important here is that we're focused on delivering value for our customers." That's a non-answer wearing a bridge's clothes, and any competent reporter will note that you dodged, sometimes in the piece itself.
Phrases that work as bridges when they're true: "I don't know, but here's what I do know." "That's outside what I can speak to, but I can point you to the person who can." "There's a more interesting version of that question" (use once, and only if you're right).
The rule underneath all of it: never answer a question you can't answer. "I don't know" is a complete sentence and costs you nothing. A confident guess that turns out wrong costs the reporter a correction and costs you their trust.
On the record, on background, off the record
Get these wrong and you will eventually say something you can't take back. They are not synonyms, and conventions vary slightly by outlet, so it's normal and smart to confirm what a specific reporter means.
- On the record. Everything you say can be quoted and attributed to you by name and title. This is the default. If you are talking to a journalist and nobody has agreed otherwise, you are on the record. That includes the small talk before the interview, the hallway afterward, the conference bar, and the Slack message you sent them.
- On background. The information can be published, but attribution is limited to a description you agree on in advance, such as "a company executive" or "a person familiar with the negotiations." Agree the exact wording, because "a source close to the company" and "the company's CEO" are very different levels of exposure.
- Deep background. The information can be used, but with no attribution at all. The reporter writes it in their own voice, and nothing points back to a source. Less common, and worth confirming what they mean by it.
- Off the record. Not for publication in any form. A reporter may use it to understand context or to go seek the same information from someone who will say it on the record, but they cannot print it from you.
The rule that matters most: all of these must be agreed before you say the thing. You cannot say something and then declare it off the record afterward. A retroactive "that was off the record, right?" is a request, not a rule, and the reporter is under no obligation to grant it. The sequence is: ask, get an explicit yes, then talk.
"Can I give you some context on background, attributed to a company executive?"
Wait for the answer. If they say no, and some reporters and outlets do decline, decide whether you still want to say it on the record. That decision is much easier before the words leave your mouth.
One more caution: off the record protects you from publication, not from consequences. A reporter who learns something troubling can and will go find it elsewhere, on the record, from someone else.
Handling hostile questions
Most questions that feel hostile aren't. They're a reporter doing the basic work of testing a claim, and founders who react defensively to normal scrutiny create the exact adversarial dynamic they feared.
For the genuinely hard ones (churn, layoffs, a lawsuit, a failed pilot, a competitor who's ahead), work through this:
- Answer it. Directly, in the first sentence, before any context. Evasion is the story. The fact rarely is.
- Don't repeat the hostile framing. If asked "why is your product unsafe," do not begin "our product isn't unsafe." Quoted in isolation, that sentence hurts you. Start with what is true: "We've had 140,000 sessions with two reported incidents, both investigated and disclosed."
- Accept the premise or correct it, not both. Half-correcting reads as squirming.
- Don't fill silence. Reporters pause deliberately. Founders fill it, and the material that spills into that gap is disproportionately what ends up in print. Answer, then stop.
- Never say "no comment." It reads as guilt. Say why you can't discuss it: pending litigation, an employee's privacy, a customer contract. A stated reason is a legitimate non-answer. "No comment" is not.
- Don't get angry, and don't get cute. Sarcasm does not survive transcription.
Practical prep before an interview
The hour before matters more than any training course.
- Read their last five pieces. The person, not the outlet. You'll know their angle, their format, and whether they're friendly to your sector. The same homework that makes a pitch land makes an interview go well.
- Ask what the story is about and who else they're talking to. Normal questions, usually answered. You're allowed to know the shape of the piece.
- Write your three messages on one page. In front of you during the call. Nobody can tell.
- List the five questions you're dreading and say the answers out loud. Out loud, not in your head, because the gap between the two is where founders get hurt. Have someone ask them at you if you can.
- Confirm the ground rules at the start. On the record unless agreed otherwise, whether anything is under embargo and until when, and when it's expected to publish. Settle embargo terms explicitly, and read how embargoes actually work before you agree to one.
- Have your numbers to hand. Headcount, funding, customers, pricing, growth. Fumbling your own metrics is the most avoidable damage available.
- Decide in advance what you will not say. Unannounced roadmap, customer names not cleared, anything about an employee, anything about a competitor's internals. A list made calmly beforehand holds up under pressure. Improvised judgment doesn't.
Two things not to ask for: approval of the piece before publication, and a list of questions in advance. Both are standard requests in corporate comms and both are routinely refused by real newsrooms. You can ask for the general topics. You cannot ask to see the story.
Finally: not every conversation is an interview. Source requests and quick expert comments are lower-stakes, and handling those well is how most founders get their first reps. Start there, and by the time a real interview matters you'll have done twenty.
Have news worth being interviewed about? [See our pricing](/pricing), public and with no sales call.