Library clips

sharing ideas thoughts and feedback

October 16, 2008

Taskonomy : assembling for use

Filed under: km, process

Patrick Lambe has a great video presentation on information neighbourhoods.

He firstly presents a typical framework of the islands or assets of information in an organisation (eg. repository, applications, Intranet), which are glued together as a content management system, tags, taxonomy, search, etc..

He then displays a workers personal information cloud including more objects like share drives, email, phone, instant messaging, SMS, people, web, etc…

When he asked the audience how do they get things done, the main answers were: email, people, phone, web

This is a predictable answer, people go to people for help, we have conversations, we are each others filter or information scent. And of course the idea of social tools like social bookmarks, blogs, wikis and social networks is more in tune to the flow of human behaviour.

I posted not long ago about knowledge tools being embedded into our flow of work, rather than being servant and frustrated with rigid tools, or having to stop and visit islands to seek stuff, then have to dive back into our flow.
Now we can use new flexible and unstructured tools, and put our own complexity into them to suit our needs, kind of like sculpturers of flow.

Another aspect is drawing pieces from the islands of information (these filing cabinets) and creating our own interfaces, to use as a toolkit, perhaps for a project team. eg. a startpage, or shared startpage.

At the moment we can even assemble these social tools into a flow, but we wait for the day when the current rigid business process tools allow us to re-model them as movable pieces.

Patrick gives an example of a taxonomy as important for a Blacksmith when they go to the shop and look to replace one of their tools. They can use a faceted search, locating by type, size, brand, etc…

But when it comes to the Blacksmith organising their own workstation, they instead group the tools by place, that is, the tools live in the flow of where they are used.

Patrick refers to an article who call this assembly of information to meet a current task as a Taskonomy:

“…what the taskonomy does is bring the usability of the information being organised closer to the user. Taxonomists cannot remain in the back storeroom keeping the shelves tidy. They also need to venture into the storefront and see how customers need their information organised for use.”

This is what we need in organisations, we need startpages, we need integration into workflow (eg. edit this, blog it), we need re-mixing (assemblage or mashups of small pieces loosely joined), we need filtering (re-mixing feeds), we need connection and expression (blogs and networks), etc…

The taxonomy as the organised filing cabinet with many points of entry and search is great, but we need to pull pieces from it to build an on-the-fly toolkit, that is be able to arrange the information objects in the context of how we plan to “use” them.

The presentation later gets into the design and integration of information assets on a page offering, using pertinent and related information. That is drawing from the filing cabinets and presenting (or assembling) an interface for the need at hand.

An example is given of a BBC sports page of a current match score
- it also shows statistics, archive, replay, photo’s
- and related stories and actions like bookmark it, email it, rate it, print it, leave a comment

Read all about it at this post, Building Information Neighbourhoods, and the more philosophical post, How to Kill a Knowledge Environment with a Taxonomy

October 15, 2008

Roundup : Edit Current Website, Print What You Like, WordOff, Encode/Decode HTML Entities, Schmap.me

Filed under: tools, roundup

Edit Current Website - edit any webpage like a wiki, see annotate and others

Print What You Like - print any webpage into a super friendly format [via DI]

WordOff - Clean your HTML [via DI]

Encode/Decode HTML Entities - ever wanted to publish code without it actually presenting as HTML, rather you just want to publish the raw code

Schmap.me - a webpage to show your profile and location on a map, you can put a button on your blog, if people ever want to know how to get to your office or house you can send them your Schmap.me URL, even put your URL in your email signature

Roundup : excla.im, Twitterkeys, Dwigger, Social Tops, Tweader

Filed under: tools, roundup

excla.im - Since Twitter has dropped it’s IM feature (which was broken), we have a 3rd party replacement…also see TwitterIM, and whatever happened to IMified Twitter.

Twitterkeys - add symbols to your tweets via a bookmarklet
eg. I ♥ you, you make me want to ♫

Dwigger - memedigging for Twitter. Enter a tweet URL or write a tweet within Dwigger and wait for the comments and voting [via m]

Social Tops - how many popular Twitter sites can you get, also see TweetMeme, TwitLinks, Twit(url)y and others

