From The Editor | November 16, 2026

How One Academic Research Team Builds Buy-In For New Technology

John Oncea Profile Photo

By John Oncea, Chief Editor, Clinical Tech Leader

collaboration, teamwork, doctors-GettyImages-2227865495

New technology doesn’t get adopted just because it works. At Duke’s spine research division, adoption runs through a deliberate, if informal, infrastructure of documentation, communication, and designated people.

“There’s a lot of infrastructure,” says Anna Thirakul, MS, CCRP, research program leader in the spine division at Duke University. “We use MS Teams whenever a new product is introduced.” She points to Advarra’s Encore and eReg platforms – two of the larger products her team has rolled out – as examples: “There’s dedicated infrastructure with tip sheets and MS Teams to support the mass users who are going to be using it.”

That infrastructure is necessary, but Thirakul is clear it isn’t sufficient on its own. The piece that actually moves adoption, in her account, is a network of designated “champions” spread across each clinical research unit; people whose job isn’t to know every feature of a new platform, but to make sure the staff who don’t have time to explore it on their own aren’t left behind.

Champions: Volunteers, Appointees, And Word Of Mouth

Duke doesn’t have a single formula for identifying who becomes a champion for a given technology. “It’s usually a mixture,” Thirakul says. Sometimes staff self-select: “If they know themselves well enough, they’re like, ‘Hey, I’d be willing to be a champion for this particular technology product.’” Sometimes leadership identifies someone directly. Thirakul’s own supervisor recruited her that way, telling her, “Anna, I know you’re pretty good at technology, so do you want to be a champion for certain things?” And sometimes it happens through internal referral, as when a colleague asked her to co-build dashboards using the Slicer Dicer tool she’d already adopted for feasibility work.

However someone becomes a champion, their job is the same: meet one-on-one with staff who aren’t comfortable navigating MS Teams or searching documentation on their own and help them set up the reports and settings that make a new system actually useful day-to-day.

The One Trait That Matters More Than Raw Skill

Asked what quality matters most in a technology champion – deep technical expertise or something else – Thirakul didn’t hesitate: communication.

“Communicator, because most likely that technology is going to go through upgrades and slight changes,” she says. “They need to be able to communicate those shifts and changes and adapt to it. They need to be able to communicate those changes as well as the overall usage of it.” A champion who understands a system deeply but can’t explain what changed in the latest version is less useful, in her framing, than one who can keep pace with ongoing updates and translate them for everyone else.

When Rollouts Don’t Go As Planned

Not every rollout at Duke has gone smoothly, and Thirakul doesn’t pretend otherwise. About a year into her time there, a new IRB system had to sync with the institution’s clinical trial management system – “That was a big challenge too,” she says. She also recalls hearing about pilot technologies, introduced to medium-sized departments for testing, that simply didn’t work out and were shelved before a wider release: it “was piloted and then it didn’t work, and then it was never released to the masses.”

That pattern – testing new systems in a mid-sized department before a full institutional rollout – functions as a kind of pressure-release valve, catching failures before they become organization-wide problems. It also depends on staff, and champions in particular, being willing to be the ones who experience that failure first.

Thirakul points to Duke’s shift to a new learning management system as a case where the rollout itself was straightforward, but the follow-through work wasn’t trivial: tip sheets and standard operating procedures across her division relied on hyperlinks that pointed to the old system, and each one had to be tracked down and updated. “That was a very seamless example,” she says, but only because staff knew in advance that the change was coming and had time to update their own documentation before the cutover, not after.

What Thirakul Says Is Worth Replicating

Asked what another organization could copy directly, Thirakul comes back to a single idea: designate someone who is comfortable failing.

“I think it’s just you’re appointing a trusted individual that’s okay with technology, that’s okay with failing with technology,” she says. “You can usually do an undo, or just even restart your computer if it’s really acting up.” That person gets their footing first, then teaches what they’ve learned to staff who aren’t as comfortable taking that early risk themselves. It’s a small, specific piece of advice, but it’s also the connective tissue between the tip sheets, the MS Teams channels, and the named products in Thirakul’s toolkit. None of it works without someone willing to go first.

What’s notable is how little of this depends on budget or headcount. Tip sheets, an MS Teams channel, and a handful of people willing to be the designated point of contact for a given system are all things most sites could stand up without a new hire or a new line item. The harder part, by Thirakul’s account, is simply deciding to formalize a role that might otherwise happen informally, or not at all.