Wednesday, February 11, 2004


4 keys to building a culture of innovation

 

Stephen Shapiro's excellent book, 24/7 Innovation, contains a list of four keys to building a culture of innovation, which is one of the best, most concise explanations I've seen anywhere. [Innovation Weblog]

2:49:47 PM    Trackback []

The Future of Business

 

Dave Pollard, author of the How to Save the World Weblog, offers a fascinating vision of the world of a typical knowledge worker in the year 2015, including the technology tools that will enable a seamless world of knowledge capture, sharing and collaboration. [Innovation Weblog]

2:49:28 PM    Trackback []

New URL for Charles Cave's creativity Website

 

Charles Cave's Creativity Web site, one of the most comprehensive guides to creativity anywhere online, recently moved to a new URL. [Innovation Weblog]

2:48:41 PM    Trackback []

Interesting series of articles on innovation management

 

Intelligent Enterprise magazine is running a 3-part series of articles on innovation management, and how several emerging types of software can be used to help catalyze and manage innovation in your organization. Here are links to the first two articles, along with a synopsis of each one. [Innovation Weblog]

2:47:21 PM    Trackback []

Edward de Bono, Robert Heller launch 'Thinking Managers' Web site

 

Thinking Managers, a new Web site featuring the writings of Edward de Bono and Robert Heller, is based on the conviction that, to succeed in management, you need better ideas and better information than your competitors. [Innovation Weblog]

2:46:54 PM    Trackback []

Capturing a conference using social software (Seb Paquet)

 

A quick link to Lee Bryant who’s at the Emerging Technology conference and enumerates some of the social software-powered parallel channels that are being used by participants. Many-to-many indeed. Various people around me are tapping away on keyboards blogging the...

[Many-to-Many]

2:41:18 PM    Trackback []

More on Google's Atom bomb

 

More information on Google's support for Atom and abandonment of RSS: One post on Blogger Blog, an independent site devoted to the software, indicates that the only syndication format available to "standard Blogger users" is Atom. Everybody else can choose RSS or Atom, but not both.

In a subsequent post, a Google employee indicates that "legacy support" will continue to be provided for RSS among Blogger users who have been offering a feed in that format.

If Google had no syndication support in Blogger, I could understand why it might decide to offer only one format and pick Atom over RSS. Atom is an interesting new format, though personally I think it would be misguided for weblog publishing software not to support RSS and thousands of existing users.

However, because the company has functional code in Blogger that supports RSS, the only reason not to offer that feature to customers in addition to Atom is political -- yet another volley in a long feud among developers regarding the subject.

Do you really want a company as powerful as Google withholding its support for a popular Internet protocol strictly to promote an alternative format?


[Workbench]

12:18:11 PM    Trackback []

Google's RSS support questioned

 

Dwight Shih asks a good question:

For a company whose motto is don't be evil, Google's drop of RSS support is quite troubling. Atom is both an API and a format. I could understand a move to the Atom API. I could even understand a migration to the Atom format. But I just don't understand the need to drop RSS support. Readers and aggregator developers are potential losers. But who are the potential winners?


[Workbench]

12:17:36 PM    Trackback []

Andrew Grumet: RSSTV, Syndication for your PVR.

 


[Scripting News]

12:06:58 PM    Trackback []

Disney Enterprise Weblogs and Wikis

 

Mike Pusateri, Elisabeth Freeman and Eric Freeman at Disney shares their enterprise blogging initative. Its very similar to the experience we have had with Socialtext, without the integration of blog and wiki with enterprise requirements in mind. The focus on blogging for project communication instead of just individual expression is spot on.


Using RSS for content distribution

Using RSS Enclosures to deliver video to 2 million broadband users. Some argue that enclosures don't scale and their not enough bandwidth, but >500M videos have been delivered in less than one year an dhav been able to scale bandwidth to demand, now moving towards caching at the edge. Most of the delivery is off-peak hours, especially from them to the cable head end, so bandwidth cost is nominal. P2P like Bittorrent and others may broaden this.

Enterprise Blogging

In ops/engineering there are 100 people that log into the 6 weblogs. In DIG, 1 blog and 50 users, the wiki has been over 1.5 year 200 users and lots of groups.

Mike works where coordination is king. Info flow between programming, marketing, traffic and operations, etc. Consistent flow is critical, constant change occured and must be communicated, catch up must happen easily or problems result, archives. People don't like loggingm dont know whats new and difficult to forward.

Shift Logs
* 24 hour positions necessitate the creation of a shiftr log to report information to coworkers and management about what occured on the shift
*Previous solution was specialized FoxPro database with minimal features, mot even search
* Now a MT-based group blog

Distribution
* New weblog styel were popularm but requests for email of entries began
* Instead of email notification, used RSS
* Newsgator chosen as aggregator because of the outlook plugin

Discrepancy Reports
*Detailed info on mistakes, problems or opther events that affect the broadcast
*RSS feed reduced use of email

Ratings Information
* Daily need for overnight ratings information
* Generating RSS feed that encloses a styled table

Furture
*News Clopping Service (currentl web app)
* Playdate Memor changes (currently email
*Addition of RSS feeds to existing intranet portal modules
* Use of ATOM to replace RSS (when 1.0 arrives) and compliant tools for simple publishing. Because it is inherently 2-directional, for interaction
* Syndication of some media content for review

Conclusions
*RSS feeds and Weblog software are useful for multitude of business need where information flow is critical. Its not about opinion its about information flow
* RSS feeds are for much more than weblog sndication
*Use of RSS feeds is inexpensive comparatively
*RSS aggregation into Outlook integration was critical.
*Client side aggregation needs to move toward server side aggregation
*Need for authentication is immeadiate

They also use wikis inside. Disney Internet Group is also using wikis and blogs

*Wide variety of areas of expertise within our group
* Each person can contribute research and articles of interest to the entire group
* Best shared through a system that will notify, Notifications have had an impact -- email and RSS
* Did some stylizing per group
* Repurpose internal datafeeds
*Had training sessions to get it going.

Reuters uses wikis instead of blogs as it was harder to adopt.

Problem security and authentication; provisioning new spaces and resources. Disney has restricted write access, but not read access. Comment from a person at the BBC affirmed they ran into this in some areas too. They don't have Socialtext's ability to manage and work with lots of workspaces.


[Ross Mayfield's Weblog]

11:55:42 AM    Trackback []

Documentation & knowledge

 

A oft repeated question / assertion in KM is the link between explicit documentation and knowledge.


The point I'm trying to make, is documentation alone does not = knowledge. To retain knowledge against attrition you have to have a community that can appreciate the context, understand the issues, talk the language, adopt the assumptions, share the tricks, interpret and adapt the explicit stuff to changing external circumstances.

Agree we need to know how to make things and deliver services, but that knowing does not come from documents, it emerges in the dialog around the practice. To capture and preserve the knowledge, - not the data or information, - but the meaning and shared understanding, you need to sustain the community, energize the questions and promote the learning, rather than capturing content or storing the document.

It is around the tacit stuff; what you may feel, observe, intuit and never 'see' or read, the relationships, the mentoring, the validation by talking, by 'being' and through doing, that creates and finally preserves the knowledge. If we loose the 'community', we revert to information and have to bring forth the knowledge in another community to enliven, validate and refresh it.

If you still have doubts read Doug Hofstadter


[Knowledge-at-work]

11:40:13 AM    Trackback []