The editor has always had it in for me

That sounds incredibly frustrating, especially when it feels like a pattern is forming rather than just a one-off critique. Three times in a row with the same feedback can definitely make it feel like there's a wall up between you and your editor. When you say you need to "go around her," what does that look like in your mind? Are you thinking of pitching to someone else in the organization, or is this more about a broader shift in how you're handling your work?

Fair enough. Let's look at the mechanics of it. Whether this is a smart move or a dumb one depends entirely on the culture of your newsroom and the relationship between your editor and the section head. In many environments, "going around" a direct manager is seen as a declaration of war. If the section head is close with your editor, your pitch might get shot down regardless of the quality, and you'll have signaled that you don't trust your boss. On the other hand, if the "fresh eyes" option is a formalized process, using it is a legitimate tool. To figure out which way this swings, a few things matter: Does the section head actually have a history of overturning the editor's decisions? And if you go this route and the section head says "yes," how do you think your editor will react to being bypassed?

That's the core of the frustration: "not enough new" is an opinion, not a directive. It’s a vague critique that doesn't give you a path toward a "yes," which is a nightmare when you're actually delivering on the goals of your beat. If you're bringing in a reliable source and digging up accountability stories, you're doing the job. But there's often a gap between a story being "important" and a story being "fresh" in an editor's mind. They might be bored with the *topic* even if the *information* is vital. Since you're tired of the ambiguity, have you tried pinning her down on a specific definition of "new"? Like, "I've had three pitches on this beat rejected for not being new enough; specifically, what is missing? Is it the angle, the framing, or is the topic itself exhausted?" If you've already tried that and got a non-answer, then the "fresh eyes" option starts to look less like a gamble and more like a necessary sanity check. But if you haven't forced her to be concrete yet, doing that might tell you if she's actually trying to steer you in a new direction or if she's just checked out on your lane.

"Let's keep an eye out for fresher angles" is the corporate equivalent of "I don't want to do the work of managing you through this." It’s a brush-off. If you're feeling like you're in a slow-motion exit interview, then the stakes of the "fresh eyes" move change. If you're already convinced she's phased you out, the risk of a "diplomatic incident" matters less because the relationship is already broken. At that point, the move isn't about saving the relationship with your editor—it's about testing whether the organization still values your work. If the section head also says "not enough new," then you have your answer: the beat is dead in their eyes. If the section head says "this is great, why wasn't this on my desk," you've just created a very awkward situation for your editor, but you've also proven your value. Do you think you're at the point where you're okay with the fallout if the section head likes the pitch? Or is there still a part of you that wants to find a way to make it work with your direct boss?

It's a brutal spot to be in because she's effectively shifted the risk onto you. By staying vague, she keeps the power; you're the one left guessing and the one who takes the heat if you try to force a resolution. If you're trying to figure out if the work is wrong or if you're the "dinosaur," the "fresh eyes" pitch is the only way to get a clean data point, but you're right—it's a high-stakes move. If it blows up, you're the "difficult" employee. Since you're not looking for a reconciliation, but you *are* looking for a diagnostic, is there any middle ground? For example, could you pitch the section head not as a "bypass," but as a "collaboration" or a request for a high-level strategy session on the beat? Or, if you're truly done with the guessing game, what's the worst-case scenario if you just send the pitch and let the chips fall where they may? If you're already feeling like you're being quietly retired, does the risk of being "the one who did something" actually feel worse than the current slow bleed?

Since I don't have the actual text, I'll tell you what usually triggers that "not enough new" reaction in an editor's brain when they're looking at a zoning or records piece. The first thing that makes an editor bored is a "process" lead. If the pitch starts with "The zoning board met on Tuesday and waived a variance for X developer," the editor is already asleep. To them, that's just a report of a meeting. They've seen a thousand zoning variances; they know the game. The "newness" usually isn't in the fact that a variance was waived—it's in the *why* and the *who*. If I were reading it cold, I'd be looking for the "so what" in the first two sentences. If the pitch is: "Developer X got a waiver, which is unusual for this district," that's a process story. If the pitch is: "Developer X got a waiver that allows them to build a luxury tower on a plot that's currently a public park, and here is the email showing the council member's brother is the lawyer," that's a story. Is your pitch framed as "here is something that happened" (the process) or "here is who is winning and who is losing" (the consequence)? If it's the former, your editor is probably bored by the *packaging*, even if the *content* is a legitimate scoop.

It's a bit of both, which is the most annoying answer possible. You're not being "bad at your job"—you're practicing a specific, disciplined kind of journalism where the evidence is built carefully so the story is bulletproof. That *is* a virtue. But the tension here is that a pitch isn't a story; it's a sales document. If you're burying the lead in the pitch because you're being "careful," you're treating the pitch like the final draft. Your editor isn't reading for legal accuracy yet; she's reading for a reason to care. If the consequence is in paragraph four, she's already decided it's "not new" by paragraph two. The real question is: are you being defensive about your leads because you believe the "slow build" is the only honest way to present the facts, or because you've just always done it this way and it worked until now? If it's the latter, you can fix this in ten minutes by moving the "so what" to the first sentence of your next pitch. If you do that and she *still* says "not enough new," then you've officially ruled out the "packaging" problem. At that point, you'll know for sure that the issue is either the beat or the person, and you can go to the section head with the confidence that you aren't just "writing boring leads."

You're right. The "ten-minute fix" is a tactical solution for a structural problem. It solves the "how do I get this one pitch through" issue, but it doesn't solve the "do I still have a future here" issue. The reality is that you're looking for a level of professional honesty that your editor is currently refusing to give you. You want a definitive answer—a "yes, you're still our guy" or a "no, we're moving in a different direction"—and she's giving you a series of vague, polite shrugs. If you're at the point where you're more exhausted by the guessing game than you are afraid of the fallout, then the "fresh eyes" option isn't actually about the zoning story anymore. It's a stress test. It's the only way to force a definitive answer because it puts your work in front of someone who doesn't have the baggage of the last three rejections. If the section head says "this is a great story," you've proven the work is sound and the problem is the editor. If the section head also says "not enough new," you have your answer about the beat. It's a gamble, but it's the only move on the board that actually gives you the data you're looking for. Does that feel like a risk you're actually willing to take, or does the thought of that "diplomatic incident" still feel too heavy?