Strategic, not tactical The working methods of the innovative designer are, for the most part, not systematic; there is little or no evidence of the use of systematic methods of creative thinking, for example. The innovative designer seems to be too involved with the urgent necessity of problem solving to want, or to need, to stand back and consider their working methods. Their design approach is strategic, not tactical. Nigel Cross & Anita Clayburn Cross, Winning by Design: The Methods of Gordon Murray strategy
Cultural relevance More than ever, people are choosing how to spend their time based on the amount of attention they can garner—and you and I are no exception. Everyone is susceptible to this logic. But what I want to argue in this piece is that tech startup founders are particularly susceptible to this tendency. Working at and around startups for several years, I’ve noticed many founders prioritizing culture, visibility, and perception over product, customer development, and strategy. Maybe this is to be expected in a time where culture moves faster and is perceived as more important than ever. But I find it unusual that the tech industry seems unaware of a whole class of typical mistakes founders make in pursuit of cultural relevance. Toby Shorin, Building for the Culture subpixel.space culturestrategybusiness
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality