✳flâneur — a map of the web's best reading

A design reset (part I)

linear.app · 1,241 words · saved by 1 readers

No software design is truly timeless. We often hesitate to do product redesigns, even when we probably need one. I've been part of these projects several times in my career as a designer and it has never been something easy to pull off. The challenges start from the fact that it's never a good time to do a redesign. It's hard to make it a priority. It's difficult to calculate the ROI on it. And if you run your product with A/B testing, every global redesign will tank the metrics in the short term. Teams get furious and try to push back as they don’t want to see their product surfaces changed outside of their control. However painful it might be, there is a real need for redesigns, and your product experience suffers if you never do it. The real need for redesigns often comes when you have created a successful product and it has evolved with the market and users over time. This is also the case with Linear. We ship small changes daily, and something major almost every week. Every year,

A design reset (part I) Skip to content → Now Craft A design reset (part I) Karri Saarinen · March 27, 2024 We have redefined the foundational layers of Linear’s application with a full redesign. This is the first post in a two-part series where we dive into why and how we redesigned the application. In this post, we share why redesigns are important. In part two , we introduce you to the new UI and cover how we‌ tackled the project. No software design is truly timeless. We often hesitate to do product redesigns, even when we probably need one. I’ve been part of these projects several times in

Explore this link on the map →

related reading