Main Sections
- Main Index
- Jammer's Blog
- Caprica
- Battlestar Galactica
- ST: Enterprise
- ST: Voyager
- ST: Deep Space Nine
- ST: Next Generation
- ST: Feature Films
- ST: Original Series
- Andromeda
- Articles & Misc.

Site Info & More
- Overview
- Jammer's Notes
- RSS Feeds
- Mobile Edition
- Review Mailer
- Comment Policy
- FAQ
- Feedback
- The Rating Scale
- About the Author
- Plain-Text Edition
- Copyright & Disclaimer

AddThis Social Bookmark Button

Valid XHTML 1.0 Transitional

Valid CSS!

Jammer's Review
Star Trek: Enterprise
"Shadows of P'Jem"
**
Air date: 2/6/2002
Teleplay by Mike Sussman & Phyllis Strong
Story by Rick Berman & Brannon Braga
Directed by Mike Vejar
Review by Jamahl Epsicokhan
"This is Sopek. Where's Commander Tucker?"
"He's unavailable at the moment. Can I take a message?"
-- Hoshi Sato, answering service

In brief: Mediocrity at its finest.

"Shadows of P'Jem" uses reasonable continuity and serviceable performances to play as a sequel to "The Andorian Incident," features some scenes that feel suspiciously padded, arrives at an ending that has little in terms of suspense or surprise, and has political situations that are left too ambiguous. If there's something to be said for the episode, it's that it doesn't do anything that feels particularly wrong. The problem, I think, is that it doesn't do enough that feels right, either.

I sometimes dread reviews like this. Good episodes feel worthwhile to review. Bad episodes are fun to rip apart. But reviews of middle-of-the-road endeavors like "P'Jem" can play like exercises in plot regurgitation. What can I say that I feel would be interesting to read? I've seen the episode a few times since it originally aired nearly seven months ago. After watching it most recently last week, I'm no more inspired to write about it than I was before. Maybe I'll exercise one of my favorite mantras -- less is more -- and write a review that is less, and therefore perhaps more.

T'Pol is busted. We learn that the Andorians destroyed the sacred grounds of P'Jem on the account that it was doubling as a spy post -- information Archer made public at the end of "The Andorian Incident." The Vulcans need a scapegoat for the incident and have chosen T'Pol since she was there, and because they apparently can't really take any direct action against Archer. So Archer is informed that the Vulcans are transferring T'Pol off the Enterprise to another post. Probably a less favorable post, we intuit. Archer is disappointed to be losing his first officer. T'Pol is frankly unmoved: "My assignment to the Enterprise was only supposed to last eight days. It was unrealistic to expect it to continue indefinitely."

Archer decides to take T'Pol on a landing mission to Coridan, to get a chance to talk with her and urge her to stand up for herself. En route to the surface where they are to meet government officials, the shuttle is shot down by Coridan insurgents, a plot-by-numbers development that employs the Shuttle Crash [TM] and Hostage Situation [TM] devices, both which have long been standbys on Trek, particularly Voyager.

Archer and T'Pol spend much of the rest of the episode tied up together on the floor in a low-tech holding cell. This gives them plenty of time to talk in scenes that feel suspiciously as if they were paced to play out slowly enough to fill an hour that had limited content. There's one lengthy scene where Archer and T'Pol attempt to escape from their ropes by pushing back-to-back against each other to stand up, and then wriggling into positions where they are free enough to untie themselves. Any scene that manipulates two bodies and physical space in the way this scene does has got to be imposing buried sexual undertones. The actors/characters and the director, however, keep the whole scene strictly professional, without a trace of anything else (I was reminded of the decontamination scene in "Broken Bow").

This scene exists, I surmise, to give the actors something to do rather than just sitting there and talking in a dark room. They instead talk while moving around and struggling. I suppose it makes sense, but the sequence is likely of only marginal interest to most viewers; the conversations about T'Pol's place in Archer's crew is more or less routine.

Meanwhile, the hostage plotting is strictly off the shelf. First we have more tensions between the Enterprise crew and the Vulcans, who arrive on the scene under the command of Captain Sopek (Gregory Itzin). Trip and Reed go on a shuttle mission to rescue Archer. This eventually leads to the usual shootouts, explosions, etc., but we first have another run-in with Andorian Shran (Jeffrey Combs), who informs Trip that the Coridan government officials are corrupt and maintain ties with the Vulcans, and that the insurgents are those who would overthrow this illegitimate government. Nevertheless, Shran is here to help rescue Archer, because he is vexed by the fact he feels indebted to Archer for his role in uncovering the evidence of the spy post at P'Jem.

I sort of liked the idea that Shran's debt eats away at him ("I haven't slept well") -- he doesn't like to owe anybody anything -- but Shran doesn't really engage us the way Combs' previous Trek roles have, in part because, like in "The Andorian Incident," Shran always seems so embittered and angry. The sly undercurrent of humor is something Combs has always been good at, and it's what seems to be missing in Shran.

The plot tidies itself by having T'Pol jump into the line of fire to save Sopek's life in the course of the action. This gives Archer just enough ammunition to convince Sopek to cut T'Pol a break, but Archer's speech at the end had me a little confused: He tells Sopek that, yes, T'Pol screwed up, but that she deserves a second chance. I'd simply like to know exactly how it is Archer is willing to grant that T'Pol "screwed up" in her involvement at P'Jem when it was Archer who gave the Andorians the evidence. Archer once again avoids true culpability and is let off the hook too easily for his actions.

