Product change template
Replace a feature before deprecation
Define an acceptable replacement, publish the decision, and keep the old path until the replacement is ready.
Contract dossier
The decision boundaries are visible before participation.
Review each value against the real product, affected group, and consequence before publishing.
Product or surfaceNorthwind Reports
ParticipantsRecent activity
MethodApproval
Result meaningImplementation-binding
Response promise14 days after opening
Example options
Compare alternatives with the same scope and consequence.
These values prefill Create. Replace them with options that are feasible under one shared set of constraints.
- 01Secure download centre
- 02S3 delivery
- 03Scheduled API pull
Contract guidance
Review the promise before publishing.
Define current users from product data. Ask about concrete replacement paths, not whether change is popular.
Escape conditions
Name the valid blocker in advance.
A binding result needs an explicit legal, platform, safety, or technical condition that can override implementation. The response must publish it if used.
Review in Create
Open the complete prefill before anyone can participate.
The editor keeps every value changeable. It does not submit or publish the decision automatically.