ING – integration and a clean slate system

The outcome

The new and responsive website of ING went live step by step without causing any inconvenience to the visitors. And although the interface or ‘the front’ had remained the same, at the back of the website things had been cleaned up substantially. No less than thirty percent of the content was removed and the redirects were refreshed as well. ING is a happy customer. Something we are proud of.

Old situation

ING had been working for five or six years in the same CMS. The system contained multiple unnecessary items and unnecessarily complicated procedures for building pages. The website had approximately 5,500 pages, 5000 images and PDFs, dozens of unnecessary flash files, complicated schemes and templates. It was about time for a big clean up

Hoewel de klant hier weinig van merkte, waren de contentmanagers en formulemanagers van ING dagelijks veel tijd aan kwijt aan onderhoud. Het was hoog tijd voor een grote schoonmaak.

Project objectives

  • Integrate ‘My ING’ in pages ‘before login’
  • Make the website responsive
  • Keep the same interface
  • Remove and clean up (duplicate) content
  • No inconvenience: minimal downtime

 

“ING is a happy customer. Something we are proud of”

Website

Employees

Days

%

Satisfied customer

Approach

ING had already prepared the project when we joined them for the migration. They had determined new templates and schemes and had given a serious thought to cleaning up the CMS. The team had decided to stick with the same CMS and to create a new body only.

The project turned into a migration from SDL Tridion 2011 to SDL Tridion 2011. The website was cut into fourteen batches and every part was migrated over a period of two weeks.

Planning

The planning for the migration was aligned with the planning of the release of the development team. For each batch we took into account a margin of six weeks in between the release and the start of the migration. This allowed us the technology to be ready in time and it left enough time for the developers and content managers to run a system test.

Team

The migration team consisted of three people. Two employees from Crossphase and one rotating content manager from ING. This way all ING employees were trained. The content managers from ING helped us with a number of issues such as naming, ‘standard behaviour’ and other ING conventions.

Apart from the content managers we provided the migration team with three more employees:

  • Contentlead
    Planner and manager of the migration team and point of contact between the content management and formula management departments.
  • Technical content manager
    Point of contact for developers, testers, functional management department and the migration team.
  • Sr. content manager:
    An extra hand to close the gap in the regular content management team from ING.

Initiation phase

Thanks to a good initiation phase the migration turned out to be very well prepared. At the start of the project we identified the general outline together with ING: planning, deadlines, deployment of staff and the workload.