My "management strategy" would be to get people involved.
Well, that's very nice and all that, but it's been tried before, many times, in many different ways, under various leaderships. And to a certain extent it's worked. Apart from Abigail, none of the 10 top committers in 2017 was around in 2000, so we've all been recruited since.
I think many people would like to contribute if they understood the system better.
There is copious documentation on the perl internals, and people on p5p are always willing to help answer questions. But fundamentally, perl is an exceedingly complex language, with many weird and wonderful features (like ties) all interacting with each other in unexpected and exponentially complex ways. To a large extent the internals are complex because they reflect this. They're also complex because they were originally written that way. And because much of the internals are exposed via the XS API (and since XS can and sometimes does access non-API internals too) it's very hard to rewrite the internals into a clean, modern form that would be easy to learn, without breaking everything; even if we had the manpower to do so.