If so, I'd say that's more a matter of prioritization (assuming at least one project is underway). For example, I think we could all agree that working on 30 projects would be an ineffective way to spend time. Mark Cuban recommends "1, not 50" [1]. You have to pick your best candidate project and run with it, and what's best depends on what your criteria are.
I think the term "fear of failure" is applied too broadly. Often this "fear" is more a healthy respect for the challenge of bringing highly functional yet simple experiences to your end user. Those experiences coupled with a product that solves a legitimate problem, absent any legal or bureaucratic barriers, is a recipe for winning. Understanding the intricacies of the challenge can make it difficult to find a single-threaded manner to work on it. It's almost more of a logical bewilderment than it is fear.
If none of the ~30 projects are being worked on then maybe fear of failure or laziness might apply but it could still be a matter of prioritization.
And I didn't say you said fear of failure was bad, I said it was applied too broadly and possibly not even applicable in this case, though you seem to have thoroughly investigated his background, personality, time expenditures and other personal preferences, so I'm sure you know better.