BOOK / SOURCE
How to Think Like Steve Jobs · איך לחשוב כמו סטיב ג׳ובס
- Material reviewed for this piece
- All 11 pages of the file were visually reviewed: 10 pages of typed notes and selected passages, plus one blank page. This adaptation covers design and critical-reading themes from the file, not the complete book.
Reading and application draft · awaiting review
AI-assisted draft based on saved library notes; authorship of the typed wording has not been verified. This is Daniel Smith’s book about Steve Jobs, not a book written by Jobs. The extensions, example and qualifications below are new editorial interpretations. They are not accounts of Shachar’s experiences or a proven Jobs method. Quotations and biographical anecdotes have not been reproduced or used as evidence of success.
Begin with the action, not the decoration
The opening notes present design as a question not only of appearance but also of how something works. User experience appears shortly afterwards. Read together, these ideas extend a review beyond colours, images and visual style.
In a new editorial example, a workshop registration page does not end with an attractive button. A person needs to understand whom the workshop is for, what participants need to prepare, what happens after registration and how to correct a mistake. If those matters remain unclear, a clean appearance does not solve the problem. Design includes wording and the sequence of actions, not only their visual frame.
Remove clutter without removing what is needed
The notes repeatedly emphasise simplicity and later mention saying no to many things. The proposed application is not to delete as much as possible, but to choose what serves the action the product is meant to enable.
On the same registration page, repeated promotional text and options unrelated to the workshop can be removed. Removing the explanation of what happens next merely to shorten the page transfers work to the user: they must now guess or ask for help. Useful simplicity is not necessarily the shortest page. It is an attempt to keep necessary information understandable and available where it is needed, without presenting every possibility at once.
SEE THE IDEA
One page, two questions: how does it look, and what is clear?
A new editorial map of the fictional workshop registration example, inspired by notes on Daniel Smith’s book about Jobs. These are two review perspectives, not scores, stages or a proven Jobs method.
- AppearanceVisual order, spacing and a clear button
- The decisionWhom the workshop suits and what to prepare
- What followsWhat happens after registration and how to correct a mistake
Review the appearance
The page may be orderly and pleasant to read. That is desirable, but it does not by itself answer the participant’s questions. A prominent button does not explain what happens after it is pressed.
Read the journey
Follow the initial information through to the confirmation: can someone decide, register and understand what follows? Look for missing explanations or unclear actions, not merely another element to remove.
Less content does not always mean less work
In the example, removing repeated promotional text can reduce clutter. Removing the next-step explanation merely leaves the user to guess. Not every shortening serves simplicity.
Both perspectives can coexist
There is no need to choose between a considered appearance and an understandable journey. The distinction allows each to be examined separately; the maker’s preference does not establish that others understand the product.
A vision is not an answer on the user’s behalf
Alongside user experience, the notes present confidence in the product maker’s intuition. This calls for a critical distinction: confidence in an idea does not, by itself, establish that another person understands how to use it. That qualification belongs to this adaptation; it is not a finding proved by the file.
A review of the page can follow the entire journey, from initial information to the confirmation message. Where is a decision required? What information is missing at that moment? Does an error message explain what needs changing? A clear design direction can coexist with revising wording or sequence when a difficulty becomes visible. Vision and attentiveness need not be alternatives.
Learn from an idea without copying a persona
The file is not simply a list of praise. It also notes what not to imitate in personal relations, alongside attention to teams and changing plans. There is no need to treat every trait attributed to a successful person as an instruction to copy it.
The question of how a product works can be taken seriously without adopting a management style, a striking slogan or a success story. For the registration page, the intended outcome is not resemblance to a famous person’s product. It is that someone can decide whether the workshop suits them, register and understand what follows. That design aim can be explained without relying on Jobs’s name.
SOURCES / FURTHER READING
Turn this reading into a next step
A new worksheet inspired by the ideas—not a form reproduced from the book.
Your working notes
Write a few words. Nothing is sent, and this site does not save your notes to an account or file. This is a temporary worksheet — copy it somewhere of your own before leaving or reloading.