Friday Oct 29, 2010

SocialChat on Sharing Best Practices

This SocialChat touches the heart of Enterprise 2.0: Why is it challenging to share best practice? Once again, we had an interesting crowd together exchanging ideas at our internal microblogging channel. Read my share top down:

  • In my opinion "sharing best practice" has at least two problems:
    1) The entry barrier is to high. If you ask yourself if your case is a good example for best practice, then it is likely that you say no. So asking for just the best is wrong.
  • 2) Collecting "best practice" is most of the time an after-though, once the project is done. But then you are already preparing for the next project and don't have time to think about the previous lessons learned. 
  • Therefore "sharing best practice" needs to happen while you are still on the project. It should not be an extra step that causes extra work that nobody pays for.
  • @gary Indeed, social software can help to identify the nuggets. But this can only happen if the information is easily accessible and has an URI to refer to. And of course #3) we need a culture of sharing, referring and recommending stuff.
  • @amy "close communications" yes, but not "closed". Other employees need to be able to participate.
  • The trick is to exploit the selfish attitude of some people. (The altruistic do it anyway). The argument to convince the selfish and ego-centric is the following: …
  • @amy Incentives don't work. They don't change the culture.
  • @amy "What's my benefit if you can do your job better and get a bonus?"
  • As nobody is asking how to convince the selfish, I guess I keep the secret. :o)
  • @frank Open source is all about sharing. And the s-curve in Sun's recent visual brand was a symbol for sharing.
  • @frank But I do not want to sound too enthusiastic. Reality was somewhere between the ideal and the average. 
  • The secret trick revealed in the final minute...
  • Share with yourself! You gain something for your future projects if you blog some notes or fill some wiki pages about the current project for later use. (psst, others might do the same and you all benefit.)
Credits for the nice infinite icon: KPT #18

Friday Nov 20, 2009

Social Enterprise Tools. Beipiel Sun.

Hier die Folien und einige Referenzen zu meinem Abschlussvortrag der Swiss Intranet Summit 09 in Zürich. – Jetzt auch als Webcast!

Wednesday May 06, 2009

Sun VDI 3 UX Story - Power of the Web

Each and every of my endeavors starts with an index page. A title, a logo, some ideas, related info, more stuff added over time, a log, and sooner than later the thing becomes a substantial project. This approach worked out fine for me for almost 1 1/2 decades now. First in the GoLive team in the late 1990s, where we developed a WYSIWYG web editor. Then the intranet for StarOffice' user experience team. And today I am still using GoLive to create and write on web pages for my projects.

All this is along the lines of the original vision of Tim Berners-Lee and Robert Cailliau to create a read/write web. Some time has passed, and their vision never came true. At least not in a way that could be called elegant or straight forward. Instead we see a cyber-landscape of wikis, blogs, microblogs and other social software that empower "users" to "generate content." Wrong perspective _BTW.

For the VDI project I've changed my habits a little. I set up a blog internal to Sun and start with a blog entry, a tag, some ideas, related info, more stuff added over time, and sooner than later the thing becomes a substantial project. The advantages are the same as in the early web zero-dot-nine days. I do not have to spend extra effort in communication, while colleagues can see what is happening and can provide feedback.

Here is a screenshot of my internal blog at Sun:

Tags are assigned to all entries, and the resulting tag cloud provides quick navigation for the blog. Concept diagrams, design sketches, and even photos from whiteboard scribblings are stored and shared on the blog. Other content like wiki pages are linked, as well as classical intranet pages for stuff that does not easily fit here.

I am not blogging. I say it again, I am not blogging. I just use the internal blog as a low key content management system; and that approach has proven to be useful for me and the team I work with.

>> VDI UX Story: Part 1: Concept Workshops | Part 2: User Research || To be continued...

Friday Mar 06, 2009

desktop virtualization wiki relaunch

Sun's wiki space for Desktop Virtualization has been relaunched. New pages, and lots of feeds from Sun bloggers. Check it out at_

Monday Feb 23, 2009 tips & tricks

I spent some time exploring and experimenting with First of all, it is a wiki that is open to people inside Sun as well as outside. Second, it is divided into spaces on various topics. Each space is created by a Sun employee, has its own set of permissions that control the access level for the users. Everything is possible -- from anybody can do everything, down to just the space owner can see and edit the pages of her wiki space.

The notation guide reveals some nice features. It is definitely worth to take a look. My personal highlight is the capability to include some external content to wiki pages. For example, the wiki page for the Sun Ray Conenctor for VMware View Manger lists all of Sun's blog postings that are tagged with 'srvc'. The wiki macro that does the trick is:


The other feature I like to discuss in brief is the page layout and a navbar with macros. Therefore, all my wiki pages are based on the same skeleton:


main content goes here




This divides the page into 3 columns: 70% width for the main content, 5% white space, 25% for the navigation bar on the right. The latter contains the same elements for all pages by including another wiki page 'navbar'. Here is my navbar:

h6. Pages
[A Social Software Pattern Language]

A light blue box with a tree view of all pages in the wiki space, a search element, and a log of recent changes in the wiki space to stimulate participation. '\\\\' is a forced empty line. Here is an example: A Social Software Pattern Language

BTW_ I strongly recommend to put such recurring elements to the right, in order not to break the visual connection between the page heading and the content.




« July 2016