BLOGS

"Our website is not set up for mobile but it's not broken so we don't need to address it yet".  This is the response and attitude that has become all too common.  Why is our response never "It's not set up for mobile but the site is still working so do you (as the web expert) see any downside to putting this off?"  An IRO wouldn't comment on the exact mining method of an mine operation or best approach without first seeking advice of those who know best (mine engineers/operators, etc) so why do some feel differently when it comes to our online communication?

SECURITY 

If there is no mobile compatibility then one can assume it's using older technology, which in turn affects the server environment it's housed in. Each upgrade in programming language, OS, and so forth brings about new security measures. If we are restricted from staying current because we are using unsupported products then we can't assure our security. Upgrades for latest security purposes are not usually infinitely backwards compatible. For example, if I'm still using windows 98 (yes as in 1998) then I most likely cannot be running even Office 2010. There are no more security updates or even support for Windows 98 at present so being out of date also means compromising your security. Therefore, when you acknowledge a lack of mobile compatibility but choose to keep doing more of the same because it's 'not broken' then you are being reactive instead of proactive.

lock

LIMITED FEATURE SET

If you do not have mobile compatibility then you are most likely not current. If you are not current then you most likely do not have the latest feature set. Why is this important? It's important because your CMS platforms now a days should not be relied upon for only content but extending out to effecting your daily workflow. The foot print a full feature set can have on a company's daily workflow is significant versus technology we used many years back. As a result this can reduce staffing costs, reduce bottlenecks within your organization, reduce probability of error, etc. IRO's have to forgo their stereotypes that CMS platforms are only for managing content and need to look outside the box.

limited features

demotoday linkedin logo mini twitter logo minii