From Greenhouse to Enterprise: How Providence Deployed AI Coaching in Ten Days to Navigate Workforce Transition

In early 2024, as generative artificial intelligence began reshaping corporate landscapes across industries, healthcare system Providence embarked on an internal experiment that would eventually culminate in a high-stakes operational rollout. Executives and learning professionals at the organization faced a familiar enterprise challenge: equipping leadership teams with the soft skills necessary to navigate complex human interactions, such as influencing without authority and delivering constructive feedback. While many organizations initially leaned into generative AI strictly for administrative productivity and automated document generation, a specialized team at Providence asked a fundamentally different question: Could language models be harnessed to simulate difficult managerial conversations in a secure, zero-risk environment?
The resulting initiative, known internally as My Conversation Companion, began not as a top-down corporate mandate, but as an isolated sandbox project. Over a two-and-a-half-year incubation period, the tool evolved through multiple iterations, platform migrations, and strict governance reviews. When Providence announced a major workforce transition plan earlier this year—designed to strengthen organizational culture by bringing remote and hybrid teams back into physical offices—the AI-guided conversation agent was rapidly repurposed. Within ten days, the tool passed formal enterprise governance and was successfully deployed to 1,300 core leaders facing sensitive personnel discussions.
The Incubation Phase and The Greenhouse Concept
The genesis of My Conversation Companion dates back to the immediate aftermath of ChatGPT’s mainstream market entry. Recognizing the profound potential for AI-driven professional development, project originators confronted a structural hurdle: Providence lacked an immediate, sanctioned internal technical infrastructure capable of supporting advanced conversational models. To overcome this bottleneck without violating institutional security protocols, the team utilized a conceptual framework termed "the greenhouse."
Operating on personal platforms entirely independent of enterprise networks, the developer tested interaction patterns, conversational flows, and scenario-building logic. Strict security guardrails were enforced from day one. No organizational data, protected health information (PHI), or personally identifiable information (PII) ever left the corporate ecosystem or entered the external testing environments. Instead, the greenhouse focused exclusively on abstract patterns of human communication—such as active listening, empathy mapping, and constructive critique.
This controlled isolation allowed the foundational prototype to mature past its fragile infancy without bearing the immediate compliance, scaling, or operational pressures of a Fortune-level healthcare enterprise. The core architectural philosophy was clear: innovations cannot be planted directly into harsh enterprise climates without prior cultivation, but they must enter through official channels once viable soil is established.
Chronology of Technical Evolution
The journey from a personal sandbox project to an enterprise-grade leadership tool required navigating four distinct technological environments over two and a half years:
- Early 2024 (The Greenhouse): Initial prompt engineering and conversational logic development on isolated external platforms, establishing generic human communication patterns.
- Mid-to-Late 2024 (ProvidenceChat): Integration into ProvidenceChat, an early internal instance of an AI chatbot. The concept was rebuilt as an uploadable PDF embedded with prompts. While functionally viable for individual users, the delivery mechanism lacked scalability and centralized messaging capabilities.
- Early 2025 (Microsoft Copilot Migration): Following the sunsetting of ProvidenceChat, the tool was restructured as a Copilot agent. User experience improved significantly with direct agent launching, though enterprise-wide deployment capabilities and accompanying governance frameworks were still under development.
- Late 2025 (Copilot Studio and Governance): The architecture transitioned to Copilot Studio, unlocking mass deployment capabilities. The primary hurdle shifted from technical execution to executive sponsorship, strategic prioritization, and formal risk mitigation clearance.
- Early 2026 (Deployment Phase): Following a strategic reframe that positioned the tool as an operational signal generator rather than a mere training aid, the system underwent a rapid ten-day pivot to support 1,300 core leaders through a critical workforce transition.
Strategic Reframe and The Operational Pause
Between the technical readiness achieved in late 2025 and the operational deployment earlier this year, the project entered a critical phase that innovators frequently encounter: the pause. With the tool built and validated, but no immediate institutional crisis demanding its implementation, projects of this nature often stall and quietly dissolve.
Rather than letting the initiative idle, the development team utilized this window to refine ancillary support systems. They constructed comprehensive SharePoint landing pages, developed communication strategies, and collaborated with enterprise stakeholders across various departments to draft realistic, scenario-specific coaching modules. Crucially, the team realized that marketing the tool as an "AI-guided conversation agent" generated minimal engagement. Instead, the messaging was fundamentally reframed around human-centric values: empowering leaders to show up effectively in critical moments and live into the organization’s core mission and promise ("Know Me, Care for Me, Ease My Way").
Concurrently, executive sponsors recognized an unpredicted secondary utility. While initially conceived as a learning and performance support mechanism, the interactions within My Conversation Companion generated qualitative signals and aggregated behavioral data regarding leadership anxieties and transition roadblocks. This telemetry provided executive leadership with real-time visibility into organizational sentiment that traditional surveys and status reports failed to capture.
Deployment and Quantitative Performance Metrics
When Providence initiated its workforce transition plan earlier this year, the executive leadership team required an immediate mechanism to support 1,300 core managers tasked with conducting sensitive, high-stakes dialogues with their respective teams. Because My Conversation Companion had already been thoroughly tested and vetted during the preceding months, the project team successfully updated the scenario topics, completed formal governance checks, and launched the system within a strict ten-day window.
To ensure responsible risk management during its inaugural enterprise run, the rollout was intentionally capped at the initial cohort of 1,300 core leaders. Post-deployment evaluation data revealed strong user reception among those who engaged deeply with the platform. Leaders who completed full scenario simulations rated the tool with a Net Promoter Score (NPS) of +54—a rating categorized as excellent within standard customer and user experience benchmarks, which range from -100 to +100.
Qualitative feedback highlighted the practical utility of the AI coach. Several managers described the simulated feedback as an "eye-opener," noting that the safe practice environment significantly reduced personal apprehension before conducting real-world restructuring conversations. Minor user friction points were documented primarily around interface speed and a preference for voice interaction capabilities rather than text-based inputs. Notably, rather than requesting the removal of the technology, highly engaged users actively petitioned for enterprise-wide expansion to grant their direct reports access to the platform.
Executive Perspective and Strategic Implications
Reflecting on the successful deployment, Sandra Murray, executive sponsor of the initiative, emphasized that technological innovation within healthcare systems must strictly align with tangible operational demands.
"As an executive sponsor, I do not start by asking whether a technology is interesting. I start by asking whether it solves a meaningful business problem and whether it helps our leaders show up more effectively in the moments that matter," Murray stated. "Role plays, simulations, and facilitated practice during in-person events are valuable, but they are limited by time, scheduling, and scale. My Conversation Companion brings that practice into the flow of work."
Murray noted that she personally utilized the tool prior to engaging in difficult staffing conversations associated with the workforce transition. The platform provided a structured cognitive space to transition from emotional reaction to proactive, compassionate execution.
Industry analysts observing the Providence rollout point to several broader implications for enterprise digital transformation:
- Agile Governance Alignment: Organizations that successfully scale generative AI tools typically establish dual-track frameworks, combining secure internal sandboxes with streamlined pathways for enterprise promotion once business use cases are proven.
- Reframing Technological Value: Adoption rates increase significantly when internal software is marketed around human mission alignment and operational support rather than technical novelty.
- Predictive Telemetry: Beyond end-user skill development, enterprise-grade conversational agents can function as critical feedback loops for executive decision-making during periods of institutional change.
Ultimately, Providence’s experience demonstrates that rapid institutional responsiveness to emerging operational needs is rarely a product of coincidence. By sustaining iterative development through years of platform shifts, organizational testing, and strategic pauses, the healthcare provider built a deployable capability well before the moment of necessity arrived—effectively engineering its own operational readiness.