Tweader - what I like about Jaiku is that when you reply to a post, your reply becomes a post itself in the stream, but at the same time it’s also a threaded comment under the post you are replying to.
Twitter can’t do this as when you reply by SMS, how does it know which tweet you are replying to, instead it default threads it under the last tweet, as well as becoming a tweet of its own. As a result of this you won’t see a comments stream under a tweet.
BUT, if many people reply to a tweet before that person makes a new tweet, this can be shown as a threaded conversation using Quotably. Twitter could easily do this, it’s just bunching up the replies between your last tweet and your next tweet. But we still have the problem that if you make a new tweet, a person can no longer direct a reply to your previous tweet, instead it will be threaded under the new tweet, which means the conversation sometimes doesn’t make sense. Tweader like Quotably does not achieve anything new…also see TweetDeck.

Sometimes people use #hashtags (and track them at Twemes), but this is more tweets about a topic, event, subject, etc…you can even limit this to a bunch of people using Twitter Teams, and Twitter Soap comes close to threaded tweets, but still it’s not an easy and regular way to have threaded conversations.

BONUS
Connect The Tweets

October 13, 2008

Wikis for exceptions and process failures

My previous blog entry was a follow up on flexible tools not being immune to being used the wrong way. My example was the danger of using a blog as a solution centre due to its news type nature, and rather using a wiki for an official solution centre.

In that example, wikis were described as a place to house explicit information, whereas the blog was more explanatory tacit based information, perhaps containing the know-how behind the solution.

Why is the blog entry important?

We may not be aware that the wiki solution page that we are reading, with a little altering, can also fix our current error we are troubleshooting.

Why?

The wiki solution page may not have much context, it’s just, “when you see this error, use this solution”.
The good thing about this is the page is succinct, we don’t want to be reading forever when we are researching for a solution.

But if that wiki solution page points to a blog entry about the experience of coming up with that solution, we may find we can apply these same techniques to our current troubleshooting.

This is the difference between explicit and tacit, with tacit know-how we learn, rather than just being informed.

It can be done without a blog

You don’t have to have a blog to share the anecdote about your troubleshooting experience, you could have a link on your wiki solution page to another wikpage that is a space for anecdotes about the solution. I just like the idea of a blog format listing a diary of experiences in time, like reading the daily news (again, this is learning by building anticipatory awareness).

Wikis vs Documents

So at the moment a wiki is preferable as a solution centre over a folder with a bunch of documents, as the website format is more usable, and one-click edit is very easy compared to having to launch a Word document in a Document Management System (DMS).
I guess a website feels like a sense of place, more a one stop shop compared to a document in a folder, a website just has more character, a front door, etc…

Know-how expressed as both explicit and tacit

Using the example above, the fact that people are taking the time to add a solution to a wiki is an act of sharing their know-how. Even though I have called it “explicit”, it blurs the line as know-how is usually synonomous with “tacit”. Perhaps it’s better to say that they share their know-how in the wikipage in a more explicit and summarized way, and they share this same know-how in a more tacit and personal way in the blog entry.

In fact I described the different ways to express information in an entry called the KM Core Sample.

Whether explicit (more formal) or tacit (more informal) we are happy that people are sharing at all, and as facilitators we are to concentrate on creating conditions for it to happen more often.

Wikis reach what procedures cannot forsee

Wikis are really valuable for people to pool their know-how for incidences where there are process failures and exceptions to the rule.

Some members of a Document Control team at my work use an Excel document (stored in the DMS) to list exceptions to procedures or just little steps that are not able to be known upfront in a procedure…we hope wikis will cover this space.

A procedure or a best practice cannot cover every context, and some clients and situations have different needs, which means we need to be able to make our workflow flexible and also keep everyone in the loop of what’s going on and how to do things that procedure’s simply cannot cover (they are thick enough already, and are not clairvoyant anyway).

Actually I mentioned this point in my KM Review article:

“These types of interactions enable learning to occur in a more informal and social way; a way we cannot cater for upfront; and a way that brings to light answers and workarounds for contexts and situations that arise, as well as those that already exist.”

There’s always a documented formal way in how to do things, and then there’s the way things are really done. I think a wiki is sharing and documenting how things are really done, they reflect the reality of where a manual cannot reach.

In a learning perspective this is the difference between formal learning (training) and informal learning (social on the job). I heard the other day that 80% of what we learn to do our job, is contextual on the job learning by experience, and 20% is from formal training. Put another way why do we spend 80% on training, when it effectively relates to only 20% of learning…this is based on the Pareto Principle of 80% of the effects come from 20% of the causes.

