4 ms·
>NASA managers have come to believe―usually correctly, Martin said―that “projects that fail to meet initial cost and schedule goals will receive additional fund
by whatshisface 8y ago
>NASA managers have come to believe―usually correctly, Martin said―that “projects that fail to meet initial cost and schedule goals will receive additional funding and subsequent scientific and technological success will overshadow budgetary and schedule problems.”
There's something else hidden behind this statement: NASA managers have also come to realize that proposals that under-estimate budgets are likely to look more attractive than proposals that accurately or over-estimate them. As a result, the equilibrium shifts and a certain percentage gets taken off the estimation for everything.
- mysterydip 8y agoThis seems to be common in the defense industry: overpromise and underdeliver, because they know good money will be thrown after bad in an attempt to finish a bad project once they get the contract.
- kevin_thibedeau 8y agoUntil Rumsfeld started waving the cancel wand and ruined some plans.
- forapurpose 8y agoIs there any evidence that Rumsfeld was more effective at managing budgets than other Secretaries of Defense? He liked to talk big, but he talked big about Iraq and was a complete failure and liar (including on the budget). Gates did a lot, canceling Cold War era projects such as the F-22 rather than throw good money after bad, especially with the U.S. fighting two insurgencies (for which advanced fighter planes were a waste). His successor Ash Carter refocused the Defense Department on planning and developing for future warfare, especially in the 'cyber' domain.
- maxxxxx 8y agoThis pretty much how you do it in a company too. You will never get the budget for 3 years but if the estimate is for 1 year then after that year you usually get more. I have also seen people getting penalized for delivering early because their estimate wasn't correct.
- AngryData 8y agoYup, if you need 10 million for a project, you quote 3 million and ask for more funding later on, otherwise you will never get any funding at all as they balk at the true costs of research and development.
- sgt101 8y agoWhere I work this gets you fired. We have a benefits tracking requirement, you put in a 3 gets you 9 case (borderline fundable - probably too small and not sufficient payback, but you might get it) and they go back and ask for another 7 over 2 years and you will leave on the ask. If you put 3 gets you 30 and then ask for another 7 you may well leave on the ask, you may get to stay for the realisation of the 30, but then you go. Probably you go on the ask because someone else will be parachuted into the project (if it's believed that the 30 really is on the table).
- buro9 8y agoI worked in a place (a bank) where an estimate that was more than 10% out in either direction would get you fired. Their view was that they valued accurate estimations that highly. But when I was there it was already being worked around... managers would create lots of smaller projects that delivered cross-functional behaviour to multiple projects and allowed them to externalise and hide the overages in what might appear to only be dependency lines to existing internal projects. The managers of multiple projects would collude to sponsor each others externalities so that they all had a layer of protection from being fired, obscuring what the costs were actually contributing to. The reason I was there was precisely to build a revenue recognition type system for their project management system to try and identify which projects had asked for some other project to start. But after that I worked at a UK govt department and they'd become so good at tracking who had been first to demand the creation of another project that their problem became one of legacy... no-one could sponsor even upgrading their long obsolete software or hardware, because even though it was a thing that benefited everyone, the project that demanded it was going to be the one that paid for it (literally paying for the certification, hardware, software, training, etc) which meant if you were the team that said "We can't support this on IE6" then you had to pay to replace laptops, OS, to get onto a later version. My conclusion... if we don't embrace a pragmatic reality of what things cost, if we try and manage the costs tightly... the side effects usually have unintended consequences that are worse than facing or embracing the original costs.
- kaybe 8y agoI know this in reverse: You want 2 years, so you ask for 4 and you will get 2. They always cut something out, even if you give an accurate number, so better put something in for them to cut.
- triggercut 8y agoThere's another slightly related aspect that a lot of people tend to overlook, that being the ability to capitalize your costs. Expense always gets pushed out as far as possible. R&D costing too much? Push it to CAPEX. CAPEX costing too much? Push it to OPEX. Unfortunately humans are fantastic at being able to create systems where by we can easily defer anything that doesn't suit us right now. This being said, I have no idea how NASA capitalize their assets. Accountants being accountants leads me to believe it's either squeezed into the same way as everything else, or there's some esoteric standard invented just for them.
- skywhopper 8y agoLike other commenters, I see nothing unique here to NASA or any engineering project of any scale, public or private. There are always unanticipated challenges, proposers are incentivized to underestimate time and costs up front, and these two things combined will always result in cost overruns and lateness.
- Scoundreller 8y agoRight. Shipping beta software/hardware to meet timelines and fixing later with a firmware upgrade (or, a for-pay upgrade...) isn't an option for them.