PSPS #7828: Create a collection of Personas to represent integrators and common use cases

4 messages Options Options
Embed this Post
Permalink
Eleonora Borelli

PSPS #7828: Create a collection of Personas to represent integrators and common use cases

Reply Threaded MoreMore options
Print post
Permalink
Championing the PSPS #7828: "Create a collection of Personas to
represent integrators and common use cases"

Aim: write down "pictures" of the users of Plone, trying to describe
their traits and background, the way they are using the system, the
problems and goals they're going into when dealing with common (or
uncommon) tasks.

The idea(s) behind this Action are:
a) we may need user profiling both to frame our audience and to market
plone to customers
b) we may need it with a focus on customization & configuration work
because it could give us a bright insight on the Plone3 experience
c) Q&A from the Plone Strategic Survey, and psps materials could be a
starting point for it

The focus is on integrators, but it sure could be expanded to other
profiles, from core developers to end-end-end-users.

If this idea have some followers we can open a page on OpenPlans and:

- gather documentation and examples: definitions, short bibliography,
models, example of profiles made for other CMS'ish software
- define the level of accuracy to reach and the parameters to use in the
characterization
- sketch some "personas" that can be representative of the mythical
integrator in his/her role
- write down some typical customization & configuration tasks
- imagine how our integrators would perform that tasks in some plone3
related scenarios

Timeline:
2/18 - 2/25: kick-off: expression of interest, questions, feedback
2/25 - 3/3:  collect resources, examples, first writings on OpenP (or
similar), discuss methodologies
3/3  - 3/18: have a first collection of personas and tasks
3/18 - 3/31: choose between profiles if needed; put things together:
make personas "alive"
4/1: spread fake results (april fool)
4/2  - 4/7: format and spread (real) results

Note: the timeline is rough and may need iterations

Success:
* we put together 2/3 good stories of integrators working on likely
real-life issues
* we provide such good typecasting that all integrators start feeling
more happy and confident
* we trigger a similar process for other figures (developers, editors,
consultants, site admins) and this leads to better docs/sites/marketing,
better understanding each other, better plone, better world..

Concern:
we do not really have ad-hoc data to build a strict characterization:
personas would be designed using hints that are coming from the psps
summit, survey and panels, but mostly from the direct/indirect
experience of the partecipants or even pure imagination..

Championship / Call for action:
Good profiles are good tools in the design process: they can be more
complex and thorough or very simple and direct and writing personas is
also a good exercise itself, so if you're interested in any way, please
reply to this message, watch the ticket and have fun!

Cheers
E.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers
Dylan Jay-3

Re: PSPS #7828: Create a collection of Personas to represent integrators and common use cases

Reply Threaded MoreMore options
Print post
Permalink
I'm an integrator so I'd like to help by contributing not just my
experiences but also various customer stories.

Eleonora Borelli wrote:

> Championing the PSPS #7828: "Create a collection of Personas to
> represent integrators and common use cases"
>
> Aim: write down "pictures" of the users of Plone, trying to describe
> their traits and background, the way they are using the system, the
> problems and goals they're going into when dealing with common (or
> uncommon) tasks.
>
> The idea(s) behind this Action are:
> a) we may need user profiling both to frame our audience and to market
> plone to customers
> b) we may need it with a focus on customization & configuration work
> because it could give us a bright insight on the Plone3 experience
> c) Q&A from the Plone Strategic Survey, and psps materials could be a
> starting point for it
>
> The focus is on integrators, but it sure could be expanded to other
> profiles, from core developers to end-end-end-users.
>
> If this idea have some followers we can open a page on OpenPlans and:
>
> - gather documentation and examples: definitions, short bibliography,
> models, example of profiles made for other CMS'ish software
> - define the level of accuracy to reach and the parameters to use in the
> characterization
> - sketch some "personas" that can be representative of the mythical
> integrator in his/her role
> - write down some typical customization & configuration tasks
> - imagine how our integrators would perform that tasks in some plone3
> related scenarios
>
> Timeline:
> 2/18 - 2/25: kick-off: expression of interest, questions, feedback
> 2/25 - 3/3:  collect resources, examples, first writings on OpenP (or
> similar), discuss methodologies
> 3/3  - 3/18: have a first collection of personas and tasks
> 3/18 - 3/31: choose between profiles if needed; put things together:
> make personas "alive"
> 4/1: spread fake results (april fool)
> 4/2  - 4/7: format and spread (real) results
>
> Note: the timeline is rough and may need iterations
>
> Success:
> * we put together 2/3 good stories of integrators working on likely
> real-life issues
> * we provide such good typecasting that all integrators start feeling
> more happy and confident
> * we trigger a similar process for other figures (developers, editors,
> consultants, site admins) and this leads to better docs/sites/marketing,
> better understanding each other, better plone, better world..
>
> Concern:
> we do not really have ad-hoc data to build a strict characterization:
> personas would be designed using hints that are coming from the psps
> summit, survey and panels, but mostly from the direct/indirect
> experience of the partecipants or even pure imagination..
>
> Championship / Call for action:
> Good profiles are good tools in the design process: they can be more
> complex and thorough or very simple and direct and writing personas is
> also a good exercise itself, so if you're interested in any way, please
> reply to this message, watch the ticket and have fun!
>
> Cheers
> E.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers
Eleonora Borelli