See more on a comparison of Learning 1.0 vs Learning 2.0.

BRP - Barely Repeatable Process

Ross Dawson explains the need to complement an ERP - Easily Repeatable Process, with a BRP - Barely Repeatable Process:

“Typically exceptions to the ERPs, anything that involves people in non-rigid flows through education, health, support, government, consulting or the daily unplanned issues that happens in every organisation. The activities that employees spend most of their time on every day.
Processes that often starts with an e-mail or a call. A process volume, measured by time and resource spent at organisations, probably larger than for the Easily Repeatable Processes.
These are mostly handled and organised - frameworked - by systems like paper based rules and policies, e-mail, meetings, calls and now in more modern organisations by wikis and other collaboration systems and methods.

Known by extensive loss of information (e-mails residing on HDDs), little knowledge acquired and reused (typical research says 70% of problems solved before without being known) and most of all, untrustworthy processes (oops, forgot to send that mail). In other words not an iota (well almost) of business process thinking or methodology applied to this huge untapped area of business processes.”

Not only do wikis offer a communal space to list these exceptions to procedures and workflows that occur due to unplanned events or just the plain reality of situational contexts, so we can do our work, but it can be seen as a knowledge re-use perspective. Once what was just “known” but not written down, is now flowing out of people’s heads onto the communal canvas.
When I’m in a urgent siutation I may not need to wait for a couple of people to get back to me with an answer, as they may have already shared a little scribble about an exception to a process in the wiki.

Ross Mayfield on the same meme:

“The way organizations adapt, survive and be productive is through the social interaction that happens outside the lines that we draw by hierarchy, process and organizational structure. The first form of social software to really take off to facilitate these discussions was email.”

“Most employees don’t spend their time executing business process. That’s a myth. They spend most of their time handling exceptions to business process. That’s what they’re doing in their [e-mail] inbox for four hours a day. Email has become the great exception handler.”

And again, there’s no knowledge re-use when we use a closed system like email to handle exceptions that procedures cannot cover.

Examples

Just say some of your work tools or applications don’t work on certain laptops
- you are never going to get a laptop that works seamlessly with everything, that’s life
- IT could create a wikipage listing tools that don’t work on a particular laptop model, or what you have to do in order to make them work
- I bet a communal effort could whip up a list in no time at all

These little things we take for granted usually come up when we are training someone new.
Like all of us, every job I’ve had I’ve been taught processes, but also been overwhelmed with things like “but on this day, or in this situation, you have to deviate from the norm and do this instead”. You usually hear about 10 of these exceptions and think, how will I ever remember what to do when I need to do it.

Part of my role is in Document Management support. When a project coordinator creates a project there are various post-duties we have to do for projects created with different templates. This is because the templates are being revamped, and procedures don’t cover these in-between stages. Once the new templates come in then everything will be more generic, but for now we need to know what to do different for which template.
There are even local differences, and these differences can’t be part of a procedure, so again this is where a wiki can be used to help you do your job.

The world is complex and contextual, and wikis help ease this situation by pooling the efforts of all the players. Wikis can also display patterns that emerge. If a manager reviews all the exceptions and workarounds in a wiki, it could reveal a usage issue, a bottleneck problem, a safety issue, etc…

Every plant site has procedures, but like everything else these procedures cannot be aware of every situation that can occur, or meet every need, so a site wiki for these heuristics, anomalies, band-aids, exceptions can be communally created by the people who actually work at the site.

A wiki would be doing a site manager a favour in the ways of safety, and possible new inclusion into the procedures…when exceptions become the rule. Now that I think of it, it’s kind of a distant cousin to an online suggestion box.

What I like about this is no-one is in charge or responsible to write such a document, it’s just stuff everyone knows or doesn’t know, so by everyone pitching in we help each other out, there is no effort on just one person, therefore it’s more prone to exist…plus none of us are smarter than the sum of us.

I’m sure everyone has seen a sign when they have travelled and stayed in hostels, that says “if toilet doesn’t flush, keep button pressed till it passes” or “first set shower hot water tap, then turn on the cold water tap”.

But we can’t have signs or post it notes everywhere, and you can’t easily put a sign on intangible things like a process step in using an online application.

Please leave a comment of an example of exceptions and workarounds in your job, that people know (or don’t know), but isn’t written down because it’s not someone’s job duty.

