Mail.Ru Meetup · December 21, 2020
Product Approach to IT
From IT as a service to IT as a product
/ Product Approach to IT · Mail.Ru Meetup 2020
Slide contents
1. Product Approach to IT
From IT as a service to IT as a product
2. Agenda
Context, models, transition
Digital ecosystems, Bank 4.0
Verticals, platforms, teams
IT as service: pros/limits
IT as product: impact
3. 01. Large Fintech Context
Where products and teams live
4. Digital ecosystems org
Four major streams
Mobile app — flagship channel
Web/marketing — growth channels
Project streams and labs
Shared platform for all
5. Banking evolution
Distribution × Friction
Bank 1.0 — branches
Bank 2.0 — ATMs and self-service
Bank 3.0 — mobile channel
Bank 4.0 — context wins
6. Product portfolio evolution
From single product to ecosystem
Credit and debit cards — core business
Investments, brokerage, insurance
Business banking, mortgages
SuperApp, voice assistant, prepaid cards
7. Business verticals
Where IT lives
Banking vertical — cards, loans, deposits
Mobile platforms — unified customer experience
Platform — shared foundation
Investments, insurance, data/ML/security
8. 02. IT as a Service
The classic model and its limits
9. IT as service
Business orders — IT delivers
Business writes requirements
IT estimates timelines
Spec → dev → acceptance
Tickets, budget, SLA
10. Service-model upsides
Why it persists
Team per project
Clear business / IT responsibility split
Centralized standards
Cost center for stable domains
11. Service-model limits
What breaks at scale
Burnout and turnover
Knowledge never settles in a domain
Initiative stays low
Long loop; IT blocks
12. 03. IT as a Product
An alternative model and the transition
13. IT as a product
Team owns outcome
Persistent product team
PO / PM inside team
Business + IT: shared goals
Metrics, backlog, hypotheses
14. Move service → product
Gradual and intentional
Pilot team, one product
Tickets → product KPIs
Own backlog / roadmap
Platform engineering + culture
15. Manageability rests on horizontal links
Team freedom needs shared rules
Shared base technologies
Shared approaches and rules
Platform teams hold the standard
Horizontal links, not hierarchy
16. Product approach impact
People and business
Engagement up, turnover down
Short feedback loop with the user
Domain expertise stays
IT becomes a driver
17. References
Product models, fintech case
Brett King — Bank 4.0
Digital Transformation Game Plan
Fundamentals of Software Architecture
My talks: ArchDays, Codefest, Russoft
18. Thank you!
polomodov.tech
All slides and links — in the Telegram channel
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube