To be successful and truly collaborative, knowledge-sharing systems require intuitive tools that connect people, reward participation, and align well with existing work and communication patterns. After IDEO's two-year internal development effort to create and implement "the Tube," their enterprise-wide intranet system, we gained new understanding and experience in balancing technology possibilities with behavior realities. The unique success of the Tube comes from the insight that effective knowledge sharing is a social activity that is enabled by technology, rather than a technological solution bolted onto an existing work culture. Now IDEO's Knowledge Sharing Team shares a set of design principles for building online collaboration systems that really work.

Context

Over the last thirty years, IDEO has grown from a handful of employees in one location to more than 500 in eight locations around the world. With this growth, IDEO’s methods needed to grow as well. We needed tools that would allow the entire organization—individuals, teams, and enterprise-wide groups—to share information and collaborate in a variety of ways. More importantly, these tools needed to encourage natural communities of passion to emerge. To tackle this opportunity, IDEO formed a Knowledge Sharing Team comprising technologists, human factors specialists, interaction designers, and software engineers to create a new suite of online tools that would meet these goals within a highly creative and collaborative culture.

Key Innovations & Timeline

The Tube comprises a suite of online tools that enables 500-plus employees around the world to collaborate, share learning, and inspire each other as an integral part of their work process. The Tube combines social networking tools such as blogs, wikis, and real-time screen sharing with legacy business systems like HR databases, asset management systems, and e-mail. The system has created ways for individuals to reveal passions and expertise, for teams to learn from each other, for offices to connect more frequently and easily, and for the company to build on shared themes and directions. This led to the design of systems that people actually want to use. Prior to the decision to create the Tube, the team reviewed or tested more than three-dozen collaboration tools and systems. They spoke with leading consultants, technologists, and domain experts in diverse areas such as collaboration, knowledge management, and organizational change. After testing as many systems as possible, we couldn't find any that met the organization's needs and fit within the culture. For example, IDEO’s culture strongly supports collaboration and sharing of information, but several systems are based on the assumption of building credit for yourself by “claiming” information or publishing white papers. The team realized that technology alone does not foster collaboration, and can create nearly as many barriers to collaboration as they enable. This led to a consideration of both technological and cultural incentives that could lead to the adoption of new tools and methods. What followed was a substantial amount of internal research, starting by observing how people work at IDEO, understanding their sources of frustration with current collaboration tools, and getting clarity on what motivates people to share information (or not). Without trying to incorporate “best practices” that would work in any organization, the team crafted a system that works well within the IDEO culture and environment. Based on the feedback they received from sharing their approach with clients and public audiences, the team has learned that the functionality built into the Tube, its ease of use and its intuitive interface, are unique and compelling. Through presentations of the system and the design principles that underlie it, they identified a latent demand for collaboration systems that are both simple to use and fit the culture of the organization they are serving.

Challenges & Solutions

The team continues to enhance the functionality and usability of the Tube through ongoing human-centered research and feedback from the community. They see an increasing need for new functionality such as workflow tools, team staffing tools, customer relationship management tools, and others, each of which requires careful consideration before it can be added to the Tube. Another developing need requires connecting the Tube, which is entirely internal and confidential today, both to the public ideo.com website and with IDEO clients for increased collaboration in specific project engagements. Given the sensitivity of the information and new types of collaboration required, this is a major task that the team is currently undertaking. The team believes that inviting IDEO's partners and public to share information and collaborate around shared interests could have enormous benefit to all involved.

Benefits & Metrics

Some utilization statistics:

More than 1,000 Project Pages created in that feature’s first six months (these pages have fields for project storytelling and document collections and sharing. They automatically include all team members who have billed to the project, as well as start date, budget, client information, and more.)
Over 10,000 wiki pages in the wiki's first 14 months, on subjects as diverse as presentation guidelines and template to travel and sightseeing tips around the world.
More than 55,000 wiki pages as of today -- a large number for a 500-person company
95% of employees voluntarily take ownership of their personal pages (which include their personal blog, fields for long and short biographies, status messages, image sharing, and project work reporting)
Over 40 special-interest blogs created by teams and individuals, which address company-specific issues such as career growth and office updates, as well as general-interest topics such as social impact, sustainability, and health and wellness projects.

Apart from utilization statistics, IDEO has not formally evaluated the impact of the Tube. Anecdotally, we have seen an increased sense of participation in the greater community, especially among those who are in smaller-sized and isolated offices. The team has seen a great deal of collaboration and sharing of information around areas of passion, such as social impact, particularly in the wiki pages. For example, prior to the Tube, IDEO had many people who were interested in doing meaningful design work in the developing world, but no single office had a critical mass to establish a like-minded community. Through the Tube, a community called “Social Impact” formed and became a major force in shaping this new and increasingly important direction for IDEO. The Tube provided the infrastructure this community needed to organize and support itself from locations around the globe.

