Wemake wrapped up Opencare workshop at Domus Academy

Greetings all,

 

Here is a final about around the earlier shared story of Wemake joinig forces with Domus Academy to develop stories and products for Opencare.  The end of the Rome Makerfaire marked the closure of the workshop lead by WeMake, in order to help interaction design students of Domus Academy start projects ideas and prototypes for Opencare.

 

The students have been documenting their projects on Edgeryders during the workshop. As the process developed, the students were researching ideas that either touch a personal story that they are part of, or a public cause that they contribute to or care about.  The initial project proposals varied between interesting, feasible (or wonderful to have if technology supports it in 50 years ;), and very helpful.  The common theme was that students managed to grasp the concept of opencare, and what does it mean to develop projects under the notion of care. Below is a sample of students suggestions which they already documented on Edgeryders (but not everyone mentioned their releavance to Domus workshop ;):

 

Group waves, was interested in a future technology that can help create a bubble space for sound treatement between mothers and their kids,  they were also excited about creating a new solution for active socializing between people with hearing/speaking disabilities, they also had ideas around creating smart stick for visiually impaired, a tool to help autistic kids coope with the surrounding, a device to help indoor noice cancelling, and a device that helps Parkinson patients track their tremors, https://edgeryders.eu/en/helping-someone-with-parkinsons-part-1all this before they finally decided to develop a bracelet for Alzhiemer patients :), where it helps track their movemet when they tend to walk away on their own.

 

Group Remit, who finally decide to develop a DIY affordable solution for newly born kids with Jaundice, in research phase they were earlier excited about leaping forward with technology to help figure sight changes instantly and on the spot

they were also excited about researching stress management techniques in public places.

 

The workshop started on Sept 19 and lasted for 4 weeks, where the last week, was a non-stop production mode at  WeMake, while focusing on fabrication.  On the last day, projects were packed shipped, and move along with Wemake projects to Rome.    

 

Four projects were displayed at WeMake booth in Rome: Nooni (a bracelet for helping Alzhiemar patients and their caregivers), Pawlino (a piano that works via vibration sensors for kids with hearing disabilities), Juvo (a device that creates a game environment for exercise routine of Parkinson patients), and Maya (a DIY lost cost solutions for kids with jaundice).   

 

This was the first time for any of the 16 students at any makerfaire event.  It was a unique experience for both the students and opencare, to have an exposure in the makers world.  Some students already got offers for crowd funding, and many visitors where interested in using the actual product after implementation.   The workshop is over, but the projects probably are not --we will keep you posted on future prospected progress.

 

poster

 

Nonni at MFR16

 

Juvo at MR16

 

pawlino at mfr16

 

maya at MFR16

 

like2

Comments

Packing for the OpenCare international network

Noemi's picture

Thanks @Moushira, seems like a marathon!

If we can prepare a presentation post for each of the four projects - similar to what Berlin students did, asking questions and detailing their process - we can better help them in their outreach, crowdfunding efforts should they wish to continue the work. We pack each story in a headline, we create a digital flyer and circulate it in a bigger effort. 

like1

Sounds good.  The one thing

Moushira's picture

Sounds good.  The one thing is that the workshop is practically over, so engaging in further activities need differend kind of planning that is not part of the formal ciriculum and course.   We had a process, and the posts that the students shared in the stories section were part of a bigger research that they were sharing with WeMake team, I believe their posts were a good comporoise, for sharing the thinking and the making of their projects while in progress  As you mentioned, it was a marathon :),  so asking for public detailed process documentation while they were already learning and developing, was going to be too much, but the material is there and maybe we can share it later, retrospectively.

like0

Curious about how the actual process went

Alberto's picture

I have been following on the platform. I left several comments and questions, but did not manage to get a conversation going (yet?). Maybe because the same user, @wave , has authored most of those posts – the poor guy or girl must be superbusy! 

With all this great, very practical work it would be a shame not to be able to extract the "how to" from it.  Specifically, we are interested in the community element of these solutions. You will see several comments in which Noemi or I ask "so, what made you think of this? What's your story? Are you testing it?" We were looking at Nighscout-style stories: my son has diabetes, glucose level monitoring is a source of stress, so... 

