Presentation on theme: "Gartner’s Top Ten Technology Trends for 2014 1.Mobile Device Diversity and ManagementMobileManagement 2.Mobile Apps and Applications 3.The Internet of."— Presentation transcript:
Gartner’s Top Ten Technology Trends for 2014 1.Mobile Device Diversity and ManagementMobileManagement 2.Mobile Apps and Applications 3.The Internet of Everything 4.Hybrid Cloud and IT as Service Broker 5.Cloud/Client Architecture
Gartner’s Top Ten Technology Trends for 2014 6.The Era of Personal Cloud 7.Software Defined Anything 8.Web-Scale IT 9.Smart Machines 10. 3-D Printing
Question How has conventional (‘mainstream’) news reacted so far? – is it good? – is it enough? – will they survive?
Prosumption A fairly big leap for current organizations – versus customization ordering a car versus modifying it – issue of control Apple versus Google/Linux/Apache – customer toolkits creator as a peer – finally, ‘sharing the fruits’
Wikis in the workplace One of the key tools in enterprise social networking Three key application opportunities: – Websites to communicate with large audiences – Private team spaces – Catalog and define facts and processes
Wikis and Tacit Knowledge Knowledge sharing Collaboration Team building
5 Key Differences Between Wikipedia and Enterprise Wikis ‘Future Changes’ blog (www.ikiw.org)
5 Key Differences Between Wikipedia and Enterprise Wikis Organization and Access Internet wikis often have all content housed in one “place,” so that anyone can access the entirety of the site’s content. Enterprise wikis, by contrast, allow for information to be organized in individual workspaces based on project, department, team, etc., and access to those spaces can be granted to specific people.
5 Key Differences Between Wikipedia and Enterprise Wikis Security – Internet wikis are often open for anyone to read and edit, sometimes without even requiring one to login. Enterprise wikis are typically not open to the public or partially open, i.e. some spaces are open but others are not. To access an enterprise wiki, you have to login, and your account has to have permissions set so that you can access particular spaces. Permissions can also be set at the page level, so that a person might login, access a particular space, and have editing rights on some pages, but only viewing rights on others.
5 Key Differences Between Wikipedia and Enterprise Wikis Integration – Enterprise wikis are designed to allow user account, group, and access information to be provisioned from authentication and authorization systems like LDAP and Active Directory, so that a person can login to the enterprise wiki with the same credentials that they use to access email, the company network, etc.
5 Key Differences Between Wikipedia and Enterprise Wikis Typical Uses – Enterprise wikis are often used for: collaboratively building documentation creating and maintaining knowledge bases project management gathering tacit knowledge (knowledge not related to any specific project but essential to getting things done in an organization)
5 Key Differences Between Wikipedia and Enterprise Wikis Typical Uses – Enterprise wikis are often used for: meeting management, from agenda to minutes and action items. Generally, an enterprise wiki will be used in a much wider variety of ways than an Internet wiki, because it is intended to support the wide-ranging needs of the people within an organization. Internet wikis tend to be used primarily for one main application, as is the case with Wikipedia.
5 Key Differences Between Wikipedia and Enterprise Wikis Contribution Level – On public wikis, we often speak of the 90-9-1 Theory, which explains that 90% of users will “lurk” or simply browse pages, 9% will contribute occasionally, and 1% will contribute frequently, and account for most of the contributions to the wiki.
5 Key Differences Between Wikipedia and Enterprise Wikis Contribution Level – On an enterprise wiki, the contribution level is much higher based on the fact that people are contributing as part of the daily course of their work, as opposed to voluntarily contributing to a public, Internet wiki. This contribution isn’t necessarily compulsory, as a top-down mandate will usually hinder more than help wiki adoption. Instead, it’s the result of well-executed wiki adoption strategies that place the wiki at the center of the core activities of a team, such as meeting management, building a support knowledge base, or collaboratively writing documentation for a product.