Indeed, I was thinking of this too when I wrote my comment.
It's natural to tightly schedule people when you think of the mission cost in $/minute. The problem is too tight a schedule is an engineering problem related to other ones we know like too thin a supply chain, too small a cache etc.
You need to put slack in your schedule to account for unplanned events -- the whole point of having humans there is to be able to respond to unplanned events, right?
Startups go into crunch mode when certain deadlines approach, but knowingly abandon other goals in the process (when companies don't, you end up in a death march). These missions are short enough that crunch is valid -- but another way of restating my point is: shouldn't the goal be that as many of the experiments you paid to get into orbit actually happen?
It's natural to tightly schedule people when you think of the mission cost in $/minute. The problem is too tight a schedule is an engineering problem related to other ones we know like too thin a supply chain, too small a cache etc.
You need to put slack in your schedule to account for unplanned events -- the whole point of having humans there is to be able to respond to unplanned events, right?
Startups go into crunch mode when certain deadlines approach, but knowingly abandon other goals in the process (when companies don't, you end up in a death march). These missions are short enough that crunch is valid -- but another way of restating my point is: shouldn't the goal be that as many of the experiments you paid to get into orbit actually happen?