User: jpmcc Date: 2009-06-18 11:00:16+0000 Modified: marketing/www/planet/atom.xml marketing/www/planet/index.html marketing/www/planet/opml.xml marketing/www/planet/rss10.xml marketing/www/planet/rss20.xml
Log: Planet run at Thu Jun 18 12:00:14 BST 2009 File Changes: Directory: /marketing/www/planet/ ================================= File [changed]: atom.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/atom.xml?r1=1.2005&r2=1.2006 Delta lines: +29 -29 --------------------- --- atom.xml 2009-06-18 05:00:07+0000 1.2005 +++ atom.xml 2009-06-18 11:00:08+0000 1.2006 @@ -5,9 +5,29 @@ <link rel="self" href="http://marketing.openoffice.org/planet/atom.xml"/> <link href="http://marketing.openoffice.org/planet/"/> <id>http://marketing.openoffice.org/planet/atom.xml</id> - <updated>2009-06-18T05:00:26+00:00</updated> + <updated>2009-06-18T11:00:27+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> + <entry xml:lang="en"> + <title type="html">Ten million</title> + <link href="http://www.mealldubh.org/index.php/2009/06/18/ten-million/"/> + <id>http://www.mealldubh.org/?p=720</id> + <updated>2009-06-18T07:04:39+00:00</updated> + <content type="html"><p><img src="http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif" alt="10,097,767" title="10,097,767" width="179" height="37" class="alignright size-full wp-image-722" />The <a href="http://marketing.openoffice.org/marketing_bouncer.html">download counter</a> at <a href="http://marketing.openoffice.org/">OpenOffice.org</a> is showing that downloads of OpenOffice.org from the <a href="http://download.openoffice.org/">OpenOffice.org download page</a> have passed the ten million mark (the counter was reset when OpenOffice,org 3.1 was launched on 7th May).</p> +<p>That&#8217;s a lot of happy users!</p></content> + <author> + <name>John McCreesh</name> + <uri>http://www.mealldubh.org</uri> + </author> + <source> + <title type="html">Meall Dubh » OpenOffice.org</title> + <subtitle type="html">a view from a dark hill</subtitle> + <link rel="self" href="http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/"/> + <id>http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/</id> + <updated>2009-06-18T11:00:15+00:00</updated> + </source> + </entry> + <entry> <title type="html">Eccles cake in Shoreditch</title> <link href="http://ooo-speak.blogspot.com/2009/06/eccles-cake-in-shoreditch.html"/> @@ -88,7 +108,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> + <updated>2009-06-18T11:00:17+00:00</updated> </source> </entry> @@ -112,7 +132,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> + <updated>2009-06-18T11:00:17+00:00</updated> </source> </entry> @@ -204,7 +224,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> + <updated>2009-06-18T11:00:17+00:00</updated> </source> </entry> @@ -226,7 +246,7 @@ <subtitle type="html">a view from a dark hill</subtitle> <link rel="self" href="http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/"/> <id>http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/</id> - <updated>2009-06-16T17:00:16+00:00</updated> + <updated>2009-06-18T11:00:15+00:00</updated> </source> </entry> @@ -247,7 +267,7 @@ <subtitle type="html">a view from a dark hill</subtitle> <link rel="self" href="http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/"/> <id>http://www.mealldubh.org/index.php/category/open-source/openofficeorg/feed/</id> - <updated>2009-06-16T17:00:16+00:00</updated> + <updated>2009-06-18T11:00:15+00:00</updated> </source> </entry> @@ -314,7 +334,7 @@ <subtitle type="html">The Magic of Open Source</subtitle> <link rel="self" href="http://www.theopensourcerer.com/tag/openofficeorg/feed/"/> <id>http://www.theopensourcerer.com/tag/openofficeorg/feed/</id> - <updated>2009-06-16T17:00:35+00:00</updated> + <updated>2009-06-18T11:00:27+00:00</updated> </source> </entry> @@ -337,7 +357,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> + <updated>2009-06-18T11:00:17+00:00</updated> </source> </entry> @@ -461,27 +481,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> - </source> - </entry> - - <entry> - <title type="html">Ideation and what's next in the Renaissance Project</title> - <link href="http://blogs.sun.com/GullFOSS/entry/ideation_and_what_s_next"/> - <id>tag:google.com,2005:reader/item/d1a38e6f8a4c00f9</id> - <updated>2009-05-25T19:56:33+00:00</updated> - <content type="html"><p> So, the collection of design proposals and their refinement is over. Thanks to everyone who has participated and spent nights to finish either in time or a bit later. Liz will post a detailed summary about that part of the current phase later this week. With this post, I'd like to share my experience with using some ideation methods I learned in Berlin for UI brainstorming, and to give a short preview of what is about to happen in the Renaissance Project and for what reason.<br /><br />But first, letâs check what we have planned and what was in the project road map. Here is how phase two of project Renaissance was initially set up:<br /><br /><b>1.   Incorporate research data</b><br />   a.   Analyze quantitative/qualitative data to understand usage/users<br />   b.   Create personas based on the analysis<br /><b>2.   Focus on the personas' characteristics</b><br />   a.   Create scenarios for key functionalities<br />   b.   Define information architecture from the scenarios<br />   c.   Flow charts<br /><b>3.   Generate design ideas using the scenarios</b><br />   a.   Paper prototypes<br />   b.   Clickable slides<br />   c.   Dynamic prototypes<br /><br />I am still convinced that our initial plan was quite well elaborated and promising. However, looking at that now I must admit that we were not able to achieve many of the tasks that are listed here. In retrospective, we jumped right from 1a to 3b, which is of course possible but it makes many other design activities a lot harder at a later stage. Due to time and resources constraints, we spent only little time on understanding our quantitative data and almost no time on qualitative research. As a consequence, we were only partially able to generate findings that support design decisions. But still, please donât get me wrong, what we got from our research is a lot more and better than relying on pure subjective assumptions. And that is a good thing and a good start.<br /><br />However, usually you would want to start with a redesign strategy that defines your redesign scope and therefore guides any of your design research activities such as what research questions youâd like to have answers to. I would say that we were quite good at this part. But as stated above, we were not able to answer a few of our important research questions such as âWhat is important to our users and what are their goals?â, âHow do they feel using our product?â or âHow would they like to feel using it?â. In practice, these are important insights that guide your design work and decisions. Insufficient answers to these questions make evaluation of designs a lot harder. That is actually related to our upcoming activities.<br /><br />So, what is the objective of ideation? As described in one of my earlier blog posts, ideation helps to generate a lot of unconstrained design ideas. By a lot I mean masses, as many as possible. This process is all about the quantity of ideas, not the quality or richness in detail. Quantity is important since you never know where a bright idea might show up. So, learn to embrace the diversity. When you think that you have enough crazy ideas, start getting some order. Sort them, check for overlapping ideas, define groups and label them. In sum, put similar things together and give them a name. Then take your design principles that youâve defined with the help of your research findings, and start refining all the crazy ideas accordingly. At the end, you should have a nice set of designs that you want to see in action in order to verify them with real users. That is basically where weâre heading next, refinement and prototyping.</p> - <p align="center"><a href="http://picasaweb.google.de/lh/photo/GsK-H2GgDckPImDvkaJ6Sw?feat=embedwebsite"><img src="http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG" /></a> <br /></p> - <p>To check how that approach works in our context and what we can actually get out of it, I did a small ideation âexperimentâ for the last two weeks. The first week I spent on drawing sketches like a maniac by myself. However, through our proposal collection phase, I was too restricted in my head. It is actually hard to let things go to which one is so used to. Last week, we repeated the ideation method with a couple of colleagues with various backgrounds. We had Dev, QA, Tooling, and UX onboard. In two groups, we started brainstorming about how we would want the ideal Impress to be. For three minutes, everyone wrote adjectives attributed to the âimaginaryâ Impress on sticky notes and then we put them on the wall, and started sorting and organizing them.<br /><br />Amazingly a lot of the adjectives overlapped. At the end, we were able to define two main groups that had a lot more adjectives than others. The first group could be described as the one concerned with usability while the second group was all about positive experiences, emotions and aesthetics of the product. That happed in both groups by the way. In sum, everyone in Dev, QA, Tooling, and UX wanted the future Impress to be easy to use and âprettyâ! These are quite basic needs, arenât they? And all from people with totally different backgrounds.</p></content> - <author> - <name>Andreas Bartel</name> - <uri></uri> - </author> - <source> - <title type="html">jpmcc's shared items in Google Reader</title> - <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> - <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2009-06-18T05:00:16+00:00</updated> + <updated>2009-06-18T11:00:17+00:00</updated> </source> </entry> File [changed]: index.html Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/index.html?r1=1.2012&r2=1.2013 Delta lines: +17 -18 --------------------- --- index.html 2009-06-18 05:00:07+0000 1.2012 +++ index.html 2009-06-18 11:00:10+0000 1.2013 @@ -36,8 +36,24 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 18, 2009 05:00 AM GMT</em></p> +<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 18, 2009 11:00 AM GMT</em></p> +<h2>June 18, 2009</h2> +<h3> +<a href="http://www.mealldubh.org"; title="Meall Dubh » OpenOffice.org"> +John McCreesh</a> : +<a href="http://www.mealldubh.org/index.php/2009/06/18/ten-million/";> +Ten million</a> +</h3> +<p> +<p><img src="http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif"; alt="10,097,767" title="10,097,767" width="179" height="37" class="alignright size-full wp-image-722" />The <a href="http://marketing.openoffice.org/marketing_bouncer.html";>download counter</a> at <a href="http://marketing.openoffice.org/";>OpenOffice.org</a> is showing that downloads of OpenOffice.org from the <a href="http://download.openoffice.org/";>OpenOffice.org download page</a> have passed the ten million mark (the counter was reset when OpenOffice,org 3.1 was launched on 7th May).</p> +<p>That’s a lot of happy users!</p></p> +<p> +<em><a href="http://www.mealldubh.org/index.php/2009/06/18/ten-million/";>by John at June 18, 2009 07:04 AM GMT</a></em> +</p> +<br /> +<hr /> +<br /> <h2>June 17, 2009</h2> <h3> <a href="http://ooo-speak.blogspot.com/"; title="ooo-speak"> @@ -411,23 +427,6 @@ <br /> <hr /> <br /> -<h2>May 25, 2009</h2> -<h3> -<a href="" title="jpmcc's shared items in Google Reader"> -GullFOSS</a> : -<a href="http://blogs.sun.com/GullFOSS/entry/ideation_and_what_s_next";> -Ideation and what's next in the Renaissance Project</a> -</h3> -<p> -<p> So, the collection of design proposals and their refinement is over. Thanks to everyone who has participated and spent nights to finish either in time or a bit later. Liz will post a detailed summary about that part of the current phase later this week. With this post, I'd like to share my experience with using some ideation methods I learned in Berlin for UI brainstorming, and to give a short preview of what is about to happen in the Renaissance Project and for what reason.<br /><br />But first, letâs check what we have planned and what was in the project road map. Here is how phase two of project Renaissance was initially set up:<br /><br /><b>1.   Incorporate research data</b><br />   a.   Analyze quantitative/qualitative data to understand usage/users<br />   b.   Create personas based on the analysis<br /><b>2.   Focus on the personas' characteristics</b><br />   a.   Create scenarios for key functionalities<br />   b.   Define information architecture from the scenarios<br />   c.   Flow charts<br /><b>3.   Generate design ideas using the scenarios</b><br />   a.   Paper prototypes<br />   b.   Clickable slides<br />   c.   Dynamic prototypes<br /><br />I am still convinced that our initial plan was quite well elaborated and promising. However, looking at that now I must admit that we were not able to achieve many of the tasks that are listed here. In retrospective, we jumped right from 1a to 3b, which is of course possible but it makes many other design activities a lot harder at a later stage. Due to time and resources constraints, we spent only little time on understanding our quantitative data and almost no time on qualitative research. As a consequence, we were only partially able to generate findings that support design decisions. But still, please donât get me wrong, what we got from our research is a lot more and better than relying on pure subjective assumptions. And that is a good thing and a good start.<br /><br />However, usually you would want to start with a redesign strategy that defines your redesign scope and therefore guides any of your design research activities such as what research questions youâd like to have answers to. I would say that we were quite good at this part. But as stated above, we were not able to answer a few of our important research questions such as âWhat is important to our users and what are their goals?â, âHow do they feel using our product?â or âHow would they like to feel using it?â. In practice, these are important insights that guide your design work and decisions. Insufficient answers to these questions make evaluation of designs a lot harder. That is actually related to our upcoming activities.<br /><br />So, what is the objective of ideation? As described in one of my earlier blog posts, ideation helps to generate a lot of unconstrained design ideas. By a lot I mean masses, as many as possible. This process is all about the quantity of ideas, not the quality or richness in detail. Quantity is important since you never know where a bright idea might show up. So, learn to embrace the diversity. When you think that you have enough crazy ideas, start getting some order. Sort them, check for overlapping ideas, define groups and label them. In sum, put similar things together and give them a name. Then take your design principles that youâve defined with the help of your research findings, and start refining all the crazy ideas accordingly. At the end, you should have a nice set of designs that you want to see in action in order to verify them with real users. That is basically where weâre heading next, refinement and prototyping.</p> - <p align="center"><a href="http://picasaweb.google.de/lh/photo/GsK-H2GgDckPImDvkaJ6Sw?feat=embedwebsite";><img src="http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG"; /></a> <br /></p> - <p>To check how that approach works in our context and what we can actually get out of it, I did a small ideation âexperimentâ for the last two weeks. The first week I spent on drawing sketches like a maniac by myself. However, through our proposal collection phase, I was too restricted in my head. It is actually hard to let things go to which one is so used to. Last week, we repeated the ideation method with a couple of colleagues with various backgrounds. We had Dev, QA, Tooling, and UX onboard. In two groups, we started brainstorming about how we would want the ideal Impress to be. For three minutes, everyone wrote adjectives attributed to the âimaginaryâ Impress on sticky notes and then we put them on the wall, and started sorting and organizing them.<br /><br />Amazingly a lot of the adjectives overlapped. At the end, we were able to define two main groups that had a lot more adjectives than others. The first group could be described as the one concerned with usability while the second group was all about positive experiences, emotions and aesthetics of the product. That happed in both groups by the way. In sum, everyone in Dev, QA, Tooling, and UX wanted the future Impress to be easy to use and âprettyâ! These are quite basic needs, arenât they? And all from people with totally different backgrounds.</p></p> -<p> -<em><a href="http://blogs.sun.com/GullFOSS/entry/ideation_and_what_s_next";>by Andreas Bartel at May 25, 2009 07:56 PM GMT</a></em> -</p> -<br /> -<hr /> -<br /> <a id="disclaimer" name="disclaimer"></a> <p><em>Disclaimer: all views expressed on this page are those of the individual contributors, and may not reflect the views of the File [changed]: opml.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/opml.xml?r1=1.2005&r2=1.2006 Delta lines: +1 -1 ------------------- --- opml.xml 2009-06-18 05:00:08+0000 1.2005 +++ opml.xml 2009-06-18 11:00:10+0000 1.2006 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Marketing Planet</title> - <dateModified>Thu, 18 Jun 2009 05:00:26 +0000</dateModified> + <dateModified>Thu, 18 Jun 2009 11:00:28 +0000</dateModified> <ownerName>Marketing Project</ownerName> <ownerEmail>[email protected]</ownerEmail> </head> File [changed]: rss10.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss10.xml?r1=1.770&r2=1.771 Delta lines: +8 -10 -------------------- --- rss10.xml 2009-06-18 05:00:08+0000 1.770 +++ rss10.xml 2009-06-18 11:00:10+0000 1.771 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="http://www.mealldubh.org/?p=720"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-3131720890077326755" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4887643299605448632.post-7675159138884344780" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4887643299605448632.post-6793350226421939452" /> @@ -32,11 +33,17 @@ <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-3644086454305576909" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4649039904546083564.post-4201241808110432115" /> <rdf:li rdf:resource="tag:google.com,2005:reader/item/78154ce7426b0c6a" /> - <rdf:li rdf:resource="tag:google.com,2005:reader/item/d1a38e6f8a4c00f9" /> </rdf:Seq> </items> </channel> +<item rdf:about="http://www.mealldubh.org/?p=720";> + <title>John McCreesh: Ten million</title> + <link>http://www.mealldubh.org/index.php/2009/06/18/ten-million/</link> + <content:encoded><p><img src="http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif" alt="10,097,767" title="10,097,767" width="179" height="37" class="alignright size-full wp-image-722" />The <a href="http://marketing.openoffice.org/marketing_bouncer.html">download counter</a> at <a href="http://marketing.openoffice.org/">OpenOffice.org</a> is showing that downloads of OpenOffice.org from the <a href="http://download.openoffice.org/">OpenOffice.org download page</a> have passed the ten million mark (the counter was reset when OpenOffice,org 3.1 was launched on 7th May).</p> +<p>That&#8217;s a lot of happy users!</p></content:encoded> + <dc:date>2009-06-18T07:04:39+00:00</dc:date> +</item> <item rdf:about="tag:blogger.com,1999:blog-4649039904546083564.post-3131720890077326755"> <title>Louis Suarez-Potts: Eccles cake in Shoreditch</title> <link>http://ooo-speak.blogspot.com/2009/06/eccles-cake-in-shoreditch.html</link> @@ -257,14 +264,5 @@ <dc:date>2009-05-27T11:12:38+00:00</dc:date> <dc:creator>frankl</dc:creator> </item> -<item rdf:about="tag:google.com,2005:reader/item/d1a38e6f8a4c00f9"> - <title>GullFOSS: Ideation and what's next in the Renaissance Project</title> - <link>http://blogs.sun.com/GullFOSS/entry/ideation_and_what_s_next</link> - <content:encoded><p> So, the collection of design proposals and their refinement is over. Thanks to everyone who has participated and spent nights to finish either in time or a bit later. Liz will post a detailed summary about that part of the current phase later this week. With this post, I'd like to share my experience with using some ideation methods I learned in Berlin for UI brainstorming, and to give a short preview of what is about to happen in the Renaissance Project and for what reason.<br /><br />But first, letâs check what we have planned and what was in the project road map. Here is how phase two of project Renaissance was initially set up:<br /><br /><b>1.   Incorporate research data</b><br />   a.   Analyze quantitative/qualitative data to understand usage/users<br />   b.   Create personas based on the analysis<br /><b>2.   Focus on the personas' characteristics</b><br />   a.   Create scenarios for key functionalities<br />   b.   Define information architecture from the scenarios<br />   c.   Flow charts<br /><b>3.   Generate design ideas using the scenarios</b><br />   a.   Paper prototypes<br />   b.   Clickable slides<br />   c.   Dynamic prototypes<br /><br />I am still convinced that our initial plan was quite well elaborated and promising. However, looking at that now I must admit that we were not able to achieve many of the tasks that are listed here. In retrospective, we jumped right from 1a to 3b, which is of course possible but it makes many other design activities a lot harder at a later stage. Due to time and resources constraints, we spent only little time on understanding our quantitative data and almost no time on qualitative research. As a consequence, we were only partially able to generate findings that support design decisions. But still, please donât get me wrong, what we got from our research is a lot more and better than relying on pure subjective assumptions. And that is a good thing and a good start.<br /><br />However, usually you would want to start with a redesign strategy that defines your redesign scope and therefore guides any of your design research activities such as what research questions youâd like to have answers to. I would say that we were quite good at this part. But as stated above, we were not able to answer a few of our important research questions such as âWhat is important to our users and what are their goals?â, âHow do they feel using our product?â or âHow would they like to feel using it?â. In practice, these are important insights that guide your design work and decisions. Insufficient answers to these questions make evaluation of designs a lot harder. That is actually related to our upcoming activities.<br /><br />So, what is the objective of ideation? As described in one of my earlier blog posts, ideation helps to generate a lot of unconstrained design ideas. By a lot I mean masses, as many as possible. This process is all about the quantity of ideas, not the quality or richness in detail. Quantity is important since you never know where a bright idea might show up. So, learn to embrace the diversity. When you think that you have enough crazy ideas, start getting some order. Sort them, check for overlapping ideas, define groups and label them. In sum, put similar things together and give them a name. Then take your design principles that youâve defined with the help of your research findings, and start refining all the crazy ideas accordingly. At the end, you should have a nice set of designs that you want to see in action in order to verify them with real users. That is basically where weâre heading next, refinement and prototyping.</p> - <p align="center"><a href="http://picasaweb.google.de/lh/photo/GsK-H2GgDckPImDvkaJ6Sw?feat=embedwebsite"><img src="http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG" /></a> <br /></p> - <p>To check how that approach works in our context and what we can actually get out of it, I did a small ideation âexperimentâ for the last two weeks. The first week I spent on drawing sketches like a maniac by myself. However, through our proposal collection phase, I was too restricted in my head. It is actually hard to let things go to which one is so used to. Last week, we repeated the ideation method with a couple of colleagues with various backgrounds. We had Dev, QA, Tooling, and UX onboard. In two groups, we started brainstorming about how we would want the ideal Impress to be. For three minutes, everyone wrote adjectives attributed to the âimaginaryâ Impress on sticky notes and then we put them on the wall, and started sorting and organizing them.<br /><br />Amazingly a lot of the adjectives overlapped. At the end, we were able to define two main groups that had a lot more adjectives than others. The first group could be described as the one concerned with usability while the second group was all about positive experiences, emotions and aesthetics of the product. That happed in both groups by the way. In sum, everyone in Dev, QA, Tooling, and UX wanted the future Impress to be easy to use and âprettyâ! These are quite basic needs, arenât they? And all from people with totally different backgrounds.</p></content:encoded> - <dc:date>2009-05-25T19:56:33+00:00</dc:date> - <dc:creator>Andreas Bartel</dc:creator> -</item> </rdf:RDF> File [changed]: rss20.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss20.xml?r1=1.770&r2=1.771 Delta lines: +8 -9 ------------------- --- rss20.xml 2009-06-18 05:00:09+0000 1.770 +++ rss20.xml 2009-06-18 11:00:13+0000 1.771 @@ -8,6 +8,14 @@ <description>Marketing Planet - http://marketing.openoffice.org/planet/</description> <item> + <title>John McCreesh: Ten million</title> + <guid>http://www.mealldubh.org/?p=720</guid> + <link>http://www.mealldubh.org/index.php/2009/06/18/ten-million/</link> + <description><p><img src="http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif" alt="10,097,767" title="10,097,767" width="179" height="37" class="alignright size-full wp-image-722" />The <a href="http://marketing.openoffice.org/marketing_bouncer.html">download counter</a> at <a href="http://marketing.openoffice.org/">OpenOffice.org</a> is showing that downloads of OpenOffice.org from the <a href="http://download.openoffice.org/">OpenOffice.org download page</a> have passed the ten million mark (the counter was reset when OpenOffice,org 3.1 was launched on 7th May).</p> +<p>That&#8217;s a lot of happy users!</p></description> + <pubDate>Thu, 18 Jun 2009 07:04:39 +0000</pubDate> +</item> +<item> <title>Louis Suarez-Potts: Eccles cake in Shoreditch</title> <guid>tag:blogger.com,1999:blog-4649039904546083564.post-3131720890077326755</guid> <link>http://ooo-speak.blogspot.com/2009/06/eccles-cake-in-shoreditch.html</link> @@ -241,15 +249,6 @@ <p>Frank</p></description> <pubDate>Wed, 27 May 2009 11:12:38 +0000</pubDate> </item> -<item> - <title>GullFOSS: Ideation and what's next in the Renaissance Project</title> - <guid>tag:google.com,2005:reader/item/d1a38e6f8a4c00f9</guid> - <link>http://blogs.sun.com/GullFOSS/entry/ideation_and_what_s_next</link> - <description><p> So, the collection of design proposals and their refinement is over. Thanks to everyone who has participated and spent nights to finish either in time or a bit later. Liz will post a detailed summary about that part of the current phase later this week. With this post, I'd like to share my experience with using some ideation methods I learned in Berlin for UI brainstorming, and to give a short preview of what is about to happen in the Renaissance Project and for what reason.<br /><br />But first, letâs check what we have planned and what was in the project road map. Here is how phase two of project Renaissance was initially set up:<br /><br /><b>1.   Incorporate research data</b><br />   a.   Analyze quantitative/qualitative data to understand usage/users<br />   b.   Create personas based on the analysis<br /><b>2.   Focus on the personas' characteristics</b><br />   a.   Create scenarios for key functionalities<br />   b.   Define information architecture from the scenarios<br />   c.   Flow charts<br /><b>3.   Generate design ideas using the scenarios</b><br />   a.   Paper prototypes<br />   b.   Clickable slides<br />   c.   Dynamic prototypes<br /><br />I am still convinced that our initial plan was quite well elaborated and promising. However, looking at that now I must admit that we were not able to achieve many of the tasks that are listed here. In retrospective, we jumped right from 1a to 3b, which is of course possible but it makes many other design activities a lot harder at a later stage. Due to time and resources constraints, we spent only little time on understanding our quantitative data and almost no time on qualitative research. As a consequence, we were only partially able to generate findings that support design decisions. But still, please donât get me wrong, what we got from our research is a lot more and better than relying on pure subjective assumptions. And that is a good thing and a good start.<br /><br />However, usually you would want to start with a redesign strategy that defines your redesign scope and therefore guides any of your design research activities such as what research questions youâd like to have answers to. I would say that we were quite good at this part. But as stated above, we were not able to answer a few of our important research questions such as âWhat is important to our users and what are their goals?â, âHow do they feel using our product?â or âHow would they like to feel using it?â. In practice, these are important insights that guide your design work and decisions. Insufficient answers to these questions make evaluation of designs a lot harder. That is actually related to our upcoming activities.<br /><br />So, what is the objective of ideation? As described in one of my earlier blog posts, ideation helps to generate a lot of unconstrained design ideas. By a lot I mean masses, as many as possible. This process is all about the quantity of ideas, not the quality or richness in detail. Quantity is important since you never know where a bright idea might show up. So, learn to embrace the diversity. When you think that you have enough crazy ideas, start getting some order. Sort them, check for overlapping ideas, define groups and label them. In sum, put similar things together and give them a name. Then take your design principles that youâve defined with the help of your research findings, and start refining all the crazy ideas accordingly. At the end, you should have a nice set of designs that you want to see in action in order to verify them with real users. That is basically where weâre heading next, refinement and prototyping.</p> - <p align="center"><a href="http://picasaweb.google.de/lh/photo/GsK-H2GgDckPImDvkaJ6Sw?feat=embedwebsite"><img src="http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG" /></a> <br /></p> - <p>To check how that approach works in our context and what we can actually get out of it, I did a small ideation âexperimentâ for the last two weeks. The first week I spent on drawing sketches like a maniac by myself. However, through our proposal collection phase, I was too restricted in my head. It is actually hard to let things go to which one is so used to. Last week, we repeated the ideation method with a couple of colleagues with various backgrounds. We had Dev, QA, Tooling, and UX onboard. In two groups, we started brainstorming about how we would want the ideal Impress to be. For three minutes, everyone wrote adjectives attributed to the âimaginaryâ Impress on sticky notes and then we put them on the wall, and started sorting and organizing them.<br /><br />Amazingly a lot of the adjectives overlapped. At the end, we were able to define two main groups that had a lot more adjectives than others. The first group could be described as the one concerned with usability while the second group was all about positive experiences, emotions and aesthetics of the product. That happed in both groups by the way. In sum, everyone in Dev, QA, Tooling, and UX wanted the future Impress to be easy to use and âprettyâ! These are quite basic needs, arenât they? And all from people with totally different backgrounds.</p></description> - <pubDate>Mon, 25 May 2009 19:56:33 +0000</pubDate> -</item> </channel> </rss> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
![http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif"](http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif"){kind=link}
![http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG"](https://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG"){kind=link}
![http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif"](http://www.mealldubh.org/wp-content/uploads/2009/06/downloads.gif"){kind=link}
![http://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG"](https://lh5.ggpht.com/_1V3VpP3YHN0/ShrsxLUS46I/AAAAAAAABKs/Worq-1_xaaM/s400/IMG_1086.JPG"){kind=link}