I also recommend you discuss with @Amelia how to bring your material into her ethno coding exercise. 

like1

Hello @Alberto,  let me reply

Moushira's picture

Hello @Alberto,  let me reply in-line:

"I have been following on the platform. I left several comments and questions, but did not manage to get a conversation going (yet?). "

Really thanks for pointing this out. This actually aligns with 2 questions that I have in mind:

We asked the students to share their ideas, in order to help them document, and help us share the work we are doing, 1. Moving on what should be the value of sharing stories, besides documentation?  2. Do we agree that the idea of having the "conversation going" without having clear aim of what to expect as an outcome of the conversation, makes it hard for people to engage.

"Maybe because the same user, @wave , has authored most of those posts – the poor guy or girl must be superbusy! "

They were busy, of course, but despite their being designers, it also took them a long while to figure out how the platform works, how to react to notifications etc. I am not saying there is something that we need to fix about UI, just acknolwdging the fact that onboarding newcomers is time consuming and not very efficient.

"With all this great, very practical work it would be a shame not to be able to extract the "how to" from it.  Specifically, we are interested in the community element of these solutions."

The community element you mean here is bringing the students _as community members_ to the platform? The only concern here is that, this is done in context of a school assignment, so there were formal excersices in order to help students formulate these ideas, and we also had tech factors controlling which idea we go for in terms of implementation.  The nightscout story is very personal, it is not possible to expect the same narrative from a school exercise, even though two of the projects were inspired by real stories. (well, this is how our excercise helped them tackle issue that they actually "care"about, when possible)

On the other hand,  we met people at the makerfaire, with "real" stories that they need to tackle. For example parents of kids with certain needs, or people who are part of certain communities who need to look for ideas for certain problems, we want to help them outline their stories and connect them with people who have implemented solutions for it, or parts of the solution, and whom they just don't know they exist. The online scenarios is that people post a story and they leave it there, until organically, someone finds it (or not) then a real conversation starts, online or offline. The other scenario, is that we poke both parties, offline (or in another channel) and we ask them to carry on the conversation on the platform. Assuming that we will stick to the second scenario, and keeping in mind the on-boarding challenge which we have seen, do you think the "share your story" model is something that we will keep? Do we need an ongoing repository of stories? Or we need to move to find a structured way to have an "objective" conversation, that has clear outcome?  What do you think?

Analyzing Berlin example that again, this is documentation of an existing, on-going, effort that has an offline plan. The comments are adding helpful links or giving thumbs up. I am not saying that this is not helpful, but we need to agree that this is falls on the rails of "documentation and feedback" and not "matching possibilities online" and the more we continue adding stories to an open repository with our current setting, then this is the model of engagement we are following, and which we need to acknowledge.
like0

That's what engagement is - balancing between them.

Noemi's picture

First, I completely understand and agree with @Amelia below, and thanks for re-iterating how we approach this.

Second, @Moushira: Students in Berlin were doing similar things to those in Milano - they were supposed to come up with challenges they want to solve and a prototype design. Because of the way the course was structured (tutor pointing to platform and offering "how to post your story" instructions as part of the coursework), the online conversation was organically feeding into the real life outcomes. No difference between the two, just the angle from which you/ Nadia or whoever was interfacing between OpenCare and students, explains the value for posting - shared learning first, then product documentation to help outreach for their project. This angle is how one does engagement, a balancing act indeed. 

like0

Agree

Alex Levene's picture

It feels to me like the process of 'documentation and sharing' is approached as a way of marketing a finished product, not as part of a developing process of investigation and enquiry.

Maybe this is why we've seen a low level of engagement with the community comments and questions. There's a sense that we are challenging them too late in the process. To us, it's just what we do, we ask questions and probe ideas, we point to areas of similarity or connection. To the makers we're just being difficult by only questioning or just saying 'great idea'.

It's not too late to change that but i sense that the drive isn't there to turn it around

like1

Possible

Alberto's picture

