September 10, 2018
The popular version of this story compresses into a sentence: Steve Jobs took over the Macintosh project and Jef Raskin left. Both halves of that sentence are true. What the compressed version loses is that Raskin’s exit was not a single clean break — it happened in stages, over roughly a year, and the documented record shows a more specific sequence of events than the one-line summary suggests.
This matters for the same reason it matters elsewhere on this site: the Macintosh’s origin story has calcified into a small number of dramatic beats, and the actual documentary record — memos, contemporaneous accounts, and the recollections of the people who were in the room — is more granular and, in places, more interesting than the shorthand.
The Project Raskin Was Leading
By early 1979, Raskin had used his position at Apple to start a small project, initially staffed with a handful of engineers, built around his own thesis about what a computer for non-experts should be. He recruited the team himself, including hardware engineer Burrell Smith, and set the project’s initial direction: a low-cost, easy-to-use machine, designed from cognitive-science premises rather than from whatever the hardware happened to make convenient.
That project was still small and still Raskin’s when Steve Jobs, in early 1981, was pushed out of leadership of the Lisa project — Apple’s other, more expensive next-generation computer — after an internal power struggle. Jobs needed a new project. The Macintosh group, quietly building something interesting with a fraction of the Lisa team’s budget, became his target.
The Confrontation and the Forced Leave
The specific triggering event, as multiple firsthand accounts describe it, was a memo. Raskin, frustrated with what he saw as Jobs’s disruptive management style intruding on a project Raskin had built and was still running, wrote Jobs a sharply critical letter. Rather than resolving the dispute in Raskin’s favor, the confrontation reached Apple’s president, Mike Scott, who intervened by putting Raskin on a leave of absence — in effect, removing him from active control of the project he had founded, while Jobs moved in.
This is the moment the popular narrative usually treats as the whole story: Jobs took the project, Raskin was out. The documented sequence is more specific than that, and it did not end there.
The Brief Return, and the Real Exit
Raskin did not simply disappear after the leave of absence. He returned to the Macintosh group in a reduced capacity — accounts describe him coming back as documentation manager, a role with none of the authority he’d previously held over the project’s design direction. By this point Jobs’s influence over the team, the hardware choices, and the software philosophy was already substantial, and the project Raskin returned to was visibly diverging from the one he’d designed. His second stint was brief. Within a couple of months, by mid-1981, he was gone from the Macintosh team for good, unwilling or unable to work inside a project he no longer controlled and no longer fully recognized as his own.
Even that was not the final administrative step. Raskin did not formally resign from Apple as a company until early 1982 — commonly cited as February of that year — reportedly timed in part to his stock options fully vesting after four years with the company. The distinction matters: Raskin left the Macintosh team in mid-1981, roughly a year before he left Apple the company. Popular tellings collapse these into a single event; the record shows two.
What the Sequence Clarifies
None of this changes the basic outcome — Jobs took over the Macintosh, and it became, in its shipped 1984 form, substantially his and his team’s machine rather than Raskin’s. But the staged departure clarifies a few things the one-line version obscures.
First, Raskin’s exit was contested, not voluntary in any straightforward sense. He did not walk away from a project he’d lost interest in; he was removed from a project he’d built, went back once under diminished terms, and left again once it was clear the diminishment was permanent.
Second, the brief return as documentation manager is itself informative. It shows Raskin was not simply erased from the org chart the moment Jobs arrived — there was an attempt, however short-lived, to retain him in some capacity. That the arrangement didn’t last says as much about the incompatibility of Raskin’s and Jobs’s approaches to the same machine as any of the more frequently repeated anecdotes about their personal friction.
Third, the year-long gap between leaving the team and formally leaving the company is a reminder that corporate departures are administrative processes with their own timelines, not narrative beats designed for a clean story. Vesting schedules are unglamorous. They are also real, and they are part of the documented record here.
The Role of Mike Scott
Mike Scott’s part in this sequence deserves more attention than the compressed narrative usually gives it. Scott was Apple’s president at the time, not a Macintosh team member, and his intervention — putting Raskin on leave rather than mediating the dispute in some other way — was a management decision made above both Raskin’s and Jobs’s heads. That detail matters because it undercuts a version of the story that frames the outcome as simply “Jobs won an argument.” What actually happened is that a company executive, faced with a subordinate’s formal written complaint about another subordinate, sided against the person who wrote the complaint and removed him from the project rather than the person the complaint was about.
This is a mundane, recognizable corporate dynamic — a manager escalates a grievance in writing and gets removed rather than the person they complained about — and it is worth naming as such rather than folding it into a more dramatic story about two visionaries clashing over a machine. Raskin’s letter was a formal act within Apple’s normal chain of command. Scott’s response was a normal, if consequential, exercise of executive authority. The subsequent mythologizing of the episode as a clash of design philosophies is not wrong, but it was decided, procedurally, as a personnel matter first.
What the Popular Retellings Get Right, For Once
It would be inaccurate to suggest every popular account of this episode gets it wrong. Most competent tellings do correctly identify that Jobs’s takeover followed his own removal from the Lisa project, that Raskin’s complaint about Jobs’s management style was the proximate trigger, and that Raskin’s departure was not instantaneous. Where the compression usually happens is in flattening the return-and-final-exit sequence into the initial leave of absence, and in treating the year-long gap between leaving the team and formally resigning from Apple as if it did not exist or did not matter.
The distinction is not pedantic. A reader who believes Raskin quit the instant Jobs arrived comes away with a different, less accurate picture of how contested the project’s direction actually was during 1981 than a reader who understands there was a documented, if brief, attempt to keep Raskin involved after the initial confrontation. The second picture is the one the record supports.
The Aftermath
Raskin’s departure did not end his relationship to the ideas he’d put into the Macintosh project. He spent the following years developing the same design philosophy independently, through his company Information Appliance, Inc., which built the SwyftCard and licensed the technology behind the Canon Cat — the clearest realized version of the appliance philosophy he had tried, with only partial success, to build into the Macintosh before Jobs’s team reshaped it. The Macintosh that shipped in January 1984 retained some of Raskin’s founding principles and abandoned others; sorting out precisely which is a separate question from the one this piece addresses, but it is the natural next one to ask.
Frequently Asked Questions
Did Jef Raskin quit the Macintosh project, or was he forced out?
The documented record shows he was placed on a leave of absence following a conflict with Steve Jobs, escalated to Apple’s then-president. That is closer to a forced removal from leadership than a voluntary departure, though he did return briefly afterward in a reduced role before leaving the team for good.
When exactly did Raskin leave the Macintosh team?
He was sidelined from active leadership in early 1981, returned briefly as documentation manager around mid-1981, and left the team entirely by roughly the end of July that year — about a year before he formally resigned from Apple as a company in early 1982.
Why is there a gap between Raskin leaving the Macintosh team and leaving Apple?
Leaving a specific project and formally resigning from the company are different administrative events. Accounts describe Raskin’s decision to delay his formal resignation as connected to his stock options vesting after four years at Apple, which would have been early 1982.
Did Raskin and Jobs ever reconcile?
This article does not address that question in detail; it is outside the documented scope covered here. What the record does support is that their disagreement in 1981 was substantive and specifically about control of and direction for the Macintosh project, not merely a personality clash.
What did Raskin do immediately after leaving Apple?
He founded Information Appliance, Inc., which developed the SwyftCard and later licensed its underlying technology to Canon for the Canon Cat — continuing the design philosophy he had begun building into the Macintosh before his departure.
Related: