Archive for the 'Design' Category

Thinking like a designer?

Over the last week, I have noticed a flurry of blog posts and articles referring to “design thinking.” This may just be a clustering illusion, though — the idea is not new, nor can I see any particular reason why it would surface now more than before. What I read does puzzle me, though.

San Gimignano

Let’s start with what is meant by design thinking.

Compare and contrast: Design Observer, October 2009: “What is Design Thinking Anyway?” and Design Observer, November 2007: “Design Thinking, Muddled Thinking.”

A quote from the latter first:

When the word “critical” is attached to the word “thinking,” the result, “critical thinking,” is a term that has clear, well defined, and well-understood meaning — certainly in the academic community, if not generally. As a counter example, the same cannot, for instance, be said about the term “art thinking.” This is not a term that can be used in any precise or meaningful way. Why? Because it could mean painting or sculpture; it could mean figurative or abstract; it could mean classical or modern or contemporary. Because it embodies so many contradictory notions, it is imprecise to the point of being meaningless — and therefore, completely understandably, it is not much used, if at all.

“Design thinking” is as problematic a term as “art thinking.” Design thinking could refer to architecture, fashion, graphic design, interior design, or product design; it could mean classical or modern or contemporary. It’s imprecise at best and meaningless at worst. More muddled thinking.

But then the more recent article takes a different view:

One popular definition is that design thinking means thinking as a designer would, which is about as circular as a definition can be. More concretely, Tim Brown of IDEO has written that design thinking is “a discipline that uses the designer’s sensibility and methods to match people’s needs with what is technologically feasible and what a viable business strategy can convert into customer value and market opportunity.” [Tim Brown, "Design Thinking" Harvard Business Review, June 2008, p. 86.] A person or organization instilled with that discipline is constantly seeking a fruitful balance between reliability and validity, between art and science, between intuition and analytics, and between exploration and exploitation. The design-thinking organization applies the designer’s most crucial tool to the problems of business. That tool is abductive reasoning.

Then there is this. Having adopted the “design thinking is thinking like a designer” approach, this site (curated by one Nicolae) goes on as follows.

When design is stripped from forming, shaping and styling, there is a process of critical thinking and creative solving at the very core of the profession. By consciously understanding and documenting this process, a new field within the design domain emerges that deals with the creativity DNA of the design mind. When properly understood and harvested, one can transfer the creative DNA from design into virtually any discipline regardless of brain direction. This process has been recognized by thought leaders as an extremely valuable tool for fostering creativity and driving innovation.

However, this is as far as it goes — there is no further analysis of what this “process of critical thinking and creative solving” might be (apart from a meaningless allusion to the left brain-right brain dichotomy, which is a widespread fallacy[1]). So that takes us no further. (I confess that in my original draft, I was much ruder.)

The reference in this week’s Design Observer piece to abductive reasoning takes us a bit further. Here is what wikipedia currently has to say about that, by comparison with better-known forms of reasoning.

Deduction
allows deriving b as a consequence of a. In other words, deduction is the process of deriving the consequences of what is assumed. Given the truth of the assumptions, a valid deduction guarantees the truth of the conclusion. It is true by definition and is independent of sense experience. For example, if it is true (given) that the sum of the angles is 180° in all triangles, and if a certain triangle has angles of 90° and 30°, then it can be deduced that the third angle is 60°.
Induction
allows inferring a entails b from multiple instantiations of a and b at the same time. Induction is the process of inferring probable antecedents as a result of observing multiple consequents. An inductive statement requires empirical evidence for it to be true. For example, the statement ‘it is snowing outside’ is invalid until one looks or goes outside to see whether it is true or not. Induction requires sense experience.
Abduction
allows inferring a as an explanation of b. Because of this, abduction allows the precondition a to be inferred from the consequence b. Deduction and abduction thus differ in the direction in which a rule like “a entails b” is used for inference. As such abduction is formally equivalent to the logical fallacy affirming the consequent or Post hoc ergo propter hoc, because there are multiple possible explanations for b.

