He also shut Bev TF in one sentence & we didn't hear from her again. Dude's batting a thousandTHAT forgives a multitude of sins. He also let Data be first officer, and he rocked it.

He also shut Bev TF in one sentence & we didn't hear from her again. Dude's batting a thousandTHAT forgives a multitude of sins. He also let Data be first officer, and he rocked it.
And he didn't even have to turn her into a dog.He also shut Bev TF in one sentence & we didn't hear from her again.
There IS proof. Riker did due diligence: he consulted the shift heads. They told him under no uncertain terms that the change would cause severe personnel issues. So, like the professional he was, Riker waited on making the change until he could make Jellico aware if the difficulties. Jellico demanded that he do it anyway. Delta Shift was most likely a cobbled together mess, and the other three shifts lost significant efficiency due to being cherrypicked of essential personnel.
These are intelligent people, not automatons. They like to understand why decisions have been taken, and Picard had set the expectation of usually making clear his thought process and consulting.Well of course it would cause issues. You can't just make a major change and have zero impact. But Jellico has obviously run the format before and knew the benefits and knew the short term pain would outweigh the benefits.
The shift heads hadn't, so weren't placed to know. And like any organisation people don't like change. They had been coddled by Picard for six years some of them. Sometimes you have to respect that someone coming in knows stuff you don't know and respect that experience. That's why they're in charge and are put in that position.
It's not Riker's place to withhold implementation of an active order, on the grounds that objections were proffered. You follow it, & present the objections & relevant issues after the fact. The incoming captain, (that everyone knows is having command transferred that day) has ordered a change, as his 1st line of business. It's a simple change in shift rotation, which he likely wouldn't be ordering, without knowing all the factors & consequences therein, already.Riker did due diligence: he consulted the shift heads. They told him under no uncertain terms that the change would cause severe personnel issues. So, like the professional he was, Riker waited on making the change until he could make Jellico aware if the difficulties. Jellico demanded that he do it anyway. Delta Shift was most likely a cobbled together mess, and the other three shifts lost significant efficiency due to being cherrypicked of essential personnel.
Riker was correct in the matter of the shift change. And yes, he was wrong about Picard. Acknowledging a covert operation of that nature is generally a bad idea, and it wasn't even Jellico's call (it was Necheyev's). But it was still Riker's job to point out an action he saw as a mistake.
If he had implemented the change during a period of routine operations, like Kira and Sisko did, that might be true. But this wasn't routine operations. It was IMMINENT COMBAT OPERATIONS. Jellico knew this; he was running battle drills and juicing up the phasers. When you're heading for a fight, you want everyone on your crew doing what they're good at. Last thing you want is to retrain your crew while the Cardassians are blasting at them.Well of course it would cause issues. You can't just make a major change and have zero impact. But Jellico has obviously run the format before and knew the benefits and knew the short term pain would outweigh the benefits.
But Jellico is not the Captain—not the boss—when he gives that order and Riker is under no obligation to follow it as long as the Enterprise is still under Picard's command.Jellico is captain. Captain is boss. If you're not the captain, you damn well better be listening to him.
If he had implemented the change during a period of routine operations, like Kira and Sisko did, that might be true. But this wasn't routine operations. It was IMMINENT COMBAT OPERATIONS. Jellico knew this; he was running battle drills and juicing up the phasers. When you're heading for a fight, you want everyone on your crew doing what they're good at. Last thing you want is to retrain your crew while the Cardassians are blasting at them.
Picard is already in prep for his op when Jellico boards. Jellico's orders, from when he steps aboard, are that of the entering commander, to be implemented at the time he will be in command. He's the superior officer, with mission specific directives that the ship is now assigned to.But Jellico is not the Captain—not the boss—when he gives that order and Riker is under no obligation to follow it as long as the Enterprise is still under Picard's command.
Maybe Data would have been XO for long enough for Jellico to promote him to full commander.It would have been interesting to me if Jellico had relieved Riker at the first sign of Riker pushing back. "I appreciate your candor, Commander, but we're in the middle of a crisis and I don't have the liberty of working with an XO I don't believe I can rely on. You're relieved." I wonder how people would feel about the rest of it at that point.
He still needed to be given all relevant information. That was Riker's job.do agree it may not be the best time to do change. But in his judgement it may be that the crew can perform better, particularly when they need to be agile and on guard for a a potentially volatile situation.
Given how utterly dreadful Delta Shift's efficiency undoubtedly was, Jellico could have just as easily exploded at Riker if he did make the change without makung him aware of the potential difficulty: "why didn't you tell me that changing rotations was going to cause all these problems? That's information I needed to have!"I suspect that's exactly why Jellico dropped it straight away, to specifically see how this simple order about shift rotation would be handled, to measure the crew's cooperation, which was abysmal out of the gate, because of Riker's entitlement
Nope. It's the moment when accountability, responsibility, duty and authority passes from Picard to Jellico. As noted and recorded by the computer.The transfer ceremony is just that, ceremony.
That's the ship's access, not the chain of command. He is the mission commander & It's a mission related order, to be implemented as of his assumption of command, which as his superior (just like Nechayev who alerted him to it) stands, as a matter of rank. If it didn't stand, then why wouldn't he report it TO Picard for his approval? Because it's going into effect after he's out. It's preemptive, from a captain, for when he is to be captain. It was advanced notice, just like if he'd wanted to replace key personnel. They wouldn't refuse to inform those people that were being replaced, until the moment it was to happen. That would be terrible practice. He knew that order was official, and so did we all. He just figured he had room to have his say about it later. He was wrongNope. It's the moment when accountability, responsibility, duty and authority passes from Picard to Jellico. As noted and recorded by the computer.
PICARD: (reading) ... Computer, transfer all command codes to Captain Edward Jellico. Voice authorization, Picard delta five.COMPUTER: Transfer complete. USS Enterprise now under command of Captain Edward Jellico.JELLICO: I relieve you, sir.PICARD: I stand relieved.
Jellico was the one out of line, IMO. YMMV
Again, nope.That's the ship's access, not the chain of command.
I let the fish business go because that's a change requested by a cast member. As was Troi's uniform.Anyone who thinks it’s appropriate to take overworked crew away from their duties to redecorate his office should be on the first shuttle back to Earth and leave the grownups in charge.
Didn't the fish not come back once Picard was back?I let the fish business go because that's a change requested by a cast member. As was Troi's uniform.
We use essential cookies to make this site work, and optional cookies to enhance your experience.