Conversation

Anyone have experience switching from weekly rotation through projects (eg: project A on Monday, B on Tuesday....E on Friday) to batched rotations (a week on A, a week on B etc but still shipping some of it on a weekly tempo, like if A is a newsletter, you queue up 5 on A-week)?
6
12
I want to try this at least partly but a) I’ve never been good at piling up ship-able inventory; something about the tight do-ship loop works much better for me) b) the practical gear shift seems kinda awkward to pull off unless I take on a very heavy week or two to transition.
1
2
I’m imagining the gains are in fewer context shifts (1-2 a week instead of 1-2 a day), but at the cost of longer feedback loops.
1
I have 3 weekly shipping things I fully control (2 newsletters and a blog), one I don’t fully control and can’t batch (consulting) and 2 cumulative projects with months between shipping events. I’d like to try batching everything except consulting.
1
1
Update : Rotating projects on a weekly basis doesn’t work for me (week 1 = project 1, week 2 = project 2...) because latencies are too high. I need to touch most projects at least once a week or they die.
Replying to
Trying out a new rotation approach. 1 week/mode, by energy. Week 1 = maintenance on all projects (highest energy) Week 2 = problem solving on all Week 3 = new starts/discovery/exploration/learning on all Week 4 = future planning/visioning/brainstorming on all (lowest energy)
3
11
This is vulnerable to energy patterns. My patterns are generally somewhat stable in a given week, but +/- 20%. If it dips too much, it’s in the zone of the next band, so gotta mix it up or let it go waste. Otoh too much mixing and you develop backlogs of high-energy tasks.
2
Replying to
concur; my experiment with doing a couple hours a week on my graph algorithm transcription project is beset by trying to remember what i was doing
1