Financial services
Here the answer is more differentiated than in industry.
Automation, digital customer interaction and analytics change the work in almost every unit, but unevenly.
For banks, insurers and financial services firms.
One initiative in figures
Example view from the platform
412
6
7
roles are changing
126 of 412
learning path assigned
93 of 412
programme started
68 of 412
Illustrative example from the platform, a supplier, not a real customer. The view is the same whatever the industry.
In financial services, cohort fit is lower than in industry, and the reason is structural.
Drivers
What changes the work
Process automation. Standard cases in applications, payments, claims and contract changes increasingly run without manual handling. What remains are the harder exceptions.
Digital customer interaction. Contact moves into channels where the customer completes part of the process. The share of simple enquiries falls, the share of the ones that need explaining rises.
Analytics inside decisions. Models support risk, pricing and steering. Anyone working with them has to judge when a model result holds and when it should be overridden with a stated reason.
New digital products. Different product logic means different processes, different evidence duties and different advice. That reaches product management, sales and back office at the same time, but not to the same degree.
Roles
Where the work shifts
Unlike industry, there is no single occupational starting point here. So we describe activities rather than job titles.
Operations and back office
Processing cases, checking, releasing, resolving exceptions.
The standard case disappears from the queue. What remains are exceptions, reviewing automated decisions and maintaining the rules the automation follows.
Customer service
Answering enquiries, triggering cases, arranging appointments.
Fewer simple contacts, more complex ones. Plus working with assistance systems whose suggestions someone has to own professionally.
Risk and compliance
Applying rulebooks, assessing cases, keeping evidence.
Model-supported assessment, explainability of decisions, changed review and documentation logic.
Analysis and steering
Producing reports, supplying metrics, explaining deviations.
From report production to framing the question: understanding data models, building analyses independently and defending results in front of the business.
Sales and advice
Establishing needs, explaining products, closing business.
Better prepared customers, digital closing journeys, different reasons for a conversation. Advice enters later in the process and has to deliver more once it does.
IT and product management
Running systems, gathering requirements, supporting releases.
Closer to the business process, shorter cycles, more responsibility for data quality and for how product logic and system fit together.
Cohort fit
Lower than in industry. We say so plainly.
Cohort fit rests on three conditions: many people going through the same change, comparable prior knowledge and a shared time window. In financial services only the first is regularly met.
- Role profiles are more heterogeneous.
- Two case handlers with the same job title often work on different products, systems and rulebooks. In manufacturing that would be the exception.
- The starting point scatters.
- There is no training occupation that standardises the target group the way a technical training regulation does.
- The trigger rarely has a date.
- A plant ramp-up is scheduled, a gradual process automation is not. Without a hard date, a cohort lacks its argument against day-to-day work.
Where it holds anyway
In large operations and service units many people work on the same type of case in the same system, and the same automation reaches all of them at once. Those are the units where a cohort genuinely works here.
So our recommendation splits in two: cohorts for operations and customer service, learning paths without group building for risk, analysis, product management and IT.
Delivery
No shift roster, and still no free calendar
The constraints look easier than in industry at first glance. They are only softer, and soft constraints are harder to defend.
- Time model
- Instead of shift groups, service hours and volume peaks decide who is free. Month end, quarter close and campaign periods are effectively blocked even when the calendar shows nothing.
- Location
- Most of the content works remotely, and a large part of the target group already works distributed. That is the clearest advantage this industry has over a plant.
- Release from work
- Without binding release, learning time becomes leftover time. So it belongs in team planning and in the manager's objectives, not in a recommendation.
- Group size
- In large operations and service units viable groups do form, in a specialist unit of ten to twenty people they do not. There the individual learning path is the better instrument.
The codetermination framework is the same as in industry: Section 97 (2) BetrVG, as soon as measures taken by the employer change work so that existing knowledge no longer suffices. In this industry Section 87 (1) no. 6 BetrVG is regularly relevant too, because many systems are in principle capable of monitoring performance and behaviour. QualiShift does not assess individuals, and here that is not a marketing line but a precondition for an introduction that moves at any speed.
The scan also tells you when a cohort will not come together.
The Transformation Scan captures the initiative, sorts the activities it touches and shows where enough comparable need exists for a group. Where it does not, that is in the result too.