Google Fights E-mail Overload With Priority Inbox

Gmail has gained an automated, trainable filter that attempts to segregate important e-mail messages.

Google on Tuesday plans to introduce a Priority Inbox for Gmail that it says could save an average of 46 minutes of e-mail processing time per week per user.




Top 15 Google Apps For Business
(click for larger image and for full photo gallery)

More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

For employers, that could translate into a productivity savings of over 40 hours per year. In monetary terms, that would be worth over $1,100 annually per Gmail user for private sector companies and almost $1,600 annually per Gmail user for government agencies, based on average employee compensation costs reported by the Bureau of Labor Statistics in June.

Priority Inbox is Google's attempt to deal with information overload. It's a visually distinct area of one's Gmail inbox that displays messages deemed to be more important than the rest. The assumption is that Gmail users can work more efficiently by dealing with important e-mail and deferring or ignoring less important e-mail.

Priority Inbox relies on a filtering system to sort significant messages from less significant ones. It differs from Gmail's existing user-configurable, keyword-based filters in that it filters automatically, can be corrected when it fails, and tries to learn on its own.

Google suggests that Priority Inbox is like the Gmail spam folder, except for the good stuff. Training is simple: A "+" icon puts e-mail into the Priority Inbox; a "-" icon takes e-mail out. The system also considers frequently e-mailed people to be important.


Page 2: 
 1 | 2 |Next Page » 

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