At this stage, then, abduction doesn’t look too promising as a means of solving problems. However, it might be attractive as a tool to suggest solutions which can then be tested separately. This is the way I imagine it being used — as an exploratory technique. This is supported by exploring a reference later in the article to Charles Sanders Peirce. His lecture “The First Rule of Logic” is apposite here. Peirce argued that whatever mode of reasoning is chosen, “inquiry of any type… has the vital power of self-correction and of growth.” Following from this, “it may truly be said that there is but one thing needful for learning the truth, and that is a hearty and active desire to learn what is true.” We then come to the heart of his argument.

Upon this first, and in one sense this sole, rule of reason, that in order to learn you must desire to learn and in so desiring not be satisfied with what you already incline to think, there follows one corollary which itself deserves to be inscribed upon the wall of every city of philosophy,

Do not block the way of inquiry.

Although it is better to be methodical in our investigations, and to consider the Economics of Research, yet there is no positive sin against logic in trying any theory which may come into our heads, so long as it is adopted in such a sense as to permit the investigation to go on unimpeded and undiscouraged.

This opens the way to the kind of instinctive, hunch-following process that appears to be presented now as “design thinking.” I am far from sure that such thought processes are unique to designers or, even, more prevalent in that community. Peirce’s suggested open-mindedness in seeking solutions, followed by clear-headed assessment of the merit of those solutions, is a model that many professionals follow, designers or not.

Neil Denny, in a post critiquing some lawyers’ thinking, points to Edward de Bono’s concept of Po. This idea is essentially the same as abduction — thinking of answers that are entirely distinct from the obvious answers in order to reach a new and achievable solutions. As Neil puts it,

Po lifts us out of the normal patterns of thinking. It does not ask “Is this a good idea?” which invites a critical progression of “…And if not, why not.” Instead, po says “Let’s just accept that the following statement, however nonsensical, however illogical is a good idea. Now, what is good about it? What would work or how would it benefit our organisation, or our clients.”

The idea or the suggestion itself is put forward to stimulate the discussion. The idea can be discarded later once it has identified benefits or methodologies.

As Neil indicates, it is the discussion, or the process by which traditional logical tests are applied, where the work really happens. Going back, again, to an old post of mine, James Webb Young’s A Technique for Producing Ideas (chronologically only slightly closer to de Bono than to Peirce) is just another expression of the same basic process.

The process can be distilled into a small set of key points:

  1. Desire to learn, adapt, or create
  2. Always be open to possibilities (however odd they may seem)
  3. Choose potential solutions intuitively and imaginatively
  4. Test the chosen solutions rigorously
  5. Discard failed (and failing) solutions (including the status quo), however attractive they may appear
  6. Learn, adapt or create
  7. Return to the beginning

This is a hard discipline, and it has to be maintained for best results.

Interestingly, if you persist in concentrating on the things you already know and are familiar with, if you avoid opening your eyes to the widest variety of options, you are likely to be persistently unlucky. Richard Wiseman has reached this conclusion after studying luck and luckiness for some years.

[U]nlucky people miss chance opportunities because they are too focused on looking for something else. They go to parties intent on finding their perfect partner and so miss opportunities to make good friends. They look through newspapers determined to find certain types of job advertisements and as a result miss other types of jobs. Lucky people are more relaxed and open, and therefore see what is there rather than just what they are looking for.

My research revealed that lucky people generate good fortune via four basic principles. They are skilled at creating and noticing chance opportunities, make lucky decisions by listening to their intuition, create self-fulfilling prophesies via positive expectations, and adopt a resilient attitude that transforms bad luck into good.

Wiseman’s work is extremely interesting, and worth exploring in more detail. (For those in Manchester at the end of the month there is even an opportunity to hear him speak as part of the Manchester Science Festival.)

It is important, however, not to get too carried away with intuition. When dealing with abstract problems, our brains tend to think in a way that can lead inexorably to error. The clustering illusion that I referred to at the beginning, together with a host of other cognitive errors, can be a real problem when assessing probability and statistics, for example, as Ben Goldacre specialises in showing us. If design thinking just means being supremely imaginative and doggedly intuitive, it is not likely to be a formula for success. If however, it is a shorthand for creative thinking coupled with critical assessment against objective standards (whether those are rules of logic or just client imperatives), then it is undeniably good.

But let’s not allow the designers to think it is their unique preserve.


[1] The reasons why this fallacy persists are beyond my scope here. However, the idea of a clear division is a fallacy. Although the mechanism is not fully understood, the brain almost certainly needs to involve both halves to function properly. Take this statement by Jerre Levy, in “Right Brain, Left Brain: Fact and Fiction,” Psychology Today, May 1985, for example:

The two-brain myth was founded on an erroneous premise: that since each hemisphere was specialized, each must function as an independent brain. But in fact, just the opposite is true. To the extent that regions are differentiated in the brain, they must integrate their activities. Indeed, it is precisely that integration that gives rise to behaviour and mental processes greater than and different from each region’s contribution. Thus, since the central premise of the mythmakers is wrong, so are all the inferences derived from it.

The New Scientist has also covered the issue (only available in full to subscribers, although it is possible to find versions of the article around the internet).


Don’t overdo it

When we think about and plan our KM activities, it can be tempting to imagine a marvellous future wherein all our firm’s know-how is carefully nurtured, categorised, exposed for all to see, tagged, analysed, or whatever it is we think would be the best outcome. However, as the Bard of Ayrshire put it: “The best laid schemes o’ mice an’ men/ Gang aft agley.” Why is this?

Gigha boatscape

One good reason is pointed out in Gall’s Law:

A complex system that works is invariably found to have evolved from a simple system that worked. The inverse proposition also appears to be true: A complex system designed from scratch never works and cannot be made to work. You have to start over, beginning with a working simple system.

I am indebted to John Gruber for the pointer to this formulation. He uses it to explain how to understand Apple’s strategy with regard to the iPhone.

If there’s a formula to Apple’s success over the past 10 years, that’s it. Start with something simple and build it, grow it, improve it, steadily over time. Evolve it.

The iPhone exemplifies this strategy. There’s a long list of features many experts and pundits claimed the original 1.0 iPhone needed but lacked. Ends up it didn’t need any of them. Nice to have is not the same thing as necessary. But things the iPhone did have, which other phones lacked, truly were necessary in terms of providing the sort of great leap forward in the overall experience that Apple was shooting for.

At this point, it is worth noting an essential qualifier to Gall’s Law: “A simple system may or may not work.” In the case of the iPhone it clearly did work. In other cases, Apple decided that it did not work.

What Gruber brings over and above a simple assertion of Gall’s Law is an insight about how to choose the original simple system: “It’s not enough just to start simple, you have to start simple with a framework designed for future evolution and growth.” When the iPhone was first launched, it was not particularly full-featured as a phone: it was not 3G; it did not support MMS. It even fell short on the music front, as it cost significantly more per gigabyte than any of the iPod range. However, as Gruber points out:

Apple started instead with the idea of a general-purpose pocket-sized networked computer. It no more has a single main purpose than a desktop PC has a single main purpose. Telephony is simply one feature among many, whereas on most other phones, the features are attached to the side of the telephone. They sold 30 million iPhone OS devices in the first 18 months after 29 June 2007, but 13 million of those were non-phone iPod Touches — proving that the platform is clearly appealing even when the “phone” is entirely removed. (Consider too that the iPhone’s two strongest competitors are BlackBerry and Android, neither of which started as phones.)

The iPhone was not conceived merely as a single device or a one-time creation. It’s a platform. A framework engineered for the long-run. The iPhone didn’t and doesn’t need MMS or a better camera or a video camera or more storage or cut/copy/paste or GPS mapping or note syncing, because the framework was in place so that Apple could add these things, and much more, later — either through software updates or through new hardware designs. The way to build a complex device with all the features you want is not to start by trying to build a device with all those features, but rather to start with the fundamentals, and then iterate and evolve.