I expect some comments as I think this happens everywhere :)

In this post I describe using wikis for a solution centre and for an exceptions list, but there are endless ways to use wikis, go check it out.

Related

The tacitness of wikis
The value of networked free-form publishing
KM 2.0 : doing your job or giving back to the organisation

October 10, 2008

The emergence of Serendipity 2.0 and Innovation 2.0

In the past many discoveries and innovations have come by accident or by chance, rather than a team hurting their heads with too much innovation think, “no matter how much I try I just can’t think of an innovation”. It doesn’t usually happen if you sit around doing nothing, it happens when you are involved in life, participating, interacting, only it’s not what your chasing, it’s what happened on the way, it’s what’s triggered, it’s the accidents (the gifts from the gods;) etc…

It’s happened to all of us that we are researching on one task and come across a gem we can use for another task…or this gem may take our current task in a new and better direction. I think as long as we are participating and active we increase the opportunity to be exposed to more great information and people, it may just trigger something inside.

Definition

This catalyst, the spark happens by serendipity, here’s what wikipedia has to say at this point in time:

Serendipity is the effect by which one accidentally discovers something fortunate, especially while looking for something else entirely”

“It was once when I read a silly fairy tale, called The Three Princes of Serendip: as their highnesses travelled, they were always making discoveries, by accidents and sagacity, of things which they were not in quest of…”

“…the word is the “sagacity” of being able to link together apparently innocuous facts to come to a valuable conclusion. Thus, while some scientists and inventors are reluctant about reporting accidental discoveries, others openly admit its role; in fact serendipity is a major component of scientific discoveries and inventions.”

“…agree that a prepared and open mind is required on the part of the scientist or inventor to detect the importance of information revealed accidentally”

And a memorable one, “Serendipity is looking in a haystack for a needle and discovering a farmer’s daughter.” Pek van Andel

Examples

The wikipedia page has a vast list of these accidental discoveries in the scientific fields and inventions, here are a few:

“Penicillin by Alexander Fleming. He failed to disinfect cultures of bacteria when leaving for his vacations, only to find them contaminated with Penicillium molds, which killed the bacteria. However, he had previously done extensive research into antibacterial substances.”

“Viagra (sildenafil citrate), an anti-impotence drug. It was initially studied for use in hypertension and angina pectoris. Phase I clinical trials under the direction of Ian Osterloh suggested that the drug had little effect on angina, but that it could induce marked penile erections.”

“Discovery of the principle behind inkjet printers by a Canon engineer. After putting his hot soldering iron by accident on his pen, ink was ejected from the pen’s point a few moments later.”

Enterprise 2.0

Then you have a military type invention like the internet which just can’t help breeding more invention, that’s the thing when you invent a tool that actually allows you to invent more tools…I don’t think we imagined e-commerce, blogging, social networking, wikis, etc…

If serendipity increases the chance of discoveries leading to innovation, then what better than a platform such as enterprise 2.0, where all can participate, interact and network.

I may be researching a few blog posts for my draft post on topicA, and links from post to post take me on another discovery, and I end up drafting 5 new posts…as I investigate these accidental findings I learn.

I browse a social bookmarks tag as part of research, and come across a great article, I then see articles from similar tags, and articles from a particular tagger, and before you know it, I’ve learnt more than I bargained for on this supposed 30 minute research window…see an indepth view.

I have my Twitter @replies turned on to full so I can eaves drop on conversations from people I follow, and the people they follow that I don’t…sometimes I come across some gems.

I search our internal blogosphere and come across an irrelevant post to my needs, but am able to leave a comment on this post as a possible solution. We work in totally different business units, live in different countries, and don’t know each other at all, yet because we both participate and are visible I increase my opportunity for serendipitous affairs, which can lead to innovation.

This serendipity can also be a product in aggregate. If everyone participates and networks on a platform we could view a tag cloud and see some emerging patterns…we could view the frequent tags and realise we need to take action on something, or realise the mood at the moment. Without a participation platform and tagging content, there is no way we would have known otherwise of these emergent patterns, and what they tell us.

The benefit of enterprise 2.0 is it helps us get our work done, share and evolve ideas, and connect with people, but at the same time the same platform exposes us to loads of know-how, quality stuff that we may discover on the way to somewhere else.

