Stage‐wise timing of new product development (NPD) activities is advantageous for a project's performance. The literature does not, however, specify whether this implies setting and adhering to a fixed schedule of gate meetings from the start of the project or allowing flexibility to adjust the schedule throughout the NPD process. In the initial project plan, managers and/or development teams often underrate the time required to complete the project because of task underestimation. Although the level of task underestimation (i.e., the unknown) is not identifiable at the start of the project, our study argues that project managers and/or teams can manage the unknown by measuring three project conditions (i.e., the knowns) during front‐end execution, and use their values to select the best gate timing strategy. These project conditions entail: (i) the number of unexpected tasks discovered during the front‐end, (ii) the willingness of customers to postpone their purchase in case the execution of these unexpected tasks would lead to a delayed market launch, and (iii) the number of unexpected tasks discovered just before the front‐end gate. Together these conditions determine whether a more fixed or more flexible gate timing strategy is most appropriate to use. The findings of a system dynamics simulation corroborate the supposition that the interplay between the three project conditions measured during front‐end execution determines which of four gate timing strategies with different levels of flexibility (i.e., one fixed, one flexible, and two hybrid forms) maximizes new product profitability. This finding has important implications for both theory and practice as we now comprehend that the knowns can be used to manage the unknown.