We should learn the same lesson with our knowledge systems. Not to try and predict all the features that might be useful in the future — that way lies excessive complexity coupled with early obsolescence and failure. Instead we should imagine and create the best platform for future possibilities — as simple as possible, but as open to development as necessary.

Beauty, truth, modernity, tradition

I have just read a perfect summary by Stephen Bayley of one of the principles underpinning my thoughts on this blog.

For me, the debate was a chance to go rhetorical about the single cultural principle I hold most dear: that history and tradition are things you build on with pride and conviction, not resorts you scurry back to when you can think of nothing better to do. I believe that to deny the present is to shortchange the future. These things I learnt from Nikolaus Pevsner.

Bayley was reporting on the National Trust ‘Quality of Life’ debate, “Britain has become indifferent to beauty.”

In Bayley’s account, the debate sounds very stimulating. Supporting the motion were David Starkey and Roger Scruton. Bayley caricatures them thus:

Starkey and Scruton see culture as a serial that has been recorded in episodes and canned in perpetuity for posterity. The task, in their view, is not to augment architectural history with up-to-date improvements, but regularly to revisit the past for edification and instruction.

Bereft of optimism or enthusiasm, bloated with sly and knowing cynicism, they see no value in contemporary life.

Opposing the motion were Germaine Greer (“after Clive James, our Greatest Living Australian National Treasure”) and Bayley himself. The outcome of the debate? The motion was lost resoundingly. Clearly the audience was convinced by the notion that beauty was not fixed at some past time, but is still being made, albeit in a different tradition.

This was not because we were so very clever, but because Starkey and Scruton were so very wrong. And what was the turning point? One, Greer said what a beautiful spring day it was. Whose mood was not enhanced by sunshine and flowers and blue skies? No dissenters, there. Two, in despair at their negativism, cynicism and defeatism, I asked Starkey and Scruton: “Why is it I like what you like (which is to say: medieval, renaissance and Victorian), but why you are so limited and snitty and crabby you see no value in what I like?” No dissenters here, either.

Wonderful to prove that the British are not, indeed, indifferent to beauty.

Reading Bayley’s account, I felt that the traditionalists’ view was not just applicable to beauty. Many things, including language and weights and measures are held by some to be better in some historical form. On the other hand, I am not sure that the resistance to modernity is a related to fear of change, which is how it is often characterised.

The problem, I think, is that we see the past in a sanitised form. The things that are left from bygone eras tend to be the most beautiful. However, we forget this and assume that we see a true picture of what our forbears experienced. Keats’s grecian urn is a prime example.

Famously, Keats’s poem ends with an assertion that truth and beauty are inseparable. For me, however, the phrase before that is more interesting:

When old age shall this generation waste,
Thou shalt remain, in midst of other woe
Than ours, a friend to man, to whom thou sayst…

Keats appears to be suggesting that the urn will always persist because of its beauty. Given the fragility of antique ceramics, this must be a forlorn hope. In general, however, the probability of survival of any given artefact must surely be proportional to its beauty: people are more likely to take care of such things than they are of their uglier counterparts. As a result, our view of the past is inevitably a sanitised one, containing only the good parts, with little of the bad.

By contrast, we experience all of the present — the good and the bad. Sometimes it is difficult to tell which is which. In the face of such uncertainty, it is not surprising that some people prefer to turn against the present and seek solace in the past. I think this is where Scruton and Starkey sit, whereas Greer and Bayley are happy to explore the present — risking the possibility that what they regard as worthwhile will turn out with the passage of time to be ugly and worthless.

I think they are right to take that risk. To do otherwise is to fail to take part in the process by which the things that are worthwhile are preserved for future generations. We need to remember to do the same in our organisations — not to hold on to repositories of old knowledge just because they are old, but to open our minds to the possibility of the creation of new knowledge by whatever means (and to risk some of that new knowledge being worthless).

