> Well, it depends: there are many strong technical reasons on each side, so it’s better to keep an open mind and not come down on either side. My heuristic in

> Well, it depends: there are many strong technical reasons on each side, so it’s better to keep an open mind and not come down on either side. My heuristic in this case is just to go with whatever option is simpler, and gives us the most flexibility to course correct in the future if we turn out to be wrong. Basically make it clear that in the absence of sufficient data to decide on the best course of action, we are being intentionally non-committal. Then outline what new information would be required for us to make a more informed decision one way or another (e.g. an actual customer asks for the hypothetical feature that we are discussing, or performance is insufficient, etc), and what actions and effort we would need to change course. When put like this, I find that everyone in the room usually ends up pretty satisfied with the plan.