In this monologue, the speaker outlines what makes a competitive intelligence (CI) team effective. The core attributes are high motivation, curiosity, strong analytical abilities, and excellent communication and influence skills. While domain expertise is valuable, the speaker emphasizes that a learning/growth mindset enables team members to acquire necessary knowledge over time. The CI process is described as a cycle of gathering intelligence, analyzing it, and communicating clear, actionable recommendations (the "so what, now what" framework) to product, marketing, or sales teams. Organizational enablers are drawn from Daniel Pink’s Drive: purpose (clear, ambitious goals), autonomy (freedom to pursue topics within the CI cycle), and mastery (continuous skill development and deep product/market knowledge). Effective communication with stakeholders—being clear about what the CI team does and does not do without antagonizing others—is also highlighted as essential for a strong CI function.
Chapters
What is the definition of a good CI team? What would you say? Well, this is a good we. Yeah, I see them like in the movie Troy with Brad Pitt. It's Myrmidon. Let's say they were in their boat and everyone was trying to get to the shore, but they were going faster and they were fearless. I would say the team For CI, it's, it's a highly motivated team, highly curious people, uh, analytical but good communicators also. That's really important. A lot of situations where we're talking about domain expertise, sometimes it's necessary, but most often it can be learned. Why? Because we are curious and we have learning mindset, so it wouldn't be an issue after a few months, few years maybe, if it's needed. People will be the experts in their fields. I'm not worried about that. I saw that firsthand. But the curiosity of people, the growth mindset or learning mindset, the analytical skills and the communication plus influence, that's really important. So the more we go in time, let's say we start with gathering intelligence, but at some point it will not be enough. From team members. Second, we analyze, or they analyze, but it won't be enough at some point. They will need to communicate that, to build their report, to make their presentations, to think what, so what, now what. And when it comes to know what, what is their recommendation for action? A competitive response, continue to monitor, or build a new feature or something like that. And it's an advice or suggestion for the, the, the, the product team or marketing team or sales. But yeah, I think the team needs to be completely comfortable with the cycle. The curiosity will allow them to learn fast about the products, the company, the industry stakeholders. Also a lot of, how to say, communication— I mean discussion with people also. So not to antagonize anyone, but to be clear about what we do and what we don't do. This kind of things. And if I refer to the book Drive from Daniel Pink, it says there are 3 things very important for knowledge workers, which I consider we are. You have purpose, autonomy, and mastery. So first thing for people in the team, and for me also, is to have a clear purpose, a clear goal, why we are here. We are not here just to ship intelligence day in, day out. So that has to be clear, and we always define it with the team, our goal— big, hairy, audacious goal. And, and autonomy— we give each other the autonomy to work on their topics following the cycle, etc. And we give each other feedback all the time. And mastery— over time, what's needed is to be the masters of our craft. Our field, our product, our market. So to become the people, uh, to, to go whenever there is a question about the market competition or even customers, what they're saying about our product or copy their products. So when you build that, uh, how to say, that, that strength for, or muscle for the organization, I think that's where you can say that you have a strong or a good team for CI.
