Prioritize features by weighing effort against impact. Build low-effort, high-value features first, skip the decades-long projects like teleportation, and use Weighted Shortest Job First to decide what actually matters to users and your business.
Chapters
Prioritizing features, it's in itself is extremely important, and I'm going to say there are techniques that, that have been defined in methodologies to help prioritize. Really what you want to do is balance level of effort versus the impact. So you want to make sure that what you're delivering has a high impact to the user. It's going to shift the needle, it's going to make the business more money significantly, but the amount of time it's going to take is also necessary to, to take into consideration. So an example, if you're going to change the world, right, you're going to build teleportation, it's just going to take 50 years or 100 years. That length of time is too much. And so that's when you have this list of features, you can objectively kind of scope them and say it's a low effort but it's high value. We can prioritize that one sooner than one that's high value but also high effort. And also you have to think about some other things too, like how is it going to, you know, work with your, with the experience of your current product? How is brand affected? How is it going to affect the reputation of your company? But generally I use the weighted shortest job first where I evaluate effort versus, um, the effort versus impact to help make the decision on which features should be prioritized.
