Transformation evidence

The problems leaders brought me in to solve.

Technology details matter. But the evidence begins with the business situation, why I was brought in, what I led and what changed as a result.

Four transformations.

Four different business problems.

One consistent leadership approach.

01 · Flagship · LUXOTTICA

Modernising a global technology estate without disrupting the business.

€150M contract

1,200 business-critical applications

3,700+ resources

185 resource groups

15 months

6 months ahead

Business context

1,200 business-critical applications. Global operations. 24x7 availability requirements. Complex international compliance obligations.

The problem

Modernise a complex global estate while preserving 24x7 operations and meeting GDPR, HIPAA and PCI obligations.

Why I was brought in

Lead the technology transformation within a €150M contract.

My role

Technology Transformation Lead

Transformation scope

  • 30-member team
  • 15-month transformation
  • 3,700+ resources
  • Hybrid Cloud / Microsoft Azure

What I led

  • Application assessment and migration strategy
  • Four migration waves into Microsoft Azure
  • Cross-functional architecture and operating-model alignment
  • Compliance and production handover

Business outcomes

€4M savings

80% CAPEX reduction

45% reduction in data-centre footprint

€1M improvement in profit margins

12% reduction in labour costs over three years

6 months ahead of schedule

What this experience taught me

At global scale, architecture, operating model and governance must be designed together. Migration speed only creates value when continuity and accountability are protected.

02 · JOLLIBEE FOODS CORPORATION

Building a digital foundation while customer behaviour was changing.

COVID disrupted traditional dining patterns. Delivery and takeaway demand increased. JFC needed to modernise infrastructure rapidly to maintain business continuity, reduce costs and respond to changing customer demand.

Build a scalable digital foundation quickly enough to support business continuity and rapidly changing customer demand.

Transformation scope

  • 15-member team
  • 300 SAP and non-SAP applications
  • 500 servers
  • AWS migration
  • Multi-region data-centre exit

Business outcomes

  • More agile operations
  • Automated sales reporting
  • Improved inventory management
  • Faster data-driven decision making
  • Improved business continuity

Cloud becomes a business enabler when simplification, security and data access are treated as one transformation rather than separate technology projects.

03 · LOTTE

Creating a digital workplace for a newly merged enterprise.

Following the merger of three group companies, LOTTE needed greater IT agility and increased support for teleworking during COVID.

Integrate three companies into a more agile digital workplace while teleworking demand accelerated during COVID.

Transformation scope

  • 2,500 devices
  • Hybrid VMware Cloud on AWS
  • Windows 7 → Windows 10
  • First VMware Horizon on VMware Cloud on AWS implementation in Japan

Business outcomes

  • 30% productivity improvement
  • 20% reduction in IT support calls

A workplace transformation succeeds when integration quality and employee experience are governed as business outcomes, not when deployment volume becomes the goal.

04 · SYNGENTA

Scaling a business-critical SAP environment around growth and seasonal demand.

Syngenta required a scalable and highly available SAP environment to support growing operations and seasonal demand.

Increase the scalability, availability and operational efficiency of a business-critical SAP estate with substantial seasonal demand.

Transformation scope

  • 2,500+ interfaces
  • 600 TB data
  • 450 virtual machines
  • 45 SAP applications

Business outcomes

  • 20% improvement in SAP performance
  • 28% operational cost reduction
  • Improved reliability

Resilience and cost performance improve together when architecture is shaped around business demand patterns rather than static infrastructure assumptions.

Four transformations. The same structural patterns.

01

Architecture and operating model must align.

02

Governance must accelerate decisions.

03

Technology follows enterprise readiness.

04

Outcomes must shape transformation from the beginning.

The technology changes.
The leadership problem often does not.

Complex transformation requires more than delivery discipline. It requires alignment across the enterprise.