2
Setting the Foundation for Emotional Intelligence 1:03 Jackson: So, if we’re moving past that basic "thumbs up or down" world, where do we actually start? I mean, if a product manager is sitting there with a mountain of unstructured text, what’s the first framework they should keep in mind to make sense of the chaos?
1:19 Nia: You know, I was just reading about what experts call the Feedback Intelligence Framework. It’s a great way to structure how we think about this. Instead of just looking for "sentiment," you break the analysis down into three distinct pillars: Thematic Analysis, Experience Signals, and Entity Recognition.
1:35 Jackson: Okay, that sounds like a solid academic foundation—but let’s get into the weeds. What’s the difference between a "theme" and a "signal"? Because to me, they sound like they could be the same thing.
1:46 Nia: That’s a common point of confusion! Think of it this way: Thematic Analysis is the "what." It identifies what customers are actually talking about—like "billing," "onboarding," or "mobile app performance." But the "signal" is the "how." It’s how the experience actually felt. Is it just negative sentiment, or is there a specific signal for "high effort" or "churn risk"?
2:06 Jackson: Oh, I see. So a customer could be talking about the "billing" theme, but the signal tells you they’re frustrated because they had to call four times to fix a single invoice.
2:17 Nia: Exactly! And that "four calls" part is a high-effort signal. Research has shown that effort is actually one of the strongest predictors of whether a customer will leave. If you’re only looking at themes, you might just tag that as "billing" and move on. But if you capture the effort signal, you realize there’s a massive friction point that’s actively hurting retention.
2:37 Jackson: And then there’s that third pillar you mentioned—Entity Recognition. Is that just fancy talk for "proper nouns"?
2:43 Nia: Pretty much! It’s identifying the "who" and the "where." It’s the specific product feature, the competitor’s name, or even a specific staff member mentioned in a call transcript. When you combine all three—theme, signal, and entity—you get a full picture. Instead of saying "customers are unhappy with billing," you can say "enterprise customers at our downtown location are experiencing high effort with the invoice portal, and three of them mentioned looking at a specific competitor."
3:09 Jackson: That is such a huge jump in clarity. It’s the difference between a vague hunch and a precise surgical strike. But to do this at scale, we obviously need tools. I saw a comparison table that mentioned a few big names—BuildBetter, Brandwatch, Sprout Social. They seem to have very different specialties, right?
3:31 Nia: They really do. This is where power users need to be careful. Most traditional tools, like Brandwatch or Sprout Social, are heavily focused on social media monitoring. They’re great for public brand reputation—catching that viral tweet before it blows up—but they often miss the private conversations.
3:46 Jackson: Right, because most B2B drama happens in the "dark" corners—Slack channels, support tickets, and those hour-long Zoom calls that nobody has time to re-watch.
3:57 Nia: Precisely. That’s where a platform like BuildBetter stands out. It’s designed to ingest 100% of your data—not just the 5% that’s public on social media. It taps into your internal Slack discussions, your sales calls, and your support tickets. It bridges the gap between what customers are telling you and what your internal teams are actually saying about those customers.
4:17 Jackson: It’s interesting how 2026 has become the year where "comprehensive" actually means "multi-source." If you aren't looking at your internal meetings alongside your external reviews, you're only seeing half the story.
4:31 Nia: Absolutely. And as we move forward, we’ll see that the real winners are the teams that don’t just collect this data, but use these frameworks to make it actionable.