Strict Standards: Non-static method CSS_Switcher::usage() should not be called statically, assuming $this from incompatible context in /home/bigblog/public_html/hipporiver/plugins/pi.css_switcher.php on line 29

Warning: Cannot modify header information - headers already sent by (output started at /home/bigblog/public_html/hipporiver/plugins/pi.css_switcher.php:29) in /home/bigblog/public_html/hipporiver/core/core.functions.php on line 707
the Big Blog Company | Corporate blogging and wikis, internal communication session
“Who yer callin' a sparrow, you schmuck?!”
The bird on the back.
April 25 2005
Corporate blogging and wikis, internal communication session
Adriana Cronin-Lukas • lesblogs 
Trackback to this post [0]

This session had Euan Semple of the BBC, Ross Mayfield of Socialtext and Lee Bryant of Headshift.

Small scale, letting it grow, connect individual pieces. Tolerance, socialising issue of trusting each other is significant. Start changing the power play within organisations. A year ago, we started blogging. Project blogs, contextual links, blogs give internal people to publish and produce content.  We use wikis to produce collaborative documents.

Internal leaks are not a new problem and we try to come up with policies of what is and what isn’t acceptable. We are creating a reputation engine finding out who is linking to who and reading/aggregating them.

Ross Mayfield

Innovation is competitive advantage. There is friction when people work together, innovation happens when there is productive friction. People need simple tools 90% exists in email, largely broken. 30% occupational spam cc/bcc. There is a need for communication using something simpler – wiki weblog email IM – social text. Wiki is a collection of pages anybody can edit and link together. Linking to a page is simple and every page has a name.

It’s how people use the tools – don’t have to have rigid boundaries. In applications and tools rely on people using them to realise their efficiencies. They need to fit IT and management infrastructure – unfortunately.

Wikipedia – collaboration on the scale not seen before. More about participation, the communities exist inside. Innovation – letting your employees to be a little bit more free to express their ideas.

Lee Bryant

Low cost way for companies to build social infrastructure. Enterprise software is usually extremely expensive and is part of the top down mentality. Out of synch with innovation. How to deploy it and integrate it? Can’t sell koolaid to companies – how can you do the non-technical work. Tools, weblogs and personal sharing publishing tools etc, open standards, such as RSS, sharing info etc. Flickr, google and Technorati that you can do to feed information to the organisation. That’s what I mean by social software.

Weblogs – people have a discussion, domain for knowledge. Wiki very good root collaboration, objective, documents, project map, cheap and easy way. Flickr – sharing presence and perspective is quite important within organisation. What you see and where you go. Delicious – social bookmarking tool, different subjects and different people tagging them too. Share knowledge, clear use within organisation. Concept of aggregation – email is broken but people use it. Can subscribe to what they are interested it – piece of glue that sticks things together. Different systems – document management, KM systems – if you think of social software is providing light weight interface that belongs to the people rather than the company. Adds value to existing technology, even before integration.

Not using systems and other communication applications – using email instead. Let people reorganise their own feeds and information and then you can start bringing stuff to life.

Use of flexible metadata. Devised top down but do not fit day to day needs. Social tagging – delicious and flick, own language and aggregation. Every piece of information should be exposed to RSS feed and then do whatever you want with it. As a result you are creating a fabric within the organisation – weblogs, wikis, limited local ways, project groups and they emerge gradually. Don’t scare them into a big system. Modular and bottom up. Then you start seeing the benefits. Add features gradually. Launch early, it will gradually work, you can start achieving something. Finally, engage people in their own language.

Which is going to be bigger? The BBC or Scoble at Microsoft?

Page 1 of 1 pages