Apple: Jobs Returns and the Power of Focus
Featuring Steve Jobs
When Steve Jobs returned to Apple in 1997, the company was weeks from bankruptcy and drowning in product, printers, handhelds, and a confusing grid of barely distinguishable Macs. He came back through Apple's acquisition of his company NeXT, became interim CEO, and started asking the question nobody wanted to answer: which of these do we actually need? His answer was brutal. The lineup collapsed to four products, hundreds of engineers were let go, and the iMac arrived in 1998 to drag Apple back to profit.
Every product, feature, and initiative competes with every other one for engineering time, sales attention, and customer clarity. Most leaders solve that by adding; cutting is harder and rarer. This case puts operators in front of their own sprawling roadmap and forces the same uncomfortable triage Jobs ran. It sharpens the discipline of saying no, without spelling out the framework he used to decide what survived.
Frequently asked questions
What did Steve Jobs do when he returned to Apple in 1997?
Jobs returned in 1997 when Apple was weeks from bankruptcy with a sprawling, confusing product line, and he ruthlessly cut it down. He collapsed the lineup to four core products, let hundreds of engineers go, and the iMac launched in 1998 to drag Apple back to profit.
How did Steve Jobs come back to Apple as CEO?
He came back through Apple's acquisition of his company NeXT and became interim CEO in 1997. At the time Apple was drowning in products, from printers to handhelds to a grid of barely distinguishable Macs.
Why was focus so important to Apple's turnaround under Steve Jobs?
Because every product and initiative competes for engineering time, sales attention, and customer clarity, and Apple's sprawl was diluting all three. By cutting rather than adding, Jobs freed resources to make a few products great, which is what the iMac's 1998 success proved.
What can founders learn from Steve Jobs and Apple's focus?
The lesson is that saying no is harder and rarer than saying yes, and most leaders solve problems by adding when cutting is what creates clarity and impact. Run the same triage on your own roadmap and ask which initiatives actually deserve to survive. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.