SpringOne Platform 2019 Session Title: Evolving Towards a Modernized Platform: Our Success Story Speakers: Pierre Braganza, Sr. Director of Architecture, Liberty Mutual Global Retail Market East/West and Brett Mathews, Senior Leader, Architecture & Modernization, Liberty Mutual Youtube Link: Coming Soon

1. #TechAtLiberty
Evolving towards a modernized
platform: Our Success Story
Pierre Braganza, Sr. Director of Architecture &
Brett Matthews, Senior Leader, Architecture & Modernization

2. #TechAtLiberty
Agenda
2Confidential & Proprietary – Not for Distribution
 Introduction
 About Us
 What are we trying to solve?
 Our Evolution Story
 How did we get there?
 Making it real: An interview with the SSM/RTE
 Lessons Learned
 The Leadership model/behavior that influenced
 A Global Perspective
 Q&A

3. #TechAtLiberty
Introduction
3Confidential & Proprietary – Not for Distribution
WHO WE ARE?
Hola
Hi

4. #TechAtLiberty
About Us
4Confidential & Proprietary – Not for Distribution
Global Retail Markets (GRM) combines the company’s local expertise in growth markets outside the U.S. with
strong and scalable U.S. capabilities.
Personal Insurance sells automobile, homeowners and other types of property and casualty insurance coverage to individuals in the United
States.
Business Insurance serves small commercial customers through an operating model that combines local underwriting, and market
knowledge.
Global East | West sells property and casualty, health and life insurance products and services to individuals and businesses in East and
West operating regions.
$41.6 billion
annual consolidated
revenue
30 countries &
economies globally
800
global offices
Nearly
50,000
employees
largest global
P&C insurer
5th

5. #TechAtLiberty
What are we trying to solve?
5Confidential & Proprietary – Not for Distribution
Evolution of our
Architecture
• Emergence of frameworks and
technologies that facilitate building
applications that are easier to evolve
and adapt to changing business needs
• Better continuous integration and
development practices maturity
• Faster provisioning and scalability of
Infrastructure with the Cloud
• Learnings from recent initiatives made
us wiser
Challenges hindering quick
delivery of capabilities
• Monolithic applications are hard to
change
• Tight coupling and dependencies among
components make the code brittle
• Managing existing technical debt and
trade-offs
• Inconsistencies in the way product sets
were implemented
• Infrastructure provisioning is very
complex, slow at best

6. #TechAtLiberty
Our Evolution Story – Business Lines Example
6Confidential & Proprietary – Not for Distribution
Where we started Pivotal engagement outcomes Today
BL-T generates 4B+ premium Learned to think differently Built trust and close alignment with the
business
Flagship monolith app Bought into Paired Programming & Test
Driven Development (TDD)
Business features drive technology
decision
Complexity in defects and testing Developer confidence Cross functional team, thin vertical slices
Developer friction Separated UI from compute Teams still pair & focus on MVP quality
No business agility Faster builds / better tests
• 300+ unit tests created
• 80 min. build time to 14 min.
• 20 min. app restart to 4 min.
Architecture is not an end state, it's a
constant evolution
End-to-end testing takes weeks You build it, you own it, you fix it Ability to deploy on demand on the new
components
Monthly release cycles Early adopters of using CI/CD pipeline Defects fixed within days
Tied to non-cloud enabled platform (IBM)

7. #TechAtLiberty
How did we get there?
7Confidential & Proprietary – Not for Distribution
Practice Scaling: Supported
by common principles and
strong core teams
• Vertical slices continued
with each team
• Everyone on the same
train and under same
leadership support
• Trust & communication
• Working off common
backlog, epics,
prioritization
• Champions sent to
mentor/augment new
teams
• Autonomous, but working
together
• Not all teams changed
philosophies

8. #TechAtLiberty
Making it real: An interview with the SSM/RTE
8Confidential & Proprietary – Not for Distribution
Q&A
 How has the business architecture vision
changed?
 How have you incrementally solved the
architecture?
 What was the biggest challenges that your
developers were facing? How did we solve it?
 What are the biggest challenge from a
requirements perspective? How did we solve it?
 What is the biggest difference you see on how
architects interacts with the teams?
 How has your relationship with the business
partners has changed?
 What challenges have you had in this new
model? Did you have clarity in roles?
 Why did our model work? Why now?

9. #TechAtLiberty
Lessons Learned – A Business Lines Example
9Confidential & Proprietary – Not for Distribution
• Business rules are embedded within the User Interface and the Product
Model, making the product tightly coupled and difficult to test or change
• Product model is not consistent in every Line of Business bringing
complexity when integrating to finance, billing, and regulatory
Sources of Record
How we define and manage
products
• Enrichments and language translations were not effective through
hubs
• Product information is translated to statistical codes before flowing
downstream brought complexity in testing and quality
• Rich detail is lost through summarizations to meet legacy ecosystem
constraints
Standardization of Data
How we connect to partners
• Circa 1970s and 80s tech on monolithic mainframe hubs
• Sequential batch processing
• Communication through fixed format flat file
• Extended test cycles due to reliance on month-end processes to move
data to the next consumer
Seamless Downstream
Integration
Replace vs. Modernize Strategy

10. #TechAtLiberty
The Leadership model/behavior that influenced
10Confidential & Proprietary – Not for Distribution
 Based on Konorti and Eng (2012)
3D leadership model
 Experimentation
− Change
− Fail Fast
− Workstyles
 Execution
− Delivery
− Measure of Success (MoS)
− Technology
 Continuous Learning
− Education
− Training
− Intelligence

11. #TechAtLiberty
A Global Perspective
11Confidential & Proprietary – Not for Distribution
Integration
Backbone
System of
Engagement
System of
Record
System of
Insights
Cloud Engineering
• Store
• Analyze
• Report
• CI / CD
• Cloud
• Security
• Customer
• Product
• Billing
• Claims
• UX / OEM
• IoT
• Comm.
API
Management
Event
Handling
Internal /
External
Integrations
• Single point of entry
• Lifecycle Mgmt.
• Create
• Manage
• Discover
• Analyze
• Catalogue
• Notifications
• Enrichments
• Transfer
• Contract First
• Third Party
• Sharable Patterns
• Make changes and deployments
faster
• Reuse of transformation and
routing techniques
• Improves overall quality
• Improves how we maintain and
manage integrations
• High reuse of global assets
from WEM
• Promotes global Inner
Source Model

12. #TechAtLiberty 12Confidential & Proprietary – Not for Distribution
Q&A