A technically excellent product that nobody understands is a tree falling in a forest. Martina Lauchengco's Loved is about the discipline that ensures the tree is heard - and heard by the right people, in a way that makes them act. Product marketing, done properly, is not the function that writes the website copy after engineering ships. It is a foundational capability that shapes product strategy, informs discovery, and is responsible for the moment of connection between what the product does and what the customer needs to believe.
Lauchengco, a former product and marketing leader at Netscape, Microsoft, and SVPG, wrote this book because she watched a generation of product organisations produce genuinely good products that failed in the market not because of what they built, but because of what they said - or failed to say - about it.
The product management canon has given technology organisations sophisticated tools for discovery, delivery, and iteration. What it has largely ignored is the discipline of making the product land - of getting the right message to the right person at the right moment in a way that creates genuine adoption and enthusiasm. This is product marketing, and most technology organisations treat it as either a creative service function or an afterthought.
For engineering and product leaders, this matters because product marketing done well informs what you build, how you frame it, and how you measure whether it is working. Done badly - or not at all - it leaves the connection between engineering effort and customer value entirely to chance.
The first and most important reframe in the book is definitional. Product marketing is not about campaigns, copy, or channels. It is about three things: market strategy (who are we targeting and why), positioning (what do we want those people to believe about our product relative to alternatives), and go-to-market (how do we reach them at the moment they are ready to act).
Done at this level, product marketing is inseparable from product strategy. Who you are building for shapes what you build. What they currently believe about the problem shapes how you need to frame the solution. How they make purchase decisions shapes the experience you need to design around the product itself. Organisations that separate product marketing from product strategy are making decisions in each function that undermine the other.
Positioning is the answer to the question: what does this product mean to this customer, relative to what they already have or believe? It is not a tagline. It is not a value proposition. It is the complete context a customer brings to their first meaningful encounter with your product - and it is either something you design deliberately or something that forms accidentally.
Lauchengco draws on April Dunford's positioning framework to make the case that positioning is strategic work that should involve product, engineering, sales, and marketing. The output is not a document - it is a shared understanding of the specific context in which the product wins, expressed clearly enough that everyone who talks to customers can do so consistently.
Lauchengco identifies four fundamentals of product marketing: defining and refining the target audience, shaping and communicating the value proposition, enabling the go-to-market motion (particularly for sales and customer success), and being the voice of the market into the product organisation.
Most technology companies do some version of the third - they produce sales enablement material and launch communications. Very few do the fourth consistently. The voice of the market - the systematic input of market intelligence, competitive context, and customer sentiment into product decisions - is product marketing's most valuable contribution to the product organisation and its most consistently absent one.
The cultural fixation on the product launch as a moment - an announcement, a blog post, a press release - produces a failure mode where enormous energy goes into the launch event and almost none into the ecosystem of activity that determines whether the launch actually results in adoption.
Lauchengco describes the launch as a system: a set of activities across awareness, acquisition, activation, and retention that together determine whether the product reaches the people who need it and converts them into genuine users. Any single element of this system - however well executed - is insufficient on its own. Launch strategy is system design.
The insight that connects Loved most directly to the product management canon is about customer proximity. Just as Cagan argues that product managers need direct, unmediated access to customers to develop genuine product intuition, Lauchengco argues that product marketers need the same - and for the same reasons.
Product marketers who understand customers only through second-hand research and CRM data cannot develop the intuition needed to create messaging that resonates. The best product marketing comes from people who have spent significant time with the customers they are trying to reach - understanding how they describe their problems, what language they use, what alternatives they have considered, and what would make them change their minds.
If your product marketing team is primarily involved in producing content after engineering ships, they are not doing product marketing - they are doing communications. The difference is whether they are shaping the product or describing it.
Positioning is not the CMO's job. It is a cross-functional decision that affects every conversation your organisation has with the market. Who in your organisation owns the positioning decision, and does that ownership reflect the actual importance of the decision?
The most common reason good products fail is not product quality. It is that the people who needed the product did not understand it was for them, or did not encounter it at the moment they were ready to act. This is a systems problem with a systems solution.
"Build it and they will come" is a strategy that works approximately as often as it sounds like it would. The market does not naturally surface the products that are technically best. It surfaces the products that are best understood.
Your product launch is a hypothesis. The message, the channel, the moment - all of these are variables. Teams that treat the launch as a designed experiment, measure what works, and iterate are more likely to find the combination that drives adoption than teams that treat it as a single, high-stakes event.
Define your product's positioning in a one-page document. Who specifically are you targeting, what problem are you solving for them, what alternatives do they have, and why is your solution better for this specific customer in this specific context? Share it across product, engineering, and sales.
Audit your last product launch. What were the intended outcomes? Which metrics did you measure? What was the actual adoption rate thirty days post-launch? If you cannot answer these questions, your launch is not connected to a learning system.
Schedule time for your product marketing team to conduct customer interviews this quarter. Not survey analysis - direct conversations. Brief them to listen for the language customers use to describe the problem, not the product.
Map your go-to-market system. From first awareness through to active, retained usage - who is responsible for each stage? Where are the gaps? Where is adoption falling off? This is the system you need to design against.
Bring your product marketing lead into your next product strategy session. Not to communicate the strategy afterwards - to help shape it. The market intelligence they carry is an input to product strategy, not a downstream output of it.
"Product marketing's job is not to explain what the product does. It is to make the right people understand why it matters to them - and to create the conditions in which they can act on that understanding."
- Martina Lauchengco