An investment management system — the platform that handles portfolios, orders, compliance and trading — is the backbone of the front office. Implementing one is a business change programme, not an IT upgrade. When it is treated as a technology installation, the go-live slips and the traders refuse to use it. When it is run as a business change, it becomes the strategic platform the front office wanted.
Why implementations fail
- Sponsorship sits in IT rather than the front office, so workflow and adoption decisions are made by the wrong people.
- Reference and static data are treated as an afterthought, though unstable data breaks almost every test.
- The platform is configured to replicate the old system instead of improving the operating model.
- A big-bang go-live across regions overwhelms the team and creates a long, painful hypercare.
- Compliance rules, exception workflows and downstream integrations are discovered late.
A pragmatic approach
1. Define the target operating model first. Agree how the front, middle and back office will operate on the platform — portfolio management, order creation and compliance, trading, allocations, settlement and positions — before configuring anything.
2. Stabilise reference data. Instruments, issuers, accounts, benchmarks and counterparty data must be clean, owned and governed. This is the single biggest predictor of a smooth go-live.
3. Configure workflows, not just screens. Model the investment and compliance lifecycle: pre-trade compliance, order routing, block and allocation, FX, and the exception and override workflow the desk actually needs.
4. Integrate and test end to end. Connect to the EMS, PMS, accounting, custodian and market data; test with realistic portfolios and real users, not just technical scripts.
5. Roll out in waves and run hypercare. Go live region by region or desk by desk, with named super-users and a short, well-staffed hypercare that ends when usage is stable.
Lessons from a regional rollout
- Waves beat big-bang: each region learns from the previous one and defects fall sharply.
- Super-users on the desk are worth more than any training deck — they make adoption self-sustaining.
- Lock reference data early and govern it; most go-live defects are data defects.
- Design the exception workflow up front; a platform that cannot handle exceptions is bypassed.
Governance that keeps it on track
A single programme plan with clear work-stream ownership, a front-office chair at the steering group, disciplined change control for scope, and a risk-and-issue process that reaches decisions quickly. Reporting should be factual and forward-looking — the milestones and blockers that matter to the business, not task-counts.
When to bring in an independent programme lead
An independent programme lead is valuable when the platform is strategic but the front office has no spare senior capacity, when the rollout spans multiple regions and vendors, or when a previous attempt has stalled. They bring the operating-model view, the governance and the delivery discipline to get the platform adopted.