White space, thinking, speaking, doing

Compare these two images.

Despite the fact that the left-hand advertisement proclaims its message in bolder and larger text than the right-hand one, I think the right-hand one has a greater impact. However, in some contexts an advertisement like the one on the left would be entirely appropriate. The image, and the insight, are taken from an interesting article by Mark Boulton at A List Apart on the use of whitespace in design.

The content is the same on both designs, as are the other elements, such as photography. Yet the two designs stand at opposite ends of the brand spectrum. Less whitespace = cheap; more whitespace = luxury.

A lot more goes into brand positioning than just whitespace, but as a brief lands on your desk for a luxury brand, it’s very likely that the client—and their target audience—expects whitespace and plenty of it to align the product with its competitors.

It is clear from the article that a key part of the designer’s job is as much judging how much to leave out as deciding what to put in. I think there is something there for lawyers to learn too.

It is difficult for someone with clearly defined skills, tasks and tools to hold back from doing what they do. A blacksmith with a hammer and an anvil needs to use them quickly and effectively. Too much time spent pondering where to strike the hot iron is not time well-spent. Likewise, a lumberjack shouldn’t pause mid-way through felling a tree. On the other hand, good craftsmen will plan their work carefully — “measure twice, cut once” is not a meaningless mantra — and so wielding the appropriate tool is not usually the first thing that they do. Sometimes I think this is not a discipline that comes easily to professional services advisors.

When a client comes to us with a problem, our natural inclination is to flex our muscles. “I see what your problem is; I’ll draft this document and we can start clearing things up…” Because of the tyranny of the billable hour (a topic best dealt with elsewhere), we need to show that we are solving problems with recorded time and demonstrable outputs (documents, meetings, e-mails, phone calls). Often, however, the client is not interested in those things — their focus is on the outcome, not the output.

A little while ago, Bruce MacEwen asked ”Are you beginning to get the same creepy feeling I am, that large organizations discourage deep or creative thinking?” This question was prompted in part by a discussion piece on Harvard Business School’s Working Knowledge site: “Why Don’t Managers Think Deeply?” That piece starts thus:

A since deceased, highly-regarded fellow faculty member, Anthony (Tony) Athos, occasionally sat on a bench on a nice day at the Harvard Business School, apparently staring off into space. When asked what he was doing, ever the iconoclast, he would say, “Nothing.” His colleagues, trained to admire and teach action, would walk away shaking their heads and asking each other, “Is he alright?” It is perhaps no coincidence that Tony often came up with some of the most profound insights at faculty meetings and informal gatherings.

I sense that, especially now, the opportunities for creatively doing “nothing” are very limited in law firms and similar organisations. Unfortunately, now is the very time in which we need profundity in our thinking. Our leaders need that space in which to ponder things, so that they can lead us out of the current mess. At any time, when working with clients, we can only produce a better quality outcome by cogitating before drafting. The white space in a magazine layout does not take away from the words on the page — it enhances them. In a similar way, the time we spend thinking about what to do, or write, or say, the better those deed or words are likely to be.

There is another school of thought, exemplified by a light-hearted essay by Heinrich von Kleist: “Über die allmähliche Verfertigung der Gedanken beim Reden” (“On the gradual formation of thoughts while speaking“). It can be read as a carefully thought-out manifesto for blogging.

My dear thoughtful friend: if there is something you want to know without being able to find it out through meditation, turn to any acquaintance you run into to talk about the matter. There is no need for him to be a sharp mind. Also, I do not mean to say that you should ask him about this matter: Oh no, never! Rather, you should tell him the solution yourself. I can see you making big eyes and telling me that you have been advised earlier to speak of nothing except of what you understand. But at that time you may have had the mad ambition to instruct others. but I want you to tell him so you instruct yourself!

