AI Digital Assistant: Making the case for a new way to work
My role was to make a high-visibility AI assistant feel worth changing for.
I joined after go-live, when legacy workflows were still the path of least resistance. I shaped the positioning, messaging and communications for 10K+ core leaders, translated business goals into a practical case for adoption, partnered on UX moments, and used success stories to replace tool fatigue with proof.
The Requisition & Internal Transfer Assistant — Providence’s AI-powered digital assistant, built with IBM Consulting on IBM watsonx Orchestrate and integrated with Oracle. It helps hiring leaders create requisitions, manage internal transfers and navigate approvals through one interface. Source ↗
Screenshot of the assistant in action goes here.
- 90%
- Drop in administrative burden
- 12 days
- Faster task completion
- 60%
- Lower transfer costs
- 70%
- Greater process accuracy
- 75K+
- Manager hours saved
- Coming soon
- App-wide & internal transfer adoption metrics
- Product marketing
- AI
- Change management
- User adoption
- Executive communications
- Customer insights
- Lifecycle marketing
- Cross-functional leadership
- Measurable business impact
A high-visibility AI launch that people weren't using.
A main strategic initiative for 2025–2026 with executive leadership focus.
Hiring leaders defaulted to familiar manual workflows and saw RITA as another HR system.
Early communications explained system capabilities, not the daily behavior change leaders needed.
10K+ core leaders — a vocal, influence-heavy group whose daily habits set the tone for everyone else.
“You can build it, but I won’t use it. I know how to use Genesis, I just don’t want to learn another administrative tool.”
Even a leader who helped shape the tool was firmly opposed to using it. This was more than an awareness gap: the communications had to make the case for changing familiar habits, not just introduce another administrative tool.
The goal was adoption of the app itself — and inside that sits an internal transfer adoption goal. Today the Internal Transfer Team (ITT) keeps people dedicated to 1:1 trouble ticket resolution. Every internal transfer task that moves into RITA is one fewer ticket that needs a person on the other end.
How I made the case for change.
- 01Customer insight
Managers weren't resisting AI. They had zero bandwidth for another tool.
Stakeholder interviews, core leader interviews, surveys and usage data showed the stall wasn't skepticism — it was tool fatigue. Leaders were already buried in administrative overhead, and learning one more system felt like more work, even when it replaced a clunky workflow they didn't love. So familiar manual habits stayed the default.
- 02Product marketing & positioning
Sell the outcome, not the system.
Repositioned RITA from technology features to human outcomes: less admin, faster hires and hours returned to patient care. Wrote the messaging framework, value pillars and persona positioning.
- 03Lifecycle marketing
Meet each leader where they are in adoption.
Built a multi-touch email nurture sequence targeted by manager persona and adoption stage — awareness first, then use cases, behaviors and change management once in market.
- 04Executive communications
Align leadership behind one adoption goal.
Wrote executive and leadership communications that tied RITA to business goals — framing leaders as budget stewards and RITA as the solution — so hospital leaders could champion the shift with a consistent, outcome-led story.
- 05Change management
Let peers make the case.
Activated early-adopter hiring leaders as visible champions and produced testimonial videos featuring respected peers showing their own time savings.
- 06Cross-functional leadership
Remove friction inside the product too.
Partnered with Product, HR Tech and accessibility teams on UX and accessibility content so the first experience inside the assistant felt fast and familiar.
What hiring leaders saw.
How leaders moved from “I won’t use it” to habit.
- 1Awareness & inertia
“I know Genesis. I don’t have time for another tool.”
My move · Leader communications that named the tool fatigue out loud.
- 2Reframe
“Why should this matter to me?”
My move · Budget-steward messaging tied RITA to business goals and time back.
- 3First use
“Fine, I’ll try one requisition.”
My move · The awareness commercial, hub content and UX moments made trying it easy.
- 4Habit & proof
“That took under a minute.”
My move · Success stories from peers turned early users into the case for everyone else.
A requisition that took 45 minutes to an hour on average now completes in under a minute — the point where the new habit stopped feeling like extra work.
RITA screens go here.
The SharePoint Community Hub.
I wrote the content for the community hub hiring leaders used as their one stop for RITA — the place every email and leadership message pointed back to.
- —Core leader communications
- —RITA commercial — the awareness video
- —Success stories from leaders
- —Updates as new use cases launched
Screenshot.
The commercial, and the people who made the case.
The awareness video — drop the film or a still here.
“A hiring leader's words about switching to RITA will go here.”
“A hiring leader's words about switching to RITA will go here.”
The assets I created.
After more than a year in production.
- 90%
- Drop in administrative burden
- 12 days
- Faster task completion
- 60%
- Lower transfer costs
- 70%
- Greater process accuracy
- 75K+
- Manager hours saved
- Adoption metrics
- App-wide and internal transfer adoption figures go here.
Several hundred thousand dollars per quarter
With strong adoption of RITA — especially for internal transfer tasks — fewer 1:1 trouble tickets need a person on the other end. At that level of adoption, the people resources no longer needed on the Internal Transfer Team could represent several hundred thousand dollars per quarter in reduced cost.
Two Pacesetter Awards for the RITA team
Both honors recognized the Providence RITA team. I was part of that team, responsible for the messaging and communications after go-live.