Not the company it used to be - Avis employé Developer Amdocs

First off, we’d like to thank you for providing this important feedback. As an organization, we recognize that we can only truly get better when we challenge one another and provide the impetus to improve. We’re super happy to see that you noted our wonderful team members in your list of Pros for Kenzan. Each one of our team members brings something special to the table and without their drive, determination, and creativity, Kenzan would be adrift at sea. In reading through your comments, it seems that your concerns are mostly in two key areas. The challenges of working with a distributed team: This can certainly be difficult and it’s a topic for which there is a tremendous amount of research and recommendation. Kenzan works to follow best practices by providing the structure of agile and scrum methodologies to keep individuals and teams on track. We leverage best-of-breed communication tools like Slack, BlueJeans, G-Suite, the Atlassian Suite. We speak early and often about personal accountability and transparency, which is modeled by Kenzan leadership. That said, this is not simply a box that can be checked and forgotten. It takes consistent effort by each and every one of us to ensure the best outcomes and make sure that folks are heard. There are times for all of us where we fall down here, but each day offers a new opportunity to succeed. Kenzan post acquisition: It is true that acquisitions can be difficult and some of our team members have moved on. That said, this change can provide space for growth and development for our current team members, all of which bring a perspective that will shape the path forward for Kenzan. Our team is smart and driven. They have made strides both as individuals and collaboratively. It’s not so much about what Kenzan was, as it is about how we evolve and support one another moving forward.