The French say l’appétit vient en mangeant, and this empirical maxim remains true if one makes a parody of it and says l’idée vient en parlant.

Often I sit over my papers and I try to find out from what angle a given conflict has to be judged. Usually, I look into the light, as the brightest spot I can find, as I try to enlighten my inner being. Or else I seek out the first approach, the first equation which expresses the obtaining relations, and from which the solution may be derived simply through plain arithmetic. And look what happens: as soon as I talk to my sister — who is sitting and working behind me — about this matter, I realise what hours of hard thinking have not been able to make clear to me. It isn’t as if she was was telling me in any direct sense. She does not know the law, and has never studied her Euler and her Kästner. Neither is that what she leads me to the crucial point through deft questions — although this latter case may occasionally occur. But since I have some vague thoughts that are in some way connected with what I am looking for, then once I have embarked on the formulation of the thought it is as if the need to lead what has been begun to some conclusion transforms my hazy imaginations into complete clarity in such a way that my insight is completed together with my rambling sentence.

I don’t think Kleist is proposing a different approach to the pursuit of white space in our work. Rather, he is suggesting a way of dealing with the inevitable consequence of thinking: thoughts. When we ponder, we may generate many possible solutions to problems. We are then faced with the difficult task of gauging which of those solutions is the best. Alternatively, some of our thoughts may be more fully-formed than others, and we need to guard against them — the inchoate ideas may actually be the better ones. If we do as Kleist advises, we can start to see how things fit together or how they might be flawed. For me (and for others, I suspect) this is one of the benefits of blogging. It helps me sort things out in my own mind, even if nobody else takes notice. (But many thanks to those of you who do, of course.) It works in other contexts as well. In the programming context Scott Ruthfield says: “when you’re stuck, write it down.”

Say you’re trying to figure out how to do something in [pick a framework], and you’ve Googled the heck out of the most-likely search terms, and nothing’s coming up.

Then write down your question as if you were going to ask a teacher/email it to a friend/post to a Google group/etc. Write down all the details: explain the thing you’re trying to do, the problem you have, and the number of things you’ve tried. Be as clear as you can, but don’t worry about being concise.

Literally every single time I’ve ever done this – and my rule-of-thumb is to do it after ~1.5 days worth of trying to figure it out myself – I find a number of new avenues to try, and almost always solve the problem on my own.

Putting these elements together, we can see that effective use of white space in our work comes when we combine thinking time with active reflection through the recording of ideas, questions, thoughts, half-baked conclusions. That will allow us to see what we know that will help the client achieve the outcome they want (or identify the gaps that can be filled by others). As a result, this approach will produce a better-quality product — as we saw at the outset, that is one of the consequences of carefully-used white space. Doing without thinking leads to the kind of cluttered, shouty, low-quality output that is exemplified by the first picture at the top of this post.

(Scott Berkun adds another benefit to writing without thinking too much about the output. It can break through a blockage. “The secret, if you can’t start, is to begin without constraints. Deliberately write badly, but write.” That is a different issue from the one I have touched on here, albeit similarly challenging.)

Lawyers: architects or bricklayers?

Yesterday lunchtime I managed to get out of the office for a walk at lunchtime. As I did so, I pondered a question that has been at the back of my mind for some time. It is my impression that innovation in law firms tends to occur most in the delivery of legal services, client care or in some peripheral law firm activity (marketing, finance, IT, etc). It is fairly rare that we see real innovation in the law itself coming out of law firms. (Some evidence for this impression is provided by the annual Financial Times survey of innovation in law firms.)

As I pondered and wandered, I admired the characteristic brickwork of Manchester’s historic cotton warehouses. Cruelly, I wondered whether many lawyers were simply bricklayers — putting the right blocks together in a particular way to achieve the desired result: an agreement or set of agreements to achieve the commercial aims of their clients. Extending the analogy further, there are significant similarities between the creation of a new building and the conclusion of a corporate or commercial transaction.

