Work

Compensation platform modernization

Modernizing a high-trust compensation system by reducing manual exceptions, improving transparency, and sequencing pilots for adoption.

Back to work

Context

Modernizing a high-trust compensation system by reducing manual exceptions, improving end-user transparency, and sequencing pilots while standardizing pay models for scale.

Early discovery showed hourly compensation logic was more complex than expected, which increased risk to timelines and clinician trust.

I validated current-state complexity with Compensation, Contracting, and HRIS, mapped incremental build effort with the vendor, and pivoted delivery sequencing to prioritize RVU workflows first.

That sequencing enabled earlier clinician access via an RVU transparency pilot while hourly requirements were re-scoped.

What I owned

  • Set governance at the right altitude with executive and clinical SteerCos plus a daily core working group during sprints.
  • Ran a biweekly sprint cadence with dated commitments, explicit dependency tracking, and visible status in Smartsheet and ServiceNow.
  • Structured staged pilots to gather clinician feedback early and validate logic before cutover.
  • Built interim workflows and templates so clinicians could self-serve common questions while platform search improved.
  • Partnered with the compensation simplification workstream to keep plan standardization and system automation aligned.
  • Shipped quick clarity improvements like standardized site naming to reduce ambiguity in multi-site views.

Constraints and complexity

  • Acquisition-driven complexity across many local pay plans and pay-cycle cadences.
  • Manual exceptions and off-system calculations that created rework and risk.
  • Low transparency into RVU and CPT-level inputs, slowing resolution and reducing trust.
  • Upstream dependencies across timekeeping, HRIS, coding and RCM, billing, and payroll.

Results

  • Enabled earlier clinician access through an RVU transparency pilot while hourly requirements were re-scoped.
  • Improved stakeholder clarity with repeatable governance, decision points, and dependency tracking.
  • Reduced friction for end users by shipping interim workflows and clearer labeling while the platform matured.

What I learned

  • Optimize for making the next decision easier because that is how programs keep moving.
  • Pilots work best when they are treated like a product feedback loop, not just a go-live.
  • Small usability fixes often buy more trust than big promises.