Lessons

Design Principles: IDEO's Knowledge Sharing Team synthesized their findings into five design principles that guided the creation of the Tube, and scale and adapt to inform similar efforts within other organizations.

1) Build Pointers to People: rather than trying to take all of the knowledge out of people’s heads and store it in a giant database, focus primarily on helping people to identify who they are -- their passion, experience, and expertise -- and connect people based on that information.

2) Build Rewarding Systems: a system that requires altruism is unlikely to be successful. Similarly, systems that require users to participate (e.g. compliance-based design) rarely get anything more than participation at the lowest required level. Effective knowledge sharing systems must simultaneously meet the needs of the organization while motivating individual participation. The Tube encourages individual participation in a number of ways, from establishing a platform to allow employees to showcase their best work, to integrating the salary range process and project resourcing process into the system.

3) Demand Intuitive Interfaces: intuitive interfaces are absolutely essential for social software because they facilitate viral adoption. The system must present as few points of friction as possible from the process of becoming an active user. For example, early wiki systems required users to set up an account the first time they wanted to add content, learn special wiki languages to format pages, and build not only the content but also the navigation to support it. These points of frustration discourage users from making the transition from consumers to contributors.

4) Take the Road More Traveled: if a tool requires people to go out of their way to use it, adoption will always be a challenge, no matter how wonderfully designed. Wherever possible, strive to integrate tools into existing work processes -- bring the system to the user rather than the other way around. For example, the IDEO blogging system didn't take off until the team added a program that sends digest emails with new content from the blogs each employee has subscribed to.

5) Iterate Early and Often: building effective systems for organizations means designing tools and workflows that mirror the social systems they are meant to support. This happens through lots of iterative design, beginning with rough in situ prototypes (paper-based or hacked existing systems) and evolving into working systems that can be tested broadly throughout the organization. This process doesn’t end with "launch" either. Knowledge sharing systems should grow with the organization they support, and in turn they shape the organization by enabling new levels of collaboration. Thus these systems and the designers creating them should think of them as an ongoing, evolving dialog with the employees using them. At IDEO, the team pushes out revisions to the Tube (both bug fixes and new features) each Thursday. Much as Google keeps all of its software in “beta” for as long as possible, this reinforce the notion that the Tube is a working prototype and set the expectation for ongoing change, which enhances our user experience without confusing it. When individual passion meets collaborative tools that fit into the flow of one’s worklife, powerful innovations can result. IDEO's goal is to continue to build a platform for innovation that builds on the passions and cooperative foundations of our culture. As is a tradition at IDEO, the team will continue to share with the outside world what they learn along the way.

IMPACT:

The Tube has had a very positive impact on the way we work at IDEO. Teams are working using the platform in new ways. People with special interests, talents and passions are easier to identify and invite to collaborate on projects. Passion is the key. Our model is based not on "compliance", which we have seen in many other companies, but on an opt-in model. Connections among people are made based on active collaboration but also by searching for people and ideas and by serendipity. We fully expect to see many other unexpected and wonderful benefits from our approach in the future as the platform and users develop and grow through our collective learning.

IMPACT:
The Tube has had a very positive impact on the way we work at IDEO. Teams are working using the platform in new ways. People with special interests, talents and passions are easier to identify and invite to collaborate on projects. Passion is the key. Our model is based not on "compliance", which we have seen in many other companies, but on an opt-in model. Connections among people are made based on active collaboration but also by searching for people and ideas and by serendipity. We fully expect to see many other unexpected and wonderful benefits from our approach in the future as the platform and users develop and grow through our collective learning.

Credits

Doug Solomon, Chief Technology Officer, IDEO

You need to register in order to submit a comment.

Sort By: Latest Oldest Likes Replies

May 20, 2010 at 9:08am

Neil Patel

excellent story

September 30, 2010 at 2:18pm

Doug Solomon

Thanks!

October 27, 2012 at 4:19am

Marianne Doczi

How refreshing to see the focus on knowledge sharing and generation as a social activity rather than a technology solution. You seem to have intuitively applied gamified systems approaches that understand how much people are motivated by intrinsic rewards, and enjoy collaboration. And, of course, I love your 'iterate early and often' approach. How other than by experimentation, assessment and trying again can we ever design what we want and need. Thank you.

May 31, 2010 at 3:12am

Madhusudan Rao

Thanks for providing so much information on your system. While creating content is good, the most difficult part in using similar Knowledge Systems is to be able to search the appropriate content quickly enough for our reference. How was this enhanced in your project?

Thanks in advance.

Regards
Madhu

September 30, 2010 at 2:18pm

Doug Solomon

We have a few ways to search:

1. an overall system search

2. a way to limit that search to various types of pages

3. a way to search only tags that people have put on pages

