Apple's New CEO Pushes for Faster, More Experimental Launches

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

Ternus said Apple needs to ship products faster and take more experimental bets to stay competitive in artificial intelligence. That is a stated intent, not a finished reorganization.

He is also considering fewer management layers between engineers and senior executives. That would shorten the decision chain for hardware and software and give working engineers more direct input on product direction.

Early personnel changes are already visible. According to the same Bloomberg reporting, Apple's hardware engineering team dismissed a number of engineering program managers, the staff who coordinate schedules and dependencies across teams, in the past two weeks. The company also considered laying off 5,000 AppleCare customer service staff but put that plan on hold. That cut did not proceed.

Ternus arrives with a hardware background. Early in his Apple career he worked on computer monitors, later oversaw product design for the original iPad, and then led Mac development, according to Bloomberg. He served as Apple's head of hardware engineering before becoming CEO. Tim Cook handed leadership to Ternus, Reuters reported on Sept. 1. As new CEO, Ternus faced the challenge of keeping top talent.

The handover has spanned three launches. Apple introduced faster Mac mini and Mac Studio models to tap the AI boom on Aug. 25, an unveiling likely to be its last major launch under Cook. In early September, Ternus described a strong product pipeline in a memo and teased a "phenomenal" Sept. 9 iPhone launch. That event, hosted by Ternus, focused 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 launch.

Looking at what this means for execution, faster cadence is easy to announce and hard to sustain. More frequent launches require parallel checks on chips, heat and mechanical design, wireless approvals, and whether the operating system is ready. Program managers usually handle that coordination work. Removing that layer can speed decisions from prototype to approval. It can also push that coordination work back onto designers and firmware owners, the engineers who write low-level software for hardware.

The broader context here is a shift from a once-a-year hardware rhythm to steadier iteration driven by AI models, developer tools, and AI workloads running on devices. Yearly design refreshes fit a spring and fall schedule. AI features do not. They improve with smaller updates, tighter feedback, and hardware built as a platform for later software. In my view, Ternus is describing that shift more than simply adding more events.

Worth weighing carefully is the risk side. More experimental products mean more distinct models to build, more combinations to test, and more support calls. That support load would fall on the same AppleCare group that was reportedly considered for cuts. Pausing those cuts keeps support capacity in place while the product lineup grows. Over time, that choice favors users, because good support decides whether faster releases feel like progress or confusion.