Corporate Productivity Tool-chain
Or what is the name for corporate "life hack"?
Discussions about an enterprise blogging project and it's culture change at the recent BlogCamp showed that channel-based semantic publishing found it's way into corporate headquarters. I guess that's because the first digital natives generation reached the corporate ladder and are about to transform their workplace.
Working for a small tech-savvy outfit (read: 80% software engineers) with a friendly corporate productive playground - we are right now at following picture (slide from an internal presentation I gave in June 2007):
Best to read from bottom to top.
Wrote about this in "Proven Setup: A People + Skype + Wiki + Task Tracking + Whiteboard" (May 2007).
Beyond the general agreement that the setup produces the wished results (increased team productivity) there are challenges in partner integration. The bridge to partners with "less web-based tool-chain" causes disruption of continuity. Further - the fallback to e-mail - instead of feed reading - causes over-head. It's surprising that "feed readers" are still not part of the default "desktop setup" - are they still too hard to use?
Discussions about an enterprise blogging project and it's culture change at the recent BlogCamp showed that channel-based semantic publishing found it's way into corporate headquarters. I guess that's because the first digital natives generation reached the corporate ladder and are about to transform their workplace.
Working for a small tech-savvy outfit (read: 80% software engineers) with a friendly corporate productive playground - we are right now at following picture (slide from an internal presentation I gave in June 2007):
Best to read from bottom to top.
Wrote about this in "Proven Setup: A People + Skype + Wiki + Task Tracking + Whiteboard" (May 2007).
Beyond the general agreement that the setup produces the wished results (increased team productivity) there are challenges in partner integration. The bridge to partners with "less web-based tool-chain" causes disruption of continuity. Further - the fallback to e-mail - instead of feed reading - causes over-head. It's surprising that "feed readers" are still not part of the default "desktop setup" - are they still too hard to use?
The default "desktop setup" is still from Microsoft and currently there's, in my point of view, no good integration for feeds in outlook and it's a pain to have one more tool just for feeds.
Posted by
leo |
October 24, 2007 8:56 PM
I am a big web guy, but still have not adopted RSS over Email, while agree RSS may be more efficient. It may be that the expectation that email is still faster (you are sending directly to someone, and thus expect them to reply quickly, vs. "broadcasting" RSS) still holds.
And RSS has to be accepted by everyone... most people in a corporate environment still don't know what RSS is, or at least not how to use it.
Posted by
Erik Samdahl |
November 26, 2007 6:35 PM
Post a Comment