Habit, Not Hack: Separating Feedback from Identity (Trainee)

Feedback is about the work. The part that makes it feel personal is you — and that part can be separated out.

"Needs more clarity." "Logic jumps here." "This isn't convincing yet."

Alex read it three times. Not because the words were unclear — they were specific, direct, actionable. But because something happened between reading the words and processing them, an automatic translation that occurred without permission, that turned critique of the document into something that felt like critique of the person who had written it.

The spiral started fast.

I should have known this already. Everyone else probably finds this obvious. Maybe I'm not as far along as I thought. Maybe I'm not cut out for this.

None of those thoughts were written in the margin. None of them appeared anywhere in the feedback. But they felt as present as the actual comments — more present, in some ways, because they were louder and harder to dismiss.

By the time Alex closed the document, the feedback wasn't about the figure anymore.

It was about Alex.

How This Happens

The spiral is not irrational. It has a logic to it, built over years of training in environments where evaluation is constant and the stakes feel personal because, in research, the work and the person doing it are genuinely hard to separate.

You chose this question. You designed this experiment. You wrote this argument. When someone says the argument isn't convincing, the implicit subject of the sentence — the person who constructed it — is right there, available to absorb the criticism.

Research feedback also tends to arrive without the scaffolding that would make the separation explicit. In most professional contexts, critique comes with acknowledgment of what's working, context about why the feedback is being given, a tone that communicates the relationship between the critique and the thing being critiqued. Research feedback — especially written feedback — tends toward efficiency. Comment. Comment. Comment. The substance without the frame.

The efficiency is practical. For the person receiving it, especially early in training, the absence of frame means the frame gets supplied by the reader. And the frame most researchers supply — particularly when they're still establishing their sense of belonging in the field — is the one that connects the work's inadequacy to their own.

What Alex Tried

A check-in with the PI surfaced the problem directly.

"How did the draft feel?"

Alex hesitated. "Honestly? It felt personal."

The PI looked genuinely surprised. "It wasn't meant to be."

That was the gap. The feedback had been given as information about the document. It had been received as information about Alex. The PI hadn't known this was happening. Alex hadn't known how to name it until that moment. And in the space between those two realities, the work of processing feedback had become significantly harder than it needed to be.

Alex decided to try something structural — not an affirmation exercise, not a mindset reframe, but a physical separation of the two things that had been getting merged.

The next time feedback arrived, Alex opened a new page alongside the document and split it into two columns.

On the left: What the feedback says.

— Argument unclear in section two — Figure needs reorganization — Methods description too long — Transition between paragraphs three and four doesn't track

On the right: What the feedback does not say.

— You are incompetent — You don't belong here — You will never get this right — Your instincts are wrong — Everyone else finds this obvious

The exercise wasn't complicated. It didn't require the feedback to be wrong, or the sting to disappear, or the comments to be reframed as secretly positive. The critique remained exactly what it was. What changed was the container — the explicit acknowledgment that the left column and the right column were different documents, addressing different subjects, and that responding to one did not require accepting the other.

What Changed When the Columns Were Separate

With the two lists visible on the page, something shifted in how Alex approached the revision.

The comments on the left had a clear answer: work. The argument in section two needed to be made clearer — there was a specific thing to do, a specific place to do it, a specific criterion for knowing when it was done. The figure needed reorganization. The methods needed trimming. These were tasks with endpoints, not verdicts with implications.

The right column had no answer, because it wasn't a question. It was a projection — the internal narrative that feedback had been triggering, dressed up as information. Keeping it visible, explicitly labeled as what the feedback did not say, made it easier to notice when the spiral started and redirect toward the column that actually required a response.

Alex worked through the comments one by one. The draft improved. The revision meeting was more focused — less energy spent managing the feeling of having failed, more spent on the actual questions the feedback raised.

And something else. The weight lifted sooner. Not because the feedback had been easier or the critique softer — it hadn't — but because the processing time had shortened. The gap between receiving criticism and being able to use it had narrowed.

Feedback stopped feeling like a verdict on Alex's belonging in research.

It started feeling like a tool for improving the work.

The Habit: Treat Feedback as Information About the Work

The two-column exercise is one version of the habit. The underlying practice can take different forms, but the core move is always the same: create explicit separation between what was said and what was not said, between critique of the work and judgment of the person, before beginning to respond.

Before opening a marked-up draft or a set of reviewer comments, try one of these:

Read through once without responding. Let the comments land without immediately beginning to process them as personal information. Note what the actual requests are — what, specifically, the work is being asked to do differently. Don't respond to any of it yet.

Identify the task, not the indictment. For each comment, ask: "What is the work being asked to do here?" Not "what does this say about me?" but "what does this ask of the document?" The comment "this isn't convincing yet" asks the argument to be stronger. It does not ask you to be more capable.

Name the spiral when it starts. When the automatic translation begins — I should have known this, everyone else probably gets it — notice it as a separate event from the feedback itself. It is not a response to what was written. It is a pattern triggered by receiving critique, and it can be observed and set aside rather than absorbed as additional information about your standing in the field.

A Note on What This Isn't

This is not a habit about pretending feedback doesn't sting, or training yourself to be indifferent to criticism, or suppressing the emotional response that critique produces. The sting is real. It comes from caring about the work — which is not a problem to be fixed.

The habit is about the gap between the sting and the response — about what happens in the time between receiving criticism and acting on it. That gap is where identity gets tangled up with the document, where "this argument needs work" becomes "I don't know how to argue," where the useful information in the feedback gets buried under the weight of what it felt like to receive it.

The separation is not permanent and it is not always clean. Some feedback genuinely is about calibration — about whether you're developing the instincts the field requires — and ignoring that signal entirely would be its own failure. The habit is not about dismissing everything that doesn't feel good. It is about making sure that the response is proportionate to what was actually said, rather than to the worst possible interpretation of it.

For Supervisors and Mentors

The separation Alex had to build deliberately is something you can build structurally, in how you deliver feedback.

Two things make a significant difference. The first is framing — a sentence before the critique that situates it as information about the work rather than assessment of the person. "This is where I'd focus the revision" lands differently than "this doesn't work." The second is specificity — critique that names the exact thing to be addressed is harder to generalize into an identity statement than critique that remains vague. "The transition between paragraphs three and four loses the thread — here's why" is actionable in a way that "the logic jumps" is not.

Neither of these requires longer feedback or softer standards. They require precision — in what you are addressing and in how you signal what you are and are not saying. The trainee who receives precise, framed feedback is not just more likely to revise effectively. They are more likely to develop the capacity to receive feedback at all — which is a skill that compounds across an entire research career.

The comments in the margin are about the work. What they feel like is about you — and those are two different things, addressed in two different ways, on two different columns of a page.

Keep them separate.

That's not a hack. That's a habit.

✨ The GLC Feedback Reflection Guide includes a feedback framing section for structuring what you're saying, why you're saying it, and what happens next — because feedback that gets acted on is feedback that was delivered clearly.

Stories are fictionalized or composite narratives, created to illustrate common challenges and patterns in research life. They are intended for educational and reflective purposes and do not represent any specific individual or institution.