Commentary

Dave Methvin
 

Can An Office Suite Be Too Powerful?

The new Microsoft Office 2010 looks like it will have lots of new features and a consistent ribbon interface across the entire product suite. There's better integration with mobile devices, and even a free browser-based subset of the suite. Are these the tools that all users need to do their jobs?

The new Microsoft Office 2010 looks like it will have lots of new features and a consistent ribbon interface across the entire product suite. There's better integration with mobile devices, and even a free browser-based subset of the suite. Are these the tools that all users need to do their jobs?For the past 15 years, Microsoft Office has been accumulating features. Some of them, like the AutoSpell feature added in Office 95, have been adopted by dozens of other applications. Others are more esoteric, like numbered lines and paragraphs in a document, but still considered essential by specific groups such as the legal profession. Yet most people who use Office never come anywhere close to using most of its functionality.

In the mid-1990s, I filed my taxes using an Excel 95 spreadsheet similar to this one. It not only looked like the real tax form, it printed out on paper like the real tax form. That inspired me to write my own Excel "application" that implemented the company's expense reporting, and it became popular with dozens of other employees. When it came to writing their own spreadsheets, most Excel users ever do more than a simple table and a graph or two.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That is actually not a bad thing. Users shouldn't be trying to use all the functionality of a product just of the heck of it, and they certainly shouldn't be using features that don't improve their work product. We've all suffered through PowerPoint presentations full of text-heavy Comic Sans bullet points, way-too-cute clipart, and random slide transitions. Instead of encouraging effective communication, those features waste the author's time and actually obscure the points they're trying to make.

With each new release, the Office suite becomes bigger and harder to master. There's nothing wrong with a big powerful tool for an expert, but it's usually not the right tool for a casual user. It's also a waste of money for a company to use a complex tool when a simple one would do the job. Not only is the complex tool more expensive to buy, but the complexity of the tool makes it more difficult and time-consuming to learn, costing employees valuable time.

What I'd really like to see in Office 2010 is the ability for most people to use the simple browser-based versions of the applications, and only burden the experts with the full-blown apps. I don't know if this will really work, though; getting Office 2003 and Office 2007 to share documents has been a hassle in my experience. If the browser-based apps can't effectively use the documents created by the full apps, everyone is back to installing the full Office 2010 suite on each system. It's almost like Microsoft has a disincentive to make the browser versions too good, so I'm very curious to see how good the browser-based versions really are.


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