Complete B2B Product Management – Strategy for the AI Era

BizatWeb
67 followers
6 Video Views·Jun 3, 2026
The Complete B2B Product Manager
Many people get into Product Management, scramble to get everything done, and burn out within a year.
Want to get clients using cold email?
Start here 👇
https://app.outboundest.com/r3emGnyc
Use code: OUTBOUND (20% OFF)
🔥 Get the exact tools I use:
👉 https://bit.ly/bizattools
🚀 Grow Your Business & Master Digital Skills with BizatWeb
🌐 Website:
https://bizatweb.com
📩 Email:
[email protected]
📱 WhatsApp:
https://wa.me/212637648713
📲 Follow BizatWeb:
Instagram → https://instagram.com/BizatWebHQ
Facebook → https://facebook.com/BizatWebHQ
TikTok → https://tiktok.com/@BizatWeb
🔥 Business • Marketing • AI • Automation • Cybersecurity • Online Growth
AI Generated·May contain errors
Product management sounds abstract, but the core of the job is actually very simple. You work out
what's worth building, why it matters, and you align a team to deliver it. But unfortunately,
that is where the simplicity ends, and fortunately, the fun begins. A lot of people get into product
because they want to influence what gets built, and you can. Engineering wants clear direction,
sales wants their deals closed yesterday, support wants the fires put out, customers want everything
for free and tailored to them, and leadership wants a brand new machine learning module
without anything else slowing down and without giving you any extra resources. And that's just
a few of your stakeholders. Your job is decision making, but it's decision making in the middle of
all of this. That's where new product managers tend to struggle without proper guidance,
and this tension is even more stark in B2B. The reason this is so complex is because you're
building for organizations, with buyers, users, and their customers, and all of those other internal
stakeholders that we talked about, and they're all pulling you in different directions. A single
feature can have ripple effects across an entire client organization that might be worth hundreds
of millions of dollars. That's why B2B needs its own playbook. In B2C, you are much more focused on
an individual user, because they are also the buyer, and the internal stakeholder incentives
are much more aligned. This course is built around five main sections. Section one is sourcing ideas,
and in that section, we'll unpack interviews, site visits, surveys, tech debt, internal channels,
market research, and competitors, all of which are crucial to you having a quality funnel of
ideas that you can work through. In section two, we'll focus on shaping ideas, including concepts
like appetite, breadboarding, fat marker sketches, risk analysis, crafting epics, and a hypothetical
scenario that will bring all of the concepts we've covered so far together into something that is a
realistic workflow. In section three, we'll unpack pitching and prioritization, which is at the heart
of product management. That'll include prioritization frameworks, pitch skills, facilitation skills,
product roadmaps, prioritization of bugs, and a practice exercise that will give you the blueprint
to put together world-class pitches that attract significant investment. In section four, we'll
focus on execution. That will include writing technical specs in the form of tickets, scoping
and estimating the size of your projects from the bottom up, project management frameworks that are
best practice in B2B SaaS, and then we'll unpack individual frameworks which have different use
cases like Lean, Kanban, Scrum, ShapeUp, and how to roll out those techniques in your organization.
Finally, we'll take a look at the QA process that you should be aware of, because that is part and
parcel of good execution. Then, in section five, we'll look at product marketing, one of the most
overlooked aspects of product management courses. That section will round out the
day-to-day workflow of product managers, which is the product idea lifecycle, with feature launch.
But we'll go further. We'll look at companies' go-to-market strategies, including sales-led
growth and product-led growth, and how that impacts what you do as a product manager. To do that,
we'll use the buyer cycle model as an organizing framework that makes all of your decisions as a
product manager so much easier. Each stage builds upon the last, giving you a practical,
end-to-end workflow with tangible skills that you can apply immediately. To wrap up, I'll briefly
give my advice on where you should focus your efforts for further learning to progress your
career quickly in the direction you want it to go. By the end, you won't just understand product
management, you'll know how to do it and how to do it well, and you'll be well-positioned to rise
quickly in one of the most exciting career paths in tech. Before we dive in, here's a quick guide
on how to pace this course so that you keep your momentum without burning out. Aim for one section
every two days. Day one, watch the videos and take light notes, and then day two, do the exercises
and quizzes and revisit anything that didn't click on the first pass. This rhythm keeps you moving
while giving your brain enough space to actually absorb and apply the skills, which is the whole
point. You can go faster, but the real value comes here from internalizing the workflows and the
concepts so that you show up as a clear and confident decision maker in your next B2B product
role. So, one section every two days, keep the pace steady, and do the exercises. Let's get into section
one, sourcing. As a product manager, you're the ideas gal or guy, but where do ideas come from?
This isn't some existential question about the nature of human consciousness.
It's more just the reality that product managers don't and cannot sit around twiddling their thumbs,
taking showers, taking baths if you're a fan of Harry Potter, or otherwise just waiting for some
stroke of inspiration. No, they put in place systems and undertake regular processes to
uncover problems. This doesn't take any particular creative genius. Most of us aren't particularly
creative, and to be honest, creativity can be a little bit of a double-edged sword. Yikes. Instead,
as a product manager, you must prioritize and sell painkillers. Not literal painkillers, obviously,
but rather things that solve a specific and pressing problem for stakeholders. Usually, this
is paying customers, but it can also be solving the problems of your sales or marketing teams,
for example, if it would help them boost revenue, or reduce effort, or your engineering team if it
will allow them to develop things faster. To do this, you have to listen, and I mean really listen.
People are going to bombard you with ideas. Not problems, ideas. Half-baked solutions to issues
that may or may not matter. Some of them are gold, most of them are noise, and your job isn't just to
say yes to everybody and then scramble to try and do it. It's to dig for the real problem and decide
if it's worth solving in the first place, and if it is, figure out how. How to do that most elegantly.
That's what listening means in product management. It's active, it's skeptical, and it's disciplined.
Because we're not in the business of building dreams, we're in the business of making bets.
And we bet on pain. Painkillers win, vitamins don't. Vitamins are nice to have. Painkillers fix
something that people care about right now. Vitamins are great, but they are much harder to sell.
To be clear, this is a metaphor. Please eat your fruit and veggies. If you'll allow me to stretch
the medical metaphor just a little bit further, listening isn't just asking your stakeholders,
what do you think I should build? That's like telling a doctor what's wrong with you and what
treatment you need and then asking for a prescription. A good doctor isn't going to
take you at face value. They'll ask for your signs and your symptoms and form an independent diagnosis
and determine the best course of action based on their expertise, not based on what the patient
told them that they needed. Your job as a product manager is to be the doctor, not just to give
patients everything that they ask for. This should all make sense, but to labour the point, let's look
at a classic case study taught in MBA programs. McDonald's milkshake case study. Milkshake sales
were underperforming. They tried the usual tricks, flavours, promotions, pricing tweaks, and nothing
was really moving their knee. And no one really knew why. So they reframed the question. Not
how do we sell more milkshakes, but what is the problem that milkshakes are solving for the
customer? It's a subtle shift, but it's a powerful one. Then they went out and actually watched people and
interviewed them. They got context. When are people buying milkshakes? Why are they buying them? It turns
out most milkshakes were not being bought as a treat or with a meal. They were being bought at
8am by commuters. One hand on the wheel and a milkshake in the other. Milkshakes weren't
breakfasts. It was instead a long-lasting, tidy, one-handed boredom buster to get through the drive
to work. So suddenly it's not a question of taste or price. It's a question of what job is this
milkshake doing? People weren't hungry. They were bored. So going back to our key question, what
problem is being solved by milkshakes here? It's not about taste. It's not about health. It's to cure
boredom. Specifically, it's to keep commuters occupied and full while they're stuck in traffic.
If that's the case, what's the obvious solution? Is it to make it thicker? Well, that's a little
risky actually because the flavor and the mouthfeel have been researched to death. Qualitatively,
people love the taste of it. The challenge was to make the milkshake do its job better
in terms of alleviating boredom without compromising on what did work about the product.
So I'm hoping I've led you to a reasonably obvious conclusion. They made the straws thinner. It was
a super successful strategy. It was elegant, it was cost-effective, and it addressed the underlying
need and it didn't throw out years of research that had already been undertaken to get the product
to where it was that was qualitatively enjoyed. But crucially, absolutely no one was coming to
McDonald's asking for thinner straws. They just weren't buying that many milkshakes and the company
wanted them to buy more. Arriving at this solution required a combination of a couple of things.
First, listening to customers carefully, not just asking for requests. Second, observing their
behavior. Third, inferring the true need, which was alleviating boredom. And then fourth, deploying
a targeted minimalist intervention. In this module, we're learning how to find problems like the
milkshake problem. The real jobs that customers are trying to get done, not just the ideas that
they throw at you. Because part of your impact as a product manager depends upon what makes it into your
ideas. Here's the reality. In a typical B2B product, only about half of all real problems will even get
raised in the first place. Of those, you only have time to properly shape around 20%. You might
formally pitch about 10%, plan half of those, and then actually build maybe three quarters of the
10% that you actually plan. So in the end, you're solving just two to three percent of all problems
that you could. That's why creating a funnel that systematically raises important problems really
matters. For the rest of this module, we're going to focus on that first step. So you're primed to
deliver real impacts by starting with the right ideas. That ends my rant. Ideas come from problems,
not solutions. And in the ensuing lessons, we'll look at how to surface those problems.
If that concept isn't burned into your brain yet, I give up. See you in the next lecture.
One of the best ways to unearth customer problems is simply by talking to customers.
Interviews allow you to dig deeper on customer problems through probing questions, which,
if posed correctly, can get to the heart of issues faced by your customers. You can also get intel on
their willingness to pay, which can prove really important in pricing decisions. This is our first
substantive skill session, and it is a little dense, but it's worth pushing through. People who
it's just talking to customers big deal tend to make the worst mistakes when interviewing.
The kind of mistakes that lead to biased insights because they don't take the discipline
seriously enough. So with that little warning, let's get into specifics. The first thing we'll
cover is getting interviewees to talk in the first place. Getting people to say yes to an interview
is half the battle, especially in B2B, where your users are quite often busy professionals.
Here's how to increase your chances of getting a positive response. First, you want to know your
advance. In sales, an advance is the next small step that somebody agrees to. In this case,
it's the interview with a specific time commitment, say 15 minutes. Don't say,
can we meet up to discuss our new product direction and get your commitment to some
ideas we're going to ship soon. That kind of feels like a sales pitch or a trap.
Good salespeople use incremental, easy to agree to steps. Second, be personal. Generic email blasts
readily get ignored. Address them by name. Mention something specific about their usage or role and
show that you've done your homework about them as a person. Be valuable. Let them know what's in it
for them. Whether it's early access to a new feature, influence over the roadmap, or just
being heard by somebody who can actually act on what they want. That's really important in getting
them across the line to actually want to speak with you. Fourth, this is not a sales pitch. If your
message sounds like marketing, it's going to be ignored, or worse, treated with skepticism. Fifth,
make them feel special. People like to be seen as important, so frame the invitation like they've
been specifically chosen because their opinion matters. And mean it, it does matter. Sixth,
appeal to their better nature. Sometimes a simple, we'd really appreciate your help goes a long way.
People generally do want to help, especially if they believe it will improve the product that
they rely on. So I'm not going to bore you by reading out an example email, but feel free to
screenshot this and use it as a template. I'll also put it in the lesson notes. It's not perfect
because it is generic, but it has the key beats which you can improve on with your own style and
contextual adaptations. I've put in brackets things that you'd want to substitute out so that they're
Before you even start interviewing customers, it's important to be intentional about who you
talk to because in B2B SaaS, roles and motivations vary quite a lot. Know who you're interviewing,
be clear on their role and their relationship to the product and to their business. Otherwise,
you might misinterpret what they say. Get a broad cross-section of these people too,
across industries, company sizes, experience levels, and usage patterns,
and include both day-to-day users and also decision makers. Day-to-day users are the
people who live in your product. They'll tell you about friction and shortcuts and
real workflow needs, whereas decision makers, they might not use your product quite so much,
but they are the ones who approve budgets and their priorities are different and different
in important ways. Include incidental users and stakeholders. These are adjacent roles like
managers, admin, support teams, people who are affected by the product even if they're not the
main user. And just remember that different users have different drives. They care about
different things like usability, ROI, integration, control. It really depends on their role and a
good product strategy accounts for all of them. Once you're in the room with them, virtual or
otherwise, how you run the conversation makes all the difference. Here are some key techniques to
keep the interview useful and honest. First, don't talk about your solution. The moment you try to
as opposed to their problem, people start to try to validate your product to make you feel good and
you lose the chance to hear what they would do without it. Also, ask questions, don't give
opinions. You're there to learn from them, not to teach them. So keep your own views out of it and
let them do the talking. Third, create an environment of comfort. People open up when they feel safe
and that means being warm and casual as the interviewer and making it feel more like a
conversation than an interrogation. And related to that, don't undermine the situation you've
created with awkward questions. So avoid leading or accusatory phrasing like, why didn't you just
do X when you face this problem? It makes people defensive and it shuts down the useful detail
they'd otherwise potentially give you. Don't react negatively to the answers. No matter how
surprising or frustrating their answer is, stay as neutral as you can. Any sign of judgment from
you as the interviewer will change how they respond from then on because they kind of want
to avoid awkwardness where they can and be polite. And then finally, guide, don't force. It's your job
to gently steer the conversation, not to control the conversation. Give them space to explore their
thoughts. That's where a lot of the insights are. Beyond those general techniques on running the
interview, the quality of your questions can make or break it. Let's look at what works and what
doesn't with some examples. First, open-ended questions tend to be good and closed questions
tend to be bad. A good question would be, can you walk me through how you complete task X? And a bad
question would be, do you use our product every day? Open questions get stories and closed ones
get a simple yes or no. That doesn't really tell you much. Avoid hypotheticals. A bad hypothetical
for example would be, if you had unlimited time, what feature would you build? Hypotheticals make
people guess. They're not sharing their real experience and that makes their answers less
reliable. Don't lead the witness. A bad example would be, you find this feature pretty confusing,
don't you? A good example would be, what was your experience with that feature? You can see that one
is open and gives them space to say what they actually think. The other one pushes them towards
an answer that you expect. Don't do that. Stay neutral. Don't ask questions that encourage
lying. An example of this would be, you never have any problems with our product, do you?
This pressures people to say things that sound good rather than what's true. If you feel like
you need practice on these questions, never mind. We will unpack some do's and don'ts of how to
phrase questions in our surveys lesson and many of the same principles do apply. And also, always
remember this fallback which is, can you tell me a little bit more about that? That's something that
you can use when you hear something surprising or unclear or there's a hint of something that's
important that's just beneath the surface and you need to prod them to unpack it a little more. So
with those general principles in mind, let's look at particular kinds of interviews that you're
likely to conduct because they're not always going to be used for the same purpose. The first type of
where you're trying to get to know customers and identify problems that they have.
Here are some key considerations in those types of interviews. Firstly, as we mentioned, use open-ended
questions. Start with these open-ended questions and invite customers to tell stories and reveal
the why behind what they do rather than just confirming your assumptions. Focus on broad
business problems. You're not yet at the point where you're solving a specific feature request
in an exploratory interview. You're solving a business problem. So aim to understand the bigger
challenge that the customer or company is facing. Kind of like we looked at with that McDonald's
example in the last lesson. Get to understand the user's day-to-day workflows in their job.
Dig into how they actually spend their time. Understanding real workflows helps you identify
pain points, inefficiencies, and opportunities that aren't always obvious to you or to the user. Also,
don't narrow the focus to your product specifically and that is very tempting to do.
Avoid anchoring the conversation around your product too early because it just invites biased
feedback and cuts off the most valuable parts of the discussion when you're just trying to
understand their business. Remember, in these conversations, you're not just listening. You're
actively hunting for key patterns. You're looking for business context. You want to understand the
broader business environment, the goals they're chasing, what pressures they're under, and what
constraints shape their decisions. You also want to understand how the customer currently meets
those needs with or without your product. Explore what they do today. Whether it's using your
product or a competitor, a spreadsheet or duct tape or willpower, whatever it is, this is where
the unmet needs and workarounds come to life. Next, you have validation interviews, which is
where you test whether your ideas are actually valuable and that means they need to be handled
carefully. These can be used for something that's not tech debt or bugs. Usually, it's for validating
new features or work problems or problems to solve, not for reactive sort of small picture issues.
Be aware of how easy it is to bias customers in doing this, in particular through politeness.
Customers, as I mentioned, do try to be nice, which means they might agree with you,
smile, or even say, sounds great, even if they never had any intention of using it.
And also, don't defend your idea. If they push back, don't argue. You're not here to win, you're here to
learn. And likewise, don't sell their idea. Don't try to convince them that it's good. If it is, it should
resonate with them without a pitch. Don't try to exaggerate your idea. Stick to the plain vanilla
version. The more you hype it up, the less honest their reaction is going to be. And as I mentioned
already, do not get offended. Don't take it personally if they don't care for your idea.
It's not a rejection, it's valuable feedback and it could save you a lot of time and money.
The next type of interview is a satisfaction interview and it's your chance to go beyond
the survey scores and uncover what users really think and feel about your product.
Use it to supplement pulse and relationship surveys for deeper insights. They're not a
replacement for surveys because they don't have the same scale, they're less efficient,
but they do help you go deeper and help you understand the why behind what users say in
the NPS or the CSAT scores that they give you. Key questions here that you'll want to cover off on
in these interviews are things like, what's your biggest source of frustration with the product?
Start by asking where things break down for them. This helps you find the sharpest pain point that
might not show up in usage data. What's the one thing you would implement to make it better?
This gets them thinking constructively and reveals what they're craving
that your product doesn't yet do. Another one on the opposite side of that coin,
what is the one thing that if removed would most harm its value? This flips that perspective,
right? It highlights the parts of the product which are truly core to their workflow
and which you should really emphasize as keeping and improving. And then, of course, remember,
that's interesting, tell me more about that. No matter what they say, your most powerful move
is to stay curious, dig deeper, and find those additional insights. Efficiency interviews help
you see how people actually interact with your product in their real work environment, not just
how they say they use it. In particular, they're used to understand how users do and don't use
your product at work. The goal here is to uncover where your product fits into their workflow and
where it doesn't. Here are some considerations that you should take into account when running
interviews that focus on efficiency of use. First, ask task-based questions to prompt them to walk
through their process, ideally using your product live while they explain it and show you how they
use it. Secondly, watch closely. What people do often tells you more than what they say.
Take note of how they go about things. Clicks, shortcuts, habits that you weren't familiar with.
These reveal how intuitive or clunky your design actually is. Look for unnecessary steps or
workarounds that they use. They're signals that something's maybe broken or missing or at least
suboptimal. Also, pay close attention to any hesitation or uncertainty when they're using your
product. These moments point to usability problems that you won't find in your analytics quite so
easily. And finally, ask how easy it feels. This captures the emotional layer of user experience
and that strongly influences satisfaction and customer retention. That's it for interviews and
thank you for staying with it. They may seem like intuitive things but they will make a big difference
in how good the data is that you collect. Usually this is the sort of thing that people have to get
corrected on by their seniors, which can be a little bit embarrassing. You've definitely spent
your time well brushing up on these fundamentals and people are going to notice your interview
skills when you get a product management job. They'll see you as being technically sound and engaging.
You'll get just as much out of our site visits content, so I look forward to seeing you in that
one too. When you're doing a site visit, you're not just watching people, you're watching roles.
And those roles break down into a few useful types. First up, primary users. These are the ones that
the product is actually built for. If it's a social media platform, they're the ones creating
and sharing content, not just scrolling. If it's a CRM, it's the sales reps. Adding leads, firing off
nurture emails, updating pipelines. They're in the trenches and their pain matters most. Then you've
got secondary users. They use the tool but more in sort of an auxiliary capacity. In a CRM, think of
the admin who sets permissions, manages billing, resets passwords. It's important, yes, but it's not
core to the value proposition of your platform. Next, you have your power users and these are your
nerds and I say that with love. In a project management tool, they're your product managers,
for example, or scrum masters. The ones who figured out every little shortcut, every edge case, every
workaround. They stretch the product to its limits and in doing so, they'll find bugs and they'll have
strong ones. On the flip side of that, you've got your novice users and no, that's not an insult,
it just means new. First-time online shoppers fumbling through a checkout, a junior hire who's
been dumped into a SaaS tool with zero onboarding. These folks show you friction fast. They don't know
where all the guardrails are because they haven't been habituated to look. So in summary, it's helpful
to broadly characterize user types into four groups. Primary, secondary, power, and novice and this will
help you to contextualize your insights. In terms of techniques to use when observing behavior,
remember, when you're doing a site visit, your goal is not to run a usability test in disguise.
This can be easily automated. Instead, you're there to observe real behaviors in a physical
context, not to get people to perform for you. So first up, observe their natural behavior. That
means don't hover, don't lead, don't make it weird. Let people do what they would normally do, where
they click, where they get stuck, and what they ignore. You'll find that you learn a lot more from what
they don't say. That said, it does help to use a think-out-loud protocol. Just ask them to narrate
as they go, what are you trying to do here? What are you expecting to happen? This gives you insight
into their mental model, not just their actions. And take detailed notes. This seems obvious, but
where things fall apart is when people don't write down exact quotes or reactions or anything that
surprises you, because you will forget it otherwise. Also, give users tasks, real tasks, not just
can you click this button. You're trying to see where the tool supports them and where it quietly
sabotages their progress. If you can, try to record user interactions. Video, screen, audio, whatever
they'll let you do. It does free you up to watch instead of scribbling, and in doing so you might
miss things if you're rapidly taking notes. And then finally, ask open-ended questions. I know I've
said this a lot of times, but don't say, do you like this? Or, is it clear? Ask, what did you expect to
happen? Or, what would you normally do if this didn't work? Or, what's the most annoying part of this
process? The goal is insight, not validation. You're here to not prove your design is great, rather
you're here to watch it break. And watching users do that can be really insightful. At the end of
your day of observations, if you're like me, you'll have been scribbling half-coherent notes like a
madman and trying to get everything down before it leaks out of your head. And now comes the hard
part, which is making sense of all of those notes. First, don't get bogged down into the weeds. Yes, the
details matter, but only if they point to something bigger. You're looking for patterns, themes, and repeated
pain points, not obsessing over one oddball comment from somebody who's having a weird day.
From there, you can start to build out your user personas. And no, I don't mean naming them like
Marketing Mary and giving them a golden retriever and what she likes to drink for coffee in the
morning. I mean real user profiles based on what you saw. So, what are their goals? What's getting
in their way? What workarounds are they using? Generalizing is helpful within reason. You're not
trying to capture every single edge case, you're trying to explain what's typical, what's representative
of behavior that you actually need to design for. And then after doing that, that's when you generate
user stories. Not the tier a ticket type of user stories, yet we will get to that, but in terms of
as a gap, I need to gap so that I can gap. And what this does is it helps you to translate what you
observed into product logic. The goal is to make your insights actionable, and we'll talk more about
what that actually means later, and how you can use those techniques to make your tickets better.
But the idea is somebody should be able to build something useful based on your synthesis of
information, and then share it with your peers. Of course, with your team, with other PMs, with
your engineers, and your designers. Get the signal out of your head and into the room with your
colleagues, because that's how it turns it into better decisions in the long run. It shouldn't be
all living in your head. Now finally, on site visits, let's talk ethics. When you're doing site
visits, you're stepping into somebody else's space. Be transparent about what you're there for. Don't
pretend that you're just there for a chat when you're clearly taking notes. Tell them what you're
doing, and why you're doing it, and how it's going to be used. You'll get better data if they trust
you, and you won't blow up any relationships in the process. And in a B2B context, that actually
does really matter. You can't churn through customers the way you might be able to in B2C
in the pursuit of learning. Second, respect their time. You're not the main character in this office.
You're a guest, and they have real jobs that they need to do. So keep your questions tight,
your tasks relevant, and if someone looks like they need to get back to work, then just wrap it
up. And third, maintain confidentiality and privacy. You might see whiteboards with sales
titles, overhear sensitive conversations, or accidentally learn things that you probably
shouldn't have. Don't document or share anything that could get somebody into trouble. Blow
screenshots, change names, be professional about how you deal with user data. Fourth, don't anger
your clients in being there. This one's obvious, but it happens more often than it should. Don't
criticize their systems to their face. Don't correct them on how to use your products. Don't
act like a know-it-all tourist. You're there to observe and not to judge. And finally, and this
is key, you're not doing a PhD. You're not there to write an academic paper or unearth deep truths
about human behavior. You're there to get insight that can be commercialized. That's the job,
and that's okay. Okay guys, thank you for staying with me through that really important
lecture on site visits. Such a powerful tool for you to use in many B2B contexts, especially if
it's in an enterprise and sales-led business. They're only useful if you approach them right,
with a clear structure, strong ethics, and a focus on action, not just academic curiosity.
So take notes, spot patterns, stay curious, and be commercial.
Our next module is on survey best practices. That one does get a little bit technical,
but it is massively worth your time. Because with surveys, if you do make mistakes,
you're making them at scale. So far, we've focused on uncovering problems faced by your customers
and your colleagues, which is exactly where your attention should be most of the time.
Meanwhile though, competitors are a reality. If they're doing things better, faster, or cheaper,
you risk losing customers and missing out on new ones. You can gather an enormous amount of valuable
competitive intelligence on your desktop now, and I strongly recommend that you don't neglect it as
a source of insight. That being said, depending on the industry that you're in, this can either be
very easy or devilishly hard. But it's worth trying your best to source, because your customers
generally will have other options, and they'll be weighing them up as to whether they go with you
or someone else at each stage of that biocycle model that we referred to in that last lesson.
If you're in an enterprise software setting, assume that they have people reaching out to them
and who are trying to woo them with competitive offers. So what sort of information do you need
to get to neutralize competitive threats, or to be a competitive threat yourself?
Forms of competitive intelligence include pricing, features, release timelines, sales tactics, and
go-to-market strategies of other teams, customer win-loss insights, hiring trends, and organizational
changes, and mergers and acquisition activity. Just be aware that there are some blurry boundaries
between obtaining information ethically and not. So where do you get competitive intelligence?
There are above-board ways to do it, as well as areas where you might want to do it a little bit
more carefully. And then there are areas where you should be very, very ethical. Let's start
with green flag tactics that you can use to get a handle on what your competitors are doing.
First, you can monitor competitors' online presence, including scraping. Say that with an asterisk.
Track changes on their website, blog, and feature pages to identify positioning shifts on new
capabilities that they're advertising and online presence, including scraping. Say that with an
asterisk. Track changes on their website, blog, and feature pages to identify positioning shifts
on new capabilities that they're advertising and online presence, including scraping. And
automate this with toolbars. Always check that you can automate any data or content updates or
structural changes. Similarly, you can track publicly available pricing information and
automate this with tools, even if tiered or partially secure, can reveal packaging strategies,
target segments, and position changes in video and stacks. This might help you to anticipate
Of course, whether or not this is readily available to you will depend a bit upon your
industry and the industries of your customers.
In smaller industry sectors, you'll frequently run into opaque pricing, and even in broadly
targeted CRMs like Upspot or Salesforce or something like that, you'll see transparent
pricing for small to medium business customers where the sales and onboarding is more automated,
then contact sales for enterprise prospects where pricing is more of a point of negotiation
and customised implementation.
Public reviews are also a great place for competitive intelligence.
Sites like G2, Captera or TrustRadius offer direct insight into what customers like or hate,
often with more candour than NPS surveys run by that business.
Pay close attention to recurring themes or ratings volatility with those businesses.
Likewise, you can also review job listings.
Job ads hint to the company's roadmap or strategic focus.
For example, five openings for machine learning engineers suggest a push into automating or
analytics or whatever.
Look for roles that mention specific customer segments or products.
Also, attend public events.
Webinars, conferences and product launches often reveal roadmap hints, messaging priorities
and how competitors pitch themselves to the market.
If you're allowed, record them or take screenshots for team debriefs.
Ask your own customers as well.
Your customers will often have trialled or used competitors before, so ask what they
liked or disliked and why they switched to you.
Consume analyst briefings.
Gartner, Forrester, even niche analysts often compare vendors directly and outline buyer
trends.
These briefings can give context onto why you win or lose those requests for proposals.
Review publicly available release notes.
Release notes and change logs reveal where product investment is going and how quickly
a team shifts.
In B2B SaaS, they can help you assess whether a competitor is stabilizing or accelerating.
Moving into more borderline tactics, here are common competitive intelligence practices
where I would suggest that you tread carefully.
If all the other ones are above board, these ones can be a little bit more ambiguous.
Note, some of them are honestly quite effective, but at the end of the day, remember that you're
probably going to be working for a company on a salaried position where you are very
easily replaceable.
So be circumspect about whether you're drinking the Kool-Aid at this company and doing anything
that you think might be unethical.
Here are some tactics which might not be technically illegal, but which you could be asked to do
and which you should view skeptically.
Signing up for a competitor's free trial is a classic one.
It can be legitimate, but using your real name may flag you or breach terms of services
around competitor's use and using fake details can cross ethical lines.
If it's not a competitor and you're just getting a free trial for ideas in an analogous
industry, then I'd feel less queasy about this strategy.
For example, if you want a legal practice management system and you're interested in
seeing what cutting-edge CRM tools are doing and whether there's anything that you might
learn from a bigger industry, I think this would probably be fair play.
Engaging in private Slack or Discord groups is also tenuous, especially if your affiliation
is unclear.
Passively listening, maybe, but contributing and asking questions to fish for information
without disclosing your affiliation.
It's bordering on a little bit dodgy.
Scraping is something to also be a little bit aware of.
I know I had it in that previous column.
That's because sometimes it is fine and totally illegal, but again, mindfulness about competitor's
terms of service is important.
Steer clear of scraping gated content, that is, something behind a paywall or login.
I wouldn't recommend doing that at all.
Also, using personal contacts at a competitor is something you should avoid.
It puts you and your friends at risk, potentially, and at the end of the day, this is corporate
work.
It's important, but it's not worth burning personal bridges over, in my opinion.
And similarly, DMing people to bait them into oversharing on LinkedIn, that's no good.
Just a general rule of thumb, actually.
Don't be deceptive.
Now, I'm going to whip through what I would consider clearly unethical, if not illegal.
It should be obvious, but just in case you get a little bit too excited in your new product
management job, don't impersonate people to obtain confidential data.
Don't access confidential documents, whether shared intentionally or not, if it wasn't
meant for you.
Don't open it.
Don't read it.
Don't hire people just so you can get inside scoops at other companies.
Of course, you can hire people from competitors, provided that they aren't breaching their
non-competes, which is a matter for them.
But if you do so just to get their info, that's sort of borderline corporate espionage.
Don't do it.
Don't fake accounts to bypass competitors' screening protocols, which pretty much falls
under impersonating people to obtain their data.
And don't share screenshots of betas without consent.
Always ask.
And finally, don't make fake support or sales calls.
Again, like free trials, just don't impersonate people and try to access a roadmap or pricing
strategy or whatever.
Are you likely to get caught in doing these things?
Honestly, at the level of a product manager, in most cases, no, but it's simply not worth
your time.
The benefit to your roadmap will be marginal in light of all of the other inputs that you
have.
If anything, I would say that being too competitor-focused can distort your priorities too much, and it
can get you chasing your tail, and the reputational risk isn't worth black hat techniques that
I've listed here.
Don't let it consume you instead of acting on real customer problems.
Remember, their roadmap and strategy might just suck anyway.
On a side note, you might have noticed I sequentially bolded the text on that slide to help you
focus on what I was talking about.
That was in fact incredibly time-consuming and honestly probably not worth it, so I may
not do it again, but hopefully it helped when I did it this time.
Next, we'll look at marketing intelligence and bring it all together.
So market intelligence is a broader discipline beyond competitive intelligence, and it's
helping you understand the external environment.
That includes trends in customer behavior and competitive intelligence, which you'll
have been researching already, but also extends more broadly to industry shifts, and regulatory
changes, and emerging technologies, macroeconomic forces, things like that.
This is the sort of thing that can consume a lot of your time, so my recommendation is
to keep the pulse of it on a surface level so you know what's going on, but otherwise
don't try to be too reactive to market intelligence.
Otherwise, you're never going to achieve the goals that you set out to achieve, which
require effort, focus, and lead time.
In short, be like this German shepherd, ignoring bright shiny objects, instead of being like
this admittedly adorable golden retriever who gets distracted by all the delicious treats.
Look at him.
That being said, do your best to keep the finger on the pulse.
Give yourself a morning briefing of your tech news and publications.
I would usually allow myself like 10 minutes with a coffee in the morning.
Importantly, I very often did nothing with that information.
It was more important to just be across the news generally, and to make sure that my
explicit decisions were based on a current understanding of the world.
Adjacent industries are also great for pre-validating ideas.
Let's say, again, legal practice management.
I just keep thinking of that, probably because of my law background, but let's say you work
in a legal practice management software company, and you see how a construction project management
tool uses timeline-based task visualization, and you think, hmm, that might be helpful
in managing legal projects.
That would be an example of validating across other industries.
Similarly, consumer-facing applications can be a great source of UX and UI trends.
They tend to be further ahead in this regard than B2B, just because of faster adoption
cycles and greater scale in B2C, which allows for better data-driven decision-making by
their product managers.
So feel free to piggyback off their trends.
There's nothing wrong with that.
And closer to home, you might establish customer and industry advisory boards with stakeholders
from your customer base, just to provide their insights on industry trends, problems that
they're facing both in technology and not.
And I've established these personally in my previous roles, and I found them to be very
valuable.
And quite often, it can make customers feel special and create a sense of loyalty to your
product, which goes a long way.
Social media listening is another one.
You're looking for mentions of your brand by name and industry, quite powerful.
There are a number of tools that aid in this, and I'd simply recommend Googling them.
Liaising with your marketing department, what you might implement there.
And then finally, if you can, commission independent surveys from high-quality research
houses to get a sense of customer sentiment in your sector, although this can be a pretty
expensive option.
So just make sure the economics of that makes sense.
As with all your research, your challenge is synthesis.
That is, connecting the dots to get something cohesive that you can actually do something
with.
One popular synthesis technique is SWOT analysis.
That is simply categorizing your market, competitors, customers, and internal information into
strengths, weaknesses, opportunities, and threats to contextualize this information
and form the basis for action.
So you would have strengths, which is the internal advantages or assets that are giving
you a strong edge, like a strong customer base or intellectual property.
Weaknesses, which is internal limitations compared to others, say for example you're
poorly resourced.
Opportunities, which are external trends or conditions that can be leveraged for growth,
such as your tech stack becoming popular, improving your competitiveness as a hire of
talent.
And then threats, which is external challenges or risks, like AI creating a risk to your
user base charging model because it makes your customers more efficient, so they don't
need to have as many users.
That might be a threat.
This is a helpful framework because it maps onto different business problems that you
might be experiencing and it can help you prioritize them strategically.
Another helpful framework is what I would call a competitive landscape, so that you
can contextualize who your closest competitors are, who to keep an eye on, and where the
opportunities might be for expansion in underserved markets.
Say for example you're in software reviews and you're trying to carve out your niche.
Maybe you map the competitive landscape based on primary go-to-market and revenue models
on the vertical axis, so B2B sales opposite pay-per-click, and whether your competitors
are generic review sites or industry or software-specific review sites, for example, on the
horizontal axis.
If that's how you map the industry, consider the top-left quadrants.
You've got Yotpo and Trustpilot, who serve companies generally regardless of their industry
in terms of reviews, and their marketing strategy is B2B sales.
They sell review collection tools, widgets, reputation management, and analytics, and
their sales involves onboarding, contracts, and account management.
In the right-hand quadrant, you can see you've got SoftwareAdvice, TrustRadius, and
SaaSworthy.
So their go-to-market strategy is similar.
However, they target software vendors in particular, so they're industry-specific.
So there'd be more direct competition to you in this example.
In the bottom-left corner, you've got Google Reviews, which is kind of the king of all
review platforms, I guess, but focuses more on businesses with physical addresses because
their infrastructure is based upon Google Maps and Google My Business profiles.
As a result, it's more useful for things like law firms or restaurants, where local
discoverability actually matters.
It operates on a pay-per-click model.
However, it is based on visibility in search results.
And then you've got the bottom right-hand quadrant, where you've got Captera and G2.
They're more based on pay-per-click, where vendors bid on listings and pay for clicks
to drive lead volume.
Captera and GetUp are examples that are highly SEO-focused and designed for lead generation
rather than reputation, but they are software-specific.
So as a software-specific reviews provider, you might be thinking, what are the possible
threats from generic review services like those on the left-hand side of this graphic?
And should I be taking an account-based or a pay-per-click strategy?
Basically, where is the market more busy?
You can, of course, map whatever variables you want on this sort of matrix.
Just try to ensure that your limits on either access are mutually exclusive in some way
and as much as possible comprehensive, and that these differences are meaningful from
a business strategy perspective so that you get useful differentiation by which you can
make better decisions about where you go in your market.
Nice work on finishing sourcing ideas.
That is the bit that throws most new product managers, that moment of, wait, how do I actually
decide what to build?
Well, you've just answered that.
Now that you've got the fundamentals, automate what you can.
Surveys, idea boards, even using large language models to make sense of messy data.
For the rest, build habits and routines.
Product managers who systematize idea flow stand out fast.
The ones who wait for inspiration stay reactive and end up getting overwhelmed.
This module tapped into your organizational and systems thinking side.
Next, you'll get to flex the creative problem-solving part of your brain as we move into
shaping.
After that comes the analytical rigor of pitching and prioritization, and that's when it all
really starts to click together.
But for now, shaping.
