+1 855 259 6624

Is Your Program Prepared for Takeoff?

Posted on June 6, 2017 by Josh Garrett

checklistEnterprise mobility has been the focus for most of my career. I’m energized by the rapid evolution of connected devices, how they impact business strategies, and how MOBI can assist enterprises in managing their devices now and as they continue to evolve. Long before connected devices were commonplace in enterprises (and before MOBI ever existed), I enjoyed learning about history and aviation.

Over the years, I’ve found it fascinating to see how often my interests parallel one another. Recently, I spent some time reading about the B-17, or the Flying Fortress as some of you may know it. What follows is a quick story of its inception and what led to an even more important discovery—one that enterprises can also use to help manage their connected device ecosystems.

Back to the Future

In 1934, the United States Army Air Force needed a long-range, four-engine bomber for its fleet. Boeing responded to this request with a new design—the Model 229.

On its second test flight, the plane quickly entered a steep climb, stalled, and crashed, killing both experienced test pilots. Boeing’s hopes for a major contract were immediately dashed, as the plane, despite its potential, appeared to be poorly designed. How many times has your seemingly perfect mobility solution crashed and burned due to unforeseen issues?

Subsequent investigations uncovered that the plane itself was perfectly suited for its mission. However, the pilots had forgotten one critical pre-flight step: to disengage the “gust locks”—the mechanisms that lock control surfaces and keep doors open while the aircraft is on the ground and non-operational. The new, complicated planes of this era had obviously become too complex to fly on memory alone.

The same can be said for today’s mobile technology.

Preventing History from Repeating Itself

To remedy the situation, a pre-flight checklist was introduced. This simple-but-critical concept confirmed the pilot was doing everything needed prior to takeoff, in flight, and during landing to ensure safety. The checklist made a complicated plane manageable for a task-oriented pilot and allowed Boeing to eventually build 18 successful test models and almost 13,000 B-17s for 24 countries.

That got me thinking: “Could an annual mobility program checklist ensure the safety of a mobility program?”

Enterprise mobility programs could miss critical elements without a proper checklist, whether they’re security-related, expense-related, program-related, or something else entirely. While MOBI’s software is the perfect copilot, your mobility program will never get off the ground without checking off a few boxes first.

Who’s responsible for your company’s mobile devices? How do users handle international travel plan and feature changes? Can your program ensure compliant devices that adhere to policy and protect data? Download our Enterprise Mobility Checklist today and make sure you’re prepared for takeoff.

Leave a Reply

Your email address will not be published. Required fields are marked *