Transformation Rescue for Specialized Medium-Sized Saas Company

Case Study

Role: Engagement Lead
Timeline: 15 months
Organization Size: 500-person technology organization (18 product teams, 4 value streams)
Distribution: US, India, Ukraine, Latin America

Challenge

A specialized SaaS company was six months into a Scaled Agile Framework (SAFe) implementation that had stalled due to a lack of transparency of the portfolio work, inconsistent agile practices, and political infighting among the Senior Leadership Team (SLT). The organization faced critical delivery and operational problems, such as:

Delivery Issues:

• Deployment times remained stagnant with work sitting undeployed for 6+ months
• No CI/CD pipeline established
• Security vulnerabilities discovered with no clear remediation path
• Bloated operations organization

Organizational Dysfunction:

• Zero visibility into teamwork or how results were measured
• Teams using fragmented Jira instances (mix of team-owned and company-owned boards, creating a lack of transparency into the team’s backlogs)
• Low trust between Product and Technology organizations
• Open conflict between the Chief Product Officer and the CTO creating a highly charged political environment
• Constant political maneuvering across the VP and C-suite levels

Mandate: The CTO brought me in to restructure the deployment strategy and transform PI planning to deliver more value in less time while moving the organization toward flow-based delivery.

Approach

Phase 1: Establish Visibility (Months 1-3)

Standardized Jira Instances Across All Teams

The priority was creating transparency into work and measurement. Teams were operating with fragmented, inconsistent Jira boards that hid problems and prevented any systemic view of delivery.

Change Management Challenge:

• Strong resistance from teams who felt they were losing autonomy
• Product managers had built elaborate but brittle workarounds
• Passive resistance manifested as avoided meetings and ignored feedback requests
• Political opposition from VPs and C-suite members

Executive Support: Secured public backing from CTO in company town hall, legitimizing the change and reducing passive resistance.

Outcomes:

• Created systemic visibility into bottlenecks and deployment process variations
• Identified teams with hidden internal dysfunction
• Enabled data-driven decisions about team restructuring (broke apart struggling teams, reducing overall strain)

Phase 2: Prove the Model (Months 2-4)

Kanban Pilot with CTO’s Moonshot Teams

Selected highly technical teams working on innovation initiatives without heavy product oversight to demonstrate the value of flow-based delivery.

Implementation:

• Transitioned pilot teams to Kanban methodology
• Established weekly demos, creating natural accountability
• Eliminated cross-departmental approval delays

Results: Within 2-4 weeks, visible progress convinced the C-suite to mandate scaling across the organization.

Phase 3: Scale and Optimize (Months 4-15)

Restructured Planning Process

• Reduced PI Planning from 4 days to half-day quarterly planning sessions
• Refocused time from process to outcomes
• Financial Impact: $250,000 annual cost savings

Standardized Deployment Practices

• Established 2-week deployment cadence across all 18 teams
• Shifted from large-batch irregular releases to small-batch frequent deployments
• Cleared 6-month backlog of undeployed work

Connected Work to Strategy

• Coached Release Train Engineers to consistently ask whether work fed into company OKRs
• Improved priority clarity and strategic alignment across teams

Improved System Reliability

• Partnered with DevOps team to establish outage reporting
• Technical Impact: 10% increase in system stability (2023)

Optimized Vendor Management

• Restructured vendors under my domain
• Financial Impact: $8,000 annual savings

Results

Operational Improvements

• Deployment Velocity: Moved from irregular releases with 6-month backlogs to standardized 2-week deployment cycles
• Cycle Time: Improved through systematic bottleneck identification and process mapping
• System Stability: 10% improvement through established outage reporting
• Risk Reduction: Smaller batch deployments reduced deployment risk

Organizational Improvements

• Strategic Alignment: Improved priority clarity through consistent OKR-to-work connection
• Team Health: Higher morale as coaches engaged more deeply with visible work
• Conflict Resolution: Surfaced and resolved previously hidden team dysfunction

Financial Impact

• $258,000 in annual cost savings: 
• $250,000 from restructured planning (4 days → half day)
• $8,000 from vendor management optimization

Constraints and Context

Political Environment: The transformation occurred within a challenging political environment. Open conflict between the CPO and CTO created friction that cascaded through the organization. Opposition from other VPs and C-suite members alternated between overt and covert resistance.

Incomplete Transformation: The engagement ended after 15 months when I was laid off as part of broader organizational cuts in January 2024. The layoff occurred before completing the full transition to flow-based delivery.

Cultural Limitations: Some cultural issues proved resistant to change within the available timeframe:

• OKR misuse (treated as commitments with 100% completion targets instead of 80% stretch goals)
• Reinforcement of wrong behaviors through promotion decisions
• Deep-rooted political dynamics at executive level

Key Lessons

Visibility as Foundation: Standardization may be unpopular, but transparency is non-negotiable. You can’t fix what you can’t see. Jira standardization, despite resistance, enabled every subsequent improvement.

Executive Alignment is Critical: Executive-level conflict limited the scope of possible change. The CTO’s public support was essential for legitimizing the work and overcoming passive resistance, but misalignment at the C-suite level ultimately constrained the transformation’s reach.

Prove Value Quickly: The kanban pilot with moonshot teams demonstrated results within 2-4 weeks, creating momentum for broader adoption. Quick wins matter when facing organizational skepticism.

Change Management Requires Sustained Effort: Passive resistance doesn’t disappear. It shifts between overt and covert forms based on political dynamics. Sustained executive support and consistent follow-through are essential.