Steve Jobs wasn't just a showman. He had a repeatable system for separating what matters from what doesn't — and he applied it to products, meetings, teams, and his own calendar.
Job's didn't "try" to focus. He built constraints that forced it. A principle you follow when you remember is weak. A technique you can't avoid is strong. Here are the moves, in order of how you can actually use them.
Draw two axes that define your decision space. Put everything into a box. If a box has more than one thing, pick one — kill the rest.
When he returned to Apple in 1997, the company had a dozen product lines — printers, the Newton, multiple Mac variants, servers. He drew this:
| Consumer | Professional | |
|---|---|---|
| Desktop | iMac | Power Mac |
| Portable | iBook | PowerBook |
Four products. Everything else died. He didn't ask "what should we add?" He asked "what box does this belong in?" If it didn't fit, it was gone.
Ask: "If you had to kill everything on this list except two, which two survive?"
Not "what's important." Everyone gives you a list of important things. The question that produces real signal is what survives triage when you have to amputate. That's where actual priorities live.
You show the working thing. If it doesn't run, it doesn't exist.
Jobs banned slides at product reviews. You had to demo the actual product. PowerPoint lets you be vague about everything — "we'll add that later," "it'll connect here eventually" — a live demo has no escape hatches. The signal is working software. The noise is a deck full of aspirations.
Explain the idea in three sentences or fewer. If you can't, you don't understand it well enough yet.
If you couldn't explain your product to Jobs in three sentences, you didn't understand it — not "you can't communicate it well," but you haven't done the thinking yet. The act of compression forces you to find the actual idea buried under the complexity.
Give a crisp "no" right away instead of "maybe" or "let me think about it."
Jobs understood that "maybe" is the most expensive word. It occupies mental model space, drains energy from the yes items, and gives hope to things that should be dead. A "no" is clean. A "not right now" is noise. "Innovation is saying no to 1,000 things."
Every seam you don't own is a source of noise. Own the full stack or make the handoffs explicit.
Jobs said: "The user's experience degrades at every seam you don't own." The iPhone wasn't the first smartphone — it was the first where one company controlled hardware, OS, and UI. No handoffs, no blame-shifting, no "that's their problem."
Assign one human as the owner of each critical piece. Not a team. Not a committee. One person.
On the original Mac team, a single person owned the system — not "the OS team" or "the apps group." One human. When something broke, you knew exactly whose problem it was. No meetings, no escalation chains, no shared responsibility that meant nobody felt it.
All seven techniques share the same move: they force a decision. They make you commit when staying open feels safer. They surface the painful tradeoff you've been avoiding. That's what separates signal from noise — a decision is signal. A consideration that stays a consideration forever is just noise you're carrying.
Pick one decision you've been avoiding — a project you should kill, a feature you should cut, a commitment you should make or cancel. Apply whichever technique fits best:
Make the call in the next 24 hours. You don't have to execute it yet — just decide. Text me which technique you tried and what happened.
Read Walter Isaacson's Steve Jobs biography, particularly the chapters on his return to Apple (1997) and the original iPhone development. The product grid story is from page 332 of the hardcover edition.
Signal is a decision. Noise is a consideration that never resolves. Every technique above is just a different way of forcing yourself to decide instead of defer. The technique matters less than the pattern: choose, commit, move on.