There Are No Bugs, Just TODOs
Super interesting, I like how the minimal skeleton for product development has been broken down.<p>Overall, I'm mostly aligned but it seems to me that it's very focused on low level product delivery. I feel like it's ignoring the bigger picture of how these "tasks" come to life and where they go after they're shipped.<p>Shipping software is much broader than moving tasks from "to do" to "deployed". If that was it, then yes, all you need is a flat & ordered list of tasks with an assignee for each. But it's not:<p>-How do you decide what do build in the first place? How do you make sure you are working on what's most meaningful?<p>-When you've prioritized the right problems to solve, how do you collaborate to come up with the right UX?<p>-How do you perform user research and user testing to validate your assumptions?<p>-How do you handle the feedback inbound you receive from stakeholders and customers? How do you take these inputs into account in your prioritization process? How do you then complete the feedback loop?<p>-How do you work with customer success and marketing to ensure everyone is informed of what you've shipped?<p>-How do you balance demonstrating product velocity while working on meaningful projects that take several weeks or months to ship?<p>What I'm saying is there is a broader context to shipping software beyond "accessing a prioritized list of tasks and getting them done". It's good to climb fast but if you're climbing the wrong wall, you're just getting to the wrong place faster.<p>That's the reason why my co-founder and I built Cycle (<a href="https://cycle.app/" rel="nofollow">https://cycle.app/</a>) – an all-in-one tool that helps engineers, designers, and product people to better collaborate in the process of shipping good stuff.