Hero Case Study — Global, Decentralized Travel + Meals Rollout (Enterprise)
Enterprise launch with SCIM provisioning via OneLogin + adoption strategy.
All content included here is sanitized, anonymized, and non-confidential.
Problem
A global organization needed a decentralized rollout for business travel and meals. Key pain points included high-cost airport transportation patterns and the need to drive adoption across business units without a single centralized owner.
Environment
- Program type: Global, decentralized travel + meals
- Existing ecosystem: TripActions for self-booking, corporate cards, expense workflows
- Integration complexity: First-time SCIM provisioning using OneLogin
- Rollout strategy: Phased launch with end-user activation focus
What I Did
- Built the business case with spend insights: surfaced cost-saving opportunity tied to real spend patterns.
- Aligned stakeholders on rollout approach: clarified decentralized ownership and established weekly operating cadence.
- Led SCIM provisioning readiness: validated lifecycle events (create/update/deactivate), attribute mapping, and ownership expectations.
- Managed launch-day execution: coordinated go-live steps, monitored access/provisioning, and triaged issues cross-functionally.
- Drove activation strategy: launched a $20 linking incentive and ran post-launch office hours to reduce friction.
Outcomes (Sanitized)
- Linkage: ~22% early linkage following launch + incentive
- Commercial impact: ~$202K gross bookings within ~90 days (trend increasing)
- Operational readiness: successful first-time SCIM go-live with launch-day risk managed through rapid troubleshooting
Linkage Growth — First 90 Days
Gross Bookings Growth — First 90 Days
By implementing SCIM roster automation at launch, we eliminated manual provisioning delays, enabling faster user access and improving early adoption. Adjusting permissions and access for executive travel use cases further translated activation into sustained commercial impact.
Learnings
- Adoption improves when the value story is tied to real spend patterns, not generic benefits.
- First-time SCIM go-lives succeed when ownership is explicit: data quality, lifecycle events, and exception handling.
- Office hours reduces friction and keeps decentralized programs moving.