Curious how others deal with this: if I focus on one vertical slice of a long project (e.g. some design problem), I become annoyed that everything else remains frozen for long periods; if I work on a horizontal slice (a few pieces at once), bulk progress is very slow. Any escape?
Conversation
The key question: What’s the most important thing I could be doing right now to make progress on the project?
Do that. Don’t worry about the parts that remain frozen. If you keep answering the question, eventually, their time will come.
4
16
185
Replying to
I really like this angle, Ken!
Sensing into why I hesitate to do this: I think it's because the scope/definition of my projects are often so contingent, continuously-negotiated. And so I feel (right or wrong) I need to pay attention to the rest to shape the scope/def'n over time
Probably the right way to resolve that last issue is to commit to thinking carefully about the meta-level every N week(s) but to otherwise just do whatever's most important and to try not to relitigate the project's shape.
1
10
For me this feeling stems from unknowing what the end state looks like. Nowadays I try to have a good understanding of what the end will feel like and look like before I start. That’s for both programming and writing.
1
Ah, yes, this makes sense! Alas, for me, understanding what the end will feel/look like really *is* the project! :)
1
1
Show replies
Replying to
The N-week(s) cycle might help, especially if you set a hard deadline.
Make a provisional meta-level decision, allow yourself to work in that direction until your deadline, and don’t fret too much over it until the deadline comes.
Of course, this is an art, not a science.
1
5
I often wind up with a dilemma. There’s a thing I think is most important and there’s some other thing I want to do more—my head vs my heart. I try to strike a balance when I choose.
1
5
Show replies
I think making a document with the full scope is helpful. I highlight in yellow the item that’s in progress and in green the parts that are done. Becomes satisfying over time too, as you work through it, and makes the meta part happen naturally.
My projects are similar, Andy. I’m not great at it, but use two heuristics
Mainly: what would I be most proud to have faced today
Once/week: shortest job first
“Most proud” differs from Ken’s to give more weight to my own fears, desires re legacy, treating ppl a certain way…
1
8
That's a nice distinction. I can imagine myself interleaving both "most important" and "most proud." eg: I have an email I'm ~afraid to reply to. It'll never be "most important," but I'd be more proud to have answered it than to have done the "most important" work I'll do today.
4
In the beginning it's often most important to work on the risky/uncertain parts first... as they get cleared away (or deemed impossible) the scope generally gets clearer