1. Intranet 2.0
Evolution from Content Management or
Revolution by Social Software?
Frank Wolf, T-Systems Multimedia Solutions
Enterprise 2.0 Summit, Frankfurt 1 1.2009
1.1

2. 2 „Problem Child‘s“

3. 1. Enterprise 2.0

5. ?

6. 2. Intranet 1.0

7. Intranet 1.0: A Digital Newspaper
Intranet 1.0
Static push information and communication.

8. Intranet 1.0: the core business is not in scope

9. Enterprise 2.0 + Intranet 1.0 = Intranet 2.0

10. Grafik: http://www.barackobama.com/downloads/

11. From
Communication to
Conversation to
Collaboration
Credible
Authentic
Decentral
Open
Convincingly

12. Intranet 1.0 Intranet 2.0
Communication
Collaboration

13. Intranet 2.0
+ Web 2.0 features are on every agenda
+ “Cost of Doing Business” vs. ROI
+ Many “given” use cases to start with
+ Smooth way to Enterprise 2.0

14. Start small – think big.
Openness is the rule:
Agile projects. closed areas only by
request.
Employees as
ambassadors on the
web.
Executive Blog. Employee Blog.
Comments allowed.

15. Define your Enterprise 2.0...
Conventional Web
Businesses 2.0
Authors few editors all employees
Approval central individual
Identity authentification necessary anonymity possible
Structure centrally determined generated by usage
Semantics taxonomy folksonomy
Inspired by an idea from J. Robes, www.weiterbildungsblog.de

16. What Technology to choose
for an Intranet 2.0?

17. Considerations
• NoGo: single Wiki, Blog, Forum,…
• CMS or Social Software Suite?
• One platform preferred
• One platform for the whole process

18. Example: Intranet 2.0

19. Is a Social Suite ready for
every Intranet 2.0?

20. CMS Features
• Import, create and edit content
• Approval workflow
• Personalisation
• Content reuse
• Archiving
• Content and navigation structure
• Site layout templates
• Performance
• Reporting (content and user)
• Roles and access
• Search
• Channels
• Multisite management

21. How CMS Features match Social Suite Features
• Import, create and edit content
• Approval workflow
Green=features are
• Personalisation
available at social suites
• Content reuse
• Archiving Yellow=basic features
• Content and navigation structure available or can be
• Site layout templates made available with
• Performance some effort
• Reporting (content and user)
• Roles and access Red=features only
• Search available with high
• Channels effort
• Multisite management

22. Thank You!
Frank Wolf, Managing Consultant T-Systems Multimedia Solutions
Mail: f.wolf@t-systems.com
Web: www.t-systems-mms.de
Blog: www.besser20.de
Twitter: www.twitter.com/frankx
Xing: www.xing.com/profile/Frank_Wolf3