Business Environment
CIC serves distributed client operations with procurement, storefront, invoicing, partner, and reporting workflows that need reliable execution across many stakeholders.
Case Study
CIC Enterprise Systems Delivery
Enterprise technology program leadership across CIC's client portfolio and internal platforms, including the completed wind-down and transition of the company's largest client account.
Context
Complexity to Operating Rhythm
Program Challenge
System knowledge, delivery priorities, reporting needs, and process ownership needed to be translated into clear backlog governance, training, and executive-ready visibility.
Operating Scope
Client transition and archive delivery, e-commerce operations, SAP and Coupa coordination, Power BI and Looker Studio reporting, Azure DevOps and Smartsheet backlogs, partner workflows, and adoption support.
Approach
How the Work Was Structured
Backlog Governance
Created clearer intake, prioritization, status tracking, and stakeholder communication patterns across Azure DevOps and Smartsheet.
Analytics and Decision Support
Used Power BI and Looker Studio reporting to surface operational and margin signals, including pricing and margin variance for leadership action.
Modernization Discovery
Mapped legacy platform complexity across 450+ stored procedures and 217 database entities to support migration planning, ERD documentation, and SAP integration work.
Adoption and Training
Translated system changes into training, role clarity, and operational artifacts so teams could adopt new workflows rather than just receive new tooling.
Outcomes
Recruiter-Relevant Signals
Data Migration
2.6M+ rows engineered for the flagship client transition and archive delivery.Migration Quality
88.3% verified cross-file match rate across the client transition data.Storefront Cutover
3 storefronts decommissioned on schedule with same-day cutover execution.Why It Matters
What This Demonstrates
Enterprise ambiguity
Ability to turn undocumented system and process complexity into a clear delivery model.
Business and technical translation
Comfort moving between operational metrics, technical dependencies, stakeholder needs, and executive reporting.
Adoption-focused delivery
Emphasis on training, governance, role clarity, and operating rhythms so change becomes durable.