Cynda Martin

Leading enterprise modernization, operational transformation, and cross-functional delivery initiatives across regulated environments.

Featured Case Studies

LEGACY APPLICATION MODERNIZATION PROGRAM

Delivered a multi-phase modernization program that transitioned 93 legacy FACETS sub-applications to web-based platforms while aligning execution to enterprise cloud migration timelines.Platform Scope:
Enterprise FACETS ecosystem modernization across 12+ departments, supporting claims processing, configuration workflows, and daily production operations.Role:
Owned execution of platform transitions, coordinating system migration, adoption readiness, and operational continuity across business and technical teams.Operational Challenge
The organization relied on a large set of legacy FACETS sub-applications delivered through a Citrix Workspace environment. These legacy components introduced long-term technical risk, limited scalability, and created operational friction as the platform moved toward web-based delivery and cloud alignment.At the same time, the business needed to maintain uninterrupted claims processing and configuration work across multiple departments. The challenge was to transition system functionality without disrupting production workflows or introducing access instability.Ownership & Responsibility
I owned platform transition execution across 12+ departments, ensuring system stability, access continuity, and alignment with Cognizant’s modernization roadmap.This included ownership of rollout sequencing, cross-team coordination, adoption readiness, and leadership communication to maintain operational performance throughout the transition.Strategy & Approach
To manage scale, risk, and adoption, I helped structure the initiative around a phased platform transition model focused on controlled rollout and readiness validation.
Key components included:
- Identifying and prioritizing FACETS legacy sub-applications based on usage and operational impact
- Aligning internal rollout cadence with Cognizant’s modernization and cloud roadmap
- Coordinating cross-team testing cycles within lower and higher environments prior to release
- Establishing structured communication through leadership forums and working sessions
- Supporting teams through change management and platform adoption concerns
This approach allowed modernization to occur incrementally while protecting production stability.Execution
I coordinated execution across 12+ departments, managing dependencies between business users, technical teams, and vendor delivery timelines.
Key execution responsibilities included:
- Sequencing migration waves
- Facilitating user acceptance testing and feedback cycles
- Managing rollout readiness checkpoints
- Tracking adoption progress
- Addressing resistance to platform change through structured communication and support
This ensured teams could transition FACETS functionality from Citrix-hosted legacy modules to web-based equivalents without operational disruption.Results & Impact
- Successfully transitioned 93 FACETS legacy sub-applications into web-based equivalents
- Supported modernization efforts across 12+ departments
- Advanced progress toward the long-term target of 347 web-based FACETS applications
- Established a sustainable migration cadence aligned with Cognizant’s roadmap to ensure cloud readiness before legacy support sunset
- Improved user confidence in web-based FACETS tools, accelerating readiness and adoption for future migration waves
An important outcome was cultural: testing teams and operational users became significantly more comfortable with the web platform after hands-on exposure, reducing resistance and improving momentum for upcoming phases.What This Demonstrates
This initiative highlights my ability to:
- Lead enterprise-scale platform modernization programs
- Coordinate cross-functional delivery within regulated environments
- Balance technical roadmap alignment with business continuity
- Drive adoption through structured rollout and stakeholder engagement
- Operate at the intersection of strategic operations, platform delivery, and execution leadership

SECURITY PROFILE CONSOLIDATION &
ACCESS VISIBILITY PROGRAM

Led a security optimization initiative that consolidated 14 profiles, reduced access complexity, and introduced real-time visibility tooling for leadership decision-making.Program Scope: Governance and access modernization initiative focused on reducing security profile sprawl, improving permission visibility, and preparing the organization for Federated Azure identity integration. This program required executive alignment, cross-department coordination, and risk-balanced decision facilitation.Operational Challenge
  The organization maintained 103 active security profiles across multiple departments, creating access complexity, governance risk, and operational overhead, especially as the platform prepared for Federated Azure identity integration and Active Directory (AD) group alignment.
  Leaders were hesitant to consolidate profiles due to highly specific access needs and concerns around compliance, risk exposure, and departmental autonomy. At the same time, the lack of centralized visibility made it difficult to quickly answer basic access questions, slowing decision-making and increasing manual effort.
  The challenge was to reduce profile sprawl without increasing risk, while creating transparency that
enabled leaders to make informed consolidation decisions.Ownership & Responsibility
  I led the security profile consolidation initiative, owning governance planning, access analysis, tooling enablement, stakeholder coordination, executive communication, and decision facilitation across multiple departments.
