Driving Innovation Through Enterprise 2.0

Download Driving Innovation Through Enterprise 2.0

Post on 14-Jan-2015




2 download

Embed Size (px)


ARK Presentation August 2008


<ul><li> 1. Stuart French Daniels Sharpsmart</li></ul> <p> 2. Take-aways </p> <ul><li>Benefits of Collaborative Innovation </li></ul> <ul><li>How culture and collaboration interact </li></ul> <ul><li>Outline some tips for implementation </li></ul> <p> 3. Enterprise 2.0 </p> <ul><li>The mix is moving towards Blogs, Wiki, RSS &amp; Podcasts </li></ul> <ul><li>The Asia Pacific region showed the greatest satisfaction in 2008 </li></ul> <ul><li>Successful use of Web 2.0 can lead to structural and cultural change dubbed Enterprise 2.0 </li></ul> <p> 4. </p> <ul><li>Making definitions clear </li></ul> <p> 5. Defining Innovation </p> <ul><li>Bring something new to the environment</li></ul> <ul><li>Bringsomething newto the environment</li></ul> <ul><li>Bringsomething newto the environment</li></ul> <ul><li>Collaboration 2.0 multiplies </li></ul> <ul><li><ul><li>The novelty of invention </li></ul></li></ul> <ul><li><ul><li>The speed of delivery </li></ul></li></ul> <p> 6. Defining Innovation 7. Defining Collaboration </p> <ul><li>Collaborate -/k labb rayt/</li></ul> <ul><li><ul><li>verb work jointly on an activity or project. </li></ul></li></ul> <ul><li>It is Not </li></ul> <ul><li><ul><li>Communication </li></ul></li></ul> <ul><li><ul><li>Cooperation </li></ul></li></ul> <p> 8. Defining Collaboration </p> <ul><li>How does Collaboration effect Innovation? </li></ul> <ul><li>My Research: </li></ul> <ul><li><ul><li>Culture effects Wiki use </li></ul></li></ul> <ul><li><ul><li>Use of the wiki also effects communications and culture </li></ul></li></ul> <p> 9. Defining Collaboration</p> <ul><li>David Snowden </li></ul> <ul><li><ul><li>Innovation requires </li></ul></li></ul> <ul><li><ul><li><ul><li>Starvation </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Pressure </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Perspective Shift </li></ul></li></ul></li></ul> <ul><li>Enterprise 2.0 helps build a collaborative culture which improves an organisations ability to shift perspective </li></ul> <p> 10. </p> <ul><li>Understanding the interaction between CorporateCultureandCollaborative Tools </li></ul> <p> 11. Successful Examples </p> <ul><li>Open source </li></ul> <ul><li><ul><li>Apache web server </li></ul></li></ul> <ul><li><ul><li>Developed with </li></ul></li></ul> <ul><li><ul><li><ul><li>No central ownership</li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>No single Project Manager </li></ul></li></ul></li></ul> <ul><li><ul><li>Out did Sun, Microsoft &amp; IBM </li></ul></li></ul> <p> 12. Successful Examples </p> <ul><li>Peer Production </li></ul> <ul><li><ul><li>Harnessing external talent </li></ul></li></ul> <ul><li><ul><li>Keeping up with users </li></ul></li></ul> <ul><li><ul><li>Reducing costs </li></ul></li></ul> <ul><li><ul><li>Taking friction out of inter-firm collaboration </li></ul></li></ul> <ul><li><ul><li>Developing social capital </li></ul></li></ul> <p> 13. Successful Examples </p> <ul><li>Clandestine Collaboration </li></ul> <ul><li><ul><li>Google Search </li></ul></li></ul> <ul><li><ul><li>Amazon Profiles </li></ul></li></ul> <ul><li>Passive, not active </li></ul> <ul><li>Benefit from others use </li></ul> <p> 14. Web 2.0 Technologies 15. Why not Inside the Enterprise ? </p> <ul><li>Web 2.0 and Enterprise 2.0 </li></ul> <ul><li><ul><li>What is the Same? </li></ul></li></ul> <ul><li>Evolutionary growth model </li></ul> <ul><li>Very intuitive and easy to use </li></ul> <ul><li>Web / Ajax based</li></ul> <ul><li>Focus on Community then Process </li></ul> <p> 16. Why not Inside the Enterprise ? </p> <ul><li>Web 2.0 and Enterprise 2.0 </li></ul> <ul><li><ul><li>What is the Difference? </li></ul></li></ul> <ul><li>Focus on Business needs </li></ul> <ul><li>Security &amp; Integration with corporate IT </li></ul> <ul><li>Integration, ie: Single Sign-in </li></ul> <ul><li>Customer Support Transparency &amp; Quality </li></ul> <p> 17. Possible Applications </p> <ul><li>Wiki study of 5 SMEs showed 31 different uses for wikis, including: </li></ul> <ul><li><ul><li>Project Management tool </li></ul></li></ul> <ul><li><ul><li>Basic CRM </li></ul></li></ul> <ul><li><ul><li>Documentation </li></ul></li></ul> <ul><li><ul><li>Collaborative spec development </li></ul></li></ul> <ul><li><ul><li>Collaborative problem solving </li></ul></li></ul> <ul><li><ul><li>Deciding which pizzas to order for the team lunch </li></ul></li></ul> <ul><li><ul><li> Its too much mucking around! </li></ul></li></ul> <p> 18. High-level Collaboration </p> <ul><li>External </li></ul> <ul><li>International cultures </li></ul> <ul><li>Out-sourcing </li></ul> <ul><li>Off-shoring </li></ul> <ul><li>Privacy concerns </li></ul> <p> 19. Internal Collaboration </p> <ul><li>Discovering Internal Resources </li></ul> <p> 20. When Collaboration Works? </p> <ul><li>Clear Purpose </li></ul> <ul><li>Common Sense of Community </li></ul> <p> 21. The Daniels Wiki </p> <ul><li>Bringing many minds to bear: </li></ul> <ul><li>Project Management </li></ul> <ul><li><ul><li>Scope documents </li></ul></li></ul> <ul><li><ul><li>Timelines and resource allocation </li></ul></li></ul> <ul><li><ul><li>Tasklists </li></ul></li></ul> <ul><li><ul><li>Progress reports </li></ul></li></ul> <ul><li><ul><li>Exception tracking </li></ul></li></ul> <ul><li><ul><li>QA </li></ul></li></ul> <p> 22. The Daniels Wiki </p> <ul><li>Bringing many minds to bear: </li></ul> <ul><li>Collaborating across Time-Zones </li></ul> <p> 23. The Daniels Wiki </p> <ul><li>Bringing many minds to bear: </li></ul> <ul><li>Collaborating up the chain of command </li></ul> <p> 24. The Daniels Wiki </p> <ul><li>Bringing many minds to bear: </li></ul> <ul><li>Collaborative Problem Solving </li></ul> <p> 25. The Daniels Wiki </p> <ul><li>Bringing many minds to bear: </li></ul> <ul><li>Collaborative Problem Solving </li></ul> <p> 26. </p> <ul><li>Supplying the Raw Materials for Innovation in a Changing Environment </li></ul> <p> 27. Staying Grounded </p> <ul><li>Its about matchingYOURDesired Outcomes, Culture and Tools </li></ul> <ul><li><ul><li>Don't get caught by hype </li></ul></li></ul> <ul><li><ul><li>What works for others may not work for you </li></ul></li></ul> <ul><li><ul><li>Get professional advice </li></ul></li></ul> <ul><li><ul><li><ul><li>Must understand </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li><ul><li>Business </li></ul></li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li><ul><li>Enterprise 2.0 </li></ul></li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li><ul><li>Preferably product agnostic </li></ul></li></ul></li></ul></li></ul> <p> 28. Focus on Holistic Capability Stages of Adoption Collaboration Technologies Stage 1: Traditional Collaboration Telephone Face-to-face Meetings E-mail, phone, fax, other classic technologies Stage 2: Specific Problems and Applications Audio, Video &amp; Data Conferencing EIM, IM, Chat &amp; presence detection Virtual Team Spaces (VTS) Stage 3: Collaborative Proliferation Multiple A/V/D Conferencing tools Yahoo, MSN, AOL, Google Groove, eRoom, WebOffice, etc. Stage 4: Consolidation and Standardization Standardize on SIP/Simple or XMPP One Client for all IM clouds Common virtual team space for everyone Stage 5: Virtual Work Environment Standard tools in place Integration with Mobile Environment Standard Desktop &amp; Web Interface for anyone 29. Research Surprises </p> <ul><li>Size does not always equate to perceived success by management </li></ul> <ul><li><ul><li>Be careful what measures you use </li></ul></li></ul> <ul><li>Wiki update is amazingly fast when transferring from other tools because of ease of use </li></ul> <ul><li><ul><li>Old system: 5 years120 pages </li></ul></li></ul> <ul><li><ul><li>Wiki system: 1 year1000+ pages (by 17 users) </li></ul></li></ul> <ul><li><ul><li>Changeovertime:2 months ! </li></ul></li></ul> <p> 30. </p> <ul><li>Required competencies for participating in an open knowledge and innovation-sharing environment </li></ul> <p> 31. Implementation Tips 32. Implementation Tips </p> <ul><li> Both too much and not enough management proved detrimental to the success of the wiki. French, 2008 </li></ul> <ul><li>Pilot for the quick ROI to prove the concept </li></ul> <ul><li>Integrate tool into existing business processes </li></ul> <ul><li>Assure smooth integration from existing work flows </li></ul> <ul><li>Develop guidelines and best practices </li></ul> <ul><li>Find a champion </li></ul> <ul><li>Plan for Change Mgt issues </li></ul> <ul><li>But most of all: </li></ul> <p>Find the balance 33. Implementation Tips </p> <ul><li>Manage the transition to Enterprise 2.0 </li></ul> <ul><li><ul><li>From Command &amp; Control </li></ul></li></ul> <ul><li><ul><li>To Connect &amp; Collaborate </li></ul></li></ul> <ul><li>Learn to balance Control with Distributed Authority </li></ul> <ul><li><ul><li>Who needs to make the decision? </li></ul></li></ul> <ul><li><ul><li><ul><li>What knowledge do they need to make the right choice? </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Getting the balance wrong stifles collaborative innovation </li></ul></li></ul></li></ul> <p> 34. </p> <ul><li>Finding knowledge and support </li></ul> <ul><li>on your Web 2.0 journey </li></ul> <p> 35. More Information </p> <ul><li>Sources / References </li></ul> <ul><li><ul><li>Blogs </li></ul></li></ul> <ul><li><ul><li><ul><li>Anecdote Shawn Callahan </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Trends in Living Networks Ross Dawson </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Enterprise 2.0 Andrew McAffee </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Delta Knowledge Stuart French </li></ul></li></ul></li></ul> <p> 36. More Information </p> <ul><li>Books </li></ul> <ul><li><ul><li>Australian KM Standard - AS 5037-2005 </li></ul></li></ul> <ul><li><ul><li><ul><li>Prescriptive not descriptive </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>SME Version - HB 190-2006 </li></ul></li></ul></li></ul> <ul><li><ul><li>Wikipatterns </li></ul></li></ul> <ul><li><ul><li>Collaboration 2.0 </li></ul></li></ul> <ul><li><ul><li><ul><li>Resource list on page 253 </li></ul></li></ul></li></ul> <p> 37. Key Points </p> <ul><li>Digital Collaboration is a powerful trend </li></ul> <ul><li>Culture is something you grow, not manipulate </li></ul> <ul><li>Innovation is cultural not just for R&amp;D </li></ul> <ul><li>Balance Command &amp; Control with Connect &amp; Collaborate </li></ul> <ul><li>Beware driving with the rear-view mirror </li></ul> <ul><li>Stay grounded, implement slow and wide </li></ul> <ul><li>Get good guidance </li></ul> <p> 38. </p> <ul><li>Thanks: </li></ul> <ul><li>IA Web Trends </li></ul> <ul><li>Daniels Sharpsmart </li></ul> <p> 39. </p> <ul><li> Collaboration is an emergent property of the complex system of relationships we call culture. </li></ul> <p>Extra 40. Influencing a complex environment </p> <ul><li> In a complex system, you can never fully know the outcome in advance Snowden </li></ul> <p>Extra 41. Influencing a complex environment </p> <ul><li>Beware 20-20 Hindsight </li></ul> <ul><li><ul><li>Retrospective Coherence </li></ul></li></ul> <p>Extra 42. Influencing a complex environment Twigs Leaves = Possible futures Branches = Possible decisions Trunk = The present Roots = The past - Edward de Bono Extra 43. Influencing a complex environment </p> <ul><li>Beware 20-20 Hindsight </li></ul> <ul><li><ul><li>Retrospective Coherence </li></ul></li></ul> <ul><li><ul><li><ul><li>Develop an environment where people are comfortable to make decisions without all the information </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>Be slow to judge after the fact </li></ul></li></ul></li></ul> <ul><li><ul><li>Learn how to look forward </li></ul></li></ul> <ul><li><ul><li><ul><li>Rear-view mirrors only work when the road is straight </li></ul></li></ul></li></ul> <ul><li><ul><li>What has this got to do with Web 2.0? </li></ul></li></ul> <ul><li><ul><li><ul><li>Unstifled innovation is key to adoption and returns </li></ul></li></ul></li></ul> <p>Extra 44. Influencing a complex environment </p> <ul><li>Do </li></ul> <ul><li><ul><li>Safe-Fail adoptions </li></ul></li></ul> <ul><li><ul><li>Let systems evolve and even die out </li></ul></li></ul> <ul><li><ul><li><ul><li><ul><li>consider starting outside the firewall </li></ul></li></ul></li></ul></li></ul> <ul><li><ul><li>Let the users decide what is more practical to achieve their local business goals </li></ul></li></ul> <ul><li><ul><li>Have IT simply focus on the provisioning and security aspects </li></ul></li></ul> <p>Extra 45. Influencing a complex environment </p> <ul><li>Dont </li></ul> <ul><li><ul><li>Insist on perfection </li></ul></li></ul> <ul><li><ul><li>Look for single solutions </li></ul></li></ul> <ul><li><ul><li>Try to control instead of encourage use </li></ul></li></ul> <ul><li><ul><li>Rely totally on official modes of communication </li></ul></li></ul> <ul><li><ul><li>Expect people </li></ul></li></ul> <ul><li><ul><li><ul><li>to never make a mistake </li></ul></li></ul></li></ul> <ul><li><ul><li><ul><li>to know everything </li></ul></li></ul></li></ul> <p>Extra </p>