At the outset there is a client and the client has a need. No legal work is done without an external driver. Similarly few if any buildings are created purely speculatively. The client’s need (for a building to fit a particular purpose or for a new acquisition) is usually arrived at entirely without interference by professional specialists. However, once the need has crystallised, the professionals are needed to make the need a reality: an architect in the case of a building, a lawyer in the case of the transaction. At this stage, the client’s need might permit innovation (in building design or in legal structure). However, it is almost impossible for that innovation to create an opportunity for a new type of client need.

An example of the kind of innovation I mean is the development of steel-framed structures. Once the potential of that kind of building was realised by clients, the development of densely-built cities like New York and Chicago became possible. I can’t think of a legal innovation with an equivalent impact on the scenery of business, work, trade or commerce. (That is not to say that there isn’t one — it is late and my mind is tired.)

So at least one lawyer seeing to the client’s needs is an architect – creating the best structure to deliver what the client wants, dealing with other professionals (including regulators), managing key specialists (including hod-carrying lawyers), and ensuring that the client is kept happy. Innovation in all of those areas is possible, but it must be secondary to the need to deliver what the client needs as effectively as possible. In many situations (probably the vast majority), that effectiveness is probably most likely to come from doing the usual job. Similarly, many architects might want to be innovative, but ultimately the client wants something from the pattern-book, so that is what they get.

If my analogy is correct, it must have implications for our KM efforts. There is scope for KM to support innovation, but bricklaying lawyers need a different kind of innovation than the key architects. And innovations created by the architects might never relate to technical legal issues. How do we support them without knowing where the opportunities are?

Ceci n’est pas un pipe

A story in the New York Times about Nokia’s work on human behaviour illustrates beautifully how things we create often end up being used for very different purposes.

Someone working in Kampala, for instance, who wishes to send the equivalent of $5 back to his mother in a village will buy a $5 prepaid airtime card, but rather than entering the code into his own phone, he will call the village phone operator (“phone ladies” often run their businesses from small kiosks) and read the code to her. She then uses the airtime for her phone and completes the transaction by giving the man’s mother the money, minus a small commission. “It’s a rather ingenious practice,” Chipchase says, “an example of grass-roots innovation, in which people create new uses for technology based on need.”

Rather than ignoring this innovation, Nokia employs people (like Jan Chipchase, quoted in the snippet above) who explore how their phones are used in the wider world. And Nokia acts on what they find.

Influenced by Chipchase’s study on the practice of sharing cellphones inside of families or neighborhoods, Nokia has started producing phones with multiple address books for as many as seven users per phone. To enhance the phone’s usefulness to illiterate customers, the company has designed software that cues users with icons in addition to words.

For me, this is an example of how our knowledge needs to step beyond the temporary boundaries that we have set for it. Nokia is a really interesting company. It started as a paper company, but diversified very early — into electricity generation. The other two companies that merged into the Nokia Corporation in 1968 operated in the rubber industry and in cable and electronics. With such a hybrid background, it is not especially surprising that Nokia moved so well into telecommunications.

This link between diversity of influences and innovation has been made in the context of law firms as well: Law Firm Innovation out of Purposeful Imagination. A quote:

Opportunities are also created by events. But those at the right place at the right time usually didn’t get there just by accident. As the French scientist Louis Pasteur said, “Chance favors only the prepared mind.” Purposeful imagination should include thinking about things that could happen and then imagining how they could happen differently. It is about doing so with an eye toward the opportunities those events would present for the firm.

In case one might think that this is something one can pick up from a book, Dave Snowden puts us right (“..sapping the vigor of the mind”):

There is a huge difference between a chef and a user of recipe books. The recipe book user (for which read the manufacturing model of consultancy) uses best practice to assemble the same ingredients in the same context to produce the same meal, time and time again. If they come into your kitchen, it will have to be re-engineered to confirm with the requirements of the recipe before they start to work (and you will pay in many ways for that). The Chef in contrast can work with whatever ingredients and utensils you happen to have to hand and create a great meal.

