Large banking and insurance groups increasingly attach their business-analysis teams to IT departments. The risk: losing the business’s voice.
For some years now, large banking and insurance groups have tended to attach their business-analysis (MOA/AMOA) teams to IT departments. The move has its logic — pooling skills, standardising methods, cutting costs. It also has its drift.
Signs that business analysis is drifting
- specifications describe the technical solution before the business need;
- functional trade-offs are escalated to IT instead of the business;
- acceptance only checks compliance with specifications, not real use;
- users discover the tool at go-live.
Keep a foot on each side
Useful business analysis speaks both languages. It knows what an accounting scheme or a regulatory return is, and it knows what an interface can and cannot do. That double anchoring does not depend on the org chart; it depends on the profiles and on how they are made to work.
Three simple practices
- a named business sponsor on every project, who settles functional trade-offs;
- workshops held on the business side, with its real cases;
- user acceptance with end users, on top of compliance testing.