DriveWorks: Where to begin

At Base 10, we often hear the same story over and over again. ‘I have this new software and it can do all this stuff, but where should we begin?’ From our point of view, that question has a straightforward formula.

Simple + Independent + Most Users

Simple. Get that quick win. A year from now when you look back at the implementation and cringe at it’s inefficiencies in the code you’d previously written it will be quicker to rewrite it!

Independent. The more connections you have to other DriveWorks projects and other systems, the more difficult it will be to build, to debug and to maintain as technology & systems evolve and improve going forward.

Most Users. The more impactful from a user perspective, the better. Obviously you want to start out on first release with a smaller number of power users to get better feedback, but casting a large net is essential. Why? The more people that know about the new tools that your company has at its disposal, the better.

A project that showcases capabilities and helps every user has the powerful effect of on-boarding more people to support the cause. A project like this improves feedback quality and it gets people excited about their ownership of their processes. Ultimately previously hidden opportunities surface because people are now being asked how they can improve in their jobs. If they are empowered to do that discovery on their own, you’ve now shifted from a work harder to a work smarter culture. A work smarter mindset also breeds a culture that is less averse to change and more focused on continuous improvement. Pair that with competent users in key areas of the business, and you’ll soon be inundated with feature requests and new project ideas.

If you’ve recently purchased DriveWorks and struggling with where to begin or you’ve reached a plateau in your implementation and you are looking to make the next big leap, please reach out to us and we can help.