Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C0146C481 for ; Fri, 8 Jun 2012 13:54:38 +0000 (UTC) Received: (qmail 53313 invoked by uid 500); 8 Jun 2012 13:54:38 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 53226 invoked by uid 500); 8 Jun 2012 13:54:38 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 53215 invoked by uid 99); 8 Jun 2012 13:54:38 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 13:54:38 +0000 Received: from localhost (HELO mail-vb0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2012 13:54:37 +0000 Received: by vbbfr13 with SMTP id fr13so1156993vbb.6 for ; Fri, 08 Jun 2012 06:54:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.97.230 with SMTP id ed6mr5375229vdb.65.1339163676632; Fri, 08 Jun 2012 06:54:36 -0700 (PDT) Received: by 10.220.190.13 with HTTP; Fri, 8 Jun 2012 06:54:36 -0700 (PDT) Date: Fri, 8 Jun 2012 09:54:36 -0400 Message-ID: Subject: [Marketing][UX] Who wants to do a Content Experiment? From: Rob Weir To: ooo-dev@incubator.apache.org, ooo-marketing@incubator.apache.org Content-Type: text/plain; charset=UTF-8 A "Content Experiment" is when we create several version of the same web page and test it with users to see which version performs best. Google Analystics has a feature where it can run such experiments for us automatically, tracking all the statistics for us, and telling us which version of a page gives the optimal results. One particular scenario I think we could really improve on is what I call the "Windows Unrecognized ODF File" scenario. It goes like this; 1. The user is a Windows user that does not have OpenOffice installed, or any other application that understands ODF files. So no LibreOffice, no AbiWord, not even Office 2007 SP2 or Office 2010 (both of which support ODF). 2. User receives an ODF document, from email, from the web, or some other means. 3. User tries to launch the ODF file. 4. Because the user does not have an ODF application installed, Windows gives the user a dialog box with the following --------------------------------------- Windows cannot open this file: foo.odt To open this file, Windows needs to know what program created it. Windows can go online to look it up automatically, or you can manually select from a list of programs on your computer. What do you want to do? -- Use the Web service to find the appropriate program -- Select the program from a list --------------------------------------- 5. User picks the first option (Use the Web service) and is brought to the following page: http://shell.windows.com/fileassoc/0409/xml/redir.asp?Ext=odt 6. User selects OpenOffice and are brought to this page: http://www.openoffice.org/download/index.html Note that we have no control up to this point. The above steps are all user interactions with Microsoft Windows and Microsoft's website. The only thing we really control is the contents of the destination website (step 6). Technically, it is easily to make this redirect to a different page just for users who come from the Microsoft web service. So we can easily show a customized page that better targets this scenario. Note that the user reaching this point probably knows nothing about ODF or about OpenOffice. They are just plopped into this download page with almost no context. For example, there is zero mention of ODF on this page. Maybe this is why only 30% of the users who reach this page from the web service actually downloaded OpenOffice. This is much lower than visitors who reach our download page from other means. Can we improve on this? Note: we get more referrals from this Windows web service than we get referrals from any other website. So helping these users quickly understand what their options are and why they might want to download/install OpenOffice is quite important. So here is the experiment. Let's try to get a handful of alternate destination pages that speak to this scenario and provide the information that would be most useful to this kind of user. It could be a modified version of the download page. It could be a new intermediate landing page that provides context and then links to the existing download page. Whatever you think would work best. We can then run the experiment, say for a month, letting Google randomly present users with the various alternate pages and measure what the download %'s are for each version. The winner will gain eternal fame and glory, maybe even a blog post. I'm willing to do the technical work on setting up the experiment and prepping the website to support it. What I need are volunteers to come up with alternate landing pages for this scenario, ones that we can include in the experiment. Questions? -Rob