I’ve just finished reading a great book called The Myths of Innovation by Scott Berkun

Myths of Innovation Book Cover

I really learned a lot of things that I didn’t know about how some innovations have materialised, and some of the factors that do and do not contribute to an innovative idea actually being brought to fruition.

Not only did I find this book interesting,  I also found some choice nuggets that I can actually use and put into practice.

I would highly recommend it for anyone who is interested in innovation, new ideas and fostering creativity within groups of people.

some useful wiki etiquette tips from the Businessweek CEO guide

DO

Be bold: Go ahead and create content or edit someone else’s work. Wikis develop faster when people fix problems, correct grammar, add facts, etc. This is a collaborative tool, after all.
Make notes: If you make changes, explain why you made those changes in the discussion or notes pages that are generally attached to wikis.
Give praise: Has someone added useful content to the page or spent a great deal of time cleaning up the page so it’s easier to read? Praise helps let people know their contributions are valued—and makes them want to contribute again.
Build structure: Wikis need people to synthesize and structure content so it’s easy to read. Even if you’re not creating content, you can still help by shaping what’s already there.
Be polite: As with e-mail and instant messaging, it’s often easy to misinterpret the tone of a comment. Disagreements over content or edits can become heated. If that’s the case, it’s a good idea to take a break for a day or two and come back to it later.

  

DON’T

Take it personally: Yes, colleagues will edit your work and you might not agree with every change, but that’s the nature of collaboration. It doesn’t mean that your co-workers dislike you or think you’re stupid.
Ignore questions: Colleagues may disagree with your changes and ask why you made them. If so, be prepared to give concrete reasons for your edits.
Delete useful content: Many times a posting can be improved by amending or editing it, but deleting content upsets people, and they may feel they’ve wasted their time.
Be chatty: A wiki shouldn’t be used as a chat room. Any discussions related to a wiki subject should take place on the discussion or talk page, not on the actual content page.
Keep it secret: If you find valuable content on your company’s wiki, tell others about it. Wikis benefit from a wide range of contributors.

I read an interesting post about Internal Blogging on Library Clips, talking about some of the benefits of internal blogging. In the beginning, blogs were something that existed on the public Internet, but soon people started experimenting with blog use inside of the organisation. The post referred to above covers many appropriate scenarios and benefits to internal blogging, and the one element that I want to expand on is group blogging.

As the name would suggest, a group blog does not have a solitary author, but rather a group of people that are able to author a single blog. This means that you benefit from the authoring power of the masses, but the content is still viewed over a single ‘channel’ – i.e. as an information consumer I only need to subscribe to the one blog.  The typical communnication mechanism that this would replace would be something like a weekly internal email newsletter, usually authored by one or two people. A group blog is a better tool for this type of internal communication, as employees become much more engaged in the process because they are now a part of it, rather than just consumers.

However, the issue with ‘empowering the masses’ is that it can lead to a loss of control. For example, if Joe Blogs (being the blogmeister that he is) decides to blog about his night out on the town, the chances are that most people don’t care, and he is just adding to the problem of information overload…. the internal group blog is just not appropriate for his musings of a personal nature… that’s what his personal blog is for. So how do you strike a good balance between empowerment and control?

A good example of how this has been achieved is an internal group blog that is used at Microsoft UK.  If you’ve ever had to deal with the Microsoft organisation, you’ll know that it can be very complex, with individuals and small groups extremely focused on their particular areas. This is a good thing in terms of business performance, because people have clear goals and can channel all their energy into a focused area. However it also means that people may not always be aware of what others are doing in other business groups, meaning that an opportunity for shared learning is lost. A group blog provides an easy way to keep up with what others are doing in the organisation.  At Microsoft, a weekly email newsletter (owned and authored by 3 comms people) has been replaced by a group blog, enabling any of the 2000+ staff to become authors of this blog. It’s a great way for people to share what has been going on in their part of the business, but how does Microsoft stop this from becoming a complete free-for-all with no control?

The answer is quite simple; they have added a short approval process for blog postings, shifting the responsibilities of the 3 comms people from being content authors, to ‘executive editors’. Now, instead of having to write a newsletter from scratch, they can review all blog postings, rejecting anything that they deem to be innapropriate. I think that this strikes a really good balance between empowerment and control. Microsoft benefits from the experience of the trained comms people, yet still manages to engage and empower employees by allowing everyone (potentially) to have their voice heard and share their views and successes.

 In the world of ‘Enterprise 2.0′, striking the balance between empowerment and control is a delicate, yet vital, principle. It doesn’t only apply to blogs, but also wikis and anything else that is ‘end-user generated content’.

