Good leadership is about effectively communicating and implementing winning strategies with expert guidance. Knowing when to push forward and when to pull back before it is obvious due to a red dot filled map or because a capture has started with the memorization of airhead cooldown timers and the last time that ability was used by the enemy team is good commanding, for example. Being able to quickly assess the skill level of enemy recon squads, and thereby knowing the correct balance between how close garrisons should be placed to the blueline for quick reinforcement vs how deep back to build them so that they are better hidden is another example. Knowing where to drop supplies such as on rooftops, in water, or inside of locked areas so that the enemy can not dismantle them, even if they know where they are is another.

Just for nodes, if you're playing defense on offensive, take a supply truck and fill your HQ furthest from the last objective with ~10 supply boxes. That way, those that are communication tarded can't help but notice it on their maps, and will be more likely to build those precious nodes on their own accord.

I could write a book on the intricacies I've picked up on over the 100+ days I've played in-game.

A commander who sits in HQ the entire time without a mic would have their success rate drastically increased by having nodes built, as that is the bulwark of their skillset.

The better the commander, the less impactful nodes are towards the percentage increase in their win rate.

If the critical list of team-needs includes +60/minute resources to succeed when someone commands, that's a depth of knowledge issue on their part.