{"id":35688,"date":"2021-07-05T09:08:53","date_gmt":"2021-07-05T08:08:53","guid":{"rendered":"https:\/\/www.okappy.com\/?p=35688"},"modified":"2021-07-02T12:21:27","modified_gmt":"2021-07-02T11:21:27","slug":"how-moving-to-okappy-increased-development-output","status":"publish","type":"post","link":"https:\/\/www.okappy.com\/how-moving-to-okappy-increased-development-output\/","title":{"rendered":"How moving to Okappy Increased Development Output by 20%"},"content":{"rendered":"

We have a confession.<\/p>\n

As workforce management innovators, not all of our job management processes have always been up to par. Whether you call it a case of the \u201ccobbler\u2019s shoes\u201d or \u201cbuilder\u2019s backyard\u201d, we weren\u2019t taking enough care of job management processes in our own development team to ensure we were reaching our potential.
\nGiving the best customer care and providing a professional service with minimum disruption are top on our list of priorities. But falling behind schedule on app improvements wasn\u2019t exactly going to put us in the best position to do those things. So, we did some navel gazing.<\/p>\n

Realising that if we truly believed in the power of Okappy we\u2019d be using it ourselves, we took the plunge. We followed in the footsteps of our customers and embarked on our very own journey of using Okappy in-house to manage our development team\u2019s activities. Richard Harris, CEO and Founder, and Robin Spinks, Lead Developer share their experiences of the journey so far.<\/p>\n<\/div>