If you want to attend a really fantastic event then I’d suggest you take a look at Thinking Digital event happening at The Sage Gateshead from 21st-23rd May, where there will be a top lineup of thought provoking, influential and inspirational people.

The event is created and is run by Codeworks – www.codeworks.net – and I can personally testify to the event quality as well as fantastic hospitality that they have shown towards my colleagues and I at past events. If you’re into new ideas, driving innovation and learning from others’ experiences then this is the event for you!

Speakers include Dan Lyons (Senior Editor at Forbes aka ‘The Fake Steve Jobs’), Matt Locke (Commisisoning Editor Channel 4), Daniel Pink (best selling author on innovation), Mark Selby (VP Nokia), Steve Clayton (Microsoft) and many more – full lineup at http://www.thinkingdigital.co.uk/speakers 

I saw these very innovative Revolution kites online so I bought one.

I’ve been kitesurfing for a while so I thought it would be easy, but it’s not. Take a look at the videos on their site – they make it look so easy! On the plus side it’s a great challenge for days when it’s not windy enough to kitesurf, but at the moment I’m still in the frustrating spend-more-time-crashing-than-flying stage. The degree of control is amazing but they are very sensitive, so even the slightest movement has a major reaction.

Anyway – check out the vids on their site to see how it’s meant to be done – I’m still a long way off :-)

A good example of how radical innovation isn’t always as easy to adopt as we may hope…

This post from accessites.org talks about the final resting of Bobby, the rather outdated accessibility testing tool from IBM that was acquired as part of the Watchfire deal. 

In my opinion this is a good thing and a bit overdue…. there are some very good online testing tools out there, my personal favourite being www.cynthiasays.com.

I was a relative newbie to accessibility until about a year ago…. and one of the most important things that I’ve learned in the past 12 months is that an online tool may be a good evaluator of a website, but it does not guarantee that the website is actually accessible. In the UK, I use the RNIB consulting teams to evaluate and audit web software… the depth that they go to is remarkable and well worth every penny!

I’ve been having a few issues with my ISP, so I’ve moved my site to www.robgray.net for now. Instead of setting up a blog on that site I’ve gone for the WordPress blog which is very easy to integrate with the SharePoint site via the RSS viewer webpart. As you can see it’s also easy to present feeds from other bloggers that I read regularly.  I’ll be adding some more stuff during the week including the Silverlight webpart to better showcase that Picture library of SharePoint Internet Sites.

Search is pretty useless. After all, there is not much point in searching for something unless you actually find what you are looking for. So we should really call it Enterprise Find rather than Enterprise Search, shouldn’t we? Nonetheless, for the foreseeable future, the term Enterprise Search seems to be here to stay.

So what is Enterprise Search anyway?

I think of Enterprise Search as the technology that can help you find information stored within your organisation. Historically this internal information may have just been Intranet content and documents, but being able to quickly find people, expertise and even structured data (such as information stored in a relational database) is becoming more and more important to the knowledge workers of today.

This means that Enterprise Search has to operate in a fundamentally different way to Internet Search, even though there are also some similarities between the two.

Differences to Internet Search

One of the main differences is confidentiality. Most web site content is there because it is intended for public consumption, with the intention of being found. In fact, most webmasters compete aggressively for their sites to appear in the top results of popular search engines by engaging in “Search Engine Optimisation” (otherwise known as SEO).

Within the organization, the approach to confidentiality may be somewhat different. Many pieces of information need to be kept confidential, and therefore should not be found if someone is looking for them. The classic example would be HR documents containing sensitive information … not exactly what you want valued employee number 217846 to be able to find.

Of course on the Internet you also have highly confidential sites such as your online banking, but the banks are very aware of the risks of Internet security and take the appropriate precautions. These are highly secure sites, with no risk of someone stumbling onto your last month’s mortgage statement by accident as a result of doing a web search on live.com (surely nobody would use another?).

Naturally, internal portals and sites should have equally stringent security measures, but often they do not, or the information that is extracted from secure internal systems gets placed in a non secure place such as in someone’s Outlook calendar, a shared collaboration site or a file share, just because it was easy to put it there at the time. Many of us are guilty of this bad practice, and instead we should be securing our document sharing portals by setting the permissions at a granular level, ensuring that only the correct people have appropriate access to the content.

