IFD:HumanCenteredDesignResearch SoSe13/team2 generalPresentation: Difference between revisions

← Older edit

IFD:HumanCenteredDesignResearch SoSe13/team2 generalPresentation (view source)

Revision as of 11:37, 12 August 2013

8,104 bytes added , 12 August 2013

no edit summary

Lisa.guth

127

edits

@@ Line 3: / Line 3: @@
 During the course Human Centered Design we conducted an exploratory user study to find out about the acquaintance of Creative Commons, potential pitfalls and caveats of its usage.
+====Preparation of the interviews====
+We initially formulated our design goal based on the question "How can we raise the awareness of creative content creators for the CC licenses?".
+Some of our early ideas consisted of a rough sketch for an advertising campaign directed towards creators, and a software solution which should be incorporated in the workflow of someone publishing his or her own content.
+Central questions were:
+* "Are users aware of general copyright issues during the process of publishing content on the web?"
+* "Do these users take any measures to attribute their work before they publish it?"
 Our probands were selected from students of the Bauhaus University Weimar from courses of studies ranging from Media Arts & Design over Visual Communication to Product Design aged between 20 and 28 years.
 All of them were selected for their unawareness of local copyright jurisdiction and licensing models (e.g. CC).
 The short interviews took place in their personal environment during the activity of publishing original content on their personal (micro)blogging platforms. In advance our group defined the basic premise of identifying the users motivation of publishing their works in the web.
 After each interview we presented the participants with the concept of Creative Commons and introduced them to the website and the function of choosing their own fitting license.
+In advance we formulated open questions:
+* "How do you upload pictures from your last project to your tumblr?"
+* "Can you show me which information you attribute to your uploaded content? Do you provide contact and copyright information somewhere?"
 One participant gladly allowed us to publish the complete interview which you can download here: (German language)
@@ Line 57: / Line 71: @@
 ==Process of development==
-During the process of evaluating our first prototype we received a short message from one of our participants who complained
-about a change on her blog platform which messed up the layout of her license tag and rendered it functionally broken.
+During the process of evaluating our first prototype we received a short message from one of our participants who complained about a change on her blog platform which messed up the layout of her license tag and rendered it functionally broken.
-[sms bild]
+[[Image:hcd_g2_nachricht.jpg|200px|thumb|Feedback from a participant - Translation: "Help, I switched to a new template and it doesn't show the (CC) icon anymore on my blog :(. I found out one can fiddle with the html, but I'm not able to do that ;)"]]
-This call for help gave us the impulse to focus our attention more towards the usability of our proposed license manager
+[[Image:hcd_g2_process.jpg|200px|thumb|Development]]
-application, which will aid the non-tech-savvy user in the process of correctly tagging his works with the approriate license.
-Our group came to the conclusion to roll back our initial development from behind and decided to approach the problem the
+This call for help gave us the impulse to focus our attention more towards the usability of our proposed license manager application, which will aid the non-tech-savvy user in the process of correctly tagging his works with the approriate license. Our group came to the conclusion to roll back our initial development from behind and decided to approach the problem the opposite way around. We assume that the typical user of our chosen target group decrees an intrinsic motivation to tag his work with appropriate copyright information.
-opposite way around. We assume that the typical user of our chosen target group decrees an intrinsic motivation to tag his
-work with appropriate copyright information.
+==Implementations==
+We propose a small browser addon which either asks the user of his sharing habits or analyses the history in a way to identify potential users who already publish their work in the web.
+If the user is a candidate the software would display a teasing comment if he knows about Creative Commons after which he can choose to be never bothered again or get a brief introduction about it. As soon as the software is aware that the user knows about CC it would provide an unobstrusive button on the navigation toolbar acting as a small license selector and manager.
-[development bild]
 ==Revised idea==
