Choosing Mobile Devices for Your Project
Taking all that you've learned, you can now start to design. At Stratix, our Solutions Architects call it a Mobile Solution Blueprint. There's lots to think about, including devices, operating systems, device management platforms, support, and even carrier networks. Your blueprint should include these elements:
Here's where your understanding of your end-user needs and desired outcomes gives you special powers. A frequent cause of poor adoption is frustration with a device because it's not easy to use. That can be caused by physical outer design or internal software shortcomings.
Are there requirements that mean you need a small or even wearable device? Perhaps the opposite is true, and a big screen is the way to go. Will you need accessories like scanners attachments or Bluetooth peripherals. Some organizations need the level of device software customization possible with Android enterprise solutions, while others will pick enterprise Apple because of end-user preferences, compatibility, or other needs. The bottom line is that the devices and operating systems have to check the boxes to get you the right results.
Throughout the enterprise mobile solution design process, keep futureproofing in the back of your mind and build it into your blueprint. The last thing you want is something that goes quickly out of date or can't be adapted if your needs change.
Calculating the life expectancy of the devices and peripherals you select is just one part of futureproofing. That includes operating system and application updates and ensuring the manufacturer intends to support the devices for the entire period you intend to use them.
Futureproofing also includes flexibility and scalability. What if you have workflow changes or new uses for the mobile solution down the road? How adaptable is it? If business goes well and you need to expand, will your devices and infrastructure handle it? Good solution design goes beyond just thinking about today. Try to plan for tomorrow too.
Learn More Opportunity
Listen to Episode >
Read More >
Equal with device choice to the success of any enterprise mobile solution is management and support. Once your devices are deployed, how are you going to track them and keep them updated? Who's going to manage the device lifecycle, swap out broken equipment, and do repairs? How will you support end users wherever they are? All of it needs to be in your blueprint.
a. Mobile Lifecycle Management A complete enterprise mobility management plan doesn't stop at purchasing devices. Even after the initial deployment, there will be an ongoing need to administer your inventory as employees join or leave the organization. You also need a solution to take in devices that need repair and send out replacements. As devices reach end-of-life and have to be replaced, you'll want an environmentally-friendly IT Asset Disposition (ITAD) solution to repurpose them or dispose of them properly.
b. Mobile Device Management (MDM) Just like PCs, mobile devices require constant management to ensure they're up to date and secure. Your blueprint will include an MDM platform for that endpoint management and control. There are many MDM vendors to choose from. Considerations include:
c. Asset Management A major challenge in managing enterprise mobility is knowing where all your devices are and their status. You can't just walk around the office and do inventory. Solutions like Stratix's itrac360 give you a single portal that aggregates orders, asset location, spare pool status, repair history, reporting and more, in real-time.
d. Mobile Help Desk The nature of the enterprise mobility environment means you need to be able to help people wherever they are and when they need it. Your 24/7 mobile help desk also must be staffed with experts on your mobile solutions so end users get effective support that minimizes downtime.
Your mobile solution blueprint should include an accurate Total Cost of Ownership estimate. You don't want to be on the hot seat down the road if the TCO is higher than your leadership expects. Your calculation should include:
Read Paper >
Testing and End User Acceptance of Your Mobile Project
Before you move to large-scale deployment, it's absolutely critical you thoroughly test your solution in as close to a real-world environment as you can get. That includes first article inspection to compare test devices with your blueprint to make sure they're delivering what they're supposed to. Small pilot programs with the actual end users who'll be working with your solution are ideal. Make sure all the bugs are worked out, or you risk poor adoption after rollout. First impressions count for a lot, so if something doesn't satisfy right out of the box, it's extremely difficult to change people's minds down the road.
With your mobile solution blueprint complete, and testing done, it's time to draw out the implementation roadmap. There are two big pieces:
a. Change Management To ensure end-user adoption, you need a plan for communication and training so that they know what's coming, what the benefits are, and how to use the solution when they get it.
b. Execution The second part of your roadmap is the plan for procurement, kitting, configuration, and distribution. How are you going to get the scale and expertise you need to do it quickly and smoothly? Do you need to bring on temporary help or set up a special room or other location to get it done?
Mobile Solution Design Examples
With a well-thought-out enterprise mobile solution that incorporates all the steps we've covered in this class, you have a much better chance of achieving the outcomes you want. In our next class, we'll do a deeper dive into mobile device lifecycle management to ensure your solution is convenient, easy, and cost-effective.
Listen to Dipesh dive into further details on creating solutions that delight end users and deliver on business goals. Listen to Episode >
View Infographiic >