Conditions for Innovation

So not only is enterprise 2.0 about sharing know-how it’s about increasing the chances for innovation…see more.

Dave Snowden says KM is about supporting effective decision making and creating conditions for innovation. This really rings true in a KM 2.0 environment as we have the ability and are empowered to connect to the right people and know-how, and at the same time be almost always subject to the conditions of serendipity, which as we mentioned increases the chances of innovation.

He says it himself:

“…its not luck, and yes you can manage for it. By increasing the number and type of things that you pay attention too then you increase the chance of serendipity (which is what SenseMaker does) and various methods such as SNS increase the encounter rations with things which are unusual or novel.”

A comment from Wayne Zandbergen says, “…’serendipity’ happens to those who are prepared to notice it, rather than mere accident…” he goes on to examine the semantics of the term.

Luke Naismith on serendipity and synchronicity:

“He defined serendipity as those events that are somewhat unusual but that are noticed and in that noticing, provide some value to the observer. In contrast, synchronicity is the meaningful coincidence between two seemingly separate events – some form of meaningful relationship between causally unconnected events. I noted that it is often through serendipity, we can find synchronicity.”

“We talked about innovation and the role that people in organisations need to play of looking for the unexpected, those anomalies that fall outside the norm, and to try and ascertain the meaning behind that difference. It goes against the notion of seeking equilibrium or getting things back to the average”

Johnnie Moore points to a post on engineering serendipity:

“…an interesting paradox here, how can we engineer that which is meant to be fortuitous?”…I think we have answered this above, by networking in a participation culture.

Rod Boothby expands on emergence:

“Just as high-level patterns of intelligence emerge from separate brain cells or individual agents within a free market economy, groups can be motivated to create intelligent decisions in other circumstances.”

“Emergent intelligence only evolves when agents have the freedom to act independently. The traditional command and control structures employed by most large firms do not lend themselves to fostering this kind of independence”

“However, that does not mean that there isn’t still a roll of management to play. Their task now is to cultivate an environment that encourages innovation.”

…read more of this post about oblique control, kind of like the light constraints on a complex system.

To learn more Rod has a paper called, Turning Knowledge Workers into Innovation Creators.

Ross Mayfield has a post about the edge (people in enterprise social networks), pointing to people such as Eugene Lee, John Seely Brown, John Hagel, JP Rangaswami, and the Cluetrain:

“The edge of the organization is the source of innovation and growth. Its also where an organization can sense and respond to change.”

“…the edge is the only source of sustainable innovation, and the edge is becoming the core”

“Social interaction often precedes economic activity.”
“Otherwise known as cluetrain. Markets are conversations. Relationship before conversation before transaction.
Just as new solutions are emerging to enable effectiveness for the edge, it may be more critical than ever.”

KM 1.0 ain’t set up for serendipity, nor innovation

…instead we learn from failure and trial and error

I’m not going to get into this for the thousandth time, so you can read these posts about the “anticipating needs, or the maybe one day KM”

Serendipity management

Dave Snowden on Knowledge Management:

“Dave appears to share my disdain for the context-free capture and ‘codification’ of people’s business knowledge in massive ‘knowledge bases’ just in case someone else might be able to benefit from that knowledge sometime in the future (assuming they can find it).”

These blog posts point to Dave’s paper, Managing for Serendipity (alternate link), his offerings to encourage learning and knowledge transfer are: Narrative Databases, Social Network Stimulation, and Disruptive Pattern Breaking.

He concludes that, “…a major area of knowlege management practice should be to create worst practice systems on the grounds that they provide better and more resilient approaches to learning.”

We are not just talking about online here, serendipity and innovation happen using participative and emergent methods such as knowledge cafes, world cafes, anecdote circles, unconference, open space, etc…

Similar to Dave’s paper above Luis Suarez posts about innovation derived from communities, and learning from failures…there is a Ning (social network) on failures called the Mistake Bank.

Dave Gurteen has found a great quote by JK Rowling on failure and living:

“You might never fail on the scale I did, but some failure in life is inevitable. It is impossible to live without failing at something, unless you live so cautiously that you might as well not have lived at all - in which case, you fail by default.”

Jay Cross on Learning from worst practices:

“Stories of failures can be used to generate “worst case scenarios.” People learn more from avoiding failure than from affirming success.”

Mary Abraham on True leaders value mistakes:

