Your SlideShare is downloading. ×
0
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Social in the Flow of Work, Enterprise 2.0 Santa Clara, 2011

1,494

Published on

Social Software Needs to Live in the Flow of Work …

Social Software Needs to Live in the Flow of Work

That's easy to say, but hard to achieve. Today's flow of work runs through a complex array of systems of record: ERP, CRM, order management, procurement, document management, intranet, and our old frienemy email. Legacy investments have been made. Work habits have been established. How--and why--should we set about to create change? Learn how to create a technology experience that has both transactionable and social elements by blurring the barriers between the social apps and non-social apps.

Published in: Education, Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,494
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The reason why McKipedia didn ’ t take off as a proprietary encyclopedia is that it didn ’ t solve the fundamental problem of knowledge management. KM asks workers to step outside their daily flow of work and contribute to document repositories, fill out extra surveys, and contribute to internal Wikipedias. The problem is, this contribution is outisde the flow of work. KM asks people to do something, outside and on top of their busy day jobs. Not surprisingly, very few workers make that contribution. Wikipedia also has authorship that is a fraction of 1%. But Wikipedia starts with the public web - 1 billion users - whereas a company is several orders of magnitude smaller. Does that mean Knowledge Management is a failure? Well, not exactly. But it has changed…
  • The reason why McKipedia didn ’ t take off as a proprietary encyclopedia is that it didn ’ t solve the fundamental problem of knowledge management. KM asks workers to step outside their daily flow of work and contribute to document repositories, fill out extra surveys, and contribute to internal Wikipedias. The problem is, this contribution is outisde the flow of work. KM asks people to do something, outside and on top of their busy day jobs. Not surprisingly, very few workers make that contribution. Wikipedia also has authorship that is a fraction of 1%. But Wikipedia starts with the public web - 1 billion users - whereas a company is several orders of magnitude smaller. Does that mean Knowledge Management is a failure? Well, not exactly. But it has changed…
  • When we work transparently, we get all the benefits of KM as a by-product of doing our daily jobs. It ’ s the holy grail!
  • 05/10/11 The public Internet is bring thousands, even millions, of people together in new and dynamic ways. New tools, new processes are enabling collaboration on a grand scale, sometimes across complete strangers.
  • 05/10/11 The public Internet is bring thousands, even millions, of people together in new and dynamic ways. New tools, new processes are enabling collaboration on a grand scale, sometimes across complete strangers.
  • 05/10/11 The public Internet is bring thousands, even millions, of people together in new and dynamic ways. New tools, new processes are enabling collaboration on a grand scale, sometimes across complete strangers.
  • Transcript

    • 1. In the beginning was the work Photo: http://online.wsj.com/article/SB10001424052748704476104575439723695579664.html
    • 2.
      • Business processes
      • Transactions
      • Meetings
      • Conversations
      • Knowledge Systems
      • Knowledge Management
      • Learning systems
      • Document management
      Daily Flow of Work Knowledge Reuse Insight Generation Expert Location Traditional knowledge systems
    • 3. The Happy Sharing Place Photo credit http://janeheller.mlblogs.com/2009/05/15/yankees-win-series-kumbaya-or-whatever/
    • 4. Knowledge Systems (a.k.a. Happy Sharing Place) “ Above the Flow” of work Daily Flow of Work
      • Business processes
      • Transactions
      • Meetings
      • Conversations
      Leap of Faith
    • 5. Enterprise Collaboration Daily Flow of Work Knowledge Capture and Reuse Ideation and Insight Generation Real-time Q&A
      • Business processes
      • Transactions
      • Meetings
      • Conversations
      Social Networking “ In the Flow” of work
    • 6. Some examples
    • 7. What it takes
      • Functional requirements:
      • Streams AND pages
      • Systems of record integration (Social Layer)
      • LDAP/SSO integration
      • One stop shop for:
      • Company directory
      • News
      • Documentation
      • Live data feeds
      • Conversations
    • 8. What do staff need? Photo credit: 123rf.com

    ×