It's not enough for platform PMs to interview their direct users (developers). To build truly enabling platforms, you must also gain wider context by sitting in on the developers' own customer interviews. This provides deep empathy for the entire value chain, leading to better platform decisions.

Related Insights

After testing a prototype, don't just manually synthesize feedback. Feed recorded user interview transcripts back into the original ChatGPT project. Ask it to summarize problems, validate solutions, and identify gaps. This transforms the AI from a generic tool into an educated partner with deep project context for the next iteration.

The most effective first step to improve developer experience (DevEx) is not building automation or buying tools. Instead, conduct a 'listening tour' with developers about their daily friction. This uncovers high-impact, low-lift opportunities that premature solutions often miss.

A platform's immediate user is the developer. However, to demonstrate true value, you must also understand and solve for the developer's end customer. This "two-hop" thinking is essential for connecting platform work to tangible business outcomes, not just internal technical improvements.

Most engineers only interact with customers during negative events like outages or escalations. To build customer empathy and a product mindset, leaders must intentionally create positive touchpoints. This includes sending engineers to customer conferences or including them on low-stakes customer calls.

Stakeholders will ask "so what?" if you only talk about developer efficiency. This is a weak argument that can get your funding cut. Instead, connect your platform's work directly to downstream business metrics like customer retention or product uptake that your developer-users are targeting.

To stay relevant, tech platform companies must obsessively follow developers and startups. They are the primary source of insight into emerging workloads and platform requirements. This isn't just for partnerships, but for fundamental product strategy and learning.

The true power of UX research is aligning the entire product team with a common understanding of the user. This shared language prevents working at cross-purposes and building a disjointed product that users can feel.

Contrary to the popular belief that it's always detrimental, for product managers, context switching is a core strength. Fluidly moving between customer, engineering, and marketing conversations is essential for integrating diverse perspectives to bring a product to life.

Even at SpaceX, many engineers first heard from customers during a company all-hands. This feedback revealed the setup process was a huge pain point, leading to a dedicated team creating first-party mounting options. This shows that fundamental user research is critical even for highly technical, 'hard tech' products.

Observe Your User's Customer Interviews to Gain Essential Context for Platform Building | RiffOn