task oriented versus object oriented interfaces

19 Jun 2004 - 11:08am
10 years ago
4 replies
711 reads
Florian Weber
2004

hi!

im interested in opinions about what is a better interface for
a cms:

a) a task oriented interface, where user click on a 'create
a new page' link and get passed thru a wizard which asks
them how they wanna name the page, in which section
they wanna create it, what the content should be, etc..

b) a objekt oriented interface, where a user clicks on a
treeview which displays sections and pages. selects the
section where he wants to create the page. then clicks
'new page', writes the title of the page. then clicks on a edit
button, edits it, etc..

the main target group is not very experienced users, who
never used a cms before and dont have a lot of experience
with more complex applications. however they will use the
cms quite a lot..

thanks a lot for any feedback!

ciao!
florian

Comments

22 Jun 2004 - 6:13am
Dave Malouf
2005

Florian,

The real answer is both.
When designing a CMS for the end user you have to realize that you are
talking about a multi-faceted interface. If you went with just one approach
in either case you will not be solving the whole of the problem.

I will say that you will hit the mark more often using task oriented flow
for the FIRST time user, a year or even 6 months from now that bullseye will
degrade more and more and users themselves will want to split between the
two models.

You should be able to easily toggle between the two modes of operating.

Basically, when building a CMS for "newbies" you have to be cognizant of the
fact that they won't be novices forever.

A task based flow of create, edit, publish will work in the beginning, but
take "edit" ... When I click there ...then what? Am I going to enter an
object oriented flow after that and when I'm done entering enter back into a
task flow when I'm ready to publish?

Yes, it is great that you are even considering a task oriented flow ... Many
CMS designers miss this mark ... But don't let someone tell you that for
"end users" task orientation is all that you need.

Ok, out of morbid curiosity, which CMS are you using?

-- dave

-----Original Message-----
From:
discuss-interactiondesigners.com-bounces at lists.interactiondesigners.com
[mailto:discuss-interactiondesigners.com-bounces at lists.interactiondesigners.
com] On Behalf Of Florian Weber
Sent: Saturday, June 19, 2004 12:08 PM
To: discuss-interactiondesigners.com at lists.interactiondesigners.com
Subject: [ID Discuss] task oriented versus object oriented interfaces

hi!

im interested in opinions about what is a better interface for
a cms:

a) a task oriented interface, where user click on a 'create
a new page' link and get passed thru a wizard which asks
them how they wanna name the page, in which section
they wanna create it, what the content should be, etc..

b) a objekt oriented interface, where a user clicks on a
treeview which displays sections and pages. selects the
section where he wants to create the page. then clicks
'new page', writes the title of the page. then clicks on a edit
button, edits it, etc..

the main target group is not very experienced users, who
never used a cms before and dont have a lot of experience
with more complex applications. however they will use the
cms quite a lot..

thanks a lot for any feedback!

ciao!
florian

_______________________________________________
Interaction Design Discussion List
discuss at interactiondesigners.com
--
to change your options (unsubscribe or set digest):
http://discuss.interactiondesigners.com
--
Questions: lists at interactiondesigners.com
--
Announcement Online List (discussion list members get announcements already)
http://interactiondesigners.com/announceList/
--
http://interactiondesigners.com/

22 Jun 2004 - 8:46am
Florian Weber
2004

hi! david!

the tricky part then is: how you wanna offer both. you could over some
kind
of way to switch from a novice to a expert interface or you could just
permanently
offer both days.

the problem is also that either solution is making the interface more
complex and could lead to confusion.

anybody got some examples where this is solved well?

thanks!

ciao!
florian

On Jun 22, 2004, at 13:13 Uhr, David Heller wrote:

