Apple's Ternus Wants Faster Launches and Fewer Layers

John Ternus, Apple's new CEO, wants the company to launch products more often than its usual fall and spring launches, according to Bloomberg reporting cited by The Verge on Sept. 29, 2026.

Ternus indicated Apple must introduce products more quickly and become more experimental to remain competitive in the artificial intelligence era. That is an intent, not a shipped reorganization. The cadence would change.

He is also considering reducing layers between engineers and senior executives. In practice, that would compress the hardware and software decision stack and put working engineers in more direct contact with product direction.

Early personnel moves are already visible. According to the same Bloomberg reporting, Apple's hardware engineering team dismissed a number of engineering program managers in the past two weeks. The company also considered laying off 5,000 AppleCare customer service staffers but put those plans on hold. The second item did not proceed.

Ternus arrives with a hardware pedigree. He developed computer monitors early in his Apple career, oversaw product design for the original iPad, and later took over development of the Mac, according to Bloomberg. He served as Apple's head of hardware engineering before becoming CEO. Tim Cook passed the leadership baton to Ternus, Reuters reported on Sept. 1. As new CEO, Ternus faced the challenge of retaining top talent.

The transition has played out across three launches. Apple launched faster Mac mini and Mac Studio models to tap the AI boom on Aug. 25, an unveiling likely to be its last major launch before Cook handed over the reins. In early September, Ternus touted a strong product pipeline in a memo and teased a "phenomenal" Sept. 9 iPhone launch. That event, hosted by Ternus, centered on an anticipated foldable iPhone. It was his first major public appearance as CEO and the company's first product launch under his leadership. Apple shares ended down 0.3% after that smartphone launch.

Looking at what this means for execution, cadence is the easy part to announce and the hard part to sustain. More frequent launches demand parallel validation tracks for silicon, thermal and mechanical design, radio compliance, and OS readiness. Engineering program managers typically absorb that integration load. Removing that layer can shorten the path from prototype to decision. It can also push coordination cost back onto design and firmware owners.

The broader context here is the shift from a tick-tock hardware model to continuous iteration driven by models, toolchains, and inference workloads. Annual industrial design refreshes tolerate a spring and fall rhythm. AI features do not. They reward smaller deltas, tighter feedback loops, and willingness to ship hardware that is explicitly a platform for later software capability. In my view, Ternus is describing that adjustment more than a simple increase in event count.

Worth weighing carefully is the risk profile. Experimental hardware increases SKU complexity, test matrix size, and support burden. That burden lands directly on the same AppleCare organization that was reportedly considered for cuts. Pausing those cuts preserves support capacity while the product surface area expands. Over the long arc, that tradeoff favors users, because support quality determines whether faster hardware cycles feel like progress or churn.