"Release early, release often"... exactly to get feedback, which is seen as important. Here we are "releasing" lived-out experiences that translate into a call to action. The very first one is in the project proposal: visually impaired engineering student walks into wemake, would like to make some kind of kit for him to design/prototype circuits even with his poor eyesight, which makes soldering very hard. The solution itself is much less appealing, mobilizing and intuitive than the solution paired with the story.

Comfirm what Noemi says: in Berlin, the students were told: "You should post what you do right from the concept phase. Do it for two reasons: (1) because it's part of the course and (2) because you are likely to get interesting feedback from the community, and it's more fun to design for and with people than do it on your own. Think of it as another feedback channel." And so they did. 

like0

Apparently we do not disagree

Moushira's picture

Apparently we do not disagree on the part of releasing often,  and which has already happened: Please take a look at the summary of the process that that the students went through. They were already sharing since round one, but in a 4 weeks workshop, and given the on boarding and the level of engagement t, how do you think the engamenet factor on ER could have been done better in a way that helps them progress, and helps opencare receieve more interesting ideas?  We already believe in the value of sharing the story early, and having a conversation "starting somwhere", as a "catalyst" to some idea development, my argument is, do we agree and acknowledge that sharing a story, the way it is done now, helps with some idea development and is bound to an organic time frame? If we agree, then do we think we need to define different engagement model that does a different job from the current possible catalyst one?

like0

Priorities...

Alberto's picture

The process you point to seems reasonable to me. If it is true that people benefit from feedback, getting feedback from the ER community would also have been useful. 4 weeks is more than enough to do that. Also, there is no extra cost, because students need anyway to write what they want to do, why etc. But that is your call, really. You are welcome to run your engagement process as you see fit, and if you cannot make it work with ER, use something else. Costantino and I agreed this in Stockholm. As long as you produce ethno data in acceptable quantity and quality, you are delivering. See this comment below for more details. 

As for your questions:

  1. do we agree and acknowledge that sharing a story, the way it is done now, helps with some idea development and is bound to an organic time frame? Yes. Although I don't understand the "organic time frame" part. Conversation tends to be ongoing: this thread started by @Pauline during the UDK course in May is still active, though the course is long over. 
  2. do we think we need to define different engagement model that does a different job from the current possible catalyst one? My answer depends on what you would consider to be the current model.
  • If the current model is the Edgeryders one, no. It's working quite well for us. People engage. We get the data. Amelia codes them. Guy aggregates everything. The results make sense. We just need more of them (perhaps twice the volume) to make for great results.
  • If the current model is the one WeMake uses ofline or in contexts different from edgeryders.eu, I don't know. I have not seen what comes out of your process. Standards of data quality in opencare have been encoded in the Data Management Plan back in June and in Amelia's comments to this thread. 
  • If the current model is what I am seeing on edgeryders.eu (posts by Wave, no reply to comments), then yes, we need a different engagement model. I think this is not generating enough data and of enough quality to justify the grant. 

 

like1

I wrote my other comment

Moushira's picture

I wrote my other comment without refereshing, hence the cross post.  A few points of clarification:

  • 4 weeks are enough to have a conversation, but if ideation phase was bound to less than two weeks, then it is a bit tight (it was a marathon, in this particular case, as @Noemi said :))
  • Organic time frame, means that under no circmestances we can expect certain amount or directin of comments in a certain time frame. Some stories have been around for weeks without interaction, some were picked up quickly.
  • The current model, as I see it, is that we have an open call for stories, and we are inspiring people, mostly those we meet on the ground, to share their story around the notion of "care". Some problems do fit opencare context, some are too broad to be solved by one project or soluion (depression, global warming..etc).  Our current focus is on harvesting a broad scheme of stories, and trying to get the conversation started (having 2-4 comments). We don't necessairly match a storyteller with a problem solver (because we don't have a call from problem solvers, like how we have a call for stories), and we don't have clear mechanisms to motivate the online storyteller to share their story (an online campaign vs on ground effort).  I am not criticizing our existing model, I am analyzing it, and asking about, if/how we will change, moving forward.  As I see, from your replies @Alberto, we want to maintain our existing model, while finding ways to harvest more stories, rather than think of applying differnet process, or motivations.
