Managing Up: How Rad Techs Can Influence Department Decisions

I learned the hard way that having a good idea doesn't mean it gets implemented.

Ten years ago, I watched my department waste tens of thousands of dollars on a new workflow software nobody asked the techs about. It was technically sound by IT standards. But it added four steps to every patient check-in process, it didn't integrate with our existing systems, and it slowed us down. We flooded our manager with complaints. Nothing changed until six months later when the radiologists started complaining about delays.

I remember thinking: "Why did it take the radiologists complaining for management to notice what we've been saying since day one?"

That failure taught me something critical. As a tech, you don't fail because your ideas are bad. You fail because you're not speaking the language management hears, you don't have the credibility they trust yet, and you haven't built the case in a way that makes action obvious.

I've spent the last five years intentionally learning how to influence decisions in my department, and I've watched good techs get completely ignored because they didn't know the game. If you want your voice to matter—and it should—you need to understand how to manage up.

Credibility Is Your Only Currency

Before you ask for anything, understand this: management makes decisions based on who they trust.

You build that trust by being consistently competent in your primary role. Sounds obvious, but it matters. If you're the tech who calls in sick twice a month, shows up late regularly, or does mediocre work in your day job, nobody is going to take your suggestions seriously. Why would they? You haven't proven you can be trusted with your basic responsibilities.

The techs who influence decisions are the ones who show up, do excellent work, and are reliable. That's baseline. If you don't have that, stop here. Develop that first. Everything else is built on it.

But competence alone isn't enough. You also need credibility in the specific area you're trying to influence. If you want to convince your director to change CT protocols, you need to demonstrate that you understand imaging physics, current best practices, and how those protocols impact your work. If you want to argue for staffing changes, you need to show you understand labor metrics and scheduling complexity, not just "I'm tired."

Here's how you build that credibility:

Volunteer for committees or projects. When your director mentions they need someone to help evaluate new software or work on protocol standardization, raise your hand. This sounds like work (it is), but you're putting yourself in rooms where decisions happen and showing that you can think bigger than your scanner.

Educate yourself. Read white papers. Understand current standards (AAPM for radiation dose, ACR for protocols, ASRT for professional development). When you reference actual evidence, you stop sounding like a complainer and start sounding like a professional. Management notices this.

Document what you observe. If a workflow problem is costing time or quality, keep notes. How many minutes does it add to each patient? What's the impact? Don't just remember it—track it. This transforms your observation from opinion to data.

Mentor newer techs. This signals to management that you're invested in the department's long-term success, not just your paycheck. People who mentor are taken more seriously.

Over fifteen years, I've intentionally built credibility in my department. I'm the tech who understands imaging physics well enough to discuss it with radiologists. I mentor techs and they respect me. I track data about our workflows. Management knows that when I come to them with something, I've thought it through. That credibility is what makes them listen.

Understanding the Constraints Management Actually Faces

Here's the thing techs often don't realize: your manager is not ignoring your suggestions out of spite. They're usually caught between competing pressures you don't see.

Your director probably wants to hire more staff. But the budget's constrained by hospital administration. They'd like to upgrade equipment, but there's a capital spending freeze. They see that your morale is low, but giving raises requires approval from finance. They're not powerless—but they're not all-powerful either.

When I finally got my director to explain what they actually decide versus what they request up the chain, it changed how I approached everything. Some decisions are truly theirs. Some are recommendations they can make but not control. Some are completely out of their hands.

Take salary bands. Your manager usually cannot unilaterally give you a bigger raise. There are hospital-wide compensation structures. But they can advocate for you internally and make your case to administration. They can point out that you're losing techs to better-paying systems and that's affecting retention. They can request a market study showing that your hospital is below-market rates.

The result is the same for you if they're effective at managing up—you get a raise. But if you don't understand that they can't just decide this on their own, you'll blame them for not fighting hard enough.

I learned this by asking directly. I said to my director: "I want to understand what's in your control and what isn't, so I can frame requests realistically." We had that honest conversation, and it completely changed how I approach conversations with management. I'm not asking them to do impossible things. I'm asking them to fight for things they can actually influence.

The Framework for Proposing Change

When you want to advocate for something, use this structure:

1. Frame it as a department problem, not a personal complaint.

Bad: "I'm tired of our schedules being terrible."

Good: "Our scheduling pattern is causing retention issues. We've had three techs leave in the last year, and exit interviews mention scheduling inflexibility. Replacing a tech costs $15,000-$20,000. We could improve retention with scheduling changes that also benefit patient flow."

