Quiz: Are you a product guru?

Well done. Though it rarely feels like a good option, often postponing key decisions to focus on other work while the situation becomes more clear can be the most effective way to proceed. An effective analogy here: spinning your wheels when you are stuck in the mud.

Get more information if possible, by polls, approximate prototype implementation and A/B testing; build understanding of the use-case. If you're in a hurry and the feature is a fundamental requirement, do the cheaper option, but let people know it's "beta", not the final solution. Also, sometimes it's better to postpone than roll out a crippled feature that everybody hates.

Get more information if possible, by polls, approximate prototype implementation and A/B testing; build understanding of the use-case. If you're in a hurry and the feature is a fundamental requirement, do the cheaper option, but let people know it's "beta", not the final solution. Also, sometimes it's better to postpone than roll out a crippled feature that everybody hates.

Get more information if possible, by polls, approximate prototype implementation and A/B testing; build understanding of the use-case. If you're in a hurry and the feature is a fundamental requirement, do the cheaper option, but let people know it's "beta", not the final solution. Also, sometimes it's better to postpone than roll out a crippled feature that everybody hates.