like0

Correct (with one add-on)

Alberto's picture

Yes, @Moushira , you are correct as far as I can see. 

Add-on: in the ER methodology, the storyteller and the problem solver tend to be the same people (like in Nightscout). We call this asset mapping. The question is not "what is needed?", but "what is already being done?". You are very welcome, however, to do things differently and frame a call for problem solvers, if you think that is a good idea. You know your community well (just look at @zoescope 's unique experience!) and will have ideas on how to motivate it. 

Once you have onboarded solution providers and they have somehow reacted (for example by providing a documented prototype) I would recommend to do online engagement being done the Edgeryders way. It's hard work (it takes you leaving 800 comments to have done engagement) but it works; also, year 2 is not a time to experiment, but a time to consolidate. But this is just a recommendation. In the end it's your budget, you answer for your own resuls, so it is your decision.

like1

Lets just acknowledge the

Moushira's picture

Lets just acknowledge the fact that we can't work on separate ways. i.e. stories like this are great, but this is not a starting material for a solution or something to be matched with a maker. Thats why I earlier asked about how we see the stories moving forward besides archival -- if we will continue to harvest stories, without a clear "criteria", then at some point, we wil have data, but most of it, doesn't fit a solution/product entry point.   This is not about the number of comments we make in order to boost the conversation, in any case, 800  comments are not a problem, only if our comments are not going to be two thirds of the overall comments.

Assuming that we will move forward with the call for makers, is there a way we can have a break down of stories, categorized by theme of "seeking solution" vs "general story sharing"?  That would be a good starting point for matching with makers. If not, we can think of alternatives.

Thanks for sharing your insights, am glad we are discussing details with transparency and dedication.

like0

Data Strategy

Amelia's picture

I want to resist the idea that there is a big difference between "objective" conversation and stories ---- I think they are not as different as we might think at first glance. 

I think if we look at the kinds of things people have been posting, we find that there is more of a continuum than a direct difference between personal stories and conversations about clear outcomes. We have people sharing their experiences making something for themselves or their loved ones (like Night Scout), but we also have people talking about their organizations and the people who are benefitting from them (like Orange House), which is still a step removed from, for example, getting stories from refugees themselves. Yet I wouldn't consider this any less of a personal experience. Similarly, students who have been given formal exercises to formulate their ideas, to me, are also valuable community members whose stories of creating technologies to deliver care are also important. From reading their posts, their contributions fit into the framework ---- presenting a problem, offering a solution. Then community members on Edgeryders interacting with them to ask for more information, make connections, etc. The important thing, from my perspective (and as @Alberto points out) is for them to stick around and respond to the comments. The value of sharing stories is to understand a) what kind of problems around care people are picking up on and addressing and b) how others react to their approach --- do they share similar problems, are they problematising the way that they are approaching it and offering other solutions, do they think the questions need to be reframed, etc. These reactions can take place on the platform (this is ideal) or in the actual world (still good, but we need a way of documenting this, as you point out @Moushira ).

It depends on what we are interested in. If we are trying, as @Alberto is, to map networks of people talking to one another, it is not entirely ideal to have someone reporting someone else's experience. If, though, we are going for a repository of knowledge and ideas, it doesn't matter so much.

Once we get to talking on a more macro level about the purpose each of the posts serve (much like we are doing now) we get into slightly different terrain. This is higher-level analytical work we are doing (for example, @Moushira , the content of your comment). I am trying to group these kinds of discussions under a "methodology" tag. 

Here would be my ideal: 

1) Tell stories in the first person as much as possible. To capture information, we need people writing on the platform itself rather than linking to information elsewhere. So, as the students are doing, writing about their projects.

2) If someone has commented or interacted with you in the actual world, in my view it would be most helpful to record those in comments below the post. We are still thinking through how to do this, but creating dummy accounts would be a way of capturing interactions. Alternatively, if this is too difficult, it is okay to put it in the body of the post itself--- we will capture the content (knowledge, ideas, reactions) but we will lose the interactive node element. 

