You type it again.
“No, the value needs to show up sooner.”
It’s the same note you gave last week. And the week before. And possibly in a past life.
The work lands back on your desk unchanged, like you’re trapped in a creative version of Groundhog Day, except Bill Murray gets to play jazz piano and you’re stuck repeating feedback about hierarchy and buried value props.
Different project. Different team. Same note. Same slow leak of patience.
It’s tempting to assume you’re bad at giving feedback.
You’re not.
You’re just stuck in a loop — and this article is about breaking it.
Why You Keep Repeating Yourself (Even When You’re Being Clear)
Nobody signs up for a career in marketing, strategy, or leadership because they’re passionate about leaving immaculate comment threads.
Yet somehow, here you are.
You’re spending a surprising percentage of your week circling the same notes, clarifying the same lines, and wondering why you’re explaining something for the third time when you were pretty sure you nailed it on the first.
It’s not happening because you’re unclear. But it’s happening because you were never taught how to give feedback in a way other people can use without needing a decoder.
Most people learn feedback the same way they learn everything else in this industry: mid-sprint, between meetings, while trying to remember what their actual job was supposed to be that day.
You open a document, something feels off, and you reach for the fastest, least-wrong phrasing available:
“Not quite there.”
“Can we make this stronger?”
“I’m not convinced.”
In your head, each of those comments carries a whole constellation of meaning: the audience you’re thinking about, the business goal looming over the project, the real constraint no one is naming, the conversation from three days ago that still matters, the thing Legal said, the thing Finance wants, and the thing you already know the CEO will flag.
But the person reading your note… gets the sentence.
Just the sentence.
No subtext, no context, no history. And certainly no internal monologue where you already played out the next five moves.
So they do their best. They adjust what they can see. Then tweak, polish, rearrange, and hope. And when the work comes back, the part that mattered most (the thing you were really responding to) is still untouched.
This isn’t a competence problem, but a perspective problem. You’re holding the full story. They’re only holding one frame of it.
That gap is where all the repetition lives. And once you close that gap, once people can finally see what you see, the same feedback stops boomeranging back to you, and the entire process gets lighter.
The Cost of Feedback That Floats Instead of Lands
Vague feedback always feels speedy in the moment.
You drop a quick “I don’t love this” and move on with the confidence of someone who has, technically, responded. But those little reactions have a way of drifting through the project like helium balloons. Sure, they’re visible, but not particularly useful.
When your direction is more vibe than instruction, your team has no choice but to guess. They tweak whatever seems guessable. Send it back, and the work returns looking slightly different but somehow unchanged. It’s the design equivalent of someone rearranging throw pillows while the couch is on fire.
And here comes the real cost: the confidence drain.
They start to wonder whether they’re failing to read your mind.
You start to wonder why you’re apparently the only person who can see the actual problem. Meanwhile, the clock keeps ticking, and everyone pretends multiple rounds are simply “how these things go.”
Clear, grounded feedback isn’t about being nicer or more patient. It’s about keeping the work and your sanity moving forward, instead of spinning in the same unhelpful orbit.
So how do you finally fix this? Here’s what you can do:
Step 1: Define What “Good” Looks Like Before You Comment
If you want your feedback to stick the first time, start by giving people a clear target. Most “Why isn’t this fixed yet?” moments happen because you and the person doing the work are aiming at two different definitions of success.
A Quick Note on What “Good” Means
“Good” gets thrown around in creative work like everyone agreed on the definition years ago. They didn’t. In this context, “good” isn’t about whether you like the layout or whether something “feels strong.”
Good means the piece is doing the job it was created to do. That’s it.
If the work helps someone decide, understand, click, care, or not get confused, it’s good. Once you anchor “good” to function instead of taste, feedback becomes far easier to aim for and to follow.
So, before you leave a comment, ask yourself:
What would this piece do for us if it worked beautifully?
That one question forces your brain out of “I don’t like this shade of blue” mode and into actual outcomes.
- A deck that works should move a decision forward, even for someone who logged into the meeting five minutes late and missed all the context.
- A landing page that works should communicate value clearly enough that a distracted visitor wants to click instead of wandering away.
- An internal announcement that works should tell people what’s changing and what it means for them before Slack invents its own narrative.
When you’re clear on the outcome, your feedback stops being a vibe and starts being direction.
So instead of:
“Make it pop.”
You can say:
“The headline needs to make the benefit obvious at a glance. Right now, it describes us; it should describe what they get.”
And instead of:
“Something’s off here.”
You can say:
“The main promise is competing with the details. First glance should land on the core message, then everything else can support it.”
This isn’t micromanaging. (Micromanaging is emailing at 10 p.m. with a list of hex codes.)
This is naming the job the work needs to do, so the team can actually do it, without guessing what part of “off” you meant.
Step 2: Review at the Right Level (So You’re Fixing the Real Problem)
A surprising amount of feedback chaos comes from everyone looking at the work from different altitudes.
You’re thinking about the story and the strategy; someone else is nudging line spacing like that’s the lever that will save the campaign. It’s not that anyone’s wrong; you’re just not all looking at the same thing.
The fix is simple: review the work in the right order: strategy → structure → details.
Not the other way around.
Once you adopt this, your first round of feedback starts moving the project instead of just rearranging it.
Start With Strategy
Before you worry about fonts, colors, or the fact that something feels vaguely “meh,” ask yourself:
Is this saying the right thing to the right person?
If the answer is no, everything else is decoration.
Strategy-level issues sound like:
- “This is written for us, not for the customer. It needs to start in their world.”
- “We’re emphasizing features when this audience is buying reassurance.”
- “This reads like internal comms wearing an external comms costume.”
If the strategy is off, polishing visuals will only make the wrong message prettier. That’s the design equivalent of putting a highlighter on a bad outline. Start here, fix this first, then move down a level.
Then Review Structure and Emphasis
Once the message itself is right, zoom in one step further and look at how it’s arranged.
Ask yourself:
- What does someone notice first?
- If they skim, what survives?
- Is the most important idea getting the most obvious treatment?
This is where hierarchy, flow, and first impressions either save the piece or sink it.
Structure-level feedback sounds like:
- “Our strongest proof point is buried. Pull it up where people will see it.”
- “The headline and the visual are fighting; let the benefit carry the weight.”
- “The part someone actually cares about is in the least visible spot.”
This layer shapes how the work hits someone, not just what it technically says. And for busy, distracted humans (i.e., everyone), this layer matters a lot.
Save Details for Last
Typography, spacing, color, and microcopy. All of these matter. But, only after the strategy and structure are doing their jobs. If you start here, you risk sending the team into pixel-polish mode on something fundamentally misaligned.
This is how people end up debating the shade of a button on a page that should have been rewritten entirely. Work top-down, and your feedback becomes exponentially more efficient.
Step 3: Put Feedback Where People Can Use It
Even the sharpest feedback falls apart if it’s scattered like confetti across your communication channels. A quick Slack message here, an offhand remark at the end of a meeting, a follow-up email with “one more thing” that subtly contradicts what you said earlier.
Individually, these moments feel harmless, but suddenly your team is piecing together your intent like they’re solving a cold case.
If you want your feedback to land and stay landed, give it one home.
One. Not three. Certainly not “wherever I happened to say it.”
Pick a single source of truth: the doc, the design tool, the dedicated comment thread. Whatever it is, treat it as the place your feedback lives.
If you say something important out loud, add it there. If a new thought arrives an hour later, put it there too, not in someone’s DMs, email, or passing hallway confession.
When it’s time to review, move through the work once and leave a clear, consolidated set of notes. Don’t give them an essay or a breadcrumb trail across multiple channels. Just a version of your direction that doesn’t require a search party.
You’ll be surprised how much unnecessary back-and-forth disappears once people aren’t decoding your feedback across five platforms.
Step 4: Use Feedback as a Leadership Tool, Not a Fire Extinguisher
Feedback isn’t just something you do to fix whatever file is in front of you. It’s also quietly teaching your team how to approach the next one, whether you intend it to or not.
People repeat what gets reinforced.
If your feedback consistently circles back to the audience, the outcome, and the message, your team starts thinking that way before they ever drop something in your inbox. The work you get already carries your logic. You don’t have to retrofit the strategy after the fact.
But if most of your comments live at the surface (spacing tweaks, kerning preferences, “this blue feels sad”), that’s what people learn to prioritize. And then guess who gets stuck hauling the strategy up the hill in every round? You. Every time.
Outcome-oriented feedback resets the entire dynamic. You stop being the person who swoops in at the eleventh hour with a fire extinguisher and start being the person whose direction shapes the work from the beginning.
This is how you break the “Why am I fixing this again?” cycle. Not by repeating yourself louder, but by showing your team what really matters and letting them build toward it before the file ever reaches you.
What Happens If You Give Feedback… and It Still Doesn’t Get Followed?
Ah, yes, the million-dollar question.
Because even when you give clear, thoughtful, outcome-oriented feedback (truly your best work), now and then the revision comes back and you think: Did… did they read the comment? Or did my feedback take a long walk into the sea?
Here’s the thing: when feedback doesn’t get followed, it’s seldom because someone is ignoring you. It’s usually one of three far less dramatic reasons, and luckily, each one has a fix.
1. They didn’t understand the feedback.
You know exactly what you meant. They didn’t.
Maybe the wording was vague, or the context just didn’t travel. It’s possible the “make the value clearer” translated into “increase the font size,” which is not the same thing.
The Fix: Ask them to replay it back.
A simple, “Tell me how you’re interpreting this,” works wonders. You’ll spot the gap immediately, and it’s often an easy bridge to rebuild.
2. They understood it, but the file wasn’t ready for that fix yet.
Sometimes your feedback is aimed at a structural or strategic issue, and they’ve been polishing details because that’s what feels doable in the moment.
Don’t interpret it as defiance; it’s misalignment with what stage the work is in.
The Fix: Reaffirm the altitude.
“Let’s stay at the strategy level before we move into design tweaks.”
This instantly resets the frame.
3. They heard you, but another stakeholder contradicted you.
Welcome to creative work in the real world.
This usually happens because the work picked up a hitchhiker on its way through the approvals maze. A stakeholder chimed in, someone got nervous, or a well-meaning manager tried to “summarize” the feedback, turning a simple request into a full plot twist. I’ve seen plenty of briefs walk in wearing a button-down and come out dressed as a pirate.
So yes, your feedback made it in, but another opinion nudged the ship off course. Suddenly, your very reasonable feedback is now fighting for its life in a political arena you didn’t know existed.
The Fix: Bring the group back to outcomes.
Not preferences. Not vibes.“What outcome are we optimizing for?” wins every argument and exposes misalignment faster than anything else.
So what if it keeps happening?
If someone repeatedly misses or ignores your direction, even after clarifying expectations and outcomes, you’re not dealing with a feedback issue anymore; you’re dealing with a role clarity issue.
That’s a separate conversation, and a necessary one.
Not punitive. Just: “Here’s what I need from this role. Here’s what keeps happening. Here’s how we fix it together.”
When you treat it as a workflow correction, not a personal failing, you stop the frustration loop long before it sinks morale (yours included).
Bringing It Back to Your Real Tuesday
No one becomes a flawless feedback machine. You’re still going to leave the occasional rushed comment between meetings and later think, Well, that could’ve been clearer. Congratulations, you’re human.
The goal isn’t perfection. The goal is a better default.
A default where:
- You define what “good” looks like before you start firing off notes.
- You review from strategy → structure → details, in that order.
- Your feedback lives in one place, not scattered across your digital footprint.
- Your comments quietly train your team to bring you stronger first drafts.
Do that consistently, and the entire feedback loop shifts. Rounds get shorter. The work gets sharper. And those “Why am I explaining this again?” moments stop showing up every week like an unwanted calendar invite.
—-
And if you want creative work that already understands this way of operating — where someone else handles the messy middle and carries the work across the finish line without needing you to say the same thing three times, that’s where Nicole Steffen Design lives.
Whenever you’re ready, we can help you get your Tuesdays back. Talk to Nicole.