“When you’re dealing with an organization that faces liability if it doesn’t reach the right result every time in a predictable, controlled fashion, mistakes take on an even greater importance. Consequently, there can be a tendency to sacrifice innovation and growth for predictability and control. In that environment, mistakes are barely tolerated and rarely encouraged. The problem is that an organization without mistakes is an organization without innovation and growth.”

Jevon MacDonald talks about Google’s trial and error, learning from failure approach…this reminds me of the Safe-Fail approach that I mention later on in this blog post.

Back to Enterprise 2.0

Patti Anklam refers to serendipity as “accidental collisions“:

“…how important it is for search engines to return information about our connections with people who may have the expertise and experience we need to tap. We must also arrange for people to bump into each other (in physical and virtual spaces) who may not know that there is experience available for the tapping. Jim calls this the art of making “accidental collisions” — causing people to bump into each other so they can whatever sparks may be, will ignite.”

Jack Vinson leads me to a post on this topic by Doug Cornelius:

“One thing I noticed in our search for an enterprise search tool is the serendipity factor. People were finding interesting and informative things that they did not expect to find.”

More on accidental collisions by Joe McKendrick:

“This is the old knowledge management conundrum — how can you capture and bottle informal, unstructured data? How do you capture serendipity — someone runs into a business colleague at an event, and learns that so-and-so is leaving because the company pulled support for a project? How do you take it out of peoples’ heads and digitize it?”

It seems a participation network (connected profiles) is always the answer here, as it mimics the conversational behaviours we have in the offline world. Who would have thought that MySpace and Facebook would have been the next innovation tools, see an example by James Dellow, on a bunch of guys forming a band by networking on MySpace. I too came across this scenario when I was listening to the local radio (RTR-fm) the other day when a local band (Apricot Rail) found each other and conversed on MySpace.

This kind of also ties in with Andrew McAfee’s rendition of the strength of weak ties, and expanded in to the enterprise 2.0 bullseye, specifically Facebook, and how the status updates of your weak ties may not be of much care to you usually, but perhaps something they update may be of use for a future need.

I like this quote from McAfee:

“…it can in fact be quite powerful because it’s a quick and easy way to form connections and make associations that might not ever occur otherwise.”

NOTE: Unlike KM 1.0 they are not anticipating this need, they are just updating their status, if you tune into them and it’s useful to you (anticipatory awareness), then the concept of KM has worked.

Brad Hinton too posts about innovation and network ties:

“The gist of the new Gratton book is that “innovation comes from people who cross boundaries (and) talk to people in all areas of the business and outside and bring foreign ideas into their own work”. Gratton rightly points out that most organisations don’t even realise the capacity and power of potential networks inside their own organisation - an untapped and relatively inexpensive resource.”

“A new employee often brings new insights and ideas to a new organisation because they have not been corralled into like-minded teams inside the organisation. Once people become ensconced with people of similar ideas and contexts, the opportunity for innovative ideas tends to break down.”

Jon Mell on serendipity and noise:

“The more you think about the random coincidences that happen on Twitter or on other social software tools, the more you realise that a lot of ideas and moments of serendipity actually come from noise.

So it’s not that noise is unwelcome, just that there is ‘good’ noise and ‘bad’ noise (spam). This relates to the idea that has been floating around the web recently that information overload is actually a filtering problem.”

More on noise by Read/Write Web:

“Some people call it “serendipity,” others call it “passive and opportunistic information acquisition.” (Erdelez, see below.) The less limited the boundaries of your scope of view are, the more likely you may be to find things you didn’t even think to look for.”

More examples

Before we move to the next section here are a few more “happy accidents“:

“An example is that of a drug company seeking an antacid based on amino acids, the building blocks of a protein. When the researcher, having inadvertently spilled some of the crystals, wet his finger on his tongue to turn a page in his laboratory notebook, he was astonished at the taste of sweetness. In this way, the artificial sweetener know as Equal or NutraSweet was born. In another instance, an engineer developing radar sets found that a candy bar in his pocket had melted. With the realization that the unit’s power device was emitting radio waves, the microwave oven was born.”

Examples of attraction and engagement

The Mystery of Attraction on the web - Luis Suarez

Lifestreaming Increases Chances of Serendipity

Dave Snowden on Innovation

Since serendipity may lead to innovation I’ve collected some quotes.

