How can product designers absorb the PM role instead of going the other way around—especially when they aren’t exposed to the business side?

Why Read This from an HCI Perspective

This article clearly illustrates the role boundary “shifts” that are common in HCI/UX practice. The flow where PMs quickly drive prototyping and decision-making can look efficient, but in reality there’s a risk that user needs, design principles, and stakeholder alignment get skipped. From an HCI perspective, it’s worth reading to understand under what conditions this becomes innovation—and under what conditions it leads to a decline in experience quality.

CIT's Commentary

From a CIT perspective, this issue is less about ‘who does what’ and more about ‘what kind of validation is performed.’ It’s a natural change for both PMs and designers to use tools like LLMs to prototype quickly. The key is whether that work reflects user context, business goals, and implementation constraints together. The current discussion may look like role encroachment, but it’s really about how the organization designs the connection between discovery, definition, validation, and implementation. Designers should explain their judgment in business language rather than ‘absorbing’ the PM role, and PMs should create a collaboration structure that brings user evidence earlier rather than replacing design judgment. In the end, what matters isn’t speed itself, but an operating model that ensures fast experiments lead to consistent experiences and clear accountability structures.

Questions to Consider While Reading

• Q.Even if PMs and designers rapidly build prototypes together, at what point should user validation and business validation be included as a must?
• Q.To keep design from being pushed to the back burner in an organization, what business language and metrics should designers learn first?
• Q.In an environment where vibe coding spreads, how should HCI-based quality criteria be shared with the team?