VMware · Enterprise operations

Colleague Experience Operating Model

Shared operating practices for intake, delivery, governance, and cross-functional collaboration.

Operating modelOrganizational capabilityIntake and governanceCross-functional alignment

Context

The Colleague Experience function had grown into a complex internal organization with many systems, processes, artifacts, engagement methods, and partner relationships. That complexity affected intake, handoffs, project visibility, consistency, and how the team worked across the enterprise.

Role

I was the first and most senior Experience Strategist and participated on the leadership team. I drafted, proposed, and championed new operating practices, brought proven methods and artifacts from earlier work, mentored staff, and helped develop a shared voice for explaining the work.

Operating model view

A shared operating model connecting intake, governance, partner alignment, and delivery.

Diagram showing the core elements of a colleague experience operating model.

Operating model

  • Introduced a structured project and initiative intake/onboarding framework.
  • Standardized project tracking and repositories around Jira, Confluence, and Trello.
  • Developed shared artifact templates tied to operating practices.
  • Created and socialized common terminology.
  • Clarified engagement expectations with partner teams.

Outcome

Intake became more informed, work became more visible, outputs became more consistent, and the function developed a more unified way of communicating with partner teams.

Scale: the core function was roughly 28 to 30 people and worked across approximately 60 to 70 partner teams spanning Product, Business, HR, Sales, Marketing, and IT.

Its significance

The intervention changed how a function received work, organized itself, collaborated, and represented its value across the enterprise.

Continue

See the broader pattern.