Episode #5: Taking Products from Development to Market with Hiro Kanno

A product can work as designed and still struggle in the market. The gap between development and adoption is where product marketing becomes essential. In Episode #5, LinkedIn Product Marketing Manager Hiro Kanno explains how PMMs shape go-to-market strategy, coordinate launches, and help product teams make better decisions with customer and market context.

What you'll learn

• How product management and product marketing divide ownership

• What a PMM coordinates after an MVP has been developed

• How customer, industry, and competitive insight informs the roadmap

• Why product constraints and pilot feedback can change a launch plan

• How structured communication can become a professional strength

Divide product strategy from go-to-market ownership

Kanno offers a clear starting point for understanding the two roles. Product managers own product strategy, working closely with engineering to shape the roadmap and determine how the product should evolve. Product marketing managers own the go-to-market strategy: how the product will enter the market, reach customers, and scale.

That division does not create a wall. PMMs contribute the voice of the customer, industry context, segmentation, pain points, and competitive information to product planning. Product managers, in turn, bring technical realities and product knowledge into launch decisions. Each role owns a different strategy while supplying inputs to the other.

Kanno describes the progression another way. A product manager may take a product from zero to one, while a product marketing manager helps move it from one to ten and from ten to one hundred. The distinction is useful because it keeps teams from treating launch as a final promotional step. Bringing a product to market involves its own choices, risks, and operating plan.

Treat launch as a cross-functional program

At LinkedIn, Kanno says the PMM acts like a general manager for the product's launch and go-to-market motion once the MVP is developed. The work can include planning charters and pilots, developing messaging, collaborating on pricing and packaging, creating the marketing strategy, enabling sales and customer success teams, and setting goals, timelines, and targets.

A launch may also involve BizOps, engineering, customer support, analytics, and other partners. Kanno estimates that ten to twenty teams can become involved depending on the size of the launch. The PMM therefore serves as a hub, bringing those groups together and program-managing the work toward a common outcome.

For product teams, the practical insight is to map dependencies early. A launch plan needs more than a release date and campaign. It needs named partners, shared targets, decision points, and a realistic view of what each function must deliver. Without that coordination, even a compelling product can reach customers through a fragmented experience.

Build feedback and constraints into the plan

Product and engineering constraints can alter a go-to-market plan. A major bug may delay a release. An unexpectedly demanding engineering requirement may make the original timeline unrealistic. Kanno emphasizes communication between PMM, product, and engineering so that launch expectations reflect resource needs and product readiness. Shipping on schedule is not worth delivering a poor product experience.

Charters and pilots create another important feedback loop after the MVP. They test whether the product and business elements, including pricing, resonate with customers. Participants may identify a missing feature, a confusing interface, or an awkward workflow that the team did not anticipate. Product and product marketing then work together to decide which feedback must be addressed before a wider release.

This collaboration is more useful than simply collecting a long request list. PMMs bring the market signal; product managers can propose product changes or workable alternatives. The shared question is whether a change resolves the customer's need strongly enough to support the launch.

Make structure a learned skill

Kanno also reflects on a weakness that became a strength. Earlier in his career, colleagues told him his communication lacked structure. During his MBA, he worked with classmates from consulting backgrounds to organize his thinking more clearly. A later consulting manager gave him a focused lesson on adding structure to his communication. Over time, people began to describe him as highly structured.

That lesson fits the launch work he describes. Coordinating many teams requires more than information. It requires a clear sequence, defined ownership, and communication that helps people understand what matters next. Structure is not a fixed personality trait. It can be practiced, tested, and improved.

Listen to the episode:

Listen to Episode #5 for Hiro Kanno's practical explanation of PM and PMM ownership, launch coordination, customer feedback, and the communication habits behind effective go-to-market work.