This is where some organisations have burned their fingers in the past. If the search engine runs under a specific user context that has admin privileges, it may be able to index the secure site and a regular user could find something “interesting” by accident. Even if the actual document is still secured, the title may give away more information than desired, for example “Due diligence for XYZ corp acquisition.pdf” or “October 2007 redundancy list.xls”… even though I cannot open the document to see who is going to be made redundant, I know that there will be a round of redundancies in October 2007. It is imperative that whatever search tool you choose, is able to assume the user context of the person doing the search, and therefore not return more information than required.

Not all information, however, is intended to be kept confidential. After all, the main point of a portal is to share information. Webmasters of Internet sites use Search Engine Optimisation techniques in order to ensure that certain “keywords” appear in the results of popular search engines. SEO is a vast topic in itself that is out of the scope of this article, but what is the approach for doing SEO inside of the organization? Unfortunately, this is usually a neglected area within the Enterprise. It’s very important to provide employees with the most relevant matches within the first few pages of results, preferably on the first page. We have all grown accustomed to finding what we’re looking for almost instantaneously in the world of the Internet, and we have the same expectation when using an Enterprise Search technology. The relevancy algorithm of the search engine is pretty important here, but what is often overlooked is the importance of ensuring that documents and content are tagged correctly and that the correct metadata and “keywords” are included so as to make them more findable.

In addition to confidentiality, another major difference is the importance of finding people and expertise. In fact, document and content searching is just soooo last year…. Expertise search is where it’s all happening right now. Microsoft is a very knowledge-dependent organisation. We have more experts than you could throw a stick at. These range from experts in our own technology, to experts in the history of the Boeing 747 or the art of making a perfect espresso. Some experts may be useful, others maybe not so much. Many people also change jobs as often as once every two years, which is a good thing because it keeps them fresh, but it does also mean that their expertise could change fairly regularly as people take on new challenges in different areas.

We often need to find some information that is related to a product, but we need the most up to date information, presented to us in the context that is relevant at that particular time. Yes, we may be able to find this information in a boring document somewhere, but wouldn’t it be better and more exciting to get the most up-to-date info from inside someone’s head? Now I know what you’re thinking, and the answer is no, we haven’t filed a patent for a new technology that indexes people’s grey matter… we’re still old school on this one, and unfortunately we actually have to communicate with them by word of mouth (preferably over VOIP or video call – or heaven forbid a face-to-face encounter). However, before the aforementioned communication can take place, we actually need to find the person. Given that we have over 70,000 employees worldwide, it could take a while if a trial-and-error approach was adopted. Instead, I can use our Enterprise Search tool (based on SharePoint 2007 of course) to find people. I don’t need to know their names, which is a good thing because if I knew them already I probably would need to do a search for them. All I need to do is look for the expertise and perhaps their location to narrow it down a bit. For example, I can search for “Groove UK” and it will return the results of all people who have something to do with our Groove product in the UK. If I left the “UK” bit out, it would find me Groove experts from all over the world.

With presence integrated with the search results, I can start an Instant Message conversation, phone them or even start a video call right then and there. This is very different to the world of Internet search where you are primarily looking for content. The exception would be the advent of social computing tools where you can indeed search for people (that’s the point of the social network), but it is usually from within that particular social network, rather than from the web search environment. With Enterprise Search tools, you should be able to find content or people from within the same environment (usually the main Intranet site).

So what’s the business benefit?

For Microsoft, our Enterprise Search on our Intranet saves us time and makes us more productive. We’ve worked out that most people spend a lot of time looking for customer information in our Siebel CRM system. By integrating a “customer search” into our Intranet portal, we reduce our time to find the relevant information by more than 15-20 minutes. Personally, it used to take me at least 25 minutes to find out who the account manager was for any particular customer in Siebel, look up their contact details in Outlook, phone them only to get their voicemail, send them a mail instead only to get an Out of Office message, go back to Outlook to find out who else in their team may be able to help me, repeated until I find someone.

Using our new customer search tab on the Intranet, I can now get the customer details including the account manager, alongside presence information such as Out Of Office status, and a list of colleagues who may be able to help, all within the search results, delivered in a few seconds. If I do that a few times a day I’ve saved hours of time… which leaves me plenty of time to work on perfecting my espresso making skills.

Rob Gray, Microsoft

« Previous Page