Management & Organization

Tony Fadell’s Note System: Using Paper to Separate What Matters

Share this article
LINEFacebook

Book excerpt (Tony Fadell’s Build)

Storage information

Bookmarks and reading positions are stored in this browser. Manage and back them up in My Reading.

Collected in Robin Shen’s Field Notes · Content type and attribution are shown above

English version published 2026-11-08 with AI assistance. Attribution, source notes, and verification limits are retained in the text. 中文原文

Reading guide

In Build, Tony Fadell describes how he manages priorities. You cannot keep everything in your head. His method is to carry a few sheets of paper listing the most important milestones in engineering, HR, finance, marketing, hardware, and every other area, plus everything required to hit them. In a meeting he can scan quickly: What are the main problems? What are customers running into? What is the team’s biggest obstacle? What is the next milestone? What deadlines have we promised? Next to the to-do list he keeps a section for good ideas people “cannot wait to make real,” and he reviews it regularly. The only way he captures information is by taking handwritten notes in meetings—no laptop, because a screen sends the wrong message that what is on the screen matters more than what you are saying, and because when you type you are often only typing; the content never enters your head. Writing by hand first and then typing and editing later means you process the same information two ways. Every Sunday night he re-ranks every task, prints a new version, and emails it to the management team; Monday’s meeting then walks the list item by item. It was on those note-sorting nights that he realized the team was overwhelmed because it had said yes to too many things—so he started practicing delegation, delay, and crossing items off. The list grew from one page to eight, then ten. The team went from hating it to liking it: nobody had to guess what was in his head anymore. The method will not suit everyone, but everyone needs a management system of their own.

Key points

  • A few sheets of paper: the most important milestones and tasks in each area.
  • A section beside the list for ideas people cannot wait to make real.
  • Handwritten notes in meetings: a screen sends the wrong message, and typing often never enters your head.
  • Reorder priorities every Sunday night, and notice where you should have said no.
  • Email the list to the team, and use Monday’s meeting to walk it item by item and hold people to it.
  • The method will not suit everyone, but everyone needs a system of their own.
Management & Organization thematic illustration
Management & Organization · Thematic illustration · AI generated

Full text — English translation

Build a system / How the author uses notes to separate what matters from what can wait --- You cannot keep everything in your head. A new crisis is always appearing, and the moment an old worry leaves, a new one takes its place. There are all kinds of small things to handle, and they often lock together: pull one thread and the whole fabric moves. Fadell says you have to calm down, find a bit of space of your own, and separate what matters from what can wait. His method was to carry a few sheets of paper wherever he went. On those pages were the most important milestones in every area in front of the team, and everything they had to do to hit them. The areas included engineering, human resources, finance, marketing, hardware, and the rest. He put all of the most important questions on those pages. So when he was in a meeting or talking with someone, he could scan them quickly. What are our main problems? What are our customers running into? What is this team’s biggest obstacle right now? What is the next important milestone? What have we promised on timing? Then there is the best-ideas section. Whenever someone raised a good idea that could not be done yet, or a suggestion for improving the product or the organization, he wrote it down. So next to each week’s to-dos and task list, he kept a section specifically for the ideas they could not wait to make real. He reviewed that section regularly to see whether the ideas still applied. They gave him inspiration and energy, and they kept him pointed at the future. That was good for the team as well. People could see that he cared about their ideas, and they knew he would keep evaluating them. For him, the only way to capture all of that information was to take notes in every meeting. He wrote down the good ideas, the priorities, the obstacles, the dates people had committed to, and the main internal and external heartbeats ahead—by hand, not on a computer. Handwriting mattered a great deal to him. He did not have to stare at a screen, and he was not pulled away by a stream of email. A laptop or a phone between you and the team does serious damage to attention. If he overused a screen, he was also sending the team the wrong message: that what is on the screen matters more than what you are saying. Even taking notes on a computer did not work. Sometimes, when he was typing, that was really all he was doing—typing. Whatever he wrote on the machine never entered his head. With so much in front of him, he could not afford to drift, or to miss a word the team said. So he chose to write by hand first, then type it up and edit it. That forced him to process the same information in more than one way. Every Sunday night he went through the notes, reassessed and reordered every task, walked through the good ideas again, updated everything on the computer, and printed a new version for the week ahead. Constantly re-ranking priorities let him narrow the field and spot the things that could be combined or dropped. It also showed him more than a few places where the team was pushing too hard. It was on those note-sorting nights that he finally understood why the team was so overwhelmed. It had said yes to too many things. It needed to start saying no. Then came the hard part: deciding what to delegate, what to delay, and what to cross off the list. He was no longer following whatever popped into his head. He was being forced to rank things by how much they actually mattered. That let him focus on higher goals and milestones, instead of only the urgent item in front of him or a sudden whim about a product feature. On Sunday night he emailed the whole list to the management team. Every item had a name on it. Anyone could look at the top of the list and know the focus for the coming week, what they were responsible for, and what the next important milestone was. Monday’s meeting was built around that list. Everyone hated it at first. When he pulled the lists out and started asking, item by item, where things stood, you could see the looks on people’s faces. “I still remember this one, because it has not been crossed off.” “On June 3 you said it would be ready by the end of the month. It is July. Where is this project?” This was not micromanagement. It was a way to make people own their work, and a way for him to keep everything in mind. Everything that had to be remembered came at him like a flood, and the list was what saved his scarce time in that rough water. It started as a single page and grew to eight, then ten. It was labor-intensive, a bit mysterious, and it never ended—but it was useful. Eventually the whole team came to like it. It helped them stay calm and keep their attention in one place. Nobody had to guess what was in his head anymore. Everyone knew what he cared about most, because he had written the priorities down and updated them every week. A lot of people on the team learned the habit, and later their own reports started using it too. Everyone is a bit afraid of lists, emails, and meetings. But if your head cannot hold everything that is in it, you start looking for a better way to manage it all. This method will not suit everyone. But everyone needs to find a management method of their own. You do need to put tasks in order of importance, get your own thinking organized, and give your team a predictable rhythm so they can stay current with what is in your head. #Build

These articles are personal notes, book excerpts, and collected reprints. Figures and events reflect the time of the original publication, are not current information, and do not constitute investment advice.

Share this article
LINEFacebook

Comments

What do you think? Share your experience or questions.

Loading comments…

My reading notes

These notes stay in this browser and are not published. Writing a note also saves the article. Back up or move your notes in My Reading.

Manage my bookmarks and notes →

STAY CURIOUS

Save a good question for your next visit.

Save this article, or follow the Facebook page and RSS feed for additions. Historical articles retain their original publication dates.

Browse All articlesSearch articles and full text →