Problem Solving with social software curriculum development

edit print PDF monitor this page

Building

Tim Bonnemann (Blog: Plansphere): Looking for Social software to problem solving For example, voting, better delieration and want to social software to do that.

Adolfo Dunayevich from LaNeta, Mexico and APC: different collaboration schemes among small NGOs, organizations.

Anna Feldman from Greennet, work with small users who are activists they need online tool to support...how they can use their online spaces..also work with APC: that level they work with different network and their access to ICTs. Problem solving depends on the strategic use of tools...finding a solution

Partha: from Bytes for All and telecentre.org

Tom Bartolero:

Erica Block, Blockwork: small arts organization, Blockwork, work with partners, Detroit, community mapping of media technologies, participatory digital storry telling that addresses digital divide, incude non-profit small organizations, individuals..the topic seems to be interesting..

Allison Hewlitt: from Bellanet, improve collaboration in between different groups, how technlogy can also be used for collaboration, People ask for tools, but they don't understand what these are going to do for them...we want people to talk about their problem and to deal with the problems using some of the tools.

Patrick Ball: Benetech: Director of Human rights, building information management and security system on human rights issues, CTO for Benetech to help develop technologies for physically disabled people...

Anna showed the flip-chart..what was there?

Using Social Software to:

Strengthen connection in our communities

Supports co-creation of content

Improve channel to share information

We can have conversation on these points..

Erica liked the conversation topics...

Patrick said, techies who build the physically disbaled people software actually come from private sector and they build a prototype which they took to a conference and it was accepted by visually impaired people. But it was pure market research, they did focus groups...we hang out when watch people's process...Geeks problem, they do not acknowledge that people have problems. Witness consciousness that you listen to people's conversation, you have to make sure that you aren't making assumption about commonalities, we need to have high standards....they need to be fluent so that they dont' make stupid recommendation..There are bullentin boards, WiKis?, CRM tools, plug them together to make mash ups ....Feed the users into the process

Anna said this drive to get them into the process may sound to be patronizing

Erica said, they have some approach to break down cultural barriers, stratigic sessions...Free your ....

Patrick, taking the joy with the tools that takes the tool further and further...

Erica: Another layer we all miss, what is learning, what is listening..

Patrick: testimony data, case management tool, wide area database solution (groups are sharing data) with all securities built in the beginning,

Learning part is: easier to use cryptographic solution..for example, no one does need to train email..so they think they need software that doesn't require any training...so they built a software...Martus (reading machine software for the blind)..version 1.0 totally rigid but its a successful venture now as they went to the clients and saught feedback..built forms, customize abilities and then they started to get double digit adoption...then they worked on marketying strategy..so model did't initiate the change but users drive the course..

ou can only apprecitetools once you've tried them. You need to get a feel for them before knowing how they can be applied elsewhere.

Need a space for people to feel safe to engage in discussion about what a tool can do to help their work.

Think about the conversations that organisations have to have - and see which tools match those conversations.

i.e. "What is the kind of communication you are trying to facilitate?"

The challenge is to capture the more intangible stuff. That's the stuff that doesn't sit so well with geeks.

DOn't try to condense the motivations people have into technical solutions.

You need to go through a sequence of modalities to get to action.

How do you move a community from its brainstorming process, to "äction"

social software tools don't address the issue of expressing an organisational voice.

10 different types of communication:

We need to establish (as geeks) if there is technology that meets the needs of the community.

THe software shouldn't be constraining

We mustn't look through the lens of technology.

THere needs to be an equal relationship between the technologist and the client.

Need to distinguish between a knowledge of how to use web 2.0 applications, and organisational needs that can be met with social software .

Perhaps think of aggregating problems and solutions which have been mapped to them, so that we can search for examples.