Embed Size (px)
Citation preview
DIGITAL PLATFORM STRATEGIESBEYOND ENTERPRISE ARCHITECTURE
BETTER FASTER CHEAPER
THE BASIC ISSUE
• Slow painful delivery • High degree of coordination
needed • Business and IT mindset
(us and them) • Project Culture • Internal impediments to
delivering value • Tech debt increasing over
time
Tightly coupled capability
Lower $$$ Better Service Increased Engagement
Customer Satisfaction Sales Targets
Strategy Strategy
IT
IT
IT Business
IT
IT
IT
Business
Business Customer
Customer
Customer
FRICTION
ORGANISATIONAL SUCCESS FACTORS FOR YOUR DIGITAL PLATFORM
5
1. CROSS-FUNCTIONAL TEAMS
2. HIPSTER CENTRALISATION
3. GROUPED BY CAPABILITY
4. CLUSTERED BY CUSTOMER
5. RETAIN STRATEGIC IP
consuming
that are
and
who
WHAT IS A DIGITAL PLATFORM? 🤔
YOUR ORGANISATION’S CAPABILITIES
AS A SET OF SELF-SERVICE APIs
SO GOOD THEY ARE COMPELLING
CROSS-FUNCTIONAL BUILD + RUN TEAMS, NO EXCUSES
1
WATERFALL ERA
ANALYSE DEV TEST RUN
INFRA DEV
- High degrees of specialism (Lower-level languages, Bare metal infra, manual installs)
- High translation cost between contexts drives up batch sizes
- Reacting quickly is difficult, more emphasis on getting it right first time
AGILE ERA
ANALYSE DEV
TEST
RUN
INFRA DEV
- Higher-level languages - Test automation - Virtualisation - Traditional Infra and Ops
organisations begin to creak under improved rate of release and shorter planning horizons
DEVOPS ERA
ANALYSE DEV
TEST RUN
INFRA DEV - Cloud computing
- Infrastructure-as-code - DB Migrations - Blue/Green deployment - Automated Configuration Management - Build pipelines - Containers
“I CENTRALISE FOR QUALITY CONTROL, AUTONOMY WOULD BE CHAOS” “10 AUTONOMOUS TEAMS ALL CONFIGURING MY ESB WONT WORK”
“THE LICENSES FOR THIS OPS TOOL I BOUGHT ARE SUPER EXPENSIVE” “I HAVE 5 INFRA/DB/SECURITY PEOPLE AND 10 TEAMS”
HIPSTER CENTRALISATION 2
HUMANS AS THE INTERFACE
TEAM 1
TEAM 2
TEAM 4
TEAM 3
SECURITY
“This is how I ensure my solutions are secure. It’s a model with fewer moving parts, so I can hold it in my head”
- managers, everywhere
PRODUCTION
TEAM 1
TEAM 2
TEAM 4
TEAM 3
SECURE TOOLS + TEMPLATES
PRODUCTION
TECH AS THE PRODUCT, API AS THE SERVICE
DESIGN-TIME
API TEMPLATES
BUILD-TIME
TEAM 2
COMMON UI TOOLCHAIN
RUN-TIME
DISTRIBUTION WITH CONSISTENCY
CONTRACT TEST
ECOSYSTEM
SECRET MANAGEMENT
TEAM 1
AUTH
PLATFORM FOUNDATIONS
DIVIDE BY CAPABILITY, UNITE WITH APIS
3
PLATFORM ARCHITECTURE - CAPABILITY MAPPING
Proprietary Knowledge
Differentiation
PLATFORM ARCHITECTURE - CAPABILITY MAPPING
Proprietary Knowledge
Differentiation
Mobile Banking
Offer Bundling
Delivery Infrastructure
Core Product
Payroll
PLATFORM ARCHITECTURE - CAPABILITY MAPPING
Proprietary Knowledge
Differentiation
Buy and Configure Custom Build
Outsource Partner
Mobile Banking
Offer Bundling
Delivery Infrastructure
Core Product
Payroll
PLATFORM MODELLING
CLUSTER BY CUSTOMER4
HUMAN CENTRIC DESIGN
CORRECTLY ALIGNED
LINKING TO STRATEGY
HOLD ON TO YOUR IP5
STABLE TEAMS, FLUCTUATING DEMAND
Capacity Line
Time
Demand
CAPACITY FUNDING REDUCES COST OF DELAY
EFFECTIVE PARTNERSHIPS
TO SUMMARISE
• Capacity funding creates stable, high-performing teams
• Capacity funding reduces cost of delay
• FTE Tech presence in areas of key IP - or risk bad partnerships
WRAPPING UP
1. CROSS-FUNCTIONAL TEAMS
2. HIPSTER CENTRALISATION
3. GROUPED BY CAPABILITY
4. CLUSTERED BY CUSTOMER
5. RETAIN STRATEGIC IP
consuming
that are
and
who
THANKS!
Al GrimesLead Consultant
Richard GlewPrincipal Technologist
