Belling the Cat
en.wikipedia.org
en.wikipedia.org
None are effective in isolation. If your CEO / tech lead is an idea people, your COO / project manager an "execution people," and the team "tell me what to do people" things work pretty amazingly.
I think the problem is that people like to hire people like themselves, so a balance is hard to find. Each group is self-perpetuating.
I'll mention: I stated my career in roomfuls of idea people, and was deeply surprised the first time I ran into a "tell me what to do" person. That person worked hard, and was possibly the best software engineer I've worked with, but:
(1) Deeply didn't care about much beyond coding.
(2) Valued having people around him who can structure his work so it has meaningful impact.
Personally, I really benefit from having a watchful project manager to keep me on track. Once I gave up on doing that myself, my productivity skyrocketed. I tend to empower project managers (and admins and similar roles) to boss me around much more than the job description entails.
Spot on. Also, the same person or group can overdiscuss one thing and underdiscuss another.
Talking and easy. Analyzing something carefully and saying meaningful things take effort.
You rarely hear of software being designed too carefully.
a) Impossible, like for a mouse to put a bell around a cats neck, or
b) Possible but just not something people want to do.
In scenario (a) you need to move on from the idea, or fundamentally change it. In scenario (b) you can deploy organizational tools to get someone to do it (provide an incentive, force someone, draw straws, share the work etc).
My more cynical take has always been that it is about the bravery of the group, cowardice of the individual.
Or, more charitably, the good intentions of the collective that nonetheless fail in practice.
If the story ended with a swarm of rats killing the cat then it would be a more positive message, and who benefits from messages that say belling the cat is impossible if not the cats?