All projects
Cross-Functional

Cross-Functional Operational Coordination

Served as the operational point of contact linking Patient Access with providers, IT, and practice managers on shared work, from scheduling changes to EMR issues to workflow rollouts.

Role
Operational Liaison
Timeline
2021 – 2025
Confidence
★★★★★
Stakeholders
5

Business Problem

Cross-functional work stalled without a clear operational owner on the Patient Access side.

Project Objective

Keep cross-functional operational work moving and clearly communicated.

Stakeholders

  • Providers
  • Practice Managers
  • IT
  • Supervisors
  • Front-line Staff

Deliverables

  • Meeting Agendas
  • Decision Logs
  • Email Communications

Planning

  • Clarified scope and decisions needed with each partner
  • Mapped dependencies and communication cadences

Execution

  • Facilitated meetings and follow-ups
  • Documented decisions and next actions
  • Escalated blockers clearly and early

Monitoring & Controlling

  • Tracked open items to closure
  • Communicated status to stakeholders

Results

  • Faster cross-functional turnaround
  • Fewer dropped items
  • Clearer decisions

Business Impact

  • Alignment across functions
  • Reduced rework
  • Trust with partner teams

Artifacts

Software Used

Microsoft TeamsMicrosoft OutlookWebExSharePoint

Skills Demonstrated

Cross Functional CollaborationStakeholder CommunicationLeadershipDocumentation

PMI Domain Mapping

People
  • · Engage stakeholders
  • · Collaborate with stakeholders
Process
  • · Manage communications
  • · Manage project artifacts
Business Environment
  • · Support organizational change

Resume Bullet

"Served as operational liaison between Patient Access and cross-functional partners, keeping shared work moving and clearly communicated."

STAR Interview Example

situation

Cross-functional operational work stalled without a clear owner.

task

Keep the work moving with clear communication.

action

Facilitated meetings, documented decisions, and escalated blockers early.

result

Faster turnaround and fewer dropped items.

Lessons Learned

  • Decisions need to be captured, not just made
  • Early escalation prevents surprise

Evidence

Meeting notes, decision logs, email trails.

Confidence: ★★★★★