> Florian,
>
> The real answer is both.
> When designing a CMS for the end user you have to realize that you are
> talking about a multi-faceted interface. If you went with just one
> approach
> in either case you will not be solving the whole of the problem.
>
> I will say that you will hit the mark more often using task oriented
> flow
> for the FIRST time user, a year or even 6 months from now that
> bullseye will
> degrade more and more and users themselves will want to split between
> the
> two models.
>
> You should be able to easily toggle between the two modes of operating.
>
> Basically, when building a CMS for "newbies" you have to be cognizant
> of the
> fact that they won't be novices forever.
>
>
> A task based flow of create, edit, publish will work in the beginning,
> but
> take "edit" ... When I click there ...then what? Am I going to enter an
> object oriented flow after that and when I'm done entering enter back
> into a
> task flow when I'm ready to publish?
>
> Yes, it is great that you are even considering a task oriented flow
> ... Many
> CMS designers miss this mark ... But don't let someone tell you that
> for
> "end users" task orientation is all that you need.
>
> Ok, out of morbid curiosity, which CMS are you using?
>
> -- dave
>
>
> -----Original Message-----
> From:
> discuss-interactiondesigners.com-bounces at lists.interactiondesigners.com
> [mailto:discuss-interactiondesigners.com-
> bounces at lists.interactiondesigners.
> com] On Behalf Of Florian Weber
> Sent: Saturday, June 19, 2004 12:08 PM
> To: discuss-interactiondesigners.com at lists.interactiondesigners.com
> Subject: [ID Discuss] task oriented versus object oriented interfaces
>
> hi!
>
> im interested in opinions about what is a better interface for
> a cms:
>
> a) a task oriented interface, where user click on a 'create
> a new page' link and get passed thru a wizard which asks
> them how they wanna name the page, in which section
> they wanna create it, what the content should be, etc..
>
> b) a objekt oriented interface, where a user clicks on a
> treeview which displays sections and pages. selects the
> section where he wants to create the page. then clicks
> 'new page', writes the title of the page. then clicks on a edit
> button, edits it, etc..
>
> the main target group is not very experienced users, who
> never used a cms before and dont have a lot of experience
> with more complex applications. however they will use the
> cms quite a lot..
>
> thanks a lot for any feedback!
>
> ciao!
> florian
>
> _______________________________________________
> Interaction Design Discussion List
> discuss at interactiondesigners.com
> --
> to change your options (unsubscribe or set digest):
> http://discuss.interactiondesigners.com
> --
> Questions: lists at interactiondesigners.com
> --
> Announcement Online List (discussion list members get announcements
> already)
> http://interactiondesigners.com/announceList/
> --
> http://interactiondesigners.com/
>
>
> _______________________________________________
> Interaction Design Discussion List
> discuss at interactiondesigners.com
> --
> to change your options (unsubscribe or set digest):
> http://discuss.interactiondesigners.com
> --
> Questions: lists at interactiondesigners.com
> --
> Announcement Online List (discussion list members get announcements
> already)
> http://interactiondesigners.com/announceList/
> --
> http://interactiondesigners.com/
>
>

23 Jun 2004 - 9:08am
Florian Weber
2004

hi david!

very good points!

i think however that in most cases a task oriented interface
makes it easier for users to figure out what they have to do. its
like somebody takes them by the hand and shows them around
a bit..

oh. and i forgot to answer which cms im using: im writing my own
one =)

ciao!
florian

On Jun 22, 2004, at 15:57 Uhr, David Heller wrote:

> HI Florian,
>
> Just a caution ... Object-oriented should not be confused for "expert"
> ...
> Mental mappings are quite personal and in user testing w/ Documentum we
> discovered that there was no corelation between user-type and their
> desire
> to be object or task oriented. Even an expert can be task-oriented and
> a
> novice can be object oriented.
>
> I think in the end you can do this through various start pages, or just
> various types of portlets of a dashboard and listing type and let the
> user
> decide the path from there.
>
> If you make the portal architecture personalizeable and configurable
> you
> will go a long way to helping users find their own way.
>
> All CMS's will require some level of training, b/c people do not
> naturally
> or intuitively think about objects or workflow this way. Some might
> see this
> as an inherent problem of CMS, but I see it has a cultural shift. I
> still
> hear people saying that they don't like cellphones b/c it dosen't fit
> their
> mental model for how to communicate w/ the world. I don't think that
> debunks
> all cellphones.
>
> Good luck!
>
> -- dave
>
> -----Original Message-----
> From: Florian Weber [mailto:csshsh at structbench.com]
> Sent: Tuesday, June 22, 2004 9:46 AM
> To:
> discuss-
> interactiondesigners.com at lists.interactiondesigners.comdiscuss-inter
> actiondesigners.com at lists.interactiondesigners.comdiscuss-
> interactiondesigne
> rs.com at lists.interactiondesigners.com
> Cc: David Heller
> Subject: Re: [ID Discuss] task oriented versus object oriented
> interfaces
>
>
> hi! david!
>
> the tricky part then is: how you wanna offer both. you could over some
> kind
> of way to switch from a novice to a expert interface or you could just
> permanently offer both days.
>
> the problem is also that either solution is making the interface more
> complex and could lead to confusion.
>
> anybody got some examples where this is solved well?
>
> thanks!
>
> ciao!
> florian
>
>
> On Jun 22, 2004, at 13:13 Uhr, David Heller wrote:
>
>> Florian,
>>
>> The real answer is both.
>> When designing a CMS for the end user you have to realize that you are
>> talking about a multi-faceted interface. If you went with just one
>> approach in either case you will not be solving the whole of the
>> problem.
>>
>> I will say that you will hit the mark more often using task oriented
>> flow for the FIRST time user, a year or even 6 months from now that
>> bullseye will degrade more and more and users themselves will want to
>> split between the two models.
>>
>> You should be able to easily toggle between the two modes of
>> operating.
>>
>> Basically, when building a CMS for "newbies" you have to be cognizant
>> of the fact that they won't be novices forever.
>>
>>
>> A task based flow of create, edit, publish will work in the beginning,
>> but take "edit" ... When I click there ...then what? Am I going to
>> enter an object oriented flow after that and when I'm done entering
>> enter back into a task flow when I'm ready to publish?
>>
>> Yes, it is great that you are even considering a task oriented flow
>> ... Many CMS designers miss this mark ... But don't let someone tell
>> you that for "end users" task orientation is all that you need.
>>
>> Ok, out of morbid curiosity, which CMS are you using?
>>
>> -- dave

