I use a priority quadrant[0]
[0] https://appfluence.com/productivity/why-you-should-manage-ta...
21–30 of 61 posts
I use a priority quadrant[0]
[0] https://appfluence.com/productivity/why-you-should-manage-ta...
Earlier quoted context omitted.
I've long thought that the single hardest problem in startups is prioritization: figuring out the most important thing to build (or do) next.
It also is that while building new product often there is no single thing that is urgent but everything needs to be done.
How to Prioritize Anything: 1) Make two lists. Write everything down in the first list. The second list is empty. 2) Something came up! One item on this list cannot be done. It doesn't matter why: you know which one that is. Which one is it? Write that down in the second list and mark it off the first list. 3) Repeat until the first list is done. Congratulations, your second list is prioritized (albeit likely in reve…
But, maybe the fact that you're going from least to most important makes it materially easier. It's functionally different because you're picking out the least important stuff when the list of unchosen items is big and the most important stuff when the list is small. I can see how this would help a lot.
How to Prioritize Anything: 1) Make two lists. Write everything down in the first list. The second list is empty. 2) Something came up! One item on this list cannot be done. It doesn't matter why: you know which one that is. Which one is it? Write that down in the second list and mark it off the first list. 3) Repeat until the first list is done. Congratulations, your second list is prioritized (albeit likely in reve…
Thanks for this. It's interesting because it's super close to another method: Write down everything, put the most important thing at the top of a list, next important next, go till done. That's maybe the most naive method possible and essentially shouldn't count as advice for "how to prioritize". But, maybe the fact that you're going from least to most important makes it materially easier. It's functionally different…
It also helps mitigate our fear avoidance strategies (ex: (a|b|c) - (x|y|z) + (w|t|f), Einsenhower quadrants, and so on) because there's just no room for it. Something has to go. What? Okay. Next.
Earlier quoted context omitted.
I've long thought that the single hardest problem in startups is prioritization: figuring out the most important thing to build (or do) next.
Strongly agree with this. One thing I realised is, startups should spend more time optimising the decision of their top priority, and less time optimising efficiency. There's no point working on the wrong thing with 100% efficiency.
So having a balanced prioritisation approach would seem to be pretty important.
Task priorities are decided based on two factors:
1. The ratio of value generated per given effort: If there are two tasks with similar value but one of them requires less effort then the one with lesser effort goes higher in priority. On the contrary if two tasks require the same effort but one of them has higher value then the one with higher value gets higher priority.
2. Time sensitivity: Certain tasks are time sensitive and should be given higher priority. Tasks can be time sensitive because they are blockers for other tasks or because they help de-risk technical or business risks and may affect the fate of other tasks going on in parallel. These are usually information generating tasks and they help reduce wasted effort on other tasks if the information is revealed early.
One makes a priority decision based on the best judgement combining the above criteria. The intent is to increase the overall value generated by the team.
[0]: fluxninja.com
How to Prioritize Anything: 1) Make two lists. Write everything down in the first list. The second list is empty. 2) Something came up! One item on this list cannot be done. It doesn't matter why: you know which one that is. Which one is it? Write that down in the second list and mark it off the first list. 3) Repeat until the first list is done. Congratulations, your second list is prioritized (albeit likely in reve…
How to Prioritize Anything: 1) Make two lists. Write everything down in the first list. The second list is empty. 2) Something came up! One item on this list cannot be done. It doesn't matter why: you know which one that is. Which one is it? Write that down in the second list and mark it off the first list. 3) Repeat until the first list is done. Congratulations, your second list is prioritized (albeit likely in reve…
Thanks for this. It's interesting because it's super close to another method: Write down everything, put the most important thing at the top of a list, next important next, go till done. That's maybe the most naive method possible and essentially shouldn't count as advice for "how to prioritize". But, maybe the fact that you're going from least to most important makes it materially easier. It's functionally different…
Instead of maximizing “benefit - cost” I would recommend maximizing “cost/benefit”. The former will bias towards big tasks with big payoffs, but often there are small tasks with extremely good ROI, which will get lost if you just look at the magnitude of the net benefit. But, +1 to the general approach of trying to put a number on it. Remember though, your numbers are uncertain, beware the McNamara fallacy.