John Ternus cuts the program managers who ran Apple's hardware timelines for decades

While he was still running hardware engineering, John Ternus showed an Apple all-hands meeting a slide charting annual headcount growth and argued that the company should be accomplishing more with fewer employees, according to Bloomberg ^[9]. He told employees at that meeting that Apple should hire fewer people and ask more of its existing engineers ^[9].

As chief executive he now wants Apple to "run faster and leaner" ^[1]. The pitch is a broader range of devices and an Apple that becomes "more experimental" to stay competitive in the AI era, MacRumors reported from Bloomberg's Mark Gurman ^[7]. The work done so far is subtraction. Early planning meetings for 2027 cut planned budget increases, held staffing flat and reduced marketing spending ^[10]. Recent cutbacks also reached the teams behind Siri, Vision Pro, AI-related software engineering and Fitness+ ^[11].

Bloomberg describes the engineering program managers as "central to Apple's product-development process for decades," with the job of "managing timelines and coordinating work across teams" ^[3]. I think a fixed spring-and-fall calendar does some of the same job, because every team knows the date it is building toward. The proposal to lean less on those two windows ^[6] would remove that shared date in the same period that the people who managed toward it are being dismissed ^[2]. The report does not say which products would move off the event calendar, or when.

Managers told Gurman there is a sense of pressure to move faster ^[14]. "Everything is a lot more hands-on than it used to be," one person familiar with the situation told Bloomberg. "It's hectic right now." ^[13] Managers in product-development groups are being pushed to deliver "more products, more frequently and on shorter timelines," the report says ^[14]. Some employees expect more layoffs later this year and early next year ^[16].

For an operator weighing the same cut, two things sort the risk: how many teams a product depends on, and whether its ship date comes from a shared calendar or is set product by product. A product that touches few teams can usually lose its coordinator whichever way the date is set. One that touches many teams but ships to a shared date still gets some coordination from the calendar itself. Many teams with a floating date is the quadrant where a dedicated timeline owner matters most, and Apple's hardware moves into it if the calendar proposal goes ahead.

The forcing function is one line per cross-team dependency, naming who owns the date once the coordinator is gone. Where that name is an engineer, the coordination has moved into engineering hours, and the plan has to count it there.