Social Media Silo's
I've been wondering about this topic for some time. I've been rereading The Cluetrain Manifesto and found it's been mentioned there as well. And now with the arrival of Google+ people are wondering if this will be the social backbone (must-read piece BTW!).
What am I talking about? Well, we have all these social tools that support parts of our lives. Some only work on the intranet, some only on the internet. Some are more for personal, private sharing, others are more work-related. Many have approximately the same functionality. So, you always get the question: Where should I share my information (without pushing the same information to all these services at once)? And where do I get an overview of all my social interactions?
I was hoping something like Friendfeed would solve this issue. It did, but then everybody left. I even tried to read tweets in Google Reader for some time. That didn't work well. So my silo's are still in place.
These silo's don't only affect creating of social content, but also consuming. A good step in the right direction is what Disqus is doing for blogs: collecting as much of the social interactions around a blogpost as possible. But what I can't do there is reply to a tweet directly from a blog comment.
And then Google+ popped up. Will Google+ solve this problem? I agree with this piece Google has a good chance. It's at least what they are headed for.
In my experience the overlap in functionality and social silo's are a huge barrier in the adoption of social tools. It's one of the reasons people stick with traditional tools, like email and even Facebook (compared to G+...). Everybody's in the email space, so why move to a space where only part of my social graph is?
I'm curious what your thoughts are on this topic. How do you solve this issue in your daily life?
Enterprise 2.0 The Book by @amcafee, A Review
Some time ago I said: Vacation First. I wanted to share my review of professor Andrew McAfee's book Enterprise 2.0 before I went on vacation. That didn't work out. I wish I could have written this review sooner, because the sooner you read this book the better. I'll tell you why.
Andrew McAfee coined the term 'enterprise 2.0' (in 2006) and has been one of the leading thinkers in the space of applying web 2.0 concepts and tools (or 'collaborative media' as McAfee likes to call them) to the workplace. This book summarizes his thinking over the years. Of course he's been blogging and speaking about this topic. So I was wondering if this book would bring me new insights. Well it did. And to me this is why I love books. You know thinking about the topic you're reading about in a book won't stop as soon as the book has been published. But a book does give you a summary of past thinking and concepts for future thinking. And all that in a limited amount of pages (instead of the endless amount of Internet pages...).
I like the way the book starts. It could have started by describing the new social tools and their underlying concepts. But it doesn't. Chapter 2 starts with several real-life cases we can all relate to. These cases make us reflect on information sharing and gathering problems in organizations. How can be solve them? What is the real underlying issue?
The next chapter goes on to explain the big shift. Is Web 2.0 really a paradigm shift or is it an incremental change? Or even just a hype? And how does this shift relate to businesses? Will it have effect only on the Internet or will it also change the way we do business?
Only then does McAfee go back to the issues mentioned in chapter 2. This interesting chapter explains the research on 'tie strength', pointing to Granovetter's work a.o. (which you should read as well!). Subsequently McAfee picks up every case of ch. 2 and shows how Enterprise 2.0 concepts and tools addresses the needs, whereas 1.0 solutions couldn't do the trick. I think this chapter will be an 'Aha moment' for many readers, definitely for those that are new to these concepts.
This book contains information for people in different stages of understanding and implementing Enterprise 2.0. The book describes 'technologies and technology based communities' like blogs, Facebook, etc. For many there is nothing new here. But what I like about the book is McAfee's honesty. McAfee describes how he got interested in Web 2.0 and how his thinking about Enterprise 2.0 started. He didn't 'get it' from the start, but slowly and steadily started to understand and research it. I think this applies to most people in this space. Almost none can say: I understood it from the start. Most experts in this field started out as sceptics. But then made the leap and started blogging, for instance, and by using social media started to understand and be excited about them. This fact is inspiring to all who just learned about Web 2.0 or Enterprise 2.0. It will hopefully get them started more quickly.
This also relates to one of the last chapters of the book: Red Herrings and Long Hauls. Many think Enterprise 2.0 is an instant success. You just set up a (micro)blog and your organization will change and speed up dramatically. McAfee warns us for this and clearly shows we should organize for the long haul. I think this also underlines the need for management and strategic choices to reap the long term benefits of Enterprise 2.0. Enterprise 2.0 requires deep changes in thinking about organizations, management, employees (users) and tools. Take time to help the organization understand these new concepts and tools.
Furthermore he also points to interesting research telling us that new tools have to be 10 times better than the tools we're using for them to be adopted. So, how much better is microblogging than email? Patience is necessary. Evangelizing, demonstrating, training and explaining as well.
This chapter also addresses the main obstacles (red herrings) to Enterprise 2.0 adoption. One topic I'd like to mention here is McAfee's research shows that "most people know how to act professionally in job-related environments, including digital ones". And therefore he has hardly seen Enterprise 2.0 adoption lead to security breaches like employees sharing IP sensitive information. He also points to the CIA using Enterprise 2.0 concepts and tools. They concluded "that the benefits of better and wider sharing of intelligence information outweigh the risks."
I love the way McAfee advises us to work on the adoption of Enterprise 2.0 concepts and tools. He starts out by saying we should connect with believers. Employees already convinced of the importance of social media and their use for organizations. Have them help educate and evangelize. Another important point he makes is to connect to the existing tool set. We use email a lot. So start there.
This book definitely calls for a follow-up! Topics for the next book could be about the following:
- There's lots of discussion about how the social tools relate to formal business and information processes. How this can be done and companies are actually doing it, is a great topic to systematically write down in a book. This would extend what McAfee says about 'in the flow' and 'above the flow' on page 184.
- There's some debate about what comes after Web 2.0. O'Reilly and Battelle call it 'Web Squared'. What does this mean for Enterprise 2.0? What would Enterprise Squared be? Or is it already there? Lots of thinking is being done on this topic as well. Again, this thinking could be summarized in a book as well.
This is not a complete summary. I picked out things I found very interesting. Just to show you I really enjoyed reading this book. I have advised many to read this book and hope this review will get you to do so as well.
Thank you for writing this book and sharing your insights, Andrew McAfee!
Note: This review has also been posted on Amazon in the review section of the book.
Relating structured and unstructured knowledge processes - KMers chat #kmers
Just a small post to invite you all to join the next KMers Chat on this Tuesday, October 5 from 17:00 - 18:00 UTC. I'll be moderating this chat. Participating is easy. All you need is a Twitter account. Just wait for the chat to begin and make sure to append your tweets with #kmers. Lots of interesting and smart people join in.
This chat will be about: Relating structured and unstructured knowledge processes.
Here's a short overview of this topic and some questions:
Knowledge Management is currently often related to the unstructured information and knowledge processes in organizations. In the past the focus of KM was on the structured side. But how can/are these combined in organizations? More specifically: how does enterprise 2.0 relate to BPM? (As you may know this is being heavily debated now on the web.)
Questions:
- Intro: Is the summary clear? Is the distinction clear? What do you call unstructured information/knowledge processes and structured processes?
- Do you agree KM currently mostly focuses on unstructured processes? Why is this?
- Are both types of processes supported holistically/in context in your company or companies you know?
- What does this mean for tools? Should tools support both processes? Or should we piece together a tool landscape?
Hope to meet you there!
Presenting at the Enterprise 2.0 Summit in Frankfurt
Just to let you know: I will be giving a talk at the Enterprise 2.0 Summit in Frankfurt am Main in October. Please find the full schedule here. My talk will be about our microblogging experiences and my vision on how the information and communications processes supported by microblogging relate to more formal business processes.
Hope to see you there!
Enough Information
When do you have enough information to make a next step or a decision? As you may know I love to process lots of information. Depending on the type of information I'll dive into it deeply or just dip my toe in it. After processing lots of information deciding when enough is enough has become easier for me. But it's hard for me to describe when I stop taking in information. Dave Snowden's Cynefin model has helped me in this sense. (By the way Snowden is currently summarizing the Cynefin model/approach/concept in several posts.
The Cynefin model basically says: look at cause and effect. Is the cause and/or effect clear? Is the relationship between both clear? Depending on your answer different 'next steps' should be taken. For instance if the relationship between cause and effect is completely unclear. This is the complex domain. Probing is the thing to do. Don't go a read volumes of books and articles. Probe and see what happens, then act, etc.
Even though I love to read lots of information I don't believe in perfection. That's one of the great things I learned from social media. Don't think you will be able to write a perfect report, blog post or book. Don't think you'll be able to process all the relevant content before you start communicating your opinion about the topic. Release as early as possible to get early feedback, to learn more quickly. Listen, think, share and learn.
How do you decide you have enough information? Do you have a problem to 'release early'? If so, why?
Is Your Organization a Process or a Network?
Is your organization a process (several operational steps to get things done) or a network (smart knowledge workers connecting to get things done)? Or is it both?
As an information architect I'm often confronted with this question. Usually not explicitly, but in a more implicit way. From an information process perspective you hear people talking about structured and unstructured information processes, for instance. I've shared my thinking about this topic in the past and I'm working on a longer post about this subject (to be published soon). I thought I'd start with something different. Three pictures to show the different views on organizations and how they relate. I'd love to hear you thoughts about these pictures.
What I see is managers and business process specialists look at organizations in this way:
So, the organization is put together as discrete, operational steps moving packets of information (the gray boxes) forward. (Loops back into the organization exist but are not in the picture).
Most employees see the organization in a different way. They see the organization as a network of people that have certain information or knowledge helping them get things done. Employees find the operational steps OK for very operational tasks, like time registration, but not for their core (knowledge) tasks. This could look like this:
I understand both approaches. Depending on how you look at (part of) an organization you see clearly defined steps or a chaotic network.
So my conviction is both are true. Both approaches exist in practice. If so, the pictures above should be combined. It could look something like this:
The interesting thing is the amount of time and money being invested in these approaches. Generally speaking you see lots of time and money being pumped into improving the first approach. Aligning and reengineering business processes, rolling out an ERP system, etc. The other approach is usually just there. It seems to be taken for granted. It's supported by email and more and more by platforms like Sharepoint. Some companies are also pushing social media into this space. In any case it is seen as infrastructure and investments are low.
This is strange to me because the largest part of the organization is organized as a community and network. People with a certain passion and expertise connect and collaborate to get work done. Of course there are operational processes in companies. And if they can be automated, we should do this quickly. However the amount of time and money being put into these operational improvements is, to me, disproportional to the amount of time being spent by knowledge workers on non-operational work.
Do you agree? Do you see both of these views in the company you work for? And do you take them as they are: related to each other? I'd love to hear your thoughts.
The Sustainability Debate Paper Versus Digital [Océ Whitepaper]
The company I work for, Océ, has a clear track record as a sustainable company. Way before it became the hot topic it is in these days.
Every year we have a Sustainability Week to focus even more on this topic. During this week an interesting whitepaper was released. It is about 'All in Balance. Océ's eco-efficient and eco-effective approach to analog and digital document'. Reference is made to a paper I wrote with others about (personal) document processes.
I hope you enjoy the whitepaper. If so leave a comment below or here.
Building on Ideas: The Wishing Well Wiki
Note: This post was written with my friend and colleague Rob Veltman (@robveltman). We carpool together and regularly talk about innovation and culture. Rob is an innovative product developer always challenging himself and his colleagues to ask the right questions to solve problems and make wishes come true. Rob is deeply interested in new product development, processes for (breakthrough) innovation and sustainability.
Introduction
How could we contribute to a more innovative organization? We ask ourselves this question regularly, help each other to come up with new ideas in this area and try to lead by example.
We would like to share with you an aspect of our daily practice, which is the observation that our colleagues can experience hesitance in being innovative. We will propose a solution to overcome this hesitance.
Situation
Knowledge companies consist of very smart people, educated in different disciplines. Their knowledge workers are confronted with all kinds of interesting issues, problems and challenges. Sometimes the assignments even seem impossible.
Generally speaking, we find most ideas for solutions and breakthrough innovations are done individually (mono-disciplinary). Furthermore we perceive that quite a number of employees are hesitant to share their drafty ideas, needs, desires, and wishes. We are convinced this can be attributed to at least three things:
- employees can feel reluctance “to put their cards on the table” because they feel their half, draft, non-100%, “unfinished” idea will be heavily scrutinized. Too often we hear: “This has already been investigated”, “This can’t be done”, “This is not your task, it’s mine”, “Unrealistic”, etc.
- employees can also experience reluctance because they feel their unfinished idea will be “stolen” and completed without getting credits for providing the seed of the innovation
- employees often speak of ‘problems’ and ‘issues’ in a way that is too restricting, almost assuming beforehand that an optimal solution will never be found. The presupposition: “a perfect solution doesn’t exist” tends to block the creative process before it has even started.
For these reasons employees tend to keep their ideas, ideals, wishes and problems to themselves. At the most, they discuss their ideas with people from their inner circle, people they trust.
Changing terms
Wouldn’t it be great if we could overcome this reluctance? We believe this is possible by helping colleagues to be more open and transparent about their (and our) profound wishes. All smart employees can formulate what they would wish for with respect to products. If this is facilitated, supported and encouraged, we believe organizations will change in the following ways:
- they will become more innovative and innovate in a more open, controlled and quick way,
- no challenge will be too big; they will truly do, and be part of, ‘beyond the ordinary’ things,
- they will build upon each other’s ideas and wishes
Proposal
We are convinced technology alone cannot be the solution. However, we do think technology can support us and help us open up and move towards the evermore-innovative organization described above.
We would like to propose the following:
- Set up a wiki called ‘Wishing-Well-Wiki’.
- This wiki is clearly supported by high-level management.
- It is fostered by a group of moderators, connecting wishes to people, and people to people, to make wishes reality.
- This wiki is open for all employees (from all disciplines and all levels). Everyone is invited and encouraged to make a contribution.
- This wiki has a clear format. All employees can describe their (product-related) wishes there. Typically these wishes are far-fetched, way-out. They are hard to realize alone, they need input from other smart people to evolve into an implementation.
- The wiki supports sudden and emerging breakthroughs.
- The wiki has built-in history. So, every input is recorded (versioned).
- When wishes become reality the contributors get support from management (in time, money and resources) to realize their joint dream. (Of course, employees may be requested for a business case.) The results of the wishing well wiki can also be used as input for the strategy.
- Regularly advertise wishes via intranet (e.g. ‘Wish of the Week’) and other channels to attract attention to them and stress their importance.
There are no costs in setting up this wiki.
What has to be clear is that:
- Few ideas can be qualified as bad. In most cases a proposed embodiment, to realize the idea, can be bad/impractical/insufficient, but an idea/concept in itself is without form and mass and thus cannot be judged by arguments that relate to physical characteristics.
- If someone qualifies an idea as “bad” or “not viable”, this person actually disqualifies his own proposal for an embodiment that first came up when he/she heard of the new idea.
- We all know that “first time right” is an utopia, especially with something like innovation. It is generally accepted that the innovating process is a painstaking process that requires the input from many different sources.
- In our view the real innovation process focuses on the process in which an embodiment is reshaped and transformed up until the moment that it is generally accepted that the end result is achieved or at least nearly met. Innovation, in our view, should not be aimed at the optimization of an idea itself.
These concepts fit perfectly on the concept of a wiki.
Concluding
This idea, which is also called ‘inbound open innovation’, can easily be extended to the whole organization. Other employees in the organization can also have (product-related) wishes. Sharing them and building upon them, leading to innovations could be done on a global scale too. (Refer to Dell’s Ideastorm, Innocentive and IBM’s Innovation Jam for inspiring examples.) A more sophisticated platform than the wiki could be needed to manage this global process.
References
[1] Phil McKinney, “The Fear of Innovation”.
[2] Ed Catmull, “How Pixar Fosters Collective Creativity”, in: HBR, Sept. 2008.
[3] Teresa Amabile and Mukti Khaire, “Creativity and the Role of the Leader”, in: HBR, Oct. 2008.
[4] Osvald Bjelland and Robert Wood, “An Inside View of IBM’s ‘Innovation Jam’”, in: MIT Sloan Management Review, Fall 2008.
[5] Allan Scherr, “Managing for Breakthroughs in Productivity”, Jan. 2005.
[6] Mihaly Csikszentmihalyi, Creativity. Flow and the psychology of discovery and invention.
[7] G.S. Altshuller, Triz.
[8] James Cash et al., “Enterprise Integration. Teaming Up to Crack Innovation”, in: HBR, Nov. 2008.
[9] Jim Collins, Good to Great. Why Some Companies Make the Leap… and Others Don’t, New York 2001.
[10] Meeting More Minds
External and Internal Activity Streams
Every now and then I run into something that really gets me thinking. Recently I ran into this presentation.
I went through it several times. And I think I'll do so in the coming days. Really great stuff!!
Activity Streams: what are they, how can we collect and understand them? This presentation focuses on public streams, mostly on the internet. But does this story also extend to the streams behind the firewall, inside organization? I think it should, but I'm thinking about how this should work. Of course the firewalls are coming down. But companies will still be protecting their information to a certain extent. My thesis is: These streams will be most useful if the distinction between protected and public information is mixed.
What do you think? And how do you think one stream of internal and external information can be devised? I'd love to hear your thoughts.
(Note: Thx Tom (@tvgtvg) for the discussion that led to this post!)
Another Knowledge Management Definition
Recently I organized an Océ-internal seminar about Information and Knowledge Management. I invited prof. dr. Robert de Hoog (of the University of Twente) to kick off this seminar with an introduction to information and knowledge management. He has a very interesting and pragmatic approach to these fields. De Hoog has written a lot about knowledge management, definitions and practice. This definition resulted from his pragmatic approach and could also help knowledge management department and knowledge managers do the right thing. I'm curious what you think of it.
Here's the definition (my own translation from Dutch):
Knowledge management is the management task consisting of a structured cycle of activities to identify, initiate and track interventions/actions, optimizing the use of knowledge in business processes, considering the positive and negative aspects of knowledge.
An example of a positive aspect of knowledge is: it can grow. A negative aspect is: knowledge is power.
Knowledge Management People
For some time now I've been participating in a group of information and knowledge management practitioners ('DutchOpen KM'). These friends work in large, international companies, based in the Netherlands.
The idea is simple: We get together about 2-3 times a year, define a topic per meeting and discuss that topic. Sometimes some participants will give a short presentation about the topic and how it's addressed in their company. Sometimes a couple of lines of text is enough to spark the discussion.
I'm always happily surprised about the way these meetings go. The open way we talk, the respectful way disagreements are discussed, the great ideas that are shared, the contacts these meetings give afterwards, etc.
Is this just a coincidence? We just happen to have a nice bunch of people grouped together? They definitely are nice. But I don't think it's a coincidence. It's what I also see in the blogging community - at least the part I interact with. It has to do with what I call 'knowledge management people'. Good KM practitioners should be open, willing to share, interested in different and strange ideas, social, etc. And the nice thing is they often are. They don't have to be knowledge manager, just to be a good KM practitioner. One other characteristic is they are not self-centered and usually share their knowledge without asking back up front.
In short, it's great to work them and be with these kind of people.
Sharing Process Information
Does your company share and manage process information centrally? And, if so, where is that information share/stored?
I usually make a general distinction when thinking about enterprise information. I distinguish four types of information:
- process information: information describing the processes of the company, the way of working and best practices, the document templates, etc.
- product information: information about products, such as designs, requirements, parts descriptions, product structure(s), etc.
- project information: information used to manage a project, like minutes, task lists, progress reports, customer visit reports, etc.
- departmental information: information about resources, monthly reports about the department, presentations given to the department, etc.
In many companies process information is shared and stored all over the place. Part of the information can be found on the intranet. I think most process info is shared here. Some process information is stored within the project team on a share or project site. Other process info is shared in a more formal quality management tool (to be able to be ISO certified for instance).
What I'm seeing is that companies are slowly moving process information to the wiki (or a wiki-like platform). We are doing this too.
Processes, working methods, best practices, etc. is daily experience for employees. They have to work with them and they know what works and why. For this reason I think a wiki is a great way to share process information. Management could start the 'process wiki' by providing an initial structure and by monitoring its content (top-down). It is very important management doesn't start from scratch but acknowledges there's all kind of process information on the wiki already, it's mostly not coordinated yet. But the content itself will be provided, bottom-up, from the employees. Following the edits to this content gives lots of information about the way employees see the company, what really works according to them, and tells you who in the company is good at rightly in an analytical way about how the company works.
By having your employees provide the process information they are also committed to right it down in the way it actually is in daily practice and keep it up-to-date. It's not "something management imposed", but it's "ours" or "mine".
Furthermore, process and ways of working are not static, but alive. They change continuously, usually with small steps. Keeping up with these changes does not work with a complex governance structure on topic of a closed intranet or quality management site.
So, I'm curious: are you seeing process info move to wiki's? If so, share your experiences with us. If not, let us know how you manage process information.
Favorite Books about Information and Knowledge Management
Some time ago a friend asked me to give him a list of my favorite books about information and knowledge management. I emailed them to him, but I'd also like to share my list with you.
I'd like to hear how this list relates to your favorite IM and KM books. If you would recommend other books, please leave a comment with the title!
Here's my list (in no specific order):
- Chun Wei Choo, Information Management for the Intelligent Organization. Basic book on information management.
- Thomas Davenport, Thinking for a living. About the characteristics of knowledge work.
- Peter Drucker, The Effective Executive. Must read because the term 'knowledge worker' is used in this book for the first time.
- John Seely Brown and Paul Duguid, The Social Life of Information. Great book stressing that information is social. This is mainstream now, but at the time this book was published it wasn't...
- Mathieu Weggeman, Kennismanagement. [Dutch] The Dutch book about knowledge management.
- Ikujoro Nonaka and Hirotaka Takeuchi, The knowlegde creating company. One of the core books in the knowledge management area. This book made KM mainstream. Their SECI model has been critiqued as too objectivistic and mechanistic. Dave Snowden has fundamental articles on this topic. He also shows that Nonaka related to the concept of ba before the book was published, showing the model wasn't meant as an all-encompassing model for knowledge management.
- Kazuo Ichijo and Ikujiro Nonaka, Knowledge Creation and management. An update of the previous book with other authors. Good overview over state-of-affairs of KM. Does not address web 2.0 though.
- Harvard Business Review on Knowledge Management. A collection of fundamental articles about KM.
- Dave Snowden's work about knowledge management (not in a book yet).
- Don Tapscott and Anthony Williams, Wikinomics. Not specifically a book about information and knowledge management. But it is a book about shifts in the way we see and manage information and knowledge.
Too Much Communication
Last weekend I read an intriguing article in the Dutch newspaper, NRC. A communication researcher, Tjardus van Citters, wanted to give us all well-meaning advice. (Dutch titel: 'Welgemeend advies van een communicatie-expert: minder communicatie, s.v.p', Sept. 20, 2009.)
His article gives an overview of the sources that are increasing the number of signals we process each day. For instance the number of communication providers has increased. And the fact that our senses are being addressed more than ever.
This overview leads to his advice to communicate less. Why? Because our health is at stake. Our brains get more impulses to process. The model of 'selective perception' is out-dated. We get irritated by communication we did not want to see, leading to restlessness, even illness.
He therefore advises us to turn off signals. Read the news once a week instead of every few hours. Unsubscribe to things you don't want to receive. Be clear what kind of emails you don't want to get. Read from paper instead of screen (- you can concentrate on paper better than with reading from a screen, he says). And remember: the interest/importance of the message is defined by the sender.
Wow. This is really different from the trend that says we we moving to 'life streaming', 'filtering' and the 'real-time web'. I don't feel I'm becoming sick, irritated, etc. by the amount of information and communication signals I'm processing. Of course I do find we should think before we communicate and share. It should be mindful.
But I feel like I'm missing something here. Are you experiencing what is described in this post? And where can I read more about this subject, also proving the statement that more communication is unhealthy?
How Does Your Boss Process Information?
A colleague of mine kindly pointed me to an interesting report: "The Rise of the Digital C-Suite. How executives locate and filter business information'. It's a Forbes Insight report, sponsored by Google.
To be clear, this report is about how executives look for and process external information. Information that is on the web. It would be very interesting to read a comparable report on how execs do the same for internal information. I think it's the case for many execs they're too busy to follow and look for external trends anyway. Surprisingly more than 60% of the execs said they accessed the Internet for business intelligence on a daily basis.
Another interesting part of the report is how execs use web 2.0. For the 50+ category 80% or more didn't maintain a blog or tweet. Only 26% of the 'under 40' category didn't tweet.
RSS is not used much at all over all categories. Only 40% of the 'under 40' category for instance. Which regrettably relates well to the world-wide RSS trends.
Do you think the way execs process information internally differs much from externally? My hunch is the difference is minimal. Within the enterprise it is clearer what needs to be read. But what I'm hearing is that these formal communications (reports, memo's, etc.) aren't being read too closely. Or do you have other experiences?
Picking Up Weak Signals
How do you pick up weak signals and make sense of them? In some cases we'd rather not pick them up at all. This goes for us personally ('what is being said about you?') and for companies ('who's talking about us and why?')
MIT Sloan Review ran a very interesting article on this topic: "How to make Sense of Weak Signals" by Paul Schoemaker and George Day (Spring 2009).
What is a weak signal anyway? Shoemaker and Day define it as:
A seemingly random or disconnected piece of information that at first appears to be background noise but can be recognized as part of a significant pattern by viewing it through a different frame or connecting it with other pieces or information.
I was surprised to read that "fewer than 20% of global companies have sufficient capacity to spot, interpret and act on the weak signals of forthcoming threats and opportunities." It would be nice to read some best-practices in this area. A general framework to make sense of weak signals is given in this article.
Shoemaker and Day say:
There are various individual biases that may cause managers to be taken unaware. In addition, there are organizational biases - such as groupthink or polarization - that may keep much of the periphery-dwelling enemy in the shadows, even in organizations with an active scanning process.
People and companies have difficulties coping with multiple pieces of evidence pointing in opposite directions. Or when crucial information is missing, "our minds naturally shape the facts to fit our preconceptions".
A very interesting remark made by the authors with respect to information and knowledge management is:
The organizational problems caused by dispersed memory and varying perceptions can only be overcome when information flows freely across departmental boundaries.
And sense making is rightly marked as a social process:
Organizational sense making occurs in a complex social environment in which people are not just sensitive to what is being said, but also to who is speaking. We judge both the signal and the source.
The authors gives nine proven approaches to reveal, amplify and clarify potential important weak signals. These approaches should be used in combined:
- Tap local intelligence. Relates well to "When Information is not the answer".
- Leverage extended networks. Ask questions!
- Mobilize search parties
- Test multiple hypotheses. "Managers often have limited tolerance for ambiguity and may be reluctant to devote additional time to develop alternative hypotheses to escape the trap of getting stuck on a simple, single view that is wrong."
- Canvass the wisdom of crowds
- Develop diverse scenarios
- Seek new information to "confront reality"
- Encourage constructive conflict. "There was no dissent. So, information never really traveled."
- Trust seasoned intuition
Good stuff! And very helpful. However, I was surprised this article did not point to several other sources, that also address weak signals. For instance:
- Jim Collins, Good to great. Collins says great companies continually confront themselves with the 'brutal facts'.
- Chris Argyris, Overcoming organizational defenses. Argyris talks about how corporate defense mechanisms work, also leading them to 'close their ears'.
- Dave Snowden's work on the Cognitive Edge/Cynefin framework and coping with complexity. It provides ways to make sense of complex, chaotic, knowable and known contexts.
- Malcolm Gladwell, Blink. Relating to the good and bad of trusting "seasoned intuition".
Anyway, how do you pick up and act upon weak signals?
---
If You Read This and Like It, Tweet This to your Followers:
Picking up Weak Signals http://twurl.nl/vklbzx #km
Re: When Information is Not the Answer
Andrew McAfee has another really nice post: 'When Information is NOT the Answer'. I advise you to go and read it, definitely if you are in IT. And for Knowledge and Information Management experts this post summarizes what you've been trying to tell IT all along.
McAfee basically shows that not all information can be processed using IT systems. Even though many think so and heavily depend on these systems for decision making. And he gives an example of a company, Zara, that acknowledges this and works with it in practice.
In a comment on his post I pointed to two books that underline the point McAfee's making. One is 'Blink' by Gladwell. (And I'll write a review of this book soon.) And the other is 'The Social Life of Information' by Seely Brown & Duguid. (The last book is one of my all time favorites.) If you haven't read them, please do so. It's very worth your time.
In 'The social life' they have that nice example of a control tower. The tower is fused with IT. But when they really tried to understand the PEOPLE that work in the tower and how they make decisions, they arrived at interesting results. These people used sticky notes, easily processed loads of data, make decisions based on intuition and experience - not on what's on the screen, etc.
And 'Blink' is loaded with examples of 'split-second decisions'. He shows that these decision can be good when they're (implicitly) based on processing lots of information in the past and becoming expert at something. Gladwell shows that some can make good decisions even though all the (objective/general) information in the world seems to be against them.
---
If You Read This and Like It, Tweet This to your Followers:
Re: When Information is Not the Answer http://twurl.nl/3nnhho #km
Different types of content
Mark Morrell of BT has an interesting post on the different types of intranet content they distinguish. I commented on this post, but would like to extend my comment here.
Mark distinguishes between personal, crowd, team and formal content. I commented:
Interesting post! What I was wondering is: is this list right? For you I understand it is. But can’t ‘team’ content be ‘formal’ for instance? And isn’t ‘personal’ a security issue? For instance, I’m working on some content I don’t want to share yet (so it’s personal), but in time it will be in the category ‘crowd’? I’ll blog about this and tell you what my categories are. Thanks for sparking this discussion.
I'm curious if you agree with my remarks. Do you make different distinctions?
Anyway, I think it's great BT is distinguishing between content. I find that lots of content that is now on intranets shouldn't be their anyway. And I see that BT is not only making this distinction but also providing different applications to create and share the content (blog, wiki, CMS, etc.).
As information architect I also distinguish information types. My list is:
- product info (product data, specs, competitor info, etc.)
- project info (tasks, calendars, meeting minutes, etc.)
- department info (presentations, etc.)
- process info (process descriptions, working methods, templates, etc.)
What we're seeing now is that our intranet contains all kinds of info. I find our intranet (traditional CMS with 1-to-many publish method) should only contain process information. Process information incorporates news and who-is-who info as well.
All these info types can be given authorization levels, allowing certain information to be kept personal or shared within a team or project.
Does this make sense? Again, do you distinguish between information types and manage them differently?
---
If You Read This and Like It, Tweet This to your Followers:
Different types of content http://twurl.nl/jqj4z7
Going 'paperless'
I prefer to read longer articles (even blog posts...) on paper. For instance I read Harvard Business Review and MIT Sloan articles. Our corporate library allows me to read those articles in hard-copy. Of course the librarians have access to the digital sources of these magazines, but I don't.
What I usually do is browse through the magazine and make copies of the articles I want to read (or I think are interesting for my colleagues). In this way I can read them when and where I want.
When I read articles I usually write comments in the sidelines and highlight what I find interesting and important to remember. These marks are very important to me. So important that I would archive the hard-copy of the article in binders. At least until recently. If I could get my hands on a digital copy I would file that one on my computer with the comments.
Over time I've collected many articles and found that I hardly reuse those articles in my work. Filing them is hard and therefore retrieving them when I need them is too.
So recently I said to myself: Let's get rid of those hard-copies and scan all those articles in. This is quite easy because I work for a company that develops copier-printer-scanners. The scanners have a document feeder so I don't have to scan page-by-page. The scan is automatically emailed to me in pdf (but is not OCR-ed...).
When I get the pdf of the article I trust the scanning process has gone OK and don't check that. I rename the filename by typing in the title, the author(s) of the article, the source it came from and the date. Because Windows wants me to put the file in one folder (I'm using XP) I also add some 'tags' to the filename (by simply adding extra text in the filename) to be able to create intersections over files and folders.
This is working out fine for me. And I'm finding I'm reusing older articles more often now. When I'm asked to look into something I start by search my desktop and collecting the info I already have. Then I move over to my bookmarks (- wouldn't it be great if you could merge bookmarks and files? -) and finally search the internet.
I'm curious what you do with your paper documents. Do you also scan them? Or do you file them in a binder? Do you reuse those documents often? Please share your best-practices!
---
If You Read This and Like It, Tweet This to your Followers:
Going paperless http://twurl.nl/aju08p
Where's Information Headed?
It would be interesting to extend this post and visualization with other kinds of information. For instance, office documents, flyers, etc. Baekdal also leaves out books. Books would come in between 'local marketplace' and 'newspapers', I think. And office documents (like Word docs) came around 1990-1995? I remember typing my first report in WordPerfect around 1993. At that time you were still allowed to write your report in handwriting. Wow, time flies!
---
If You Read This and Like It, Tweet This to your Followers:
Where's Information Headed? http://twurl.nl/56qrqe