In my head, "20% time" is actually "work on what I want to work on", and I spend all week working on things someone else tells me to do. If I take some "me time", it's not going to be used for someone else. And if I'm going to do something for someone else, I'm going to just get my regular projects done.
There's a small possibility that someone else has a great idea that I really want to help with, but that idea would have to be big enough that 2 people could work on it at the same time, too.
So in the end, I think 20% Collab is a bit of an oxymoron.
I've seen a few of these in 20%ish projects where there is no revenue in sight but it sounded like a cool idea to each participants.
> It's not as if the things people work on wouldn't be of interest to others either.
People on the team feel different pain points differently, and don't see the full picture for things they don't feel pain on until they see the solution. Alice has no problem writing a lot of similarly-shaped code and doesn't see the point of Bob's refinements to the code generator. Bob isn't on the on-call team and doesn't care about Alice's unified metrics collector that simplifies 20 different alerts.