4. some custom search screens that are interactive and allow users to search, for example, for people with certain skiils, interests, and time availability.

Thanks for your question.

Doug

May 31, 2010 at 6:17am

Ryan Nichols

Hi Doug-- fascinating story... would love to see a screenshot or a video demo! Curious whether you built "the Tube" from scratch, or built it on top of an existing collaboration platform (e.g., Jive, Google Apps) .

Thanks,
Ryan

September 30, 2010 at 2:16pm

Doug Solomon

Thanks, Ryan. Sorry to be so late in replying. We built this mostly from scratch, using some licensed software and some open source tools. Now, however, we've teamed up with Moxie Software and they are selling and supporting our latest generation design called Spaces. This should allow people to buy something already done and customize it to the extend they want to.

December 30, 2010 at 2:57am

Robert Spencer

Fantastic article, Doug. We're looking to create some collaborative structures at Brambles, and I am going to take your lessons to heart. Thanks

January 3, 2011 at 12:24pm

Allen Roberts

Hi Doug,
A great article.
As an advisor to a range of SME's in Australia, i have been trying to articulate the notion of an internal ongoing innovation workshop by the use of collaborative tools emerging from web 2.0.
Your article has just made the job easier for me, thanks.

January 4, 2011 at 9:44am

Doug Solomon

Thanks, Allen. Please let me know how things progress.

Best,

Doug

January 4, 2011 at 7:26am

Mike Richardson

Thanks so much for sharing Doug. I enjoyed reading your story and the inspiring benefits that can flow from such a collaborative community. I just posted my latest submission/Story entitled, "The Power of a Peer Group: How come something so proven is not more pervasive, and what are we willing to do about it?" at: http://www.managementexchange.com/story/power-peer-group-how-come-someth...) and wondered what your thoughts are about the blending of these approaches (which i speak to in the Challenges & Solutions section - the 3rd challenge/solution). My sense is that they are additive, addressing overlapping and underlapping needs and neither is as powerful alone as they can be together. Welcome your thoughts. Thanks again for sharing. Best.

February 5, 2011 at 5:54am

Alan

Great story. Would love to know what tools, platforms, development resources The Tube is based on. Can you share? Thanks.

February 7, 2011 at 4:06pm

Doug Solomon

Thanks, Alan. The Tube is built on a Ruby on Rails framework. We have recently teamed with Moxie Software (www.moxisoft.com) and they are selling and supporting our next generation Tube which they call Spaces. You can find more information on their website. Hope this helps.

February 11, 2011 at 10:08am

Roberto Machare

I like it. Good initiative.

February 18, 2011 at 6:19pm

Doug Solomon

Thanks!

February 18, 2011 at 3:56pm

Steve Adelman

This is great - not compliance-driven, but inclusive.

A couple questions:
- Can an area be segmented off for a specific group - e.g., only those working on a confidential project having access?
- Can access to The Tube be shared across company boundaries - include the client team, for example?

February 18, 2011 at 6:19pm

Doug Solomon

Thanks for your question. The answers are : yes and yes.

April 20, 2011 at 11:06am

Richard Demato

Hey Doug,
Thanks for sharing, I'm always inspired by IDEO's push to collaborate and harness creativity.
Just came across this link from Alec Ross, thought it would be interesting to you.
Maybe IDEO should help the State Department take their collaboration to the next level?
http://www.businessofgovernment.org/blog/business-government/new-corrido...
All the best,
Richard

April 22, 2011 at 2:48pm

Rogério Costa

Hey Doug A very great story indead. Do you think that is possible to creat a platforme like Tube using open source platforms like Buddypress? Thank you in advance and congratulations. Rogerio

May 2, 2011 at 12:44pm

Doug Solomon

I'm not familiar with Buddypress, but believe that the principles I've outlined for building collaboration systems that really work can be built on many platforms. The key is to find a platform that is flexible, simple and can support the five design principles without having to bend over backwards and sacrificing usability and integration of disparate data sources.

doug

April 22, 2011 at 10:34pm

Gavin McLeod

