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

Example Answer

I would first identify the affected platform users: developers, admins, operators or external partners may have different problems. I would combine tickets and usage evidence with observation of their current workflow, including workarounds and users who have not adopted the platform. I would state the specific problem and its consequence before choosing a feature.

Then I would compare credible alternatives: build, improve documentation or an existing interface, integrate an available capability, or defer. With engineering and operations, I would estimate implementation, migration, support and ongoing reliability costs, dependencies and security constraints. I would look at expected reach and strategic value, with uncertainty shown rather than hidden in a precise score.

I would test the riskiest assumption with an appropriate prototype or bounded pilot. A prototype can show usability or demand; it does not prove production scalability or willingness to migrate. I would recommend a staged investment only when the expected benefit and strategic fit justify the full cost and opportunity cost, with owners, acceptance evidence and a stop/reconsider point. Discovery is useful only when it informs that commitment decision.

Why this works

• It completes the investment decision with alternatives, operating cost and explicit evidence limits.