Commentary

Tom Smith
VP, Web Analytics  

The Good, The Bad, And The Ugly Of Mobility

Our two most relied upon computing/communications devices--the laptop and the cell phone--are making headlines today. The failure rate on laptops (and desktops)--failure defined as necessitating replacement of a hardware component--is dropping, but remains higher than a rate I'd consider optimal.

Our two most relied upon computing/communications devices--the laptop and the cell phone--are making headlines today.

The failure rate on laptops (and desktops)--failure defined as necessitating replacement of a hardware component--is dropping, but remains higher than a rate I'd consider optimal.The annual failure rate of notebooks ranges from 15% for systems bought today to a projected 20% in three years (the rates are significantly lower for desktops). In my experience, the corporate-issue laptop has been a stalwart; I can't recall a hardware failure in more than 10 years with a notebook. The personal laptop I purchased about 18 months ago--a middle-of-the-road model from a top-name supplier--is flaking out, with failures or near-failures of critical components that have me convinced I'll be replacing it before it reaches two years of age. Are 15 to 20% of you experiencing hardware failures on laptops less than three years old? If so, that's not a great indicator of product quality, even if it's better than it was before.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Laptops, with poor handling and inadequate security practices, have emerged as another weak link in a long string of customer data losses. There's a must-read update from The Wall Street Journal. Companies, it seems, are finally responding to the problem. In a report called "Laptop Lockdown" (subscription required), the Journal details companies that are aggressively tightening (or creating) policies regarding data that can and can't be on laptops, how those laptops must be handled, and so on.

Boeing now requires laptops to be physically locked with a cable to a stationary object in offices, conference rooms, and cars so that no one can walk away with them. It forbids confidential data from being stored on laptops. And it's begun random audits of laptops to check for unauthorized or unsecured files. The most sensible and obvious of these measures is the policy defining what can't be stored on a laptop. There's no excuse for other companies not to follow suit, at least on this one obvious security practice.

As much as we rely on laptops, the cell phone is equally critical for business and personal communications. Yet when traveling by air, one of the last things many of us want is a chatterbox on a cell phone within earshot. Despite some earlier signs that cell phones would become ubiquitous in the air, progress has slowed. A closely watched Boeing service may be terminated, Verizon is ending its Airfone in-flight service, and the near-term outlook for cell phones on planes in the United States is "bleak," according to our report. There's nothing bleak in that news.

An in-flight cell phone slowdown won't matter to Intel, which made an unceremonious exit from the cell phone processor business following what InformationWeek blogger Darrell Dunn labels as a failure of historic proportions, leading to the sale of the business to Marvell for $600 million despite an investment estimated in the billions. Dunn observes that Intel tried to slip that one by quietly under its splashy Woodcrest server processor announcement earlier this week. No such luck.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links