Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
I don’t have any hard data. It’s been a successful launch. We rolled to half of our user group on one project. We have and online and offline capability which has been the biggest challenge with the application. We have quite a bit more development that we’re going do with them in 2017. That’s the next phase of this project.
The thing I’m most proud of with this is that this is a big cultural change for our field force. One thing Software For Good was insistent on, and we really liked, is that we wanted to bring the field team in and gain their input on the development from the beginning. We knew what we wanted to accomplish but what it looked like, what it felt like, and the content that was relevant to the end user was going to be something that we worked on from day one. Our field team has been overwhelmingly receptive to the content and the ease of use, as it’s the largest IT initiative and biggest technological transformation that our company has gone through in 30 years.
What did you find most impressive about Software For Good?
Their availability. They are really receptive and were really available whenever we needed them and our demands fluctuated. The scope of the project evolved as it often does, and Software For Good was able to keep up with the demand. Then, when the workload shifted down, they were very open and accommodating to that too. We’ve gone up and down in our programming needs. They’ve been really available to us and really collaborative with our team. We had regular iteration meetings and those were really helpful. This is the first mobile app that I’ve launched with a company. It helped me understand the overall process and the benefits and things to be aware of. It’s something they do all the time and that was really helpful in me being a non-developer. I’m not a developer or a programmer but I was able to be involved in the process and they were able to close some of the gaps that I didn’t necessarily understand.
Are there any areas Software For Good could improve?
The only aspect, which they were very up front with, were the challenges associated with Android. Because of the variety of devices within our team - we have a “bring your own device” policy. So our application works on 9,000 different devices. The complexities that can come up and solving the issues that came up with Android were tough, whereas, with iOS, you only have 7 platforms that you have to worry about. That was something they were upfront about. I personally underestimated the challenges with that.