My role focused on balancing operational efficiency, security compliance, and future platform readiness.Strategy & Approach
  To shift consolidation from opinion-based discussions to data-driven decision-making, I introduced a structured, visibility-first approach.
Key elements included:
- Building an internal tool that exposed line-level access visibility for every security profile
- Enabling side-by-side profile comparison to identify overlap and redundancy
- Creating a shared data foundation leaders could trust
- Framing consolidation in the context of Azure AD group scalability and long-term identity management strategy
- Facilitating leadership discussions focused on risk-balanced standardization rather than isolated access control
This approach moved conversations from “what might be impacted” to “what is actually configured.”Execution
  I coordinated consolidation planning across multiple leadership teams and departments, guiding
stakeholders through:
- Profile usage analysis
- Redundancy identification
- Risk evaluation
- Consolidation opportunity mapping
- Governance approvals
At the same time, I deployed the internal access visibility tool that eliminated manual lookup processes and significantly reduced turnaround time for security-related questions.Results & Impact
- Reduced active security profiles from 103 to 89 through consolidation of 14 profiles
- Enabled near-instant access visibility, thereby reducing lookup time from manual investigation to seconds
- Eliminated repeated ad-hoc SQL queries and backend lookups for leadership access questions
- Improved decision speed and confidence by giving leaders direct access to accurate permission data
- Reduced future Azure Active Directory group complexity by minimizing identity group sprawl
- Lowered operational waste while maintaining compliance and existing risk thresholds
An important outcome was cultural: leadership shifted from access hoarding toward strategic standardization aligned with modernization goals.What This Demonstrates
This initiative highlights my ability to:
- Lead governance modernization programs
- Build data-driven decision frameworks
- Design internal tooling that enables operational scale
- Balance compliance, security, and efficiency
- Facilitate executive-level alignment on complex technical topics
- Drive long-term platform readiness

CLAIMS REQUEST INTAKE PROCESS REDESIGN

Designed and implemented a centralized intake workflow that reduced SLA turnaround from one week to under two days across seven operational teams.Program Scope: Operational workflow transformation initiative focused on improving service delivery performance, request transparency, and turnaround time across multiple operational teams.Operational Challenge  The original Claims Test Pro request process relied heavily on unstructured email intake, creating delays, visibility gaps, and inconsistent turnaround times.  Requests were often buried in inboxes, follow-up questions required additional email cycles, and status tracking was manual. At the same time, the technical workflow itself was complex, involving query creation, Claims Test Pro configuration, 837 keyword file generation, adjudication timing dependencies, and environment-specific batch constraints.  This created a high-risk operational environment where requests were easy to miss, turnaround times were unpredictable, communication was fragmented, and rework was common due to adjudication failures or timing conflicts.Ownership & Responsibility  I led the end-to-end redesign of the Claims Test intake workflow, owning process architecture, implementation coordination, documentation rollout, and cross-team adoption.  My goal was to improve reliability, speed, and transparency without disrupting existing technical execution workflows.Strategy & Approach  To eliminate email dependency and improve operational consistency, I introduced a centralized ticket-based intake model using Jama.  Key elements of the solution included:
- Standardized request forms capturing required criteria up front
- Automated request notifications to eliminate manual inbox monitoring
- In-platform communication for clarification and updates
- Centralized status tracking and request history
- Structured closeout process with delivered outputs attached to the request  This shifted the process from reactive email handling to proactive workflow management.Execution  I coordinated the rollout across 7 impacted teams, ensuring request templates were aligned to operational needs and the transition was fully supported through documentation and training.  Key execution responsibilities included:
- Aligning request templates to the needs of each impacted team
- Testing intake logic and notification flows before go-live
- Documenting the new process clearly for all stakeholders
- Training teams on how to submit and track requests in Jama
- Managing change adoption to move teams away from informal email habits toward structured intake workflowsResults & Impact
 
- Reduced official SLA from one week to three business days
- Consistently exceeded SLA performance, with average turnaround of approximately 1.5 days
- Eliminated missed requests caused by inbox overload
- Improved transparency into request status and ownership across all teams
- Reduced back-and-forth email cycles through in-platform communication
- Centralized operational tracking and historical auditability in a single systemAn important outcome was operational: the team shifted from an unpredictable, inbox-dependent process to a reliable, structured workflow that requesters and delivery teams could both depend on.What This Demonstrates  This initiative highlights my ability to:
- Design scalable operational workflows
- Apply tooling to eliminate manual process bottlenecks
- Lead cross-team change adoption
- Improve service delivery performance
- Balance technical constraints with operational efficiency

