Changing the Minds of Employees in Finance
Read Part I of the case study
The second meeting with the group was well attended, everyone made time on their calendar and attended the meeting. This was a good sign! We knew we still had a few resisters, but we also knew that they were interested enough to show up!
We took the first hour of the meeting to answer questions about the product being selected which had been submitted to us after the first meeting. We also knew there would be other questions that would arise. We had the vendor in attendance so that we could be sure to provide answers to all questions at that time and need no, or little, follow up. We knew that the quicker we could get people what they needed, the sooner we could increase their comfort level and move forward on the project.
After the demo at the first meeting, it was apparent that individuals in the room were excited about the possibilities of the new financial system. Certainly it would make their job easier and that was apparent to everyone. Even the individuals who implemented the system being replaced seemed excited, though we still knew we had to win them over.
Once all questions were answered, we focused our conversation on the need for participation on the project in a number of areas:
- Helping to determine exactly how the system will work for the organization (what features and functionality would be needed)
- Providing data necessary throughout the project
- Assisting in refining processes and procedures within the finance and payroll function
- Assisting in the design of the system and testing the functionality
- Helping to roll out the system and train end users
Everyone wanted to participate in some way; although we knew that some simply wanted to participate to maintain a feeling of control. That was fine with us. As long as we could get them to participate, we knew that we could eventually get them to come along and support the project. By participating on the project, they would feel that they had some control over what was happening rather than idly sitting by and waiting for the project to be rolled out.
We set up a preliminary resource grid as follows (shows key responsibilities):
Name |
Role/Title |
Involvement on Project |
Allan Parker |
Asst Payroll Manager |
Project Team Lead – Payroll |
Jasmine Simmons |
Asst Financial Manager |
Project Team Lead – Finance |
Alice Rush |
Payroll |
Provide data, assist with refinement of processes and procedures, assist in the design of the system, testers |
Sam Jameson |
Finance |
Provide data, assist with refinement of processes and procedures, assist in the design of the system, testers |
John Pittman |
Members of payroll and finance functions |
Testers |
Other members of the payroll and finance functions would also be involved in the project, participating as needed in meetings and workshops related to the new system rollout and supporting the core project team members. The individuals in the table above, however, would be actively involved in the project and participating on a day-to-day basis – they were members of the core project team. They represented a variety of backgrounds, experiences and longevity with the company.
In summary – our introductory meeting with these individuals enabled of us to begin to establish a working relationship with them and get them engaged in the project. This second meeting enabled for continuing that relationship building and getting members of finance and payroll involved in the day-to-day work of the project, thereby increasing their commitment to the project. We knew that as they began to work on the project, their commitment would continue to increase and they would become our project champions – engaging others in their functions in the project and pushing to its success.