3) non-stories are fine too --- analysis is really important, especially for writing reports, generating new and innovative methodologies, and making sense of data. We can gather these kinds of conversations and use them to make higher-level decisions about the project itself, what the data means, etc. I can still capture this information through codes and hierarchies. 

 

like1

This is the discussion we need to have!

Alberto's picture

Thanks @Amelia – much needed. In the coming phase of opencare you'll be fairly central, because we do need the ethnographic data, and people need to know what consititutes "good" ethnographic data. opencare is funded by DG CNECT (formerly known as DG Information Society); more specifically, by the Collective Awareness Platforms Programme. This program funds research on how online platforms can be used to elicit collectively intelligent responses. Putting a project on a website does not qualify as collective intelligence: in the proposal, we have argued that online conversation around a project does. That is what we promised to do. Of course, discussion does not always catch on: that's well understood. But on the whole, we should have enough conversation to be able to argue that ours is a really collective process.

I think that is defensible: we have 323 posts and 1,423 comments authored by 201 people, so an average of over four comments per post. 13 threads have 20 comments or more, two of them started by Berlin students. This translates into a social network with 201 nodes and 766 edges. The network's topology suggests a dense conversation, with all 201 nodes part of the giant component. Today it looke like this: 

Opencare social network, the graph

It did not come for free: over 800 of the comments come from either Noemi, Nadia or myself. These are all questions, encouragement, feedback, requests for clarification. Without this kind of work, you cannot expect results.

Summarizing: 

  1. We need to produce high-quality ethnographic data. That means both stories and formal exercises.
  2. It's important that proponents of either stick around to reply to comments and questions.
  3. Engagement is done by having paid staff spend a lot of time on the platform to move the conversation along with prompts, thoughtful comments, encouragement and questions. 

This does not have to be done on edgeryders.eu. In June, @Costantino and I agreed that WeMake is free to use other platforms if that works better for you. In this case you will have to do what we have done for edgeryders.eu:

  1. Cover the ethical issues by installing a consent funnel or equivalent.
  2. Secure legal clearance to reuse the content (IPR on uploaded content).
  3. Organize a workflow so that the content can be coded by an ethnographer, without losing the contextual information of who authored the coded content, in which context, talking to whom, etc. 
  4. Secure machine-readable access to the primary data (content) and the secondary data (ethnographic coding), so that @melancon can import them in his dashboard. We can demo the dashboard in Milano, already with real data. 
  5. Document steps 2-4 in the Data Management Plan. 

 

like1

Detail

Amelia's picture

One final other comment ---- the other important thing is that posts have a certain level of detail. The main problem I see with some of the student posts is they don't have quite enough information in them for people to be able to interact well. As @Noemi mentions in her comments on one of the posts, including a call to action, asking questions, or suggesting points of intervention allows community members to interact more with the post. Framing the narrative as a "story" is less important than offering a certain amount of information about process. And it doesn't have to be too much more, but more is definitely needed. 

like1

the value of the story, the value of data

Moushira's picture

One the value of the story: From a design or product perspective, without a story, it is nearly impossible to progress, because then there would be no clear problem to solve. The one minor concern here is that writing is a skill, so not everyone is able to craft a catchy story (in their second language) and as a student, the influence of presenting research and work, can mask the empathy factor in the story, even if the story is quite personal.  This can happen with any formal assignment and imo, there is no problem with that.

@Alberto thanks for sharing the data. The qantitative approach is interesting, according to the numbers:  Paid stuff are doing nearly 60% of comments, then a) do we need to target different audiance? (match storyteller with a problem solver) b) do we need to explore a new process?,  if no, then,  do we need to discuss the future of the repository of stories, besides archival?   Needless to say, storytelling is a leading and trending tool in design, we can not undermine the power of a story, and we can't claim that a story alone isn't important, but we can still question, which direction do we want the story to serve, besides contributing to our diverse repository. 

We need to keep questioning our processes as we move on, it is not a sign of conflict at all, it is a sign of care for what we do and passion for getting the most to our global community and world problems, from the tools and mechanisims we use.  Thanks, and nice to meet you @Amelia, btw :)