23 Jun 2004 - 9:11am
Dave Malouf
2005

If I was forced to choose between the two (though I wouldn't like to be) I
would go w/ task oriented approach. :)

Good luck on the coding!

-- dave

-----Original Message-----
From: Florian Weber [mailto:csshsh at structbench.com]
Sent: Wednesday, June 23, 2004 10:08 AM
To: David Heller; discuss at interactiondesigners.com
Subject: Re: [ID Discuss] task oriented versus object oriented interfaces

hi david!

very good points!

i think however that in most cases a task oriented interface makes it easier
for users to figure out what they have to do. its like somebody takes them
by the hand and shows them around a bit..

oh. and i forgot to answer which cms im using: im writing my own one =)

ciao!
florian

On Jun 22, 2004, at 15:57 Uhr, David Heller wrote:

> HI Florian,
>
> Just a caution ... Object-oriented should not be confused for "expert"
> ...
> Mental mappings are quite personal and in user testing w/ Documentum
> we discovered that there was no corelation between user-type and their
> desire to be object or task oriented. Even an expert can be
> task-oriented and a novice can be object oriented.
>
> I think in the end you can do this through various start pages, or
> just various types of portlets of a dashboard and listing type and let
> the user decide the path from there.
>
> If you make the portal architecture personalizeable and configurable
> you will go a long way to helping users find their own way.
>
> All CMS's will require some level of training, b/c people do not
> naturally or intuitively think about objects or workflow this way.
> Some might see this as an inherent problem of CMS, but I see it has a
> cultural shift. I still hear people saying that they don't like
> cellphones b/c it dosen't fit their mental model for how to
> communicate w/ the world. I don't think that debunks all cellphones.
>
> Good luck!
>
> -- dave
>
> -----Original Message-----
> From: Florian Weber [mailto:csshsh at structbench.com]
> Sent: Tuesday, June 22, 2004 9:46 AM
> To:
> discuss-
> interactiondesigners.com at lists.interactiondesigners.comdiscuss-inter
> actiondesigners.com at lists.interactiondesigners.comdiscuss-
> interactiondesigne
> rs.com at lists.interactiondesigners.com
> Cc: David Heller
> Subject: Re: [ID Discuss] task oriented versus object oriented
> interfaces
>
>
> hi! david!
>
> the tricky part then is: how you wanna offer both. you could over some
> kind of way to switch from a novice to a expert interface or you could
> just permanently offer both days.
>
> the problem is also that either solution is making the interface more
> complex and could lead to confusion.
>
> anybody got some examples where this is solved well?
>
> thanks!
>
> ciao!
> florian
>
>
> On Jun 22, 2004, at 13:13 Uhr, David Heller wrote:
>
>> Florian,
>>
>> The real answer is both.
>> When designing a CMS for the end user you have to realize that you
>> are talking about a multi-faceted interface. If you went with just
>> one approach in either case you will not be solving the whole of the
>> problem.
>>
>> I will say that you will hit the mark more often using task oriented
>> flow for the FIRST time user, a year or even 6 months from now that
>> bullseye will degrade more and more and users themselves will want to
>> split between the two models.
>>
>> You should be able to easily toggle between the two modes of
>> operating.
>>
>> Basically, when building a CMS for "newbies" you have to be cognizant
>> of the fact that they won't be novices forever.
>>
>>
>> A task based flow of create, edit, publish will work in the
>> beginning, but take "edit" ... When I click there ...then what? Am I
>> going to enter an object oriented flow after that and when I'm done
>> entering enter back into a task flow when I'm ready to publish?
>>
>> Yes, it is great that you are even considering a task oriented flow
>> ... Many CMS designers miss this mark ... But don't let someone tell
>> you that for "end users" task orientation is all that you need.
>>
>> Ok, out of morbid curiosity, which CMS are you using?
>>
>> -- dave

Syndicate content Get the feed