Mots-clés : Office 2.0, Wearesmarter.org, collaboration, Facebook, IT departments

Following on from the various discussions Xavier launched on l'Entreprise 2.0, while surfing on Wearesmarter.org I found Aaron Strout's blog where he discussed the recent Office2.0 Conference in the States.
Here he was summing up a panel chaired by Om Malik (of Giga Om) on the subject : the Future of Work...thought you might be interested...

(the abreviations refer to the panel participants...) For more check out Citizen Marketer on Wearesmarter.org.

What is office 2.0?

• SA/Intuit - 100 years ago, 20% of works were "information workers". 20 years ago, 60% of workers were information workers. Now, nearly everyone in the workplace plays some role as an information worker.
• DB/SAP - The key to the future is flexibility.
• JR/Google - Collaboration is key (downside is that it makes it difficult to separate home life from work life.)
• DK/Etelos - The market is demanding products before they are ready i.e. product innovation has become demand driven vs. supply driven.
• RM/Microsoft - If you look at the enterprise, the requirements are different than they are in the consumer space. Key is, how do you move consumer innovation into the workplace. IT demands that it still has some control over worker's desktop.

What role does "ease" play vs. "collaboration in Google Docs?

• JR/Google - Ease was the original focus for the application but collaboration was a bi-product. Now that it's there, people really like to work with it.
• DK/Etelos - Consumer demand is causing havoc in the workplace. IT's biggest concern is "where is data" hosted. This is true across all "shadow IT" applications.

What will be key ingredients of Office 2.0 going forward? Key features?

• RM/Microsoft - It's important to look at what people are trying to do. If what you're building isn't needs-based, likeliness to succeed will be minimal. Something like FaceBook in the workplace could be huge (like search, e-mail and ecommerce in the past.)
• DB/SAP - They are using every imaginable consumer web 2.0 application internally so they are aware of what's out there and how they can be harnessed to help users in the enterprise. SAP is doing a lot of experimenting with widgets in the enterprise (simple and complicated) to evaluate which bring the most value.
• DK/Etelos - One thing that must be considered is "what is an enterprise."

How do we fix problems with 1.0 applications like e-mail (we love the functionality but hate having to hunt and peck for the meaningful e-mails that we want to read?)

• RM/Microsoft - Customization is one thing that will make things easier.
• DB/SAP - We shouldn't have to work ourselves. Let the apps use inference engines and collaborative filtering.
• SA/Inuit - Innovation WILL happen at the small business level. They don't have the baggage of large IT departments and they are inclined to do what they love.
• DK/Etelos - The technology underneath each app needs to get smarter and smarter.
• RM/Microsoft - Apps that learn over time ARE the future.

Parting thoughts:

• RM/Microsoft - We can't forget the importance of documenting and debugging applications for the enterprise.
• DK/Etelos - Integration of Web 2.0 apps will be critical (we're at the bleeding edge.) As a sidebar, I had this conversation with a number of people last night. There is already an emerging industry that is called "integrators of software as a service." This should be huge moving forward.
• SA/Intuit - Data standardization and how data is presented is key.

CM Intranet, Blog et RSS 1 commentaire Lu 485 fois

Article précédent

Commenter

Article suivant