I dunno. It's just the sort of episode that doesn't leave much of an impact either way. With all the would-be political intrigue, you'd think this might be interesting, but it proves mostly inconclusive: Shran's undetected presence on Coridan strikes me as awfully convenient, and the nature of the Vulcans' role in this world's affairs is left completely unresolved. Is Shran's interpretation of a corrupt government accurate, or merely spin control in favor of the insurgents because he hates the Vulcans? By the end, the story makes little effort to deal with the question at all.

That leaves us with Archer and T'Pol and the writers' desire to bring them a little closer together in their relationship as captain and first officer. It's not a bad sentiment, but nor is it a fresh one. It's of some consolation that this series at least tries to put its emphasis on the characters, but this is not what I would call deep character work. It's character work that is enough to qualify as present -- which is better than absent but miles short of fascinating.

Previous episode: Sleeping Dogs
Next episode: Shuttlepod One

7 comments on this review
David - June 24, 2009 - 02:00 am (USA Central Time)
I liked this one more than you did- as indeed I liked most Enterprise episodes more than you did. This episode had a nice mix of action, storytelling and character work, and every Shran appearance automatically elevates the episode.
Marco P. - September 14, 2010 - 05:57 pm (USA Central Time)
I agree with everything you said Jammer. "Miles short of fascinating" could not only be used to qualify the character work, but this episode as a whole.

I will be more severe with your episode rating, because to me mediocrity is many paces away from awesome and a just a few steps short of awful. I'm far from expecting mind-blowing stuff from ST Enterprise at this venture, but I cannot and will not settle for just "something okay". Anything on that level will get 1/4 in my book, especially since this is a series supposed to "refresh the franchise".

From context to characterization, all the way through script flaws, there's just too many things that feel "off" in this episode. The absence of a political context for the Coridan situation is one thing you mentioned, and I also agree on the unnecessarily long let's-get-out-of-these-ropes scene featuring Archer & T'Pol. I can't even remember what was said during all their twitching and turning, so meaningless it was.

At this point, I really feel continuing to watch this series is only worthwhile so I can read the sfdebris review afterward.
( sfdebris.com/enterprise/e114.asp )
Chuck - November 13, 2010 - 08:20 am (USA Central Time)
A new low for Enterprise in my opinion. This and "Dear Doctor" represent the Enterprise promise. Namely being a huge pile of crap. Our main characters are racist xenophobes with the vulcans in this episode and it's so full of cliches it makes your eyes water. It would get one star from me. And that's being generous. But then, I'm just a viewer with an opinion.
Jonathan - March 13, 2011 - 06:29 pm (USA Central Time)
I liked this episode. I viewed it purely as a character building episode between the captain and T'pol and didn't expect anything more. What impacted me the most is when the doctor told T'pol that this is not the first time a vulcan had been put on a ship with humans, but this is the first time a vulcan is actually considered part of the crew. Consider it a milestone. A bridge connecting the two species. Sure, the episode premise, rescue mission, Cordon itself was a bit vague and unexplored, but I find the character building of T'pol to be very satisfying.
Cloudane - April 23, 2011 - 02:17 pm (USA Central Time)
Re: "In brief: Mediocrity at its finest." - frankly that's my impression of the whole series so far. Apart from (very arguably) the highly controversial "Dear Doctor" I've not really seen this series dip more than a toe into anything deeper than mediocrity yet.

I don't get the impression that the series is *proud* to be mediocre like Voyager was, and at least it's trying for a bit of long term growth and storytelling, but nothing has really made me go "wow what a good episode"

Anyway, this one...

Let the A/T shipping begin. The "tied up" scene - blech. It was so obvious when they decided they needed to face each other while tied up so closely that we were going to see "a moment", that when we did I wanted to throw something at the screen. Blatant setup to intimate moment = bluuurgh

I'm also tiring of seeing the Vulcans portrayed as, well, complete a-holes. I could understand the overprotective parental aspects being shown at times, but these guys were just douches. Why do this to the previously friendly and honorable people. Oh well. At least we got a follow-up from that spying story.

Guess I'm on a bit of a rant, and I know it takes until season 3 or 4 before Enterprise gets properly interesting, it just kind of wears thin at this point IMO.
chris - October 11, 2011 - 03:53 am (USA Central Time)
Another boring Enterprise episode :( I miss all the excitement I used to feel while watching for the 1st time most of the Voyager and TNG episodes.

I feel sad :(
Michael - November 1, 2011 - 07:38 pm (USA Central Time)
Oh come on, guys, this was an O.K. show. It wasn't spectacular, but it had pretty much everything I like in this genre.

The captivity scenes were protracted and--as Cloudane remarked--at times pathetically engineered to contrive "special" "moments." But hey, what better way to portray T'Pol's heaving and curvaceous character and skin-tight personality, right? *wink wink - groan*

I remember back in the 80s I'd rush home from elementary school to catch the latest T.N.G. show. A few times I even skipped the last class (PhysEd). I was fascinated by the fictional technology and its clever use, rather than any character drama. (Oh, and I had a little crush on Martina Sirtis :D) Plus, there were some clever plots, like the time Picard's Enterprise went to "the edge of the Universe."

I guess the technology angle has been exhausted by now and there can only be so many spatial phenomena thought up, so there's not much they can come up with to keep me truly riveted anymore.

With that in mind, ST:Enterprise could be MUCH worse. I guess the idea has simply run its course.
Name:
E-mail:
Below, type the last name (only)
of the captain on Star Trek: TNG
Antispam:
Notify me about new comments on this page
Hide my e-mail on my post
Comment:
Comments powered by Scriptsmill Comments Script