Senior Clinical Development Specialist · MR / Imaging
Fri Jun 5 · Time TBD MR Bldg, Grandview (Waukesha)
Persona
The Rhythm MakerSteady BeatBold Pulse
Location
Waukesha, WI · MR building on Grandview
Segment
MR / Imaging · Clinical Development · USCAN
Priority
High-Medium
Campaign Use
Supporting / secondary-primary innovation story · clinical-to-product recruiting proof point · thematic montage voice
Score
3.33 avg — Mission 4 · On-Camera 4 · Clarity/Specificity/Resonance/Distinctiveness 3. Articulate and grounded; what's thin is the specific lived moment.
Two Interviews
Interviewed twice. Garrett Ewald (GEHC, May 5) — product-forward, missed the human spine. Rich / Chris / Jess (Fusion) — captured the conversion arc and emotional beats. The strong material below comes from the Fusion conversation; recapture it cleanly on camera.
Story in One SentenceA former MRI technologist who once preferred competing scanners now brings the patient room into the engineering room — helping GE HealthCare build MR technology that works better in real life.
Emotional TargetGrounded pride · credibility over melodrama · quiet impact at scale · the conviction that clinical experience makes technology more human
Story SpineOrthopedic-office origin (mom managed surgeons; he processed X-ray films) → radiology school → MR part-time at night → 11.5 years as an MRI tech → Siemens homer, skeptical of GE → "miserable" on a GE scanner at a clinic → a research project on faster, better-looking imaging changes his mind → joins GE HealthCare → becomes the clinical voice inside MR product development → Sonic 3D / 10,000 scans / 5–6 min → 2–3 min → "scanned across millions of patients around the world"
Story Hierarchy — Rich Must Know ThisSpine: The skeptic-to-believer conversion arc — the tech who disliked GE scanners and now helps build the next generation.
Hero moment (still missing): A specific instance where his clinical judgment changed, stopped, or improved a product. Neither interview delivered it. This is the one beat to land on camera.
Emotional bridge: The Mayo "day in the life" — a customer picked Trevor's feature out of everything he saw; "my heart warmed up." Use near the close.
"If it doesn't help the technologist, it doesn't help the patient" is the thesis line, not a story center.
What Rich Must Get
The conversion arc cleanly on camera (what made him dislike GE → what he saw that changed his mind) — plus one concrete moment where his clinical feedback changed a product (do not settle for the coil example; it doesn't resolve) — plus one vivid patient memory from his tech years — plus the Mayo "my heart warmed up" beat and the "millions of patients" scale line at the close.
Trevor is credible, candid, and practical — he doesn't need to be pushed into melodrama. His default register is feature names. Keep redirecting into the patient room and what a technologist actually experiences.
What Paul Must Capture
Trevor physically bridging clinical/demo and engineering/product spaces; hands on a coil; reviewing safe demo images with a colleague; a cross-functional discussion; scanner bore, table, and console details. Not generic office footage and not product beauty shots without his human explanation. Confirm clearance on bays, equipment, screens, and unreleased tech before building the visual plan.
Sensitivity — ConfidentialityUnreleased next-generation MR system, AI features (AI camera landmarking, AirX, contactless gating), Sonic DL / Sonic 3D specifics, coils, live development screens, customer bays, patient data / PHI, customer names (incl. Mayo Clinic), and unsupported product claims must not be filmed unless cleared. Use safe or staged demo content; shoot screens over-the-shoulder with shallow depth of field where needed.
Sensitivity — "I Didn't Like GE Scanners"His most credible and most sensitive material. Confirm GEHC's comfort before it anchors a cut. Frame it as an honest practitioner's starting point that resolves into changed belief and pride — never a criticism of the company. The arc must close on conversion.
Key Coaching NoteThe story isn't "Trevor works on MRI innovation." It's that someone who spent 11.5 years in the room with patients now makes the technology better for the people still in that room. Story, not spec sheet. Moments, not feature lists.
Soundbite Targets
◦ We bring the scan room into product development
◦ I didn't like GE scanners — then I saw something that changed my mind
◦ If it doesn't help the technologist, it doesn't help the patient
◦ MR is hard — there's no room for error
◦ I'm helping build the things I wish I'd had as a tech
◦ We have to be brutally honest sometimes
◦ My heart warmed up
◦ The stuff I've done is scanned across millions of patients around the world
Recommended Interview Arc
Let Trevor settle into his own voice on familiar ground before the product talk. He's practical, candid, and enthusiastic, but defaults to technical explanations — ground him in specifics early.
1
"For someone who has never met you, how would you describe what you do at GE HealthCare?"
2
"Before GE HealthCare, you spent more than a decade as an MRI technologist. What did you love about that work?"
3
"What first drew you into imaging? You mentioned your mom's orthopedic office and processing X-ray films."
4
"When you think back to your technologist days, what did a typical hard day in MR look like?"
5
"What still feels familiar when you walk into the MR building here?"
Listen for: Plainspoken descriptions of patient care, scan pressure, image quality, workflow, and the physical realities of the job.
If vague, probe: "Can you give me one day or one patient that captures that?" · "What would I have seen standing next to you in that room?" · "What made that hard — physically, emotionally, or operationally?"
Clarify his current job in human terms: he's not scanning patients anymore, but his clinical perspective shapes technology before it reaches technologists and patients.
1
"What does clinical development mean in the MR world?"
2
"Who do you work with most — engineers, physicists, pulse-sequence engineers, product managers, marketing, coil teams?"
3
"You've said your team is among the only ones in the building with real patient hands-on experience. What does that let you see that others can't?"
4
"What happens in your weekly image reviews?"
5
"You said you've become a kind of clinical engineer. What changed about how you think about your job?"
Listen for: The bridge role — clinical judgment translating technical work into real-world readiness.
If vague, probe: "What would an engineer or AI scientist need you to explain?" · "What makes an image technically impressive but not clinically good enough?" · "What would a radiologist or tech notice that a non-clinical person might miss?"
This is the spine. Get the skeptic-to-believer turn in his own words — clean, specific, and resolving into belief.
The TurnTrevor was a Siemens homer who disliked GE scanners and was "miserable" on a GE scanner at a clinic. Then he was asked to help on a research project — technology that made images faster and better-looking — and "six months earlier I'd have said absolutely not." Get the scene: what was the project, what did he see, what was the moment he reconsidered.
1
"You were very honest that you didn't like GE scanners at first. What specifically shaped that opinion?"
2
"What was happening in your career when that research project landed on your plate?"
3
"What did you see in the images or workflow that made you think, 'Wait, something different is happening here'?"
4
"What was the moment you went from 'absolutely not' to 'I might look into this'?"
5
"You said you've totally changed sides. How would you describe that shift now?"
Listen for: Honest skepticism, the specific thing he saw, the turn, and pride in helping make the products better.
If vague, probe: "Take me back to the day you saw it." · "What exactly was different about those images?" · "What did you tell your friend who recruited you?"
This is the missing beat. Both interviews gesture at "we have to be brutally honest" but never deliver a concrete instance where his judgment changed an outcome. Land it here.
Do Not Accept the Coil ExampleWhen asked for a specific instance, Trevor offers a coil he thought was suboptimal — but the team didn't change the design; they gathered feedback that confirmed the existing approach. It validates collaboration but has no payoff. Keep pushing for a moment where something actually changed.
1
"You said when your clinical team flags something, the engineering team listens. Walk me through one specific time you said, 'This isn't good enough yet.'"
2
"In that moment, what exactly wasn't acceptable — image quality, reconstruction time, workflow, patient comfort, usability?"
3
"How did you explain it to the engineering or product team in clinical terms?"
4
"What did they do differently after that conversation?"
5
"Was there a point in Sonic DL / Sonic 3D when the technology looked promising but still wouldn't have worked in the real world? What changed?"
6
"How did you know it was finally ready?"
Listen for: A real conflict — what was wrong, who heard it, what changed, what it improved for the customer or patient.
If vague, probe: "Even a small one — when did you stop the presses?" · "What would have shipped if you hadn't spoken up?" · "What would a radiologist have rejected?"
Move from feature proof to human stakes. Connect speed, image quality, and workflow to patient comfort, technologist stress, radiologist confidence, and backlogs.
1
"What does a faster scan mean for a patient who is anxious, in pain, moving, or struggling to hold still?"
2
"What does it mean for the technologist trying to keep a full day on track — the one who doesn't get lunch?"
3
"What does a better image mean for the radiologist, and ultimately the patient?"
4
"Tell me about the 'day in the life' here — the customer who said, out of everything, that's the feature he wanted. What did that do to you?"
5
"You hear about two-week backlogs and staffing shortages. How does that change how you think about what to build?"
Listen for: Fewer repeat scans, less discomfort, less pressure, more confidence, more patients helped — and the personal warmth of the Mayo moment.
If vague, probe: "Help me explain that to someone who's never had an MRI." · "What would that mean at 4 p.m. on a packed schedule?" · "What did you feel when he picked your feature?"
Show GE HealthCare as a place where clinical voices matter and cross-functional teams listen. Important for employment-brand differentiation.
1
"What surprised you about how much GE HealthCare values clinical input inside product development?"
2
"When you challenge an idea or say something isn't clinically ready, how does the team respond?"
3
"You said it takes every skill set in the building to make one product. Who are the people who make it possible?"
4
"What does collaboration look like when clinical, engineering, physics, product, and marketing all come together?"
5
"How has GE HealthCare let you carry your patient-care background into a different kind of impact?"
Listen for: Respect, trust, candor, cross-functional problem-solving, and the idea that clinical experience is amplified, not left behind.
If vague, probe: "Can you remember a meeting where your clinical background really mattered?" · "What did someone say that made you feel heard?"
Capture concise, usable lines about meaning, pride, scale, and #EveryRoleIsVital. Let him answer imperfectly, then bring him back to specifics.
1
"You've called this a dream job. What makes it feel that way beyond the technology?"
2
"What does it mean to know something you helped shape is being scanned across millions of patients?"
3
"What would you want MRI technologists to know about the people inside GE HealthCare building these tools?"
4
"What would you tell someone considering a clinical development role here?"
5
"Finish this thought: If it doesn't help the technologist, then…"
6
"What does #EveryRoleIsVital mean from where you sit?"
If vague, probe: "Say that more simply." · "What does that feel like personally?" · "What would your former technologist self say if he saw this technology now?"
Must-Ask Questions
1
"What did a hard MRI day feel like when you were a technologist — hour by hour, not technically?"
2
"You didn't like GE scanners. What specifically shaped that opinion?"
3
"What did you see in that research project that made you think something different was happening here?"
4
"What do you know from the scan room that an engineer or AI scientist might not know unless someone tells them?"
5
"Give me one specific moment where your clinical perspective changed, challenged, or stopped a product decision."
6
"With Sonic 3D, what was hard about getting from promising technology to something clinically useful?"
7
"What does cutting a scan from five or six minutes to two or three minutes mean in human terms?"
8
"Tell me about the customer who picked your feature out of everything he saw. What did that do to you?"
9
"What does it mean to know something you helped build is being scanned across millions of patients?"
10
"Finish this thought: If it doesn't help the technologist, then…"
11
"What does #EveryRoleIsVital mean for someone whose work happens before the product ever reaches a patient?"
Should-Ask Questions
1
"Can you remember a patient whose journey stayed with you from your technologist years?"
2
"What was the first moment after joining GE HealthCare when your technologist background felt genuinely valuable?"
3
"How do radiologists, technologists, and administrators react differently to the same innovation?"
4
"What happens in a weekly image review when the team disagrees?"
5
"How do you balance speed, image quality, usability, and patient comfort?"
6
"When you say you have to be 'brutally honest,' what's one example?"
7
"How have customer struggles changed since your tech days — what are they up against now?"
8
"Why do you still get excited after seven years?"
Rescue Questions
For when Trevor becomes too technical, too general, or too product-focused.
R
"Can you give me one specific example?"
R
"What did that look like in the room?"
R
"What would that have meant to you back when you were the tech?"
R
"Say that without the product names."
R
"Who was depending on that outcome?"
R
"What changed because you spoke up?"
R
"How would you explain that to someone who has never had an MRI?"
R
"Bring me back to the patient — what does that change for them?"
R
"What did that feel like personally?"
R
"What would your former technologist self say if he saw this now?"
Interviewer Coaching — For Rich
Best StrategyTrevor is credible, candid, and practical — you don't need to push him into emotion. His strength is authority. Let him sound like a grounded practitioner who earned his point of view. The work isn't drawing him out; it's keeping him out of product-list mode and in lived moments.
Trevor's Profile
Candid, technically fluent, authentically enthusiastic, believable as a builder/practitioner. He's strongest on the reality of a hard MRI day, the conversion from skeptic to believer, and the customer reactions that confirm the work matters.
He becomes less useful when he lists features and explains physics or pulse-sequence detail. Ask him to tell the story, not recite the spec sheet.
Product-List Drift — Active Steering RequiredWhen Trevor lists features — Sonic DL, Sonic 3D, AirX, contactless gating, AI camera landmarking, coils, electronic drive table — let him establish credibility once, then redirect immediately:
"What would that have meant to you when you were the tech?" "What does that change for the patient?"
The product details are proof, not the story. This needs active steering, not just awareness.
Four Key Moments to Slow Down1. A hard MRI day as a tech — The human stakes. Pain, motion, running behind, no lunch, one challenging patient throwing off the day. Don't skip past it.
2. The conversion — "I didn't like GE scanners" → the research project → "I would have said absolutely not." This is the hook. Get the scene of the moment he reconsidered.
3. The moment his judgment changed a product — The missing beat. Keep digging until something actually changed (not the coil example).
4. The Mayo "my heart warmed up" moment — The heart bridge. Save it for the close. Ask what he felt when the customer picked his feature.
Slow Down When He Mentions
◦ The orthopedic-office origin and processing X-ray films
◦ A patient whose journey he followed across return visits
◦ Running behind, missing lunch, one hard patient throwing off the day
◦ Being a Siemens homer / being "miserable" on a GE scanner
◦ The research project that changed his mind
◦ "We're the only ones in the building with real patient hands-on experience"
◦ The Mayo customer who wanted Sonic DL 2D — "my heart warmed up"
◦ "The stuff I've done is scanned across millions of patients"
Don't Spend Too Long On
◦ Long feature-name lists (Sonic DL/3D, AirX, contactless gating, AI landmarking, coils, drive table)
◦ Physics or pulse-sequence detail
◦ The coil example — it doesn't resolve; validates process but has no payoff
◦ Generic "MR has evolved so much" framing without a specific moment
◦ Customer or product specifics that raise clearance issues
The Coil Example — A NoteWhen asked for a specific instance, Trevor mentions a coil design he thought was suboptimal — but says they didn't really change the design; they gathered feedback that confirmed the existing approach was okay. It shows good collaboration but has no dramatic outcome. Don't let it stand in for the "moment that mattered." Keep pushing for an instance where something actually changed.
"I Didn't Like GE Scanners" — Guardrails
This is his most credible material and his most sensitive. It gives him authority — but only if it resolves cleanly into changed belief and current pride.
Confirm GEHC's comfort before using it. If captured, make sure the arc closes on conversion: an honest practitioner's starting point, not a knock on the company. If he stops at the criticism, follow up: "And then what changed your mind?"
Language That Unlocks Stronger Answers
the room with the patientwhat a technologist would actually experiencenot good enough yetwhat changed because you spoke upthe patient behind the scanwhat your former technologist self would noticetechnically impressive vs. clinically readysay that without the product namesbring me back to the patient
Main Steering MoveWhenever Trevor drifts into features, bring him back to one person, one moment, one change: "What did that mean for the technologist? What did that mean for the patient?"
Story Beats to Hit
1 · The Setup
11.5 years as an MRI technologist; orthopedic-office origin; the scanner room, patient care, workflow pressure, and the physical realities of MR.
Strong — capture it cleanly on camera
2 · The Tension
MR is hard. Patients in pain, moving, uncomfortable. Schedule pressure, repeat scans, backlogs, no room for error.
Needs Sharpening — get one vivid patient or hard-day example
3 · The Turn
Siemens homer who disliked GE scanners; "miserable" on a GE clinic scanner; a research project on faster, better-looking imaging changes his mind.
Strong — get the scene of the moment he reconsidered
4 · The Action
Brings clinical judgment into product development; reviews images, tests features, helps decide whether technology is truly usable.
The Gap — needs one "I pushed and it changed" moment
5 · The Collaboration
Works with scientists, physicists, pulse-sequence engineers, marketing, coil teams. Weekly image reviews are a strong proof point.
Strong — get a human collaboration moment, not a stakeholder list
6 · The Outcome
Sonic 3D / Sonic DL; 10,000 scans; 5–6 min → 2–3 min; radiologist, technologist, and administrator reactions.
Strong — make it human, not technical
7 · The Meaning
Clinical experience shapes the technology; his patient connection scaled rather than ended. "Millions of patients around the world."
Very Strong — let him land it and the thesis line in his own words
Personal Meaning
I used to be the person in the room with the patient — I still carry that into every product decision.
Prompt: "How does your time as a technologist still show up in your work today?"
This is a dream job — I'm helping build the things I wish I'd had as a tech.
Prompt: "You've called this a dream job. What makes it feel that way beyond the technology?"
I didn't like GE scanners. Then I saw something that changed my mind.
Prompt: "What specifically shaped your opinion before — and what changed it?" (Confirm clearance before using.)
I know what it feels like when a scan is hard — and that changes how I judge technology.
Prompt: "What do you understand from the scan room that you can't learn from a spec sheet?"
Patient / Customer / Clinician Impact
A faster scan can mean less discomfort, less anxiety, and fewer chances for a repeat.
Prompt: "What does a faster scan mean for a patient in human terms?"
A better image gives the radiologist confidence and the technologist a better day.
Prompt: "What does a better image mean beyond the screen?"
There's no room for error — so saving a few minutes really matters on a full schedule.
Prompt: "What does saving a few minutes mean during a full day of MRI exams?"
When a customer says, 'holy cow, that's fast,' I know the work is changing something real.
Prompt: "What goes through your mind when a customer reacts like that?"
Team and Culture
When the clinical side says something isn't good enough, the team listens.
Prompt: "What happens when you tell the team something isn't ready yet?"
We're among the only ones in the building who've been in the room with a struggling patient.
Prompt: "What does your team bring that the engineers and scientists can't?"
It takes every skill set in this building to make one product.
Prompt: "Who has to come together to make an MR feature truly work?"
We may be on different teams, but in practice we're solving the same problem.
Prompt: "How would you describe the partnership between clinical development and engineering?"
#EveryRoleIsVital Connective Lines
If it doesn't help the technologist, it doesn't help the patient.
Prompt: "Finish this thought: If it doesn't help the technologist…"
Every decision before launch can reach someone in a scan room later.
Prompt: "Why does your role matter before the product ever reaches a customer?"
The work behind the scenes becomes part of patient care.
Prompt: "What do you want people to understand about behind-the-scenes roles here?"
Clinical experience can shape the future of the technology.
Prompt: "What does your story say about the kind of impact someone can have here?"
Montage-Friendly Lines
"MR is hard."
Prompt: "In the simplest terms, what should people understand about MRI?"
"There's no room for error."
Prompt: "What pressure does a technologist feel during a full day of scans?"
"We bring the scan room into product development."
Prompt: "What is your role in one sentence?"
"The stuff I've done is scanned across millions of patients around the world."
Prompt: "When the scale of this hits you, what does it feel like?"
"Just when you think you've hit a ceiling, there's more."
Prompt: "Why does the work still feel exciting after seven years?"
Visual Guidance — For Paul and Crew
If Time Is Limited — Top 5 Shots
1. Trevor in an MR scanner / demo environment with cleared equipment
2. Trevor reviewing safe MR demo images on a monitor with a colleague
3. Trevor handling or explaining a coil
4. Trevor in cross-functional discussion with engineering / product colleagues
5. The bridge shot — Trevor walking between clinical/demo space and engineering/product space
MR building on Grandview — the home base. Prioritize spaces that feel hands-on and specific to MR.
MR demo or customer-facing bay — if cleared. Trevor offered to look at one of the customer bays.
Bridge: Trevor moving between clinical/demo and engineering/product space — clinical experience crossing into design.
Hands-on expertise: Trevor's hands on a coil or pointing to a scan detail.
Signal metaphor: Coils as antennas capturing signal — Trevor translating human signal from the scan room into product decisions.
Image review: The team gathered around images — judgment, care, collaboration.
Speed with empathy: Table, scanner, and workflow details that suggest reducing patient burden, not just throughput.
From one room to many: Trevor alone in a scanner bay, then with a team — his patient-room experience now scaling through product development.
The visual challenge is that the most compelling spaces — scanner rooms, screens, unreleased tech, customer bays — are also the most restricted. Plan around it:
Clear early: get permissions on bays, equipment, screens, and any next-gen visuals before the shoot, not on the day.
Stage safe content: prepare non-identifiable demo images for any on-screen moments.
Shoot screens carefully: over-the-shoulder with shallow depth of field if anything is sensitive.
Lean on the safe wins: coils, table, bore, hands, and collaboration carry the story without exposing confidential work.
Favor the bridge: transition shots between clinical and engineering spaces carry meaning without revealing anything restricted.
Live patient data or protected health information
Customer names, accounts, or customer-specific configurations (incl. Mayo Clinic)
Unreleased system details or next-generation features not cleared for external use