Failure and Innovation:

“Innovation happens when people use things in unexpected ways, or come up against intractable problems. We learn from tolerated failure, without the world is sterile and dies. Systems that eliminate failure, eliminate innovation.”

Creativity and Innovation:

“…creativity is a symptom of innovation not its cause”

and again:

“I have long argued that there are three necessary, but not sufficient conditions for innovation to take place. These are:

1. Starvation of familiar resource, forcing you to find new approaches, doing things in a different way;
2. Pressure that forces you to engage in the problem;
3. Perspective Shift to allow different patterns and ideas to be brought into play.

Creativity is just one way, and not necessarily the most effective to achieve perspective shift. In fact I am increasingly of the opinion that creativity is not a cause of innovation, but a property of innovation processes, its something that you can use as evidence of innovation, but not to create it.”

What inspired this blog post…

Nassim Taleb (The Black Swan) on Trial and Error (stochastic tinkering) and Failure:

“We have psychological and intellectual difficulties with trial and error, and with accepting that series of small failures are necessary in life.”

This is something that Dave Snowden calls a Safe-Fail culture, he expands here.

Back to Nassim Taleb:

“In fact, the reason I felt immediately at home in America is preceisely because American culture encourages the process of failure, unlike the cultures of Europe and Asia where failure is met with stigma and embarrassment. America’s speciality is to take these small risks for the rest of the world, which explains this country’s disproportionate share in innovations. Once established, an idea or a product is later “perfected” over there”

This totally links up with Thomas Friedman’s (The World is Flat) thinking that America is an ideas and design country, which is then passed on to countries like China to process and manufacture. His notion is that America will always be the intelligent and innovative country in this respect, as manufacturing-type countries don’t have time to think as they are busy manufacturing.

Here are a few interesting quotes by Thomas Friedman:

“What the carpenter or nanny has to sell can be bought by only one factory or one family at a time…while what the software writer or drug inventor has to sell-idea based products-can be sold to everyone in the global market at once.”

This is something Nassim Taleb also talks about in relation to the scalability of idea vs labor, which I expand on. The corollary is that ideas based jobs is very competitive, there are many losers, that are not as secure as labor based jobs. At the country level what about all those people in America who are not idea’s inclined and are more labor type workers, how do they fit in an idea’s country.

“The ideal country in a flat world is the one with no natural resources, because countries with no natural resources tend to dig inside themselves. The try to tap the energy, entrepeneurship, creativity, and intelligence of their own people…”

I like the global idea that countries are locked in a global supply chain, kind of like war prevention and self preservation.

BTW - I keep lots of notes from book reading in my Tumblr (archive).

[ADDED 13/10/08: I forgot to add some related stuff like crowdsourcing, recommendation engines and implicitness.]

[ADDED 13/10/08: Tony Hirst in the comments below surfaced this gem by Nanneet Bhusshan, well actually I used Tony’s tool, in which it then surfaced:

“INNOVATION IS AN EMERGENT FEATURE OF A SYSTEM!

When one starts - from any condition in a system, one doesnt know the end result although there is a desire to minimize entropy to reach the objective - sometimes the more one tries to reach the desired objective further one goes - in some cases, the objective may be achieved by moving away from the objective rather than towards it. The inherent stochasticity, entropy and unpredictability of Innovation emergence makes it a science closer to non-linear and complex systems rather than the linear system theory that we are taught!“]

[ADDED 13/10/08: I had some more Tumblr thoughts - We make choices…it’s what we choose…]

[ADDED 14/10/08: Ross Mayfield: “When we implement there is issues of control, we structure apps to automate business processes to drive down cost, in the end this is what everyone replicates, not a sustainable competitive advantage”]

[ADDED 16/10/08: Everything is fragmented—Managed serendipity]

[ADDED 16/10/08: In search of failure]

[ADDED 20/10/08: First, second and third generation innovation practice…]

[ADDED 15/03/09: Fostering Innovation: Lots of Little Fires or One Inferno?]

[ADDED 16/03/09: How Enterprise 2.0 Fosters Innovation: Stop Groupthink]

[ADDED 05/04/09: Do You Need a Failure Target?]

Related

An ecosystem is emerging
Participation is the currency of the knowledge economy

Get free blog up and running in minutes with Blogsome | Theme designs available here

Related Posts Plugin for WordPress, Blogger...