# Linear App Authors - Linear Method: Introduction (Highlights)  ## Metadata **Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png **Source**:: #from/readwise **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Linear App Authors]] **Full Title**:: Linear Method: Introduction **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [linear.app](https://linear.app/method/introduction?cmdid=A81W2CWATWRYQ8) **Host**:: [[linear.app]] **Highlighted**:: [[2021-07-25]] **Created**:: [[2022-09-26]] ## Highlights ### Principles - We should find a cadence and routine of working. In cycles, we decide priorities and assign responsibilities. - Our daily work might be filled with tasks but we should understand and remind our teams of the purpose and long term goals of our work. ### Practices - Set monthly, quarterly or/and annual roadmaps - Connect daily work to larger goals with projects - You don't need to save every feature request or piece of feedback. Important ones will resurface and low priority ones will never get fixed. - All software has bugs, more than we can ever fix. Include bugs and other fixes as part of your cycles. Invest in tooling as it is a force multiplier if done right. - The purpose of a spec is to briefly communicate the "why", "what" and "how" of the project to the rest of the team. - Don’t worry too much about organizing all the feedback. Collect it and use it as a research library when developing new features. - It's hard to see visible progress when working on large tasks, which can be demotivating. Break down work into smaller parts and create an issue for each one when possible.