Technology is an incredible asset that has the ability to solve a wide range of problems. The most powerful tool in our lives are now tiny rectangular objects that live in our pockets and allow us to access anything we need to know anytime, anywhere. Technology designed for specific business processes help teams run more efficiently and provide analytics that help define success and enable decision makers to act based on data. However, technology can also fail organizations at an enterprise level when:
1) Acquiring technology without a specific problem in mind
Oftentimes, organizations assume that if they buy a solution - whether it is software or hardware - that it will be adopted and everyone in the organization will see immediate benefits from this new 21st century initiative. This logic fails when technology is purchased without having a specific problem that you are trying to solve. Michael Horn highlights this dilemma in a Wired article (http://www.wired.com/2015/05/los-angeles-edtech/) in reference to school districts:
“Districts are starting with the technology and not asking themselves: ‘What problem are we trying to solve, and what’s the instructional model we need to solve it?’ and then finding technology in service of that.”
Horn is specifically referencing institutions purchasing iPads for all their students, but the iPads were effectively dead weight without the necessary software to solve targeted problems.
2) Not taking a mobile first approach
It is not enough to simply have great software that solves a problem. Software needs to adapt to take advantage of the fact that everyone is always connected through their personal devices. If first responders only have an apparatus check solution that works on desktop, then they have substituted one problem for another - A) lack of accountability and insight into checks for B) double entry of data. With a desktop solution, first responders still have to walk around the truck running checks on a clipboard and then deliver their report to an administrator that enters the report into their reporting tool. A true solution is not substituting problems - it is solving the complete problem.
Take the evolution of navigating in your car. For years we used Ran McNally folded maps for navigating. Then Mapquest came along and we were now printing out our routes ahead of time, but we still had a static piece of paper that wouldn’t provide us any flexibility if our routes had to change. Mobile devices solved this problem with instant access to applications like Google Maps and ultimately provided everyone the flexibility we need in planning out routes.
3) Maintains the Status Quo
Software needs to be held to a higher standard that is easy to adopt and constantly improving.The pricing model should be straightforward so you know exactly what you are paying for, and the software needs to be simple to use and, ultimately, adopt across all of your key stakeholders. Your initiatives are only successful when they are adopted. Perhaps most importantly however, is for your software to be dedicated to constantly evolving with your organization so you don’t have to worry about purchasing upgrades or installing new versions. As a department, you are constantly improving - individual performance, new equipment, dynamic planning - so why wouldn’t you expect the same from your software?
Modern SaaS solutions are often good examples of software that meets these new standards of service, and Halligan is one such solution that has these problems in mind. Sign up for a free trial today and get started today! http://app.halligan.io/front/register