[MUST READ] How Linear builds product
On planning
- Our goal was usually to figure out what was blocking us the most from getting more users on the product, and fixing things we heard from our beta users.
- We believe that if the leadership team and the whole company spend time with customers and use the product regularly, the needs and opportunities become more apparent. Then it’s just a matter of sequencing and scoping.
- We only have a single product team, which means that we can keep the planning process quite centralized, and there is only one roadmap for the whole product. This makes it very clear to everyone what we are working on. Additionally, everyone feels responsible for the whole product and how it all works together.
On execution
- We don’t have formal product or design reviews. It’s more ad hoc and iterative, which enables us to move faster. For example, our designers share an early design in a project-related Slack group and get informal asynchronous feedback from many different people that way.
- We’ve had a robust feature-flag system from the beginning, so we push new features to internal testing as fast as possible, sometimes in days or weeks from starting the project. At that point, everyone can try out the feature and see if something feels wrong or if they have ideas for how things could be improved. Because of these feature flags, there is no excuse to wait to ship.
On teams
- We have purposely avoided product-area-specific teams as it can be a way for people to get too trapped in their specific product area and potentially lose the broader context and/or start working on more minor details with diminishing returns.
- We only have mobile and infrastructure as specialized teams, as they require specialized skills and focus.
On hiring
- We always look for product sense, taste, and judgment for all product roles, like engineering and design.
- Product thinking or taste for us means the person is interested in and can form opinions on products or specific features.
- For example, if the person worked at Airbnb in the past, I’d ask them if they disagreed with something they built there and why. Opinion also doesn’t mean that you just personally like something; you need to be able to articulate why and what the rationale is.
Linear things
- One of the unique aspects to Linear is that we expect the project team to be the PM. With dedicated PMs, you outsource all the thinking to the PM, and the rest of the team—engineers and designers—just execute based on that thinking. I think it’s a waste of opportunity and talent.
- We run a beta customer testing program called Linear Origins where our customers get earlier access to new features and we can get product feedback early. Sometimes this happens a month or two before we aim to launch a feature, and sometimes it happens days before.
- At Linear, we fix these every week, but we also dedicate concentrated time at the end of the year to these efforts through Polishing Season. We have users tell us what we should fix or improve, or would make their lives easier. As we fix bugs and make product improvements, we notify the user who made the request that we shipped their fix and make live updates to the public page
Others
- I think it can work for some teams, but what I think works better is to build a team where the project team both thinks and executes. I like to compare how Apple combines CPU, GPU, RAM, and other functions on the same M1 chip to make it more efficient.
- Anyone who has built things knows that a lot of ideas and opportunities emerge when you actually start building something.
- My take is that this is one of the reasons why so much of the software we have today seems fine on paper but doesn’t actually work well in practice. We as an industry optimized the process too much and created a Henry Ford–style feature factory where each role is very specific and production speed is more important than craft.
How do you build a good platform? (cc: )
- Prioritize stability. With enough users, any change in behaviour of your platform—even fixing a bug—will change how the things built on top of that platform function, usually for the worse.
- Set expectations of backwards compatibility. The things people build on your platform will be 100% dependent on that platform in order to live. Set expectations with your creators for how long they can leave their creations before they need to be maintained or updated.
- Be judicious about your API surface. Because of the requirements of backwards compatibility and stability, every feature you build into your platform brings with it major maintenance costs. Err on the side of not adding APIs that you don’t strictly need.
- Build small, flexible, composable systems. If someone asks you for a feature, consider how you can provide it with the minimum amount of new APIs. The ideal case you’re aiming for is is zero, where they can build their intended feature by stringing together APIs you already provide.
- Build systems that generalize. Build APIs that are applicable to a wide array of circumstances. Otherwise, every time someone wants a slight change in the way an API or feature functions, they have to go through you. Making things generalizable can sometimes (though not always!) mean more work, but it almost always gives you a better return on investment in the long run.
- Make sure your platform works consistently everywhere. You don’t want the creations people make to work incorrectly on some devices, operating systems, etc. You can explicitly choose not to support some of them, but if you do choose to support them, they can’t be broken or inconsistent.
Why does Michelin publish a restaurant guide?
- Michelin began publishing its “Red Guide” in 1900 when cars and food tourism were novel luxuries. Its creators hoped that a guidebook offering information about hotels, restaurants, and roadways would lead people to drive more—and buy more Michelin tires.
- The star system that Michelin uses goes up to three and is broken down by whether or not it’s worth driving to the restaurant:
- One star: A very good restaurant in its category
- Two stars: Excellent cooking, worth a detour
- Three stars: Exceptional cuisine, worth a special journey
- Michelin continues to judge restaurants in order to promote the company name authoritatively. It’s a bit like if the Coca-Cola Company ran the Oscars, creating the ceremony in the 1920s so that people would go to the movies and drink more soda.
- It’s debatable whether the guide still helps Michelin sell tires, but Michelin’s ownership has been instrumental to the renown and authority of its restaurant guides.
OpenAI and Jony Ive in talks to raise $1bn from SoftBank for AI device venture
- People familiar with the matter said Sam Altman, OpenAI’s chief, has tapped Jony Ive to develop OpenAI’s first consumer device.
- The people said that Altman and Ive had held brainstorming sessions at the designer’s San Francisco studio about what a new consumer product centred on OpenAI’s technology would look like.
- The plan is to create a more natural and intuitive user experience for interacting with AI in the way that the iPhone’s innovations in touchscreen computing unleashed the mass-market potential of the mobile internet.
- SoftBank’s founder and chief executive Son has also been involved in some discussions, pitching a central role for Arm — the chip designer in which the Japanese conglomerate holds a 90 per cent stake — and offering financial backing.
- Discussions are said to be “serious”, but no deal has been agreed, they cautioned, and it could be several months before a venture is formally announced. Any resulting hardware product is likely to take years to bring to market.
Others
- Don’t plan to do it, just do it.
- One trick to programming faster is to do less in your head and run the code more (cc: )
- OpenAI can now see, hear, speak and search the web in real-time
- Amazon will invest up to $4 billion in Anthropic
Substack edition
How Linear builds product
On planning
Our goal was usually to figure out what was blocking us the most from getting more users on the product, and fixing things we heard from our beta users.
We believe that if the leadership team and the whole company spend time with customers and use the product regularly, the needs and opportunities become more apparent. Then it’s just a matter of sequencing and scoping.
We only have a single product team, which means that we can keep the planning process quite centralized, and there is only one roadmap for the whole product. This makes it very clear to everyone what we are working on. Additionally, everyone feels responsible for the whole product and how it all works together.
On execution
We don’t have formal product or design reviews. It’s more ad hoc and iterative, which enables us to move faster. For example, our designers share an early design in a project-related Slack group and get informal asynchronous feedback from many different people that way.
We’ve had a robust feature-flag system from the beginning, so we push new features to internal testing as fast as possible, sometimes in days or weeks from starting the project. At that point, everyone can try out the feature and see if something feels wrong or if they have ideas for how things could be improved. Because of these feature flags, there is no excuse to wait to ship.
On teams
We have purposely avoided product-area-specific teams as it can be a way for people to get too trapped in their specific product area and potentially lose the broader context and/or start working on more minor details with diminishing returns.
We only have mobile and infrastructure as specialized teams, as they require specialized skills and focus.
On hiring
We always look for product sense, taste, and judgment for all product roles, like engineering and design.
Product thinking or taste for us means the person is interested in and can form opinions on products or specific features.
For example, if the person worked at Airbnb in the past, I’d ask them if they disagreed with something they built there and why. Opinion also doesn’t mean that you just personally like something; you need to be able to articulate why and what the rationale is.
Linear things
One of the unique aspects to Linear is that we expect the project team to be the PM. With dedicated PMs, you outsource all the thinking to the PM, and the rest of the team—engineers and designers—just execute based on that thinking. I think it’s a waste of opportunity and talent.
We run a beta customer testing program called Linear Origins where our customers get earlier access to new features and we can get product feedback early. Sometimes this happens a month or two before we aim to launch a feature, and sometimes it happens days before.
At Linear, we fix these every week, but we also dedicate concentrated time at the end of the year to these efforts through Polishing Season. We have users tell us what we should fix or improve, or would make their lives easier. As we fix bugs and make product improvements, we notify the user who made the request that we shipped their fix and make live updates to the public page
Others
I think it can work for some teams, but what I think works better is to build a team where the project team both thinks and executes. I like to compare how Apple combines CPU, GPU, RAM, and other functions on the same M1 chip to make it more efficient.
Anyone who has built things knows that a lot of ideas and opportunities emerge when you actually start building something.
My take is that this is one of the reasons why so much of the software we have today seems fine on paper but doesn’t actually work well in practice. We as an industry optimized the process too much and created a Henry Ford–style feature factory where each role is very specific and production speed is more important than craft.
How do you build a good platform?
Prioritize stability. With enough users, any change in behaviour of your platform—even fixing a bug—will change how the things built on top of that platform function, usually for the worse.
Set expectations of backwards compatibility. The things people build on your platform will be 100% dependent on that platform in order to live. Set expectations with your creators for how long they can leave their creations before they need to be maintained or updated.
Be judicious about your API surface. Because of the requirements of backwards compatibility and stability, every feature you build into your platform brings with it major maintenance costs. Err on the side of not adding APIs that you don’t strictly need.
Build small, flexible, composable systems. If someone asks you for a feature, consider how you can provide it with the minimum amount of new APIs. The ideal case you’re aiming for is is zero, where they can build their intended feature by stringing together APIs you already provide.
Build systems that generalize. Build APIs that are applicable to a wide array of circumstances. Otherwise, every time someone wants a slight change in the way an API or feature functions, they have to go through you. Making things generalizable can sometimes (though not always!) mean more work, but it almost always gives you a better return on investment in the long run.
Make sure your platform works consistently everywhere. You don’t want the creations people make to work incorrectly on some devices, operating systems, etc. You can explicitly choose not to support some of them, but if you do choose to support them, they can’t be broken or inconsistent.
Why does Michelin publish a restaurant guide?
Michelin began publishing its “Red Guide” in 1900 when cars and food tourism were novel luxuries. Its creators hoped that a guidebook offering information about hotels, restaurants, and roadways would lead people to drive more—and buy more Michelin tires.
The star system that Michelin uses goes up to three and is broken down by whether or not it's worth driving to the restaurant:
One star: A very good restaurant in its category
Two stars: Excellent cooking, worth a detour
Three stars: Exceptional cuisine, worth a special journey
Michelin continues to judge restaurants in order to promote the company name authoritatively. It’s a bit like if the Coca-Cola Company ran the Oscars, creating the ceremony in the 1920s so that people would go to the movies and drink more soda.
It’s debatable whether the guide still helps Michelin sell tires, but Michelin’s ownership has been instrumental to the renown and authority of its restaurant guides.
OpenAI and Jony Ive in talks to raise $1bn from SoftBank for AI device venture
People familiar with the matter said Sam Altman, OpenAI’s chief, has tapped Jony Ive to develop OpenAI’s first consumer device.
The people said that Altman and Ive had held brainstorming sessions at the designer’s San Francisco studio about what a new consumer product centred on OpenAI’s technology would look like.
The plan is to create a more natural and intuitive user experience for interacting with AI in the way that the iPhone’s innovations in touchscreen computing unleashed the mass-market potential of the mobile internet.
SoftBank’s founder and chief executive Son has also been involved in some discussions, pitching a central role for Arm — the chip designer in which the Japanese conglomerate holds a 90 per cent stake — and offering financial backing.
Discussions are said to be “serious”, but no deal has been agreed, they cautioned, and it could be several months before a venture is formally announced. Any resulting hardware product is likely to take years to bring to market.