Thanks for your thoughts on the next-gen pay system
In my last blog in August, “Next Generation HR and Pay, and how we’re going to do things differently”, I invited people to submit their thoughts on what a next-generation pay system should be capable of, and how it should work.
Since then, the next-gen team has received some great suggestions from current and former public servants with direct experience in the complexities of pay policy, including a retiree and former pay-policy trainer.
I want to thank everyone who provided their thoughts and opinions. Your experience and advice are valuable, and I’m very thankful for the good, constructive feedback. I’ve read every one of your e-mails. For me, it’s part of putting people’s needs and experiences at the centre of the initiative, and involving them at all stages of system design and delivery.
One person thought we should keep in mind the lessons learned from the Australian experience, when they tried and failed to implement a pay system like Phoenix, and should work closely with them to see how they were able to fix their pay issues.
There was also a suggestion that we fix Phoenix rather than ripping it out and implementing a new solution, because it’s already integrated in our systems — and creating a new solution would “be more expensive and more of a mess.”
Another person was “overjoyed to hear about the open and transparent approach to design and the call-out for feedback from any interested party,” saying it’s “a refreshing take on problem-solving that challenges existing cultures and can only lead to important shifts in government technology.”
I’m excited and encouraged that people are not only contributing their ideas, they’re also asking whether they can help with designing and developing the system. They see this initiative as a new way of working as a government, and they want to be part of it.
And they’re right! This is about being involved in a more nimble form of government. It’s about working in a culture of openness, innovation and agility — one that gives us more freedom to experiment with technology, and breaks down the old risk-averse bureaucratic culture.
So developing the new pay system is about more than just bits and bytes; it’s an exciting culture shift and new way of working that employees fully support.
Please keep the comments coming! There are a lot of smart people out there, and we look forward to hearing from all of you.
Chief Information Officer, Government of Canada
Alex Benay currently serves as the Chief Information Officer of the Government of Canada. Prior to this appointment, Alex was the President and Chief Executive Officer of the Canada Science and Technology Museums Corporation since July 2014.
From 2011 to 2014, he was Vice-President of Government Affairs and Business Development at OpenText. He has played a leadership role in Canada's digital industry, as well as in promoting the global shift to digital in organizations such as the G20, the Commonwealth Secretariat and the Olympics. Before joining OpenText, Alex managed various teams and programs at the Canadian International Development Agency, Foreign Affairs and International Trade Canada, Natural Resources Canada, and Library and Archives Canada.
John (former Compensation Advisor) - October 09, 2018
First and foremost, listen to those that process pay. When Phoenix was being developed I worked with PWGSC for six months under KPMG guidance. When a process came up and they did not like the process, they ignored my comments / caution / risks. They simply stared they would get the rules changed. This type of thinking is why they current version of Phoenix is failing.
If those that knew pay were fully consulted and listened to, the outcome might have been different.
Alexandre Leroux - September 27, 2018
Has developing the next pay system as open source software been considered? That's really the best way to ensure tax payers money is well spent ; any stakeholder will be able to help improve the system, including outside consultants, internal experts, universities, etc. Thanks -- Alex
Guy Levert - September 26, 2018
Failures with large systems design and development abound. Think about the Obama care healthcare.gov. They failed catastrophically, got back on their feet and fixed it. UK had its failures too, so did Australia, etc... All of them adopted an open, agile, iterative, teams of experts, open source, AI, cloud-based, new staffing regime, etc,... And they fixed or are fixing the issues.