Doug thanks for the story - lots of useful insight for an intra-company exercise or exchange to learn from.
I wonder if there are insights that could apply to the wider web community as well. I understand the desire to build depth into relationships within a known community as it helps the agents within the "system" to link, understand and respect each other - and this supports info transfer and growth. Ego is moderated enhanced understanding and trust. The problem with the wider web community is that the biggest blocker to passionate embrace is trust or perhaps more correctly the lack of trust. There is a lot of "fronting" and image maintenance on social network sites and a visit to many boards and chats soon reveals a lot of egos on display.
I an wondering if an opposite approach could work to some extent - the use of totally anonymous unattributed chat rooms (Each particpant is recognised simply by a color/font and Unique i.d. alpha/numeric code. Chatroom rules could focus discussion on the idea in addition to community feedback - with no reference to participant CVs, likes, dislikes etc to color the conversation or provide bias of information introduced into the conversation. The only feedback mechanism being provided over time directly by the community sharing the online environment.
I have been thinking about this because in numerous corporate environments that I have encountered around the world the nature of profiles, the definition of how people are viewed, is influenced by the bias of the environment designers and the gravity associated with comments and input is, I believe, seriously coloured by the apparent "expertise" and noteworthiness of the source.
For instance a great marketing idea could be introduced by a new cadet to the company but could be criticised by a long standing or senior team member which and his/her critique can have a strong influence over the group in many cultural settings (perhaps not IDEO which I wholly admire...). The idea can be lost because many participants don't wish to rock the boat or simply trust the experience of the senior member - mediocrity can be a powerful force in a herd setting.
Would IDEO ever consider a completely anonymous environment where ideas are championed and egos are submerged? I understand the need for personal attribution in order to incent participation, but that can come later once the idea has found its legs and a group has pinned their colour to its mast so to speak...

I would love to chat with you about this if you are ever available.

Regards
Gavin

May 2, 2011 at 12:42pm

Doug Solomon

Hi. Wow, interesting ideas. I can see the benefits of both anonymity as well as being linked to every comment one makes. Both can have a place in the world of social media. In general, I think that anonymity leads to more problems than benefits, although in large organizations it might be an interesting way to generate feedback on ideas and directions without the fear associated with being frank.

Best,

Doug

May 2, 2011 at 10:12am

Gio' Morse

Doug:
Yes, good story and useful insights. But I 'm puzzled by the name chosen for the group. To me it indicates a closed system not one that gives incentive to collaborathe. Why not express with a word what the group does. I.e, Walter Gropius and the company he helped found, The Architects Collaborative.
Cheers,
Gio' Morse

May 2, 2011 at 12:39pm

Doug Solomon

Thanks. We call our group "knowledge sharing". Are you commenting on the name of the system, "The Tube"?

Doug

May 3, 2011 at 1:46pm

Tim Nicklas

Doug . . . This is fantastic! I have been reviewing similar tools for the Innovation Center we are creating at Children's Hospital Colorado in the Orthopedic Institute. The Innovation Center will facilitate clinician and staff development of ideas for improving patient care via novel services and products. This will be accomplished through collaboration with academic and industry partners, and by utilizing our number most valuable resource - our patients and their families. Do you have any suggestions for software that you think would be appropriate (since the Tube doesn't appear to be commercially available anytime soon)?

Thanks! - Tim

May 3, 2011 at 4:36pm

Doug Solomon

Thanks for your feedback.

Let's talk. Please email me at doug@ideo.com and we'll set up a time.

Best,

Doug

May 3, 2011 at 4:36pm

Doug Solomon

Thanks for your feedback.

Let's talk. Please email me at doug@ideo.com and we'll set up a time.

Best,

Doug

June 6, 2011 at 5:16pm

David Arella

Doug,

Congrats on capturing the intelligence of the whole group for the benefit of all. I appreciated your description of all the technologies you used and how you dealt with the concerns about adoption.

I have a suggestion on where to go next in response to what you said the team sees as "an increasing need for new functionality such as workflow tools, team staffing tools, customer relationship management tools, and others." Sharing information is foundational, but this alone does not produce action. Co-laboring is really about two or more people delivering some outcome together. So the next step is to introduce software that helps people create and track agreements to deliver.

Software for managing explicit, two-person conversations for action is coming which will improve coordination, visibility into execution, and accountability by presenting a clear picture of who will do what by when. One person (the requester) makes a specific request of someone else (the performer). The performer is obliged to make an explicit response, i.e. agree to deliver on the request, decline, or make a counter-offer. Presenting the performer with the opportunity to negotiate their delivery commitment clarifies ownership and assures accountability, not to mention increases the likelihood that the delivery will be made on time. The whole organization can be seen as a network of these conversations around negotiated commitments. The principles are the same whether individuals make requests or each other, departments make requests of other departments, or the CEO makes requests of Vice Presidents.

Commitment based management has been described as the most important new management principle to emerge in the last several decades. These simple, but profound innovations in work management have been profiled in the Harvard Business Review, MIT Sloan Management Review, and the Wall Street Journal. These innovations will also disrupt current top-down/command-and-control work norms and increase trust by capturing performance metrics and exposing patterns of behavior. Check out my blog (4spires.com/blog) if you'd like to learn more.

Keep up the good work!

David

June 5, 2012 at 12:37am

Kayla

Thanks a bunch for this amazing writeup Doug! I've recently switched to Ruby on Rails and hopefully can leverage my knowledge for my potential business needs (my project is dedicated to the methods of screen capturing i.e. how to record screen and I'm having hard times with the software I use). As far as I can see, your approach works perfectly, and that's quite understandable. Congrats!