For example, given the task of building a complex system under a time constraint, it's easy to exhaust the time granted, be it a week, a month, or a year. A complex system can always be more perfect, so you can always spend more time on making it better. A limited resource (e.g. a week) can force you to focus on the essential solution whereas an abundance (e.g. a month) can lead to frivolous design and overengineering.
The antidote seems to be organizational restraint, concrete milestones, and constant readjustment to keep in line with greater goals. Scope creep, perfect-as-enemy-of-good, and bike shedding are all aspects of this behavior.
This overspending problem happens a lot in startups too (though VCs sometimes pressure startups to burn fast for various reasons having to do with the next round, which isn't really a factor with Star Citizen and crowdfunded projects). It's crazy there aren't more widely recognized best practices for teaching founders how to handle this issue.
Reminds me of: https://twitter.com/mcgd/status/850347746452099072
"When the kleenex box is full, you take two. When it's almost empty, you might use one twice. That's why oversized financings are bad."
It seems like the better route would be for them to make the $10 million game, and then to ramp up from there.