like0

Stories as processes, not literature

Alex Levene's picture

I understand your point about writing being a skill and the students not feeling confident in sharing in a second language. However, i would suggest that the process of writing about the project is more important than the literary value of the content. If you look at the posts below you see a story developing between 3 members of a design team and the community.

https://edgeryders.eu/en/day-1-reflexions

https://edgeryders.eu/en/redewendung-turn-speech

https://edgeryders.eu/en/language-barrier-how-can-we-build-a-bridge

 

Equally with @Tomma and her team you can see the development from the inital thoughts:

https://edgeryders.eu/en/questionmark

through the initial personal process of asking questions:

https://edgeryders.eu/en/not-a-clash-of-culture-but-a-merge-of-culture

The beginnings of the external research project:

https://edgeryders.eu/en/home-sweet-home

collecting the idea into a practical application:

https://edgeryders.eu/en/fostering-productive-potential-in-refugee-camps

At each stage the community engages to some degree, initailly to say hello and encourage development and thought.

By the final post there is a high level of engagement, including other ideas, suggestions and development possibilities. We also start to see where the project might go next.

A few students also didn['t feel comfortable writing in English so chose to include content in German. We translate to the best of our abilities and then ask questions seeking clarification.

like2

Again, apparently we don't

Moushira's picture

Again, apparently we don't disagree :).  The level of narrative in the stories the student put together isn't bad, imo, and it falls along the lines of the engagement model here, I guess:  https://edgeryders.eu/en/not-a-clash-of-culture-but-a-merge-of-culture  it could of course have been made different, but has nothing to do feedback, imo. I was just acknolwledging the fact that different stories have different motivations and styles.  The refugee story has been around for long, has an ongoing on the ground plan, hence, imo, the different number of comments.

like0

Stories as process + 1

Alberto's picture

Great examples, @Alex Levene ! Thanks for prompting me to re-read these stories in sequence. You are absolutely right. It's quite amazing as collective problem solving goes: it starts with "stubs" of "why are people in Germany afraid of migrants?", and three posts later you get @trythis (an honest-to God material scientist) getting in touch about the many great things you can do with epoxy in refugee camps, and where you might get it for cheap in Germany. You have gone from abstract to fully technical, and have done so in a group of people who have never met in real life, nor are likely to.

Two methodological notes:

  1. Everyone: @Alex Levene himself is a recipient of one of the opencare fellowships. Impressed by a post he wrote, we asked him to write a new one and rewarded him with gratitude and a small sum of money. So, @Costantino , this is a motivating move that you could copy: make it clear that you will reward small contributions. 
  2. The examples of @Tomma and the team with @MarieScheurer are great also because these are all people who speak English as a foreign language. Their expression is English is not perfect (and neither is mine), yet it's good enough for engagement. 

One meta-methodological issue: @Amelia , how is this great thread by @Moushira for meta-ethnography? Does it qualify? 

like0

Yes!

Amelia's picture

Most definitely--- I am finding this thread fascinating. 

like1

Nice to meet you, too :)

Amelia's picture

And totally agreed about continually questioning our processes -- this is a vital part of any project that wants to be successful! 

Stories are very important (as has been discussed on this thread) and can take many forms. I am glad we are keeping an open mind as to what qualifies. 

like1

nice

Moushira's picture

glad we are on the same page :). 

like0

Feature, not bug

Alberto's picture

Many comments by staff are not a problem at all. Reason: they typically do not get coded by Amelia anyway. They are in large part encouragements and requests for clarifications. They are a major part of the motivating mechanism that @Costantino is searching for.  So, the ethno analysis still represents what the community thinks and does – and there are hundreds of comments written by the community. 

Pro tip: do not think in shares (60% of the comments are written by the staff!). Think in absolute numbers (the community has written 600 comments and 300 posts!). As with any data problem, discarding stuff is fairly easy, whereas getting it is expensive (and slow). If you can bring Guy 500 more comments and 1-200 posts, and ScImpulse can do the same, we are good. 

