Experiment, Feature, Platform

A product-development distinction among work intended to answer a question, work intended to provide an ongoing user capability, and work intended to support multiple capabilities. Experiment, feature, and platform imply different evidence, support, and maintenance needs; they are not mandatory stages every idea must pass through.

These three labels distinguish what an initiative is for. An experiment seeks useful evidence, a feature offers a capability to users, and a platform supports other capabilities. The same piece of work may evolve across those roles, but progression is optional. An experiment that rules out an idea can succeed without becoming a feature, and a useful feature may never need to become shared infrastructure.

Define the intended consumer and the commitment implied by each role. A temporary trial needs an answerable question and a clear end; an ongoing feature needs support; a shared foundation needs dependable interfaces and maintenance. The labels help discuss those differences, but they do not authorize low-quality data, broken promises, or unnecessary infrastructure.

When to use it

When scoping a prototype, deciding whether to maintain a feature, or considering whether repeated needs justify shared infrastructure.

How it can help

Makes investment and commitment more explicit by asking what the work is currently for and who will depend on it.