Archiv für Kategorie Awareness
Auf dem Blog e-gineer.com hat Nathan Wallace schon mehrfach über Microblogging in Unternehmen berichtet. Gestern stellte er einen ausführlichen Bericht zum Jitter-System bei Jassen-Cilaq Australia und New Zealand bereit. Sehr interessant zu lesen.
Vor allem fand ich interessant, dass das Microblogging mit einer “Facebook-like”-Social-Networking-Plattform verknüpft wurde.
Doch ich frage mich, ob es wirklich um Microblogging im Sinne von “Ich sag auch wie ich mich gerade fühle” geht oder mehr um das Mitteilen von Neuigkeiten / Aufmerksammachen auf Neuigkeiten – also eher Awareness-Feeds in Blog-Form. Letzteres ist meiner Meinung nach sehr sinnvoll in Unternehmen – Mitteilungen über neue Projekte, Schulungen, die man besucht hat, Kundenkontakte, die man gehabt hat/haben wird.
Der Begriff “Microblogging ala Twitter” für den Unternehmenseinsatz ist meiner Meinung nach negativ belegt. Ausserdem erfinden wir damit einen neuen Begriff für die Awareness-Feeds, die es auf Social-Networking-Plattformen eh schon gibt.
Wir werden übrigens bis Jahresende eine “solche Plattform” (SNS mit Awareness-Feeds) für unsere Universität bereitstellen. Sowohl für die Kommunikation nach innen (zu Kollegen) als auch nach aussen (was für tolle Forschung wir machen ;-)). Da ist glaube ich großes Potential.
Finally pictures from day 0 and day 1 start to appear on flickr – have a look.
And then to day 2 which started with paper session – as usual here some comments on the ones I found worth commenting ;-)
- “‘… and do it the usual way’: fostering awareness of work conventions in document-mediated collaboration”, Federico Cabitza, Carla Simone: “without conventions work could be hardly be done by practitioners (and be hardly understood by researchers)” – goal: supporting conventions through a “learning device”, need to understand their nature to create a common ground, clarifying ambiguities – conventions vs. business rules (spring from practice, not necessary a best practice, generated locally from the bottom, to solve local problems) – this seems to be quite important! use to support awareness (browsing awareness, alerting/reminding awareness, provisionality awareness, inconsistency awareness, amending awareness, accounting awareness, enabling awareness); “conventions are about action you are expected to do”, “conventions are about interpretation this means that”, conventions and awareness are expressed in terms of condition -> effects; further developed (visualization of awareness) in the WOAD approach … comparable to the approach of expectation awareness (by Prinz et al.) – the paper is surely worth reading in more detail (at least for me ;-)) – interesting idea to use conventions to support awareness event filtering and visualization …
Other blog postings on this talk: ECOSpace Blog
- “A safe space to vent: Conciliation and Conflict in Distributed Teams”, L. Watts: conflict as potentially destructive (e.g. storing bad feelings for future interactions) vs. conflict as a creative process; conversations through CMC technologies are prone to conflict escalations, polarisation and entrenchment (Thomson & Nadler 2002) but also can encourage disclosure and reduce uncertainty! very good analysis of recent work on conflict in CMC
- “Semi-Synchronous Conflict Detection and Resolution in Asynchronous Software Development”, Prasun Dewan and Rajesh Hegde: Problem in software development: adding people to the team does not add to productivity in the same way; one reason for this: conflicts; not adequately addressed by versioning systems; solving problem: change virtual environment by new conflict management model (no synchronous pair programming!, but asynchronous work); they built a new systeme CollabVS = Visual Studio + Semi Synchronous Conflict Management and evaluated it; the core idea is somehow providing awareness by automatically detecting concurrent activities (editing code files that are somehow related) and visualizing the information.
One comment in the discussion: “Great and I would like to have it” ;-)
Other blog postings on this talk: ECOSpace Blog
After the first keynote the paper program started. Just some thoughts on these:
- “What Did I Miss? – Visualizing the Past through Video Traces” – A work from Saul Greenbergs group on awareness in video media spaces – They presented the Timeline System which tries to provide an overview of a video stream while at the same time addressing privacy issues. See videos of Saul Greenbergs group.
- “Social bookmarking and exploratory search”, David R. Millen (IBM): A very nice report from the Dogear project at IBM – an intranet social bookmarking service. They presented a lot of material (both numbers and quotes) from the internal usage of Dogear. An interesting information was also the list of upcoming papers on Dogear – One which seems to be especially interesting is on “Expertise Search” (using social bookmarking) by Shami, Ehrlich and Millen – Sadly, there was no reference to where this paper will show up – sometimes in 2008. Another interesting idea briefly mentioned in the discussion: Use Dogear to generate personal tag clouds to be printed on the name badges for conferences.
- “Instrumental action: the timely exchange of implements during surgical operations”, Marcus Sanchez Svensson: A piece of work looking at how coordination around objects happens in the operating theatre. Nice examples and some conceptual reflections, but little new insights (that inform design) – as it was mentioned during discussion …
- “Designing Family Photo Displays”, A. Taylor et al.: Thinking about the display of photos, what do they do, how do they achieve their “goal” (end up doing certain sorts of things); some nice ideas (informed by ethnographic research) on how to design family photo display.
- “The Awareness Network: Should I display my actions to whom? And, whose actions should I monitor?”, C. de Souza: Work about filtering incoming and outgoing awareness events – which they call “awareness network” – the sum of incoming and outgoing links. The basis of the work are observations of two software development teams – analyzed using grounded theory techniques – which more or less shows some dependencies in the teams (depending on the system developed – modular vs. non-modular) – which affected the awareness network (no big surprise …).