How would you prefer to keep the screen elements which are rarely useful in the modules/applications/screens?

1 Dec 2009 - 7:15am
4 years ago
1 reply
754 reads
Sohel Kapasi
2008

Most of the time while working with heavy data intensive application I
have encountered that there is 20 to 30% of the
modules/webparts/portlates/functionality are rarely useful for the
end-users in most of the applications for example elements like News,
Article, Record Summery, Archive Records, User Summery, Report
Summery, etc.. They are defiantly useful for the user to make some
business decision while accessing that module or page but they still
occupying area on screens and therefore designer end-up compromising
business critical data/fields on the screen for the information which
is rarely or occasionally useful for end-users.

I have my way to handle this situation but I want to understand how
are you handling this, let me evaluate your methods with mine and I
am sure I will improve a lot.

Thank you very much for your suggestions well in advance.

sohelkapasi at gmail.com

Comments

1 Dec 2009 - 9:50am
bminihan
2007

It could be your page is trying to do too many things at the same time. In
this situation, I tend to make the case for a new page (sub-page, community,
whichever fits your application) so that the task-at-hand can take up more
real estate without having to fight for space with superfluous portlets.

Alternatively, if your application supports it, minimize the non-critical
elements in the page, and allow the user to expand them if needed. That's
not terribly common or easy to do, but if it's a custom application, perhaps
you have the means to do so.

Bryan Minihan

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Sohel
Kapasi
Sent: Tuesday, December 01, 2009 4:16 AM
To: discuss at ixda.org
Subject: [IxDA Discuss] How would you prefer to keep the screen elements
which are rarely useful in the modules/applications/screens?

Most of the time while working with heavy data intensive application I
have encountered that there is 20 to 30% of the
modules/webparts/portlates/functionality are rarely useful for the
end-users in most of the applications for example elements like News,
Article, Record Summery, Archive Records, User Summery, Report
Summery, etc.. They are defiantly useful for the user to make some
business decision while accessing that module or page but they still
occupying area on screens and therefore designer end-up compromising
business critical data/fields on the screen for the information which
is rarely or occasionally useful for end-users.

I have my way to handle this situation but I want to understand how
are you handling this, let me evaluate your methods with mine and I
am sure I will improve a lot.

Thank you very much for your suggestions well in advance.

sohelkapasi at gmail.com
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Syndicate content Get the feed