See the difference? One is about you. One is about department metrics and cost-benefit.

2. Present data.

Don't say "everyone's burnout." Say "We had three resignations in the last year. Two cited scheduling. Our ARRT radiation dose per patient is 15% above the benchmark we set in 2023."

This is why I keep notes. Your opinion matters less than your data. Management doesn't make decisions on anecdotes—they make them on metrics.

3. Offer solutions with realistic tradeoffs.

Bad: "We need better equipment."

Good: "Our CT equipment is 2012-model. New equipment would improve image quality and reduce patient scan times by an average of four minutes per patient. At 50 CTs per day, that's 200 minutes of efficiency gain. The capital cost is $500K and the ROI is approximately 18 months based on reduced patient stays and fewer repeat scans."

Notice you're not just complaining. You're acknowledging cost and quantifying benefit.

4. Anticipate objections and address them preemptively.

If you know budget is tight, acknowledge it. "I understand capital spending is limited this year. Would it be possible to plan this for FY 2027 and start building a business case now?"

If you know staffing is thin, acknowledge that too. "I know we can't pull people for this project right now, but if we could allocate even 20 hours per month from current staff, here's what we could accomplish..."

This shows you understand the constraints, which makes you more credible.

5. Ask what success looks like.

End with: "If this is something you think we should pursue, what would help you make the case to administration?" or "What data would be most helpful for me to gather to make this stronger?"

This shows you understand their job. You're not asking them to say yes or no. You're partnering with them on the next step.

Knowing When to Push and When to Back Off

There's an art to choosing your battles.

I learned this the hard way. Early in my career, I was frustrated about everything and vocal about all of it. "The protocols are outdated! The equipment is old! Staffing is low! The EMR is terrible!" I was right about most of it, but my credibility got shredded because I seemed like I was always complaining.

Eventually, I realized the wins came when I picked one specific thing, built a careful case, and pushed hard on that one issue. Then I let it go and waited for the win before choosing the next battle.

Don't come to management with a list of ten problems. Pick two or three that really matter. Make those cases airtight. Let other things go.

Here's how I decide: Is this a patient safety issue? That gets pushed hard. Is it affecting retention in a measurable way? That gets prioritized. Is it an efficiency problem that has financial impact? That's worth advocating for. Is it something that bothers me personally but isn't affecting the department's core function? I let that one go.

I had a situation five years ago where I was frustrated that our PACS workstations weren't ergonomically set up. My wrists were sore. I wanted new desk setups. But I realized: this isn't a retention issue (I'm the only one complaining), it's not a safety issue, and it's not affecting patient care. So instead of pushing it as a formal request, I worked with facilities informally. We adjusted what we could and I adapted my setup. The problem wasn't important enough to burn credibility on.

Real Wins From Actually Managing Up

To show what's possible, here are actual changes I've driven in my department over fifteen years:

Protocol standardization. I spent six months reviewing our CT and MRI protocols against ACR standards and identified 12 protocols that didn't match current best practice. Documented the gaps, presented the research to our medical director, and worked with our informatics team to update them. This improved image quality and reduced patient complaints about scan times.

Radiation dose reduction. I noticed we were exceeding our self-set benchmarks on certain protocols. I tracked this formally for three months and then presented the data. We implemented dose optimization, and our average patient dose dropped 18% while maintaining diagnostic quality. The hospital loved this (regulatory compliance and cost reduction), so it got approved quickly.

Mentorship program. I proposed a formal mentorship structure for new techs, with dedicated time allocated. I showed how poor onboarding was contributing to turnover and how other hospitals structured this. Got approved and now manage the program. This actually changed my role and increased my influence.

Staffing adjustment. We were understaffed on night shift specifically. I tracked metrics showing that night shift was running 20% behind on throughput compared to day shift, and it was driving overtime costs. Showed that hiring one full-time night shift tech would save money on overtime within six months. Got approved.

None of these were me being the smartest person in the room. They were me understanding the system, building credible arguments, and knowing how to talk to management.

The Long-Term Game

Here's what I'd tell any tech who wants to have influence: it takes time. Credibility builds over years, not weeks. But once you have it, management starts coming to you. They ask your opinion. They seek your input on decisions that affect your work.

That's when you know you're actually managing up well. You're not begging for change anymore. You're partners in making the department better.

That didn't happen for me in year three or four. It took until year seven or eight. But now, in year fifteen, I have genuine influence on how my department functions. And I didn't get there by being loud. I got there by being credible, strategic, and understanding the game.

You can do the same thing. You just have to understand that influence is a skill, and like any skill, it takes practice.