-In our new proposed solution we would offer the user a tiny license manager interface which would initially provide a default
-license corresponding to "all rights reserved". We deliberately chose an empty looking tag icon similar to those provided by
+For our final idea we decided to abolish the concept of interrupting the user in his workflow. (Let's be honest, even if we try to be as non-bothersome as we can, it will still be an unwanted interruption, which usually would result in negative feelings. This would not be a good starting point to educate someone)
-Creative Commons, and would arrange those in view to spark the users interest in the CC licenses just because of their look.
+We condensed the workflow of the license manager down to 3 steps.
+* Stage 1: Which media to publish (pictures, audio, video)
+* Stage 2: Where (on which platforms) to publish it.
+* Stage 3: Which license or what kind of copyright attribution
-As soon as a license has been chosen the software would provide an option for the most common blogging platforms (tumblr,
+Stage 2 would adjust possible options according to the media type selected in stage 1. I.e. it does not make sense to upload images or video to a platform like soundcloud.
+After the user has made a selection at stage 3 the software should warn him if one or more of his chosen combinations of platforms and license collide with potential clauses in the terms of service of a platform.
-soup.io, wordpress, facebook, google+, etc). In case the user choses a platform whose own license agreements for publishing
+[[Image:Hcd_android_share.png|200px|thumb|Possible integration in the "share function" on mobile platforms]]
-material collide with a Creative Commons license it warns the user about arising difficulties concerning his rights. Through
+We deliberately chose a screen format for our application which can be easily adapted to mobile platforms (smartphones, tablets). We imagine that our solution is not only suitable for desktop use in times where more and more people handle their tasks using mobile devices.
-this methology we achieve our goal of creating interest in the CC model and are able to educate the user during his usual
+During our midterm presentation one of our mentors mentioned that we should focus on identifying the pain of users of our target group and try to ease it. After a reassessment of our conducted interviews we made the assumption, that creators struggle with the proper attribution of a license or their copyright information of their published work. At this point in time, services like facebook or tumblr do not offer their users to select and attribute a CC license to content they upload on their platform. In case the user wants to attribute basic copyright information or a CC license, he would need to manually add this information (i.e. by watermarking images, adding an intro or outro to a video, or add meta information like an ID3 tag for mp3 files). This process can be rather time consuming, especially if different attributions have to be made for different platforms (i.e. watermarking an image for tumblr, adding a caption containing the information on facebook).
+A software which can aid the user in this process and save his time should create enough motivation to download and install such a solution.
+Our chosen tactic to educate the user about the existence of the CC licenses and possible benefits resulting from their usage is to create curiosity for them. We plan to subversively communicate to the user in the process of the license selection stage. The default option of "(c) All rights reserved" would be visible at the top of the interface represented by an image similar to those tags known from the CC website. This icon is deliberately designed to look rather empty, especially in contrast to the CC icons. The visual contrast should communicate to the user that waiving some rights of his work adds benefits to it aswell.
+[[Image:hcd_c_all_rights_reserved.png|200px|thumb|The "all rights reserved" tag]]
-workflow.
-During the course we want to conduct a quantitive user study if there exists a particular interest in such a software. At the moment we concentrate on developing a testable prototype and invited our previous participants to take part in such a study.
+==Final work - functional overview==
+[[File:hcd_g2_funktionsübersicht.jpg|700px|Übersicht aller Funktionen]]
+===Revised/ final work (4 th) PaperMockUp===
+<gallery>
+File:hcd_g2_papermockup4_1.png|start screen
+File:hcd_g2_papermockup4_13.png|start screen + help
+File:hcd_g2_papermockup4_2.png|Choose your file
+File:hcd_g2_papermockup4_3.png|Choose your license
+File:hcd_g2_papermockup4_14.png|Choose your license + help
+File:hcd_g2_papermockup4_11.png|Choose your last license
+File:hcd_g2_papermockup4_4.png|Choose your platforms
+File:hcd_g2_papermockup4_5.png|warnings
+File:hcd_g2_papermockup4_7.png|Upload
+File:hcd_g2_papermockup4_8.png|succsessful Upload
+File:hcd_g2_papermockup4_6.png|Settings
+File:hcd_g2_papermockup4_9.png|History abstract
+File:hcd_g2_papermockup4_12.png|History abstract + help
+File:hcd_g2_papermockup4_10.png|History detailed
+</gallery>
 ==Scenario==
@@ Line 105: / Line 142: @@
 Bei Anmeldung in einem Blog, bei dem die Inhalte noch nicht unter einer Lizenz der CC stehen, blinkt der CC-Button in der Symbolleiste auf.
-==Implementations==
+===Szenario 2===
-We propose a small browser addon which either asks the user of his sharing habits or analyses the history in a way to identify potential users who already publish their work in the web.
+Ich bin Bloggerin und teile Bilder in Beruf und Freizeit mit anderen Nutzern. Ich bin Studentin der Gestaltung und lade regelmäßig Bilder auf mehreren Platformen hoch, um meine Werke einer breiteren Öffentlichkeit zugänglich zu machen – d.h. Mitstudenten, Agenturen und anderen Interessenten. Ich würde gern den Aspekt der Professionalität verstärken, indem meine Bilder durch einen juristischen Lizenztext abgesichert werden, der leicht zugänglich ist. Dies ermöglicht mir und anderen Nutzern ein unkompliziertes weiterverwenden der Bilder ohne ständiges Nachfragen, da gestalterische Arbeiten im Netz prinzipiell unter dem Urheberrecht stehen.
-If the user is a candidate the software would display a teasing comment if he knows about Creative Commons after which he can choose to be never bothered again or get a brief introduction about it. As soon as the software is aware that the user knows about CC it would provide an unobstrusive button on the navigation toolbar acting as a small license selector and manager.
+Das Konzept der Creative Commons ist mir bekannt, daher öffne ich den CC-Publisher, der in der Taskleiste des Browsers erscheint. Dieser ist in einem Format gestaltet, das es erlaubt, den Publisher auch als App für ein Smartphone zu nutzen.
+Zuerst habe ich die Wahl zwischen dem direkten Upload und der History. Ich öffne diese und erhalte einen Überblick zu meinen veröffentlichten Dateien mit all ihren Details wie Dateiname, Dateiart, Bildgröße, verwendete Lizenz, Datum des Uploads und Plattformen, auf denen das Bild hochgeladen wurde. Ein Pfeil-Button bringt mich zu weiterführenden Schritten. Ich gehe zurück zur Ausgangsansicht.
+Nun möchte ich eine neue Bildserie hochladen und gehe auf 'Upload' im Publisher, ich wähle die gewünschten Dateien aus. Im zweiten Schritt des Uploads habe ich die Möglichkeit, mir eine individuelle Lizenz zusammenzustellen.
+Ich kann die zuletzt genutzte Lizenz verwenden oder aber aus den verschiedenen Kombinationen von Namensnennung, Weitergabe unter gleichen Bedingungen, nicht kommerziell und keine Bearbeitung wählen. Hilfestellung zur Lizenzauswahl erhalte ich über den Fragezeichen-Button.
+Im finalen Schritt wähle ich noch die Plattformen aus, auf denen die Bildserie veröffentlicht werden soll. Als ich Facebook ankreuze, erscheint ein Hinweis-Fenster. Dieses besagt, das Facebook seine eigenen Lizenzbestimmungen hat, die ich auf der Website des sozialen Netzwerks nachlesen kann. Ich entscheide mich gegen das Hochladen meiner Bilder auf Facebook, demnach werden diese nur auf meinem Blog veröffentlicht. Bevor ich den Upload-Button betätige, gehe ich zu dem Menü der Settings, um weitere Einstellungen an meinen Bildern vorzunehmen, ich befinde mich in einer Art 'Profi-Modus' des Programms. Ich wähle die Position des Lizenzlogos im Bild und die Auflösung. Das eigene Logo kann ebenfalls eingesetzt werden. Den Uploadfortschritt kann ich schließlich über einen Balken mitverfolgen und erhalte nach erfolgreichem Upload eine Nachricht.
 <gallery>
@@ Line 131: / Line 172: @@
 File:hcd_g2_paper6.png|Remember CC
 </gallery>
+===Revised (2nd) MockUp===
+<gallery>
+File:hcd_proto2_process1.jpg|
+File:hcd_proto2_process2.jpg|
+File:hcd_proto2_3.jpg|
+File:hcd_proto2_2.jpg|
+File:hcd_proto2_1.jpg|
+File:hcd_proto2_4.jpg|
+</gallery>
+===Revised (3 rd) PaperMockUp===
+<gallery>
+File:hcd_g2_papermockup3_1.png|start screen
+File:hcd_g2_papermockup3_4.png|Choose your file
+File:hcd_g2_papermockup3_2.png|Choose your license
+File:hcd_g2_papermockup3_3.png|Choose your platforms
+</gallery>
+==User study==
+During the course we conducted a quantitive user study to verify our assumptions if there is a real need for creative users to attribute their work and publish on several online platforms.
+[[Media:Poll_HCD.pdf]]
+==Poster - summaery==
+[[Image:hcd_g2_plakat.jpg|200px]]
+==Our conclusion==
+We can say that we were introduced to a robust set of tools to tackle different problems arising during the human centered design process. The course offered us a good opportunity to experiment with different approaches of designing a software solution. We underestimated the huge effort we had to invest into our final prototype. The component of abolishing ideas during different iterations in the process was a painful but educative experience. Several participants of our user studies showed great interest in our proposed solution, so we would like to actually implement our idea and test it under real life conditions.