Re: PSPS #7828: Create a collection of Personas to represent integrators and common use cases

Reply Threaded MoreMore options
Print post
Permalink
Dylan Jay ha scritto:
 > I'm an integrator so I'd like to help by contributing not just my
 > experiences but also various customer stories.

Great!
Sorry for the delay. I'm starting a page on Open Plans called
"Profiles and Stories from the Plone World"
http://www.openplans.org/projects/plone-stories

I think we should also keep an eye on Donna's project on
http://www.openplans.org/projects/ploneintegrators
and interact as much as possible.

Let's start!
Eleonora

> Eleonora Borelli wrote:
>> Championing the PSPS #7828: "Create a collection of Personas to
>> represent integrators and common use cases"
>>
>> Aim: write down "pictures" of the users of Plone, trying to describe
>> their traits and background, the way they are using the system, the
>> problems and goals they're going into when dealing with common (or
>> uncommon) tasks.
>>
>> The idea(s) behind this Action are:
>> a) we may need user profiling both to frame our audience and to market
>> plone to customers
>> b) we may need it with a focus on customization & configuration work
>> because it could give us a bright insight on the Plone3 experience
>> c) Q&A from the Plone Strategic Survey, and psps materials could be a
>> starting point for it
>>
>> The focus is on integrators, but it sure could be expanded to other
>> profiles, from core developers to end-end-end-users.
>>
>> If this idea have some followers we can open a page on OpenPlans and:
>>
>> - gather documentation and examples: definitions, short bibliography,
>> models, example of profiles made for other CMS'ish software
>> - define the level of accuracy to reach and the parameters to use in the
>> characterization
>> - sketch some "personas" that can be representative of the mythical
>> integrator in his/her role
>> - write down some typical customization & configuration tasks
>> - imagine how our integrators would perform that tasks in some plone3
>> related scenarios
>>
>> Timeline:
>> 2/18 - 2/25: kick-off: expression of interest, questions, feedback
>> 2/25 - 3/3:  collect resources, examples, first writings on OpenP (or
>> similar), discuss methodologies
>> 3/3  - 3/18: have a first collection of personas and tasks
>> 3/18 - 3/31: choose between profiles if needed; put things together:
>> make personas "alive"
>> 4/1: spread fake results (april fool)
>> 4/2  - 4/7: format and spread (real) results
>>
>> Note: the timeline is rough and may need iterations
>>
>> Success:
>> * we put together 2/3 good stories of integrators working on likely
>> real-life issues
>> * we provide such good typecasting that all integrators start feeling
>> more happy and confident
>> * we trigger a similar process for other figures (developers, editors,
>> consultants, site admins) and this leads to better docs/sites/marketing,
>> better understanding each other, better plone, better world..
>>
>> Concern:
>> we do not really have ad-hoc data to build a strict characterization:
>> personas would be designed using hints that are coming from the psps
>> summit, survey and panels, but mostly from the direct/indirect
>> experience of the partecipants or even pure imagination..
>>
>> Championship / Call for action:
>> Good profiles are good tools in the design process: they can be more
>> complex and thorough or very simple and direct and writing personas is
>> also a good exercise itself, so if you're interested in any way, please
>> reply to this message, watch the ticket and have fun!
>>
>> Cheers
>> E.
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Plone-developers mailing list
> Plone-developers@...
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>


--
Eleonora Borelli             Email:  eleonora@...
Reflab S.r.l. - Plone Design, Development and Consulting
Phone:  +39 3471841847             http://www.reflab.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Plone-developers mailing list
Plone-developers@...
https://lists.sourceforge.net/lists/listinfo/plone-developers

Eleonora Borelli

Re: PSPS #7828: Create a collection of Personas to represent integrators and common use cases

Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Eleonora Borelli