WASH framework / system workshop

Experiences with ComPart in the

ICCO-Alliance

September 7, 2011IRC, the Hague

About the presentation

1. Backgrounds of ComPart2. What is ComPart?3. Which tools are used?4. Administration of ComPart5. Successes and Failures6. Lessons learnt (successes and failures)

• Started in 2007• Need for on-line learning platform• Later also communications platform• Developed by ICCO and Euforic Services

Background of ComPart

• ‘Web’ space to share information; find information– Support reflection and learning– to communicate; discuss– to document experiences and ideas– to add value to your work

• Collection of tools• Open, collaborative, participatory

What is ComPart? [1]

• Open content• Content that ‘flows’• Standard ‘toolkit’• ‘Pick and mix’ approach • Low threshold to create and use (bandwidth, pricing)

What is ComPart? [2]

CONFERENCESInterWise

STORIESBlogger

DOCUMENTS

wikis

DISCUSSION

DGroups

BOOKMARKS

Delicious

SEARCHToolbar

EVENTSGoogle Calendar ComPart[wiki]

What is ComPart? [3]

• Dgroups• PBworks• Blogger• Flickr• Slideshare• Google:

– Search (customized)– Calendar– Maps– iGoogle

Which tools are used?

• Conduit toolbar• Blip.tv• Vimeo• Delicious• Skype• AT&T-connect• Yammer (lately)

ComPart network

• Finding enthusiasts to get first content• Snowball effect• Training sessions– Only on tools → Web2Do

• Stimulating active users / teams / departments• Involving management• Working with partners in South• Support network (enablers – ambassadors)

Process of introduction

Usage statistics

• Direct User support & training• Editing FAQ pages • Platform maintenance• Adjusting to changes• Statistics (Google analytics)

• Adding feeds (feedburner)

• Reporting

Toolset administration

• Toolset used for:– learning strategy ( ±12 CoP’s)– Internal discussions (challenge 2020)

– (internal) communication (the Studio)

• Awareness • Acceptance• Enthusiasm

Successes

• Insufficient organisational alignment– Tecnically– In business processes

• Over estimating users abilities• Late integration with on-going processes • ….

Problems

• About objectives– Learning processes– Business processes

• About Who and where are the intended users• Make sure of internal alignment– Agreed upon way of working– Agreed upon definition of what is success

• Keep things (even more) simple (e.g. single sign on)

Lessons learnt

Thanks for your attention!

Maarten Boersmaarten@eapproach.nl

Euforic Services associate:

www.euforicservices.com