One is the issue of micromanagement versus giving people the initiative to achieve the desired result. Ironically, even the military leans heavily on the side of initiative, if only because that's the only way you can effectively lead a large number of people. You only address the details that are important at your level in the chain of command. This takes dialogue and even a degree of pushback. You don't just say "I want to fly this many sorties per day" and punish people for not living up to that if it's unreasonable. They're expected to tell you it's impossible to maintain the aircraft on that kind of schedule.
There's also the separate issue of whether there's such a thing as non-negotiable orders. It seems clear to me that there has to be such a concept for any organization to work. It's even necessary for that to be the case in order for initiative and delegation to work. There will always be decisions made far above your pay grade, and the people who made those decisions can't delegate the details down the chain unless there's some assurance that the people down the chain won't deliberately sabotage the high-level decisions. That way lies politics and other bullshit.
In the OP's situation, both sides failed. The CEO made the high-level decision that 1:1's were mandatory. The VP's mistake was his failure to enforce the decision down the chain, and the manager's mistake was to silently ignore or disobey the decision. (If the manager disagreed and pushed back in the first place, it wouldn't have become a problem). When the CEO became aware that the manager was not holding the 1:1's, he was immediately forced to attend to details below his level. This wouldn't have happened had it been clear from the outset that the decision was not, at the present time, negotiable. By making that point, the CEO resets expectations and from then forward has regained the ability to delegate.
One is the issue of micromanagement versus giving people the initiative to achieve the desired result. Ironically, even the military leans heavily on the side of initiative, if only because that's the only way you can effectively lead a large number of people. You only address the details that are important at your level in the chain of command. This takes dialogue and even a degree of pushback. You don't just say "I want to fly this many sorties per day" and punish people for not living up to that if it's unreasonable. They're expected to tell you it's impossible to maintain the aircraft on that kind of schedule.
There's also the separate issue of whether there's such a thing as non-negotiable orders. It seems clear to me that there has to be such a concept for any organization to work. It's even necessary for that to be the case in order for initiative and delegation to work. There will always be decisions made far above your pay grade, and the people who made those decisions can't delegate the details down the chain unless there's some assurance that the people down the chain won't deliberately sabotage the high-level decisions. That way lies politics and other bullshit.
In the OP's situation, both sides failed. The CEO made the high-level decision that 1:1's were mandatory. The VP's mistake was his failure to enforce the decision down the chain, and the manager's mistake was to silently ignore or disobey the decision. (If the manager disagreed and pushed back in the first place, it wouldn't have become a problem). When the CEO became aware that the manager was not holding the 1:1's, he was immediately forced to attend to details below his level. This wouldn't have happened had it been clear from the outset that the decision was not, at the present time, negotiable. By making that point, the CEO resets expectations and from then forward has regained the ability to delegate.