Optimize for momentum
muratbuffalo.blogspot.com
Optimize for momentum
1–7 of 7 posts
Re: Optimize for momentum
#2Momentum works well so long as you have enough alignment, clarity, and certainty.
When you don't know what you're building though, the last thing you want is a heads down project that you can't change course on or kill because it has too much momentum going in the wrong direction.
Re: Optimize for momentum
#3Re AI: I find that Claude can massively help and massively hurt with this, the devil is in the details.
Re: Optimize for momentum
#4If proceeding requires a review/input from someone, its a difficult balance between respecting their busy workload may mean they only get to it next week, or letting momentum die.
Re: Optimize for momentum
#5Whiteboarding or taking notes can be a good proxy for thought work in early stages. Iow, those are good ways to "get something imperfect out" early because they are at a high enough level that they don't kill much time. However, hacking code out before it's been thought through tends to be a massive time suck.
I definitely agree that there's a shitton of value in hitting things regularly though (usually daily).
Re: Optimize for momentum
#6And remember, you win by showing up each day, not by tilting at windmills.
Re: Optimize for momentum
#7This is good advice, but I struggle to apply it when many people are involved in a project. If proceeding requires a review/input from someone, its a difficult balance between respecting their busy workload may mean they only get to it next week, or letting momentum die.