Every editorial team has a meeting like this: a piece isn’t working, a deadline got missed or a decision needs to get made that someone won’t love. Most leaders either avoid scheduling it, let it drift into a vague status check or rush through it to get to the parts of the job that feel better.
That instinct is understandable. It’s also, in my experience, exactly backward. The meetings a team most wants to avoid are usually the ones doing the most work to keep a team functional — or the most damage if they never happen.
Avoidance Has a Cost, Even When It’s Invisible
When a leader consistently avoids the harder conversation (the underperforming piece, the missed deadline, the disagreement about direction) the team doesn’t stop noticing. They just stop expecting the conversation to happen. That expectation shift is quiet, but it compounds: standards drift, unspoken problems fester and the people doing the best work start to wonder why it doesn’t seem to matter as much as it should.
The cost of avoidance rarely shows up over time, as a slow erosion of the standard the team believes actually applies.
The Goal Isn’t Comfort — It’s Clarity
A hard editorial conversation doesn’t need to be adversarial to be effective. The goal is to make sure everyone leaves with the same understanding of what happened, why it matters and what changes next. Vague, softened feedback often feels kinder in the moment but leaves people guessing, which usually means the same problem resurfaces because nothing concrete was actually communicated.
Clarity, delivered directly but without unnecessary edge, is almost always kinder in the long run than a comfortable conversation that doesn’t actually land.
A Simple Structure for the Hard Conversation
Over the years, I’ve found a consistent structure makes these conversations easier to run and less likely to spiral into either vagueness or unnecessary conflict. Here’s a sample structure you can use.
- Name the specific issue, not the pattern. Start with what actually happened (“this piece missed the editorial angle we discussed”), not a broader indictment (“you’ve been missing the mark lately”). Specificity keeps the conversation grounded and harder to argue with.
- Ask before you conclude. There’s often context a leader doesn’t have, such as a resourcing issue, a miscommunication or competing priorities that were never surfaced. Asking what happened, genuinely, before delivering a verdict changes the entire tone of the conversation and often changes the actual solution needed.
- Separate the standard from the person. Make clear that the issue is about the work meeting a standard, not a judgment on someone’s overall value or ability. This distinction is often obvious to the leader and much less obvious to the person hearing the feedback. It’s worth saying explicitly, not assuming it’s understood.
- Agree on what changes, specifically. End with a concrete next step both people can point back to later. Don’t end the meeting with a shared feeling that the conversation “went well.” If the same issue can’t be checked against something specific, it’s likely to repeat.
Why This Builds Trust
Teams tend to trust leaders who are direct and predictable far more than leaders who are only warm when things are going smoothly. Predictability (knowing that a real issue will be named clearly and handled fairly) is part of what makes a team feel safe enough to do ambitious work in the first place. Paradoxically, the leaders who are willing to run the uncomfortable meeting consistently often end up with teams that trust them more than leaders who avoid it to keep the peace.
The Real Skill Is Consistency
None of this requires being naturally comfortable with conflict. Most effective editorial leaders I’ve worked with aren’t, particularly. It requires being willing to run the meeting anyway, on a predictable basis, with a structure that keeps it fair and specific rather than personal or vague.
The teams that hold together under real deadline pressure are rarely the ones with the fewest hard conversations. They’re the ones where hard conversations happen reliably enough that nobody has to wonder whether a real problem will get named, or whether it’ll just quietly slide.
FAQ
Why do editorial leaders avoid difficult feedback conversations?
Most leaders avoid these conversations because they anticipate conflict or discomfort, not because the conversation itself is unimportant. The avoidance is understandable, but it has a compounding cost: teams stop expecting accountability, and standards quietly drift.
What’s the difference between direct feedback and harsh feedback?
Direct feedback is specific, clear and focused on the work or the standard, not the person’s overall value. Harsh feedback often conflates the two. Being direct doesn’t require being unkind. In fact, vague feedback delivered gently often causes more confusion and repeated problems than clear feedback delivered plainly.
How should a leader start a difficult editorial conversation?
Start by naming the specific issue that happened, rather than generalizing into a pattern or broader criticism. Then ask what happened before drawing a conclusion. There’s often context the leader doesn’t yet have.
Does giving direct feedback regularly damage trust with a team?
Generally the opposite. Teams tend to trust leaders who are predictable and willing to name real issues more than leaders who are only warm when things go smoothly. Predictability about how problems get handled is part of what makes a team feel safe doing ambitious work.
How often should a leader have these harder conversations?
As often as a real issue arises. The goal is reliability, not frequency for its own sake. Teams that handle deadline pressure well aren’t the ones with the fewest hard conversations. They’re the ones where such conversations happen consistently enough that problems don’t go unaddressed.
Tim Ronaldson has spent 20 years as a writer, editor, and leader in media, building and managing editorial teams through the deadlines, disagreements, and decisions that actually shape how good the work gets.
Leave a Reply