How would you figure out whether a new platform feature is worth building?

Example Answer

Before building a new platform feature, I would start by identifying which users actually feel the problem because platform products often serve multiple audiences at once: admins, developers, operators, or partner teams. I would review support tickets, usage patterns, and known workarounds, then talk directly to a small set of representative users to understand what job they are trying to do and where the current experience breaks down.

Once I have that, I would turn the learning into clear problem statements and validate the proposed direction before committing a large build. That might mean prototypes, design reviews with customers, or testing a lighter-weight version first. The goal is to avoid building a technically elegant feature that solves the wrong platform pain point.

Why this works

• It shows that platform discovery starts with user segmentation, not assumptions.
• It combines qualitative and quantitative inputs.
• It emphasizes validation before committing engineering effort.