Think Faster, Talk Smarter: What I Actually Learned From Matt Abrahams

I watched Matt Abrahams' talk on thinking faster and talking smarter. My first reaction was skepticism — another communication expert telling me to "breathe" and "structure my thoughts." But I kept watching. Because the problem is real.

Every founder knows the feeling. You're in a customer call. Someone asks a question you didn't prepare for. Your brain goes blank. You fumble. Later, you think of the perfect response. Matt's point is that this isn't a personality flaw — it's a lack of a mental framework.

Here's what I actually use now.

The real insight isn't "be more confident"

Most advice on speaking under pressure is useless. "Just be yourself." "Practice more." "Breathe." Fine, but none of that helps when you're in the moment and your amygdala is screaming.

Matt's approach is more practical: have a structure ready before you need it. He calls it "structured improv." You don't need to memorise scripts. You need a skeleton you can hang words on.

The one I've started using in customer calls is simple:

1. Acknowledge the question (shows you heard them)
2. Pivot to what you know (connect to your expertise)
3. Give a specific example (makes it real)
4. End with a question back (keeps the conversation going)

It's not new. But having it front-of-mind changes how I respond when someone throws a curveball.

Why this matters for founders

If you're bootstrapped, every conversation matters. A rambling answer in a sales call can cost you a deal. An unclear explanation to a potential partner can slow things down for months.

I don't do investor pitches — I don't have VC money. But I do talk to customers, prospects, and team members every day. And I've noticed: when I'm prepared with a structure, the conversation feels less like a test and more like a collaboration.

Matt also talks about reframing anxiety as excitement. That one I'm still working on. But I've started telling myself before important calls: "I'm not nervous, I'm energised." It sounds like a trick. It works better than I expected.

One practical takeaway

Stop trying to "be quick on your feet." Instead, prepare one or two structures you can drop into any situation. I use the four-step above for unexpected questions. For longer explanations, I use: Problem → Cause → Solution.

That's it. I don't need a dozen frameworks. One for short responses. One for explanations. I practice them in low-stakes conversations first. Then they're there when I need them.

If you're a founder who struggles with thinking on the spot, don't buy another course. Pick one structure. Use it this week. See if it helps.

It did for me.