This is a lot harder with feature work. My team might be working on a new API that enables team A to build feature A. Now someone interested in feature B needs

This is a lot harder with feature work. My team might be working on a new API that enables team A to build feature A. Now someone interested in feature B needs "just a small API change" to enable their feature B which "was promised to important customers to be available this month". It gets pretty fuzzy. Your idea of having some standard questions pre-answered is always helpful though. In this case that might be stuff like expected revenue. Of course in my example the person interested in feature B also needs a talking to for committing both fixed scope and fixed time externally (already bad) while not talking to all impacted parties ahead of time.