In practice, change management consisted of regular discussions within the Administration and close co-operation and communication between the business units, personnel unions, and personnel with managerial duties. The most work intensive and demanding task was planning and arranging the training for tax officers. Additionally, post-implementation support was planned right from the beginning of the program to support the transition and resolve any issues that people could face.
Always fluently forward with correct situational awareness
The Valmis program was divided into five separate annual implementation projects to manage the risks and to ensure relative ease of implementation. Each project involved between 300-500 people from the Administration.
Every project consisted of hundreds of meetings for requirement definition and thousands of built functionalities. Monitoring the project implementation was performed using the main system supplier’s project management tool minimizing the administrative work needed for collecting and updating data and allowing people to focus on more important tasks.
Inspecting the project timeline, tasks and statuses were separated into task categories – for example definition, development and testing. Each task was assigned to a specific person who oversaw ensuring progress for the task and to keep the status up to date. Updates were done when each task had been implemented, reviewed or approved. Based on the insights gained from this tracking, it was possible to predict the completion of the tasks.
“We wanted to manage and lead the program relying on accurate and up-to-date information. EY’s contribution in for example this area was irreplaceable. We were able to operate as we wanted and direct the complex and large-scale program in the right direction, and to make corrections when needed. EY’s competencies supported our own organization’s know-how, and co-operation with EY was fluent,” says Program Director Pikkarainen.
The follow-up mechanism was tuned together with the suppliers throughout the program using continuous improvement principles. When information on possible bottlenecks and progress was available, it was possible to improve the ways working and the system development process to be even more efficient. Developing the tools together with the suppliers to satisfy the needs of both parties, and a common view on the actual situation, reduced discussions related to differing views on, for example, quality or progress.