John Ternus wants Apple launching products outside its usual spring and fall windows

Some senior employees and several program managers at Apple were given two weeks to find another job inside the company ^[12]. Those who don't will be laid off this year, according to Mark Gurman's Bloomberg reporting as relayed by Notebookcheck ^[12]. A number of engineering program managers were dismissed over the last two weeks ^[11]. "Everything is a lot more hands-on than it used to be. It's hectic right now," one of Gurman's sources said ^[9].

John Ternus, the former hardware engineering chief now running Apple ^[1], is pitching speed, with fewer layers between departments ^[6]. BusinessToday ties the push to an industry increasingly shaped by AI and to making a large organisation more efficient ^[15]. The staffing cuts have already started. The launch calendar is still a set of ideas Ternus has discussed with colleagues ^[2]. Apple is also reportedly exploring using AI to replace some workers, though nothing concrete has been decided ^[13].

The two accounts differ on how far the calendar moves. Notebookcheck describes plans that involve "moving away from traditional launch windows" ^[2]. BusinessToday says Apple is "considering a faster approach to product development" that could see it launch more often "instead of depending so heavily on its usual spring and fall launch windows" ^[5]. The first version is a year with no fixed seasons. The second keeps both seasons and adds launches between them. For a company that makes cases or companion apps, those call for two different plans.

A partner that plans backward from spring and fall is relying on Apple's habit of putting its major launches there ^[3]. Neither report describes a launch that has already moved, or how Apple would give partners notice of dates ^[16].

For a team outside Apple, two questions sort the exposure. The first is whether the product depends on a specific Apple device, such as a case for an unannounced iPad, or on Apple's platform in general. The second is whether the team's lead time is longer than the notice it gets today.

Device-specific work with a long lead time is where I'd expect a looser calendar to hurt most. The hedge there is to tool later or run smaller first batches, and the cost is missing launch day. Device-specific work with a short lead time can wait for the announcement and still ship close behind it. Platform work changes little in either lead-time box, because these reports concern device launches ^[5]. The forcing question is how many weeks of notice a team gets now, and whether its plan still works if that number shrinks.