Take the initiative, don't always wait for a commandIn some situations, it is imperative to wait for a command, such as in a war zone where the troops wait for the signal to attack from the one leading them, or in the launch of a satellite where the support team waits for the directive to start the process. Even in the corporate world, employees will wait for instructions for particular tasks from the higher-ups. Impetuous decisions in such cases are likely to be harmful, as strategies will have been drawn up to start or launch something in a particular way, at a particular time.
However, there are other situations where you can take the initiative to do something and not wait around for somebody in authority to give the command. Take the recent migrant crisis. Many individuals and NGOs took the initiative to help them in multiple ways, not waiting for directives from the Govt. that so and so steps should be taken. Another case is seeing somebody hurt on the roadside. A crowd will surround the individual, talking about calling an ambulance or taking the injured person to a nearby hospital, with nobody doing anything. Instead of being a mere bystander in that gaggle, it would help to take the initiative and not wait for somebody else to take the first step and issue directions to organize the needful arrangements.
It thus requires quick assessment and taking a decision independent of an order from somebody that can prove beneficial in some situations. A command is not always required.
[Entry for Topic-based TOW]