How many WIPs are too many? This is the question I’ve been wrestling with lately.
As a knitter, one of my greatest weaknesses is I have more ideas than time. This means I fight a constant battle between what I want to knit (all the things, all at once) and what I can knit (a few things, not all at once).
Theoretically, I’m showing remarkable restraint, because at the moment, there are only three projects on the needles:
(This project is well underway, but it's too gloomy to take a current photo.)
So what's the problem? Well, there are multiple concept swatches in various stages of completion, and there’s at least one ancient UFO cowering in the cupboard. I’m also scouting patterns and stitch dictionaries for several projects in the immediate line up:
I’m fighting the overwhelming urge to start more swatches and cast on all the things, all at once.
One discovery is helping me exercise restraint. Strangely, I’ve observed that in the knitting zone (often similar to the Twilight Zone), casting on tends to create more WIPs. The more WIPs on the needles, the less time and effort I can devote to any one project.
More WIPs means fewer FOs in the near term, even though they might translate into more FOs in the long run. Eventually. Some day. Way off in the misty future. (It took years, for example, to decide and then convert the Swafghan from a sweater into the Color Check afghan.)
In short, for me too many WIPs can be distracting. Too few WIPs can be demotivating.
How many WIPs are too many? I still don’t know. I was hoping you had the answer.