UPDATE – I checked again my script, and found there was some double counting in team comments (really it's a MySQL known issue, that you can get rid of via code). The data as of now are: 

  • 1,439 comments
  • 602 authored by either Noemi, Nadia or myself. 
  • 837 authored by the community.
like0

This is important ethnographic work

Amelia's picture

We should remember that a large amount (I would venture to say 60% ;) ) of ethnographic data is generated through interviews with research participants. And what are interviews if not "encouragements and requests for clarifications"? The ethnographic process assumes a person (or in our case, people) asking participants more in-depth questions, prompting them to think more deeply about things they might take for granted as parts of their daily process. If we are doing collective ethnography, I see the work that the team does as important ethnographic work. 

Also on the subject of stories.... I was reminded of this quote from anthropologist Michael Fischer (in a 2015 American Ethnologist article):

"Stories are not just stories of, but stories for. They are ways of thinking about how we want to build communities of the future, for ourselves as well as others...they provide the mental tools as well for sur-vie"

like1

Thanks for the updates, I

Moushira's picture

Thanks for the updates, I just got lost in the last scentence: "If you can bring Guy 500 more comments and 1-200 posts, and ScImpulse can do the same, we are good." What does that mean?

Data is a very powerful and (and very flexible) indicator, indeed. Talking earlier about meta topics, I am drafting another separate post for some questions around how we outline our lessons learned. Thanks again!

like0

About the last sentence

Alberto's picture

Sorry for cloudy writing. It means this: Guy and his group at UBx are aggregating ethno data into and crunching it. For now, they have the 322 posts and 1,442 comments (of which 840 written by community members – the numbers keep changing as new material rolls in) on edgeryders.eu. Most of these (almost all the comments) are the result of engagement done by Edgeryders.

What I am saying is: WeMake and ScImpulse should each do engagement activities that result in 500 community-authored comments of reasonably high quality. In this way, we would have roughly 800 + 500 + 500 = 1,800 community authored comments, perhaps 3,000 comments overall, and we would be good. "Good" means we have enough high-quality content to mount a large scale, network powered ethnography and see if (a) our method works at scale; and (b) how communities go about inventing and deploying care services. This is consistent with the added value of our project (section 1.3.6 of the proposal). 

You can execute on our methods, or try something else. You can do it on edgeryders.eu, or anywhere. The comments could be reaction to posts, like here, or to schematics or videos of instructables, as you prefer. But that. I would say, is your goal (see also section 1.1.3 of the proposal). 

like0

qualitative vs quantitative?

Moushira's picture

Thanks @Alberto for the update, just wondering about any qualitative criteria that we have besides the numbers?   As with the approach of doing activities on the ground then transferring the stories narratievly on ER, where 80% of those will be written by staff, and not surprisngly a good chunck of comments will be by staff as well. As long as the number is sufficient, then the metric is still OK?  There are some cases studies around openIDEO, with a qualitative analysis that involved interviews.   I wonder if a brief booklet analysing the experient on ER will be compiled at some point?  Thanks!

like0

the meaning of the conversation - and how to

Costantino's picture

"Putting a project on a website does not qualify as collective intelligence: in the proposal, we have argued that online conversation around a project does."

We all agree of the value of the conversation that can be "exploited" while is online and codable as in ER. Consider this well bought by me.

To me the central point is this: 

how do we REALLY motivate people to overcome the friction in the process of writing on line?? What's the gain in writing here on ER or writing on line in general? Of course these are not question for a black or white answer. We need to discover and levarage on the trade-off: as more value I can fell/exctrat as more "pain"/friction/effort I can accept.

Concerning some experiments:

  1. if we have students (as in this case) we can give them "homework" and also in this case is not smooth AT ALL  
  2. when we don't have students the "homework" apporoach is not feasible.
  3. as previoulsy said the OpenANDChange strategy is not working in a design/making environment mainly because the "stuff to be produced" is not a document; if the subject of your development is a doc -> you're writing the doc -> you're already writing -> it's the same environment / approach

