Determine implementation benefits

- [Instructor] Other than understanding the jobs that are being accomplished by my organizations devices I must design the mobile program around all of the moving parts necessary to provide those jobs without interruption while also protecting the company's valuable assets and data. There are seven big points to consider. First, I need to define what devices will be allowed in my organization. Will I have corporate owned or user owned devices? Can I support Windows, Android, and iOS? How will the devices become managed? Second, I'll choose how users are enrolled in the program.

Will my users be basic or directory users? What about mobility support users? What kind of groupings do I need? Third, I want to determine what applications are needed. Will I deploy public or private applications? How will I manage application updates or new applications? Fourth, I'll have to determine how my mobility platform will integrate with the organizations infrastructure. Will I build a platform that integrates with directory services? Will I need to integrate proxy servers? Fifth, I'll mold how end users will be supported.

How will my end users understand how to get help? How will they anticipate changes and accomplish their jobs? Sixth, I'll need to lay out a plan to manage mobility's high change rate. How will I prepare my organization for changes that we cannot control? Finally, I need to consider the security of the organization. How is each part of the mobility program secured? It's critical for me to cover these concerns before I begin to roll out a platform. My goal is to build a successful mobility program, therefore I must anticipate a dynamic set of interconnected pieces.

Mobility does not have the option to set it and forget it.