Mobility / Product Transformation
Locavia — Fleet & Contract Lifecycle Transformation
Replacing fragmented legacy systems with a consolidated platform for fleet and contract operations.
A large-scale product transformation focused on consolidating operational journeys, replacing legacy systems and improving the efficiency, reliability and scalability of fleet and contract lifecycle processes.
- Role
- Product Management / Product Transformation
- Focus
- Strategy · Discovery · Platform · Operations
- Period
- 2024 — 2025
41%
Reduction in contracting lead time
Time to contract certain products · 2024 — 2025 · Associated with the Locavia transformation.
20–30%
System performance improvement
Range reported across the platform transformation, 2024 — 2025.
~25–30%
Reduction in operational inefficiencies
Approximate range reported for the transformation, 2024 — 2025.
The context
When the product is also the operating system of the business.
Locavia was a large-scale transformation involving the replacement of legacy systems — including EuroIT — and the consolidation of fleet and contract lifecycle operations into a unified platform.
Operational processes were distributed across multiple systems and teams. The challenge was not simply to build a new system: it required aligning every part of the operation around it.
- Business
- Operations
- Product
- Technology
- Integrations
- Migration
- Data
The problem
The challenge was bigger than replacing a legacy system.
Fragmentation
Operational journeys were distributed across legacy systems and processes.
Complexity
The platform needed to support multiple business journeys and operational scenarios.
Migration
Existing data and processes had to transition to the new platform without compromising business continuity.
Adoption
New capabilities had to be integrated into the way teams actually operated.
The product challenge
How do you transform a core operational platform without turning the migration into a Big Bang?
The transformation required incremental delivery, prioritization and coordination — not a single technical replacement.
Each step had to deliver value to the operation while the broader platform continued to evolve.
My role
Connecting business problems, product decisions and technology execution.
João played a critical product role in the implementation and evolution of Locavia, connecting business objectives, operational journeys, product discovery, prioritization and technology execution.
Discovery
Understanding operational journeys and business needs.
Product strategy
Defining priorities and transformation objectives.
Prioritization
Structuring and sequencing product demands.
Cross-functional alignment
Connecting business, product, technology and operations.
Architecture & integration
Participating in decisions involving platform architecture and integrations.
Migration
Supporting migration objectives and operational transition.
Performance & reliability
Driving attention toward scalability, reliability and operational stability.
A Product Management and functional product leadership role within a broader cross-functional team.
Transformation model
From a fragmented landscape to a unified platform.
Legacy landscape
- Multiple systems
- Multiple journeys
- Operational fragmentation
Locavia
- Unified platform
- Standardized journeys
- Integrated operations
Business outcomes
- Faster contracting
- Improved performance
- Reduced operational inefficiency
- Greater scalability
- Better data consistency
Discovery
Start with the operational journey, not the system.
Product discovery focused on understanding how the business actually operated, where operational friction occurred and which journeys were most critical to the transformation.
- Business objective
- Operational journey
- Pain points
- Product opportunity
- Priority
- Delivery
Prioritization
Turning a large transformation into product decisions.
The product challenge involved many competing needs across business and technology. Decisions balanced four dimensions.
Business impact
What creates the most value for the operation.
Operational criticality
Which journeys the business cannot afford to disrupt.
Technical dependencies
What must exist before something else can be built.
Migration readiness
What can move to the new platform safely, and when.
A conceptual view of the trade-offs involved — not a formal scoring model.
Platform
Product management at the intersection of platform and operations.
Locavia required coordination between the platform and everything around it. EuroIT was one of the legacy systems involved in the transition.
- Business
- Integrations
- Enterprise systems
- Operational processes
- Platform capabilities
- Operational workflows
- Integrations
- Data
- Migration
- Business rules
- Reliability
- Scalability
Key product decisions
Transforming a complex operational platform while keeping the business running.
Incremental transformation, not a Big Bang
- Context
- Legacy systems, including EuroIT, supported contract lifecycle and fleet operations the business could not stop.
- Options
- Replace the landscape in a single cut-over, or evolve the platform in increments.
- Decision
- Deliver in product increments, each one adding value to the operation while the platform evolved.
- Trade-off
- Operational continuity and lower risk, in exchange for continuous sequencing and coordination across a longer transition.
- Outcome
- Contracting lead time reduced by 41% for certain products during 2024 — 2025.
Start from the operational journey, not the system
- Context
- Operational processes were spread across multiple systems and teams.
- Decision
- Anchor discovery in how the business actually operated and where friction occurred.
- Trade-off
- More discovery effort with operations before building, in exchange for capabilities teams would actually adopt.
- Outcome
- Standardized journeys and integrated operations on one platform.
Prioritize by criticality and migration readiness
- Context
- Many competing needs across business and technology.
- Decision
- Sequence demands by business impact, operational criticality, technical dependencies and migration readiness.
- Trade-off
- Some high-value items waited for dependencies or migration readiness, so critical journeys were not disrupted.
- Outcome
- 20–30% system performance improvement and ~25–30% fewer operational inefficiencies reported.
Execution
From transformation strategy to incremental delivery.
The transformation was executed through product increments, prioritization and coordinated delivery rather than treating the platform replacement as a single delivery event.
- Incremental evolution
- Prioritization
- Operational validation
- Cross-functional coordination
- Migration planning
- Reliability
Impact
The transformation translated into measurable operational improvements.
41%
Reduction in contracting lead time
The Locavia transformation resulted in a 41% reduction in the time required for contracting certain products.
20–30%
System performance improvement
Performance improvements associated with the platform transformation.
~25–30%
Reduction in operational inefficiencies
Reported reduction in operational inefficiencies associated with the transformation.
Outcome map
How the transformation connects to business outcomes.
- Product transformation
- Platform consolidation
- Operational improvement
- Business outcomes
- 41% faster contracting
- 20–30% performance improvement
- ~25–30% lower operational inefficiencies
- Improved scalability
- Improved data consistency
- Reduced rework and stability issues
What made this hard
Transformation happens while the business keeps running.
Legacy
Existing systems could not simply disappear overnight.
Operations
The platform had to support real operational workflows.
Integration
The transformation depended on interactions with surrounding systems.
Data
Migration and consistency were critical.
Delivery
The business needed incremental value while the broader transformation continued.
What I learned
Three things I took from this work.
Platform transformation is a product problem.
Replacing technology does not automatically improve the business. The product challenge is understanding which capabilities and journeys actually create operational value.
Migration is part of the product experience.
A successful transformation must account for how data, processes and users move from the old operating model to the new one.
Incremental delivery reduces transformation risk.
Breaking a large transformation into meaningful product increments creates opportunities to validate assumptions, learn from operations and reduce the risk of a single large cutover.
The takeaway
Modernizing the platform means modernizing how the business operates.
Locavia was not simply a technology replacement. It was a product transformation connecting operational journeys, platform capabilities, integrations and business outcomes.