So we need to have other working strategies (and than protocols and tools and how to ....) that consider other human approach and use cases. Just to mentions some cases: 

  1. - when the product of the process are no docs file
  2. - when the second language is an issue/barrier
  3. - when the platform is not frictionless
  4. - when a human is not "verbose" type
  5. - when the value of writing is not exaclty valuable for the "supposed to be" the user
  6. - when the process of writing -> gaining value it's not clear or recognized from a user. 
  7. when the value of this "collective intelligence" is hidden and not available for the user

@Alberto IMHO this is what we need to takle in order to demonstrate not only that is possible to analyze the "data" when they are available, but we also have sustainable way to create the right conditions to foster the users creating these shared value, maybe considering this kind of approach for the whole process. 

focusing on the user, what are: 

-  the gain creators

- the pain relievers ?

value map

 

 

 

 

 

like1

Self-selection, engagement and a pinch of innovation

Alberto's picture

Yes. The "what's in it for me" question is, as always, the central one of engagement.

Your list of use cases is, as far as I can see, fundamentally splittable into two parts.

On case 1, I have no answer. Your experience is much deeper than that of any of us in the consortium. If you can't solve it, no one can. Zoe is almost certainly in the worldwide top 10 experts on this issue. We go back to the Commission and say "not happening. Collective awareness platforms are not possible when the collective process is aimed at producing something other than a document." It is a dignified negative result, still a result.

We have, however, met cases 2-7 many times. I have done my best to share this experience with you all, many times, but it seems it is so counterintuitive that you cannot bring yourselves to try it :-) I think this is why Guy finds this conversation theoretical: practices that (sort of) work are already there, generating the data for this project, in exactly this context. Also, I am sure there are others. And yet, here we are, with 10 months at the most to wrap up the data generation phase, asking ourselves how to do engagement... 

So, how do you want to proceed? How can we help? Shall I ask Noemi to give you a how-to presentation, maybe contextualized to the opencare experience? @johncoate gave one in LOTE5, but at the time opencare was just starting. 

I am  a bit worred, because it was our main promise that few people get this stuff, and we are among these few. This case is made in Section 1.3.2 of the proposal (Approach). The key passage is this: 

We are also aware that, while successes get a lot of exposure, most attempts at mobilizing communities towards collectively intelligent outcomes fail.
OpenCare moves from the hypothesis that many unsuccessful outcomes are predicated on bad execution, in turn often caused by theoretical misunderstanding. Few would dispute that a smart community runs not only on ICT technology and infrastructure, but also on a web of correctly aligned incentives, shared values, social conventions, and common vocabulary. However, we propose that, in practice, most of the attention and resources of people and organizations wishing to convene smart communities are concentrated solely on ICT artefacts. The result is, unsurprisingly, empty platforms that host little meaningful conversation (Prieto-Martin et. al. 2012).
like0

Getting online seen as a barrier (?)

melancon's picture

On one side, I do agree with you, that users may refrain posting on a platform, even more if they're asked to do so after an activity has ended. Earlier comments underline the usefulness of having this takeplace while the process develops. The language barrier might not be that a barrier, assuming the content can be ethno coded from any language (usgin multilingual tags, let's say).

Bottom line, users must of course see the added value of posting online, otherwise it may indeed be quite hard to have them spend the necessary effort to do so.

I also agree that we could/should develop other working strategies to get the material we are after.

--

On the other, more pragmatic, side, we need to make sure we deliver what we promised to deliver. Looking at things from the different tasks UBx is involved in, it is true we can only put our methods and tools at work if we can harvest some data echoing the excnahges between people. Stories or conversations, I have no firm opinion on this question, as long as the content can be tagged I'll be fine :-)

--

What I hear is that this thread oscillates between these two sides, looking at the issue from a "theoretical" viewpoint; or from a more pragmatic DG CNECT viewpoint keeping in mind we are bound to project deliverables.

--

I might be wrong, I count on you guys to help me get a better understanding of this issue.

like0

nothing teorethical at all

Costantino's picture

I'm not a researcher, I'm a practitioner. 

There's nothing meta in my comment. Just things to be analized and solved if we wanna make "more than homework". 

focusing on the user, what are: 

-  the gain creators ? 

- the pain relievers ?

like0