It is all about preparedness, imagination, ideas, innovation and expertise.

If books were valued according to their price per page, A Technique for Producing Ideas would be one of the most valuable that I own. In fact, its real value is entirely consistent with its cost of 10 pence per page. The book outlines a simple technique to generate ideas. Although it dates from the 1940s and is directed at people working in advertising, it contains insights that we can all still benefit from. (The author, James Webb Young, is ranked above Rupert Murdoch in a list of the top 100 players in advertising history.)

It feels a bit strange to summarise a book that is already very concise, but I’ll give it a go, using quotations from the text.

The starting point is one that should be familiar to people working in knowledge management:

In learning any art the important things to learn are, first, Principles, and second, Method. This is true of the art of producing ideas.

Particular bits of knowledge are nothing, because they are made up of what Dr. Robert Hutchins once called rapidly aging facts. Principles and method are everything.

So with the art of producing ideas. What is most valuable to know is not where to look for a particular idea, but how to train the mind in the method by which all ideas are produced and how to grasp the principles which are at the source of all ideas.

So what are the principles and method?

There are two principles:

  • An idea is nothing more nor less than a new combination of old elements
  • The capacity to bring old elements into new combinations depends largely on the ability to see relationships

The way these principles work can be seen by looking at the method, which has five stages (as summarised by Anecdote):

  1. Gather raw material
    You need to collect specific and the general information about the issue you are working on. It’s important to be a maven and get interested in the peripheral areas and keep saying to yourself, “this might be useful.”
  2. Digest the material
    “This part of the process is harder to describe in concrete terms because it goes on entirely inside your head.” Play with the material you’ve collected. Look at it from different angles and perspectives. Don’t be too literal, use metaphors and most importantly jot down partial ideas as they come to you, regardless of how crazy they seem. Keep going until you get to the hopeless stage and everything seems like a jumble.
  3. Put the issue out of your mind completely—an incubation period
    Forget about the problem and just like Sherlock Holmes, abruptly drop the case mid-way through and got to a concert. Do anything that keeps you mind off the issue at hand and engages your emotions.
  4. An idea will appear
    At some point the “ah ha!” moment happens. Don’t let it slide past. Write down the idea immediately.
  5. Expose the idea to reality
    The idea is likely to need work. So now is the time to build it up, think about the practicalities, and work out how it might really work in practice. Test the idea with colleagues and clients and be ready to adapt.

The more widely one reads and digests, the better the source material for ideas (in any walk of life). This is an area where knowledge management can help. When talking about the first and second stages of idea generation James Webb Young refers to his habit of keeping a scrapbook of things that occur to him, and a set of index cards to help categorise the things he sees and likes, so that they can readily be brought back to mind when necessary. These are tools for personal knowledge management.

Nowadays, however, we can do better than this. Del.icio.us is a kind of digital scrapbook, consisting of things that people see on the web that might be of interest at some point. Rather than index cards, users can use tags to classify things in a way that makes sense to them. Because the ’scrapbook’ is online, anyone else can see it too. (Although it is possible to mark it as private.) You can see my things at http://del.icio.us/innominate_lex.

The final stage in the ideas process is probably the hardest one. This is where Nokia’s experience shows. They take the insights from their research and create prototypes and examples of potential designs. Those are then tested out with potential users, generating new ideas and insights. Nothing could more clearly demonstrate how development is never static. Our knowledge should also be dynamic, and therefore any systems we design and use to improve that knowledge must reflect that dynamism.


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,222 other followers

RSS Recent mini-blog posts

  • An error has occurred; the feed is probably down. Try again later.

Recent micro-blog posts

Categories

Interesting stuff...

Bookmark and Share

When…

May 2013
M T W T F S S
« Nov    
 12345
6789101112
13141516171819
20212223242526
2728293031  

Follow

Get every new post delivered to your Inbox.

Join 1,222 other followers

%d bloggers like this: