Source
Business lines, service lines, and platforms @ T-Bank
Three-post series on federated company structure and transformation patterns.
Source
Business lines, service lines, and platforms @ T-Bank
Three-post series on federated company structure and transformation patterns.
#Management
In a federated organization, leadership mechanics depend on unit type. Business lines, service lines, and platforms look similar on org charts but require different economics, interfaces, and strategy choices.
Three unit types
Business lines
External product and PnL
- Own external customer products (B2C/B2B/B2G/B2B2C).
- Usually have a business track (CPO, product managers, analysts) and a technical track (CTO and engineering teams).
- Operate with product metrics, roadmap, and explicit profit-and-loss accountability.
Leadership question: How do we keep business and engineering goals aligned instead of running two separate roadmaps?
Service lines
Centralized service for business lines
- Provide a reusable internal service through a clear interface and quality expectations.
- Centralization is used to gain economies of scale.
- Need governance around shared resources to avoid tragedy-of-the-commons effects.
Leadership question: How do we implement fair cost allocation and protect capacity prioritization across internal customers?
Platforms
Internal product in self-service mode
- Designed for internal users and their end-to-end workflows.
- Capabilities are integrated into one coherent product, not a loose toolset.
- Adoption happens through self-service, not ticket-driven manual support.
Leadership question: Which platform capabilities remove dependency bottlenecks and increase team autonomy?
Service-line case: acquisition
Business-line input
Business teams define growth targets, budget, and expected contribution model to product PnL (NPV/LTV).
Operational interface
Marketing teams work through internal tooling integrated with external ad systems, controls, and recommendations.
End-to-end analytics
External ad analytics is merged with internal and offline events for channel and product-level decisions.
Attribution and audience models
Multi-touch attribution and audience services reduce distortions from pure last-click optimization.
Practical takeaway: service lines should operate like internal service businesses. That means explicit contracts with internal customers, predictable capacity planning, and strong automation to preserve scale efficiency.
Transition case: service model -> platform model
- Until late 2019, the mobile bank was treated as a standalone product with a monolithic team structure.
- The super-app strategy required feature autonomy for business vertical teams inside one app shell.
- Dedicated platform teams were formed for architecture, build/test tooling, performance, reliability, and design-system decisions.
- The transition followed an inverse Conway sequence: business goals -> target architecture -> org boundaries and operating model.
- Over time, product/API teams moved into business verticals, while platform teams remained as internal acceleration layers.
Transformation pattern
At this scale, sequence matters: first define business outcomes, then target architecture, then team boundaries. Reversing this order often produces expensive org change without delivery impact.
Common anti-patterns
Calling every internal tool a platform without self-service adoption.
Evaluating service lines only by throughput and ignoring allocation economics.
Using one org design pattern for all units despite different economics and interfaces.
Running reorgs without a traceable chain from business goals to architecture and ownership boundaries.
Recommended practices
Classify the unit type first, then choose KPI and org model; not the other way around.
For service lines, formalize internal contracts: SLA/SLO, backlog model, cost allocation, and prioritization rules.
For platforms, build a capability map around core user journeys and track self-service adoption.
For service-line-to-platform transitions, use staged rollout with pilot workflows before org-wide scaling.
In business lines, maintain CPO/CTO alignment through shared objective cascades and consistent decision cadence.
Sources and related chapters
External links
- [1/3] Business lines, service lines, and platforms @ T-Bank
- [2/3] Acquisition service-line case
- [3/3] Mobile bank platformization case
- CNCF Platforms Whitepaper
- Thoughtworks: Inverse Conway Maneuver
- Tragedy of the commons (Wikipedia, RU)
- Mobile bank evolution case article
- Highload++ Spb 2022 talk
Internal links