The Imaging Department Manager's Guide to Performance Reviews

I've conducted somewhere north of 500 performance reviews over my career, and I can tell you with absolute confidence that most imaging departments are doing them wrong. Not incompletely wrong or slightly inefficiently wrong—fundamentally, completely wrong.

The reason is that most performance reviews are designed by HR departments for legal protection, not for actual human development. They're a box to check, a documentation step, a CYA process. And techs know it. They walk into a review expecting to hear the same generic praise and vague development suggestions they heard last year, and they check out mentally.

I'm going to tell you how I evolved my review process over 20 years—what actually moved the needle in terms of retention, performance, and department morale.

What's Wrong With Standard Performance Reviews

Let me be direct. If your performance review process looks like this, you're wasting everyone's time:

You fill out a form with ratings on a 1-5 scale for things like "teamwork," "communication," and "initiative." You maybe write a paragraph about what the tech did well and what they need to improve. You schedule 30 minutes on their calendar. You sit across from them, read from the form, and give them a copy at the end. You maybe talk about a raise or lack thereof. Done.

Here's what's wrong with that approach:

It's too late. If this is the only feedback a tech hears about their performance, it's already too late to fix problems. Performance management isn't a once-a-year event. It's ongoing. When I was doing reviews this way, I'd find out in November that someone had been struggling since June, and now I'm trying to remediate a whole season of unaddressed performance issues.

It doesn't account for context. A 1-5 scale can't capture why someone's performance is what it is. Is their communication awkward because they're naturally quiet or because they're burned out? Are they not showing initiative because they're lazy or because they're confused about expectations? You can't address the actual problem if you're just rating the symptom.

It's backwards. You fill out the form before you talk to the tech. You've already made up your mind. Then you sit across from them and deliver a verdict rather than having a conversation. That's not development. That's judgment.

It treats everyone the same. The form is the same whether you're reviewing someone in their first year or their fifteenth. That makes no sense. Career stage matters. Tenure matters. The development plan for a new CT tech should look completely different from the development plan for a senior tech.

It focuses on the wrong metrics. When you're rating someone on a scale, you end up measuring easy things: attendance, punctuality, basic competence. You don't measure the things that actually matter in an imaging department: do other techs respect this person? Can patients trust this person? Does this tech make the department better or worse?

When I was managing my second department, I had a tech with perfect attendance, solid technical skills, and great communication ratings. But she was actively making the department worse. She undermined other staff members. She created drama. And I had no way to address it on the standard form because she "wasn't doing anything wrong." She just had a negative impact that the review system couldn't capture.

How I Redesigned My Review Process

At my third hospital, I basically threw out the standard form and built something that actually worked. Here's what I did:

I made feedback continuous, not annual. I started having brief one-on-ones with each team member every month. Not formal reviews—just 15 minutes to check in. "How are things going? Anything you need? Anything I should know about?" These conversations served as early warning systems. If something was going sideways, I'd know about it in the moment, not six months later.

I moved away from ratings and toward actual narrative. Instead of circling a number, I wrote specific observations and examples. Instead of "Communication: 4/5," I'd write something like: "Jennifer did an excellent job communicating with the radiologist about the protocol change for spine imaging. She asked clarifying questions, took notes, and then brought the information to the team. This demonstrates strong professional communication in technical contexts."

That's actionable. That's real. And Jennifer knows exactly what good communication looks like because she just saw an example of her doing it.

I got the tech's input first. I started asking techs to write their own assessment before the review meeting. Not a performance rating—just their reflection on the year. What did they accomplish? Where did they struggle? What do they want to focus on next year? This served two purposes: first, it gave me insight into how they perceived themselves and their performance, and second, it made them an active participant rather than someone being evaluated.

I separated pay conversations from development conversations. This was critical. If you're talking about salary in the same conversation you're giving development feedback, people stop listening to the development part because they're focused on whether they're getting a raise. I started doing compensation conversations separately, and it freed up the performance review to actually focus on growth.

I made room for relationship building. I know this sounds soft, but it fundamentally changed my reviews. I'd spend some time at the beginning just talking. "How was your weekend? What's new with you?" Not fake, not superficial—genuine interest. When someone feels like you actually know them as a person, they're more receptive to feedback and more motivated by development opportunities.

Structuring Reviews That Actually Work

Here's the framework I settled on that genuinely improved retention and performance:

Part 1: Recognition and Strengths (15 minutes)

Start here. Be specific about what this person does well. Use examples. Not "you're a great team player"—"you stayed late three times this month to help orient new staff, and they've all mentioned how patient and clear your explanations are."

I'm not being nice to soften them up for criticism. I'm being honest about what they're genuinely good at. Everyone has strengths. Acknowledging them builds trust and sets a collaborative tone for the harder parts of the conversation.

Ask them: "What do you feel good about from this past year?" Listen to their answer. You might learn something. They might mention accomplishments that didn't make it into your observation because they happened outside of your direct line of sight.

Part 2: Growth Areas (15 minutes)

Now talk about where they could improve. But frame it around their goals, not judgment. "You've mentioned wanting to get your CT certification. To make that happen, you need to strengthen your understanding of acquisition protocols. I want to pair you with Sarah for the next six weeks so you can observe and ask questions."

That's growth framing. You're not saying they're deficient. You're saying here's a path forward.

Ask for their perspective: "What do you think is holding you back? What do you need from me?" Again, this makes it a conversation, not a verdict.

Part 3: Goals and Development Plan (15 minutes)

Get specific about what comes next. What's one thing they'll focus on improving over the next year? What skills do they want to develop? Is there a certification they want? A new modality?

Write it down. Make it concrete. "Jennifer will complete her MRI certification by June 30, 2027. She'll attend the two-day course in May, and then she'll work shifts with the MRI tech lead through the summer to gain practical experience."

This gives them something to work toward. And it gives you something to follow up on.

Part 4: Compensation (separate meeting)

Maybe they're getting a raise. Maybe they're not. Maybe they're not eligible yet because they're new. But have that conversation separately, without all the performance stuff in the mix. Be clear about the reasoning.

And here's the thing I learned: if you're doing the rest of this right, people care less about the raise. I had a tech ask me one year not to give her a raise because she wanted to keep her health insurance plan and the raise would bump her into a different tier. Someone once told me a $1,500 raise was perfect because it covered her certification exam costs. People respond to actually understanding what's happening. When you're transparent about compensation decisions, they're less likely to resent them.

What This Looks Like for Different Career Stages

Your review approach should evolve with the person's tenure and career stage.

New techs (0-18 months). These reviews should be less about assessment and more about clarity. Are they meeting your minimum competency expectations? Do they understand the department's culture and expectations? Are they getting the support they need to succeed? Don't be evaluating their future potential yet—they're still ramping up.

Developing techs (18 months-5 years). This is where you're building their specialization. They should be starting to develop expertise in particular modalities or areas. Your reviews should focus on their growth trajectory. Where do they want to go? What certifications make sense? This is when you're thinking about succession planning.

Senior techs (5+ years). These reviews are less about basic competence and more about their role in the department. They're probably training newer staff. Are they doing that well? Are they innovating? Are they maintaining their own competence and continuing to grow? Senior techs need to be pushed to keep developing, not complacent.

The Real Impact

When I implemented this approach, I saw measurable changes. Our annual turnover rate went from 18% to 7% within two years. Not because I suddenly had more money to pay people, but because people felt genuinely seen and developed rather than rated and judged.

I also saw performance improvements. When people had concrete, specific development plans, they actually worked toward them. I had three techs get new certifications in a two-year period because we'd identified those as development goals and supported them.

And honestly? The job got easier. When you're doing continuous feedback throughout the year, the formal review is just a summary of conversations you've already had. There are no surprises. You're not sitting down to deliver disappointing news. You're both on the same page.

The Manager's Mindset

The fundamental shift is this: you're not a judge conducting a performance review. You're a manager responsible for helping this person succeed in their role and develop in their career. That's a completely different mindset, and it changes how you approach the whole process.

You're asking yourself: "What does this person need from me to be better? What are their goals? How can I support them? What's my responsibility in their development?"

Not: "Do they deserve a good rating?"

When you're in service of the person's development rather than in judgment of their performance, everything changes. You have better conversations. You get more honest feedback. People stay longer. They work harder. Your department gets better.

That's how you make performance reviews matter.