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?
