Within the first weeks, every one of the 24 Agile teams — all 250+ members — was interviewed individually. Every CxO, senior executive, and key stakeholder was met. The purpose was not to confirm what leadership thought was happening. It was to understand what was happening: the team-level resistance, the political fault lines, the gap between reported status and operational reality. All 36 KPIs and dashboards were reviewed. Status and performance reports across daily, weekly, and monthly cadences were analyzed. Data sources were validated. Within 45 days, a full Transformation Health Assessment was delivered to the CSO and CEO — an honest, complete diagnosis of where the organization was, where it needed to go, and the best transformation roadmap to get there. The CIO challenged the approach; his concerns were addressed directly and on record.
The executive misalignment between CIO, CSO, and CEO was identified early and named directly — not managed around. A detailed transformation plan was developed jointly with the CSO, reviewed with the CEO, and presented to the full CxO suite. The plan was approved unanimously with minor revisions. The CIO's resistance was managed with transparency and rigor: his concerns were answered one by one; his challenge converted into conditional acceptance. When the CIO later moved to consolidate all Agile resources under his organization — eliminating the separation of duties — the argument was made directly to the CEO on structural grounds. The political outcome was not ideal, but accountability was maintained through a dotted-line reporting structure to the CSO. The lesson embedded here became a cornerstone of the PKZEE Method™: identify the key influencers and decision-makers first, capture their individual expectations before building the strategy, and align CxOs privately before presenting publicly.
With the executive landscape navigated, the transformation architecture was built from scratch:
- All 20 Agile teams were reorganized around value streams rather than functional areas — ensuring each team was as self-contained as possible to define and deliver features independently
- 36 KPIs were rationalized to 16 — eliminating duplicates, removing redundancy, and defining threshold and target values for each remaining metric
- Lean Portfolio Management was designed for the enterprise, replacing one-time annual budget planning with OKR-based strategic planning reviewed and refined every quarter
- Annual budget allocation was restructured to value streams — projects funded by priority from the portfolio funnel rather than by annual negotiation
- Two Agile Release Trains (ARTs) were designed, staffed with Release Train Engineers, Product Managers, and Solution Architects, and product backlogs built, estimated, and prioritized for one to three years
- A Transformation Execution Team of seven senior leaders was formed — with a technology senior leader as Scrum Master and the transformation lead as Product Owner — establishing cadence, deliverables, and accountability
The detailed implementation plan was printed and displayed on office walls. The participant training schedule was posted company wide. Visibility was intentional — it created accountability and curiosity simultaneously.
This was the stage that turned the transformation from a management initiative into an organizational movement. All 250+ team members, plus 15 executives and leaders, were trained across 15 SAFe workshops covering Leaders, Teams, Scrum Masters, Product Owners, and Release Train Engineers — every program running two full days for 30–40 people.
- Every training program was kicked off by the CEO, CSO, or CIO — making executive endorsement visible and personal rather than nominal
- Every training session used real project problems, team examples, and live questions from the organization — not theoretical scenarios
- A dedicated certification support group was established, helping participants pass SAFe certification exams
- Training progress was announced at weekly corporate all-hands meetings — creating a wave of company-wide excitement that had not been experienced before
- HR published training reports and participant interviews, amplifying the visibility of the program
- An Agile Playbook was created covering all Agile concepts, roles, deliverables, metrics, and processes — owned and used by the teams themselves
By the third training workshop, the conversation in the organization had shifted: the new Agile Transformation Officer "knows a lot and is doing great." Resistance gave way to curiosity. Curiosity gave way to capability.
Two separate PI Planning sessions were launched for the two ARTs — in the presence of the full executive suite. The transformation team and the transformation lead coached and supported ART execution across a full PI cycle of three months, measuring performance against the rationalized KPI framework throughout. The before-and-after story was presented in a company-wide all-hands meeting — showing, with full transparency, where the organization had been and how far it had come. The presentation was met with thunderous applause from teams and executives alike. The CEO announced the success to the entire organization. Key contributors received Person of the Month recognition. The transformation team received a two-day group retreat.