SQL MERGE GENERATOR & CONFIGURATION AUTOMATION ENGINE

Built a Python-based automation engine that eliminated manual SQL scripting for configuration updates, reduced deployment risk, and standardized database change workflows across environments.Project Scope: Internal tooling initiative focused on automating the creation of SQL configuration scripts used across enterprise environments. This tool directly supported database update workflows for teams responsible for configuration management, environment promotion, and production deployments.Operational ChallengeConfiguration updates across enterprise environments required hand-written SQL MERGE scripts. This process was time-consuming, error-prone, and inconsistent across team members.Scripts were built manually from scratch for each update cycle, with no standardization in structure, logging, or validation. A single syntax error or missed row condition could cause incorrect updates in production. There was no dry-run capability, meaning teams had limited ability to verify script behavior before execution. The reliance on individual SQL expertise created a knowledge bottleneck and introduced unnecessary deployment risk on every configuration cycle.Ownership & ResponsibilityI owned the full development lifecycle for this tool, from problem identification through design, build, testing, iteration, and deployment. I gathered requirements from the teams executing these workflows, validated the tool against real configuration scenarios, and documented usage for adoption.Strategy & ApproachRather than optimizing the manual process, I replaced it entirely with a schema-driven generation engine that encoded best-practice SQL patterns into reusable automation.Key design decisions included:
- Building dynamic schema inspection so the tool adapts to any table structure without manual configuration
- Supporting three generation modes: INSERT only, UPDATE only, and full MERGE, to match different deployment scenarios
- Including a dry-run preview mode that shows exactly what the script will do before any execution
- Adding row-level logging that tracks inserted, updated, and skipped records for full auditability
- Designing the output to be production-ready and peer-reviewable without additional editingExecutionI built the tool using Python with SQLAlchemy for schema inspection and database connectivity. Development was iterative, with testing conducted against real configuration tables across multiple environments.Key execution steps included:
- Mapping the existing manual scripting workflow to identify every point of risk and inefficiency
- Designing the schema inspection layer to handle variable table structures across environments
- Building and testing the three generation modes against real configuration scenarios
- Implementing dry-run logging and validating output accuracy before production use
- Documenting usage and running working sessions to onboard impacted team membersResults & Impact
- Eliminated hand-built MERGE query errors by replacing manual scripting with automated generation
- Standardized configuration update patterns across team members, removing individual variation
- Enabled safer deployments through dry-run preview and row-level logging before production execution
- Accelerated lower-environment testing cycles by removing scripting bottlenecks
- Reduced dependency on individual SQL expertise across the configuration workflow
- Improved audit readiness by generating structured, reviewable output on every runAn important outcome was operational: the team shifted from treating configuration updates as high-risk manual events to a repeatable, predictable process with built-in safeguards.What This DemonstratesThis initiative highlights my ability to:
- Identify operational risk and eliminate it through purpose-built internal tooling
- Design and build production-grade automation tools independently
- Encode enterprise best practices into reusable, scalable systems
- Reduce operational dependency on individual expertise through standardization
- Drive adoption of new tooling across technical teams

Tools & Automation

Internal Platforms Built to Accelerate Delivery and Reduce Operational Risk

SQL MERGE Generator & Configuration Automation Engine

Problem
Manual SQL MERGE scripting for configuration updates was time-consuming, inconsistent across team members, and introduced unnecessary deployment risk on every production cycle.Solution
I designed and built a schema-driven MERGE generation engine that dynamically inspects database structures and generates INSERT only, UPDATE only, or full MERGE statements on demand. A built-in dry-run preview mode and row-level logging allow teams to verify exactly what a script will do before any execution touches production.Impact
• Eliminated hand-built MERGE query errors across all configuration update workflows
• Standardized scripting patterns across team members, removing individual variation and knowledge dependency
• Accelerated lower-environment testing cycles by removing manual scripting bottlenecks
• Improved deployment reliability and audit readiness through structured, reviewable output on every run
• Reduced production risk by enabling full pre-execution validation before any changes are appliedStrategic Value
Rather than optimizing a broken manual process, this tool replaced it entirely. Best-practice SQL patterns are now encoded into reusable automation, giving the team a consistent, scalable approach to configuration management that does not depend on any single person's expertise.

• Back to Portfolio