Being hijacked via the Metro – An Unwanted Windows 8 Journey

Recently, misfortune struck when a key system failed at a rather inopportune moment.  Fortunately, a replacement was quickly obtained, and I thought it would be up and running quickly.  My hope the matter would be resolved quickly faded when I turned on the machine.  To my disappointment, Windows 8 was pre-installed, and that is when the fun began.
My first reaction was one of minor annoyance, but I comforted myself thinking I would learn a few new things during the restoration process.  I certainly learned a lot, far more than I wanted or expected.  The key lesson for me: avoid Windows 8 unless you have a lot of time to invest.
The degree of change, particularly with the new interface, Metro (now called "modern UI style") is substantial.  Personally, I did not find the interface intuitive, and it seemed poorly structured.  This caused me to spend a lot of time searching online for guidance to accomplish even the most basic tasks.  Moreover, in an effort to unclutter the interface, Microsoft has removed features they deemed were infrequently used. I wish I could have reached through the internet and magically dope-slap the design team back in Redmond.
The simple task of configuring both wired and wireless network connections turned into a royal pain.  Generally this task takes me less than 10 minutes with Windows XP, Vista, or 7. Adding multiple locations is only a minor additional effort.   Using Windows 8, it took at least 3 times longer, and I am still having some issues.
Even with the experience gained during restoration, basic processes seen much more complex and less straightforward than before.  More than once during this experience I wondered how much harder it would be to “throw in the towel” and buy a Mac.  I still might; time will tell.
All this before I mention the new Start screen – the metro interface.  Where or where did the Start menu go (you can get it back with add-ons)? The new Start screen seems is missing in action.  One of objectives for Windows 8 is to provide a unified, touch enabled, interface across platforms.  A noble goal to be sure, but I suspect it might end up being substandard on all devices.  I am not ready to turn in my Apple iPad as of yet.

With experience, I became “functional” using Windows 8.  However, I still find it stressful.  There are some positive aspects of the interface, and I am sure more will follow.  The system is young and with Microsoft’s substantial backing it will mature quickly.
For Chief Information Officers (CIOs) and other key IT Leaders, adopting Windows 8 will be a major undertaking.  Beyond all the typical tasks associated with moving to another operating system (client or server), Windows 8 will present additional challenges for both users and IT staff alike.  Much of the accumulated knowledge, directions, procedures, and training material are obsolete.  Help desk personnel will require additional training and resources to support the system.  The change is far more significant that the Windows XP -> Vista -> Windows 7 migration path or combination thereof.

 In today’s world of BYOD, Windows 8 is a reality organizations are being forced to deal with on an increasing basis.  Irrespective of BYOD policies, organizations will need to support and accommodate Windows 8.
Windows 8 does have some intrinsic features IT organizations will appreciate.  The concept of a “common” operating system across platforms has the potential to provide many benefits:  simplified administration, better security reduced training, and more.   Even noting these benefits, the cost of change will be significant.  It is going to be a difficult business case for most IT organizations to make, especially in the near term.
So what is a CIO to do?  My recommendation is to take steps to ensure their organizations are building Windows 8 skills and start thinking about migration planning.  The only given here is that change is inevitable.  Take some aspirin and hold-on, it will be an exciting ride via the Metro!  With planning, you should be able to direct the ride and arrive as planned.



Blogger - WiseTechGuy
Executive Profile - ClintonGilliam.com

Popular posts from this blog

How to Communicate Your IT Budget, Part IV

Image
Step Four – Presenting the Budget With the work you accomplished in the previous steps, it is time present the budget. In all but the smallest organizations, standardize approaches for submitting and presenting budgets are mandated. These approaches may include spreadsheets, online tools, and presentation templates. A common goal is to produce submissions that are consistent with respect to organization and content. They also provide a way to ensure critical issues are addressed. For example, how each group will manage / be impacted by growth, potential reductions, or other significant events. Show Time Presenting an Information Technology (IT) budget can be challenging. The forces driving IT costs are not always understood, and even more fundamentally, the very essence of IT is often unclear to executives. Other factors can complicate the effort. As previously discussed, costs might be held by organizations outside of IT. This can make it difficult to calculate the
Read more

How to Communicate Your IT Budget, Part I

Image
In many organizations, Information Technology (IT) represents a  significant portion of the overall budget.  In fact, IT is typically among the top expenditures.  Consequently, this budgetary prominence drives a corresponding level of scrutiny by management; an exercise that is often found to be time-consuming and frustrating for all concerned. Much is written about capturing the value of IT and leveraging processes to ensure value-delivery.  Organizational cultures typically dictate the overall budget process.  During my career, I have labored under many of these systems; each has their advantages and disadvantages.   I am going to leave the overarching budget process for others to debate; the focus here is on how to communicate and sell your budget.   Your budget proposal needs to be communicate in a manner that will resonate with executive charged with approving the budget.  In my experience, this is where the process fails.   As with many issues, ineffective communicati
Read more

How to Communicate Your IT Budget, Part III

Image
Step Three – The Unveiling  With the work you accomplished in step one and two, it is time to begin focusing on communication. Specifically, how the budget is built, the primary drivers, and validation. Focus on the Core Elements I like to begin by going back to the key elements picture from Step 1: Take time to walk through each circle on the diagram above. Doing so allows you to establish a standard vocabulary with your audience while illustrating your primary budget drivers. Be sensitive to local conventions and vernacular; consider adjusting your own when necessary. Avoid unproductive discussion about terminology whenever possible, the goal is to arrive at a common and informed view. As a side note, one of the benefits of previewing the budget, as discussed in the Validation section of Step Two, is to identify and resolve many, if not all, these issues early in the process. Assembling the Pieces With the essential core elements driving the IT budget defined, it
Read more