I am chomping at the bit about the 3D Internet (of which virtual worlds and massive multi-player online games are early iterations). What I see is its potential to improve my work experience dramatically — and the work experience of information workers world-over. Not that I've got it rough — I am privileged to be able to work from my home office in rural Rhode Island when I'm not on the road. But working remotely has two major downsides:
It's Thursday night of Forrester IT Forum and I've had 19 formal one-on-one meetings with attendees so far, and talked with dozens of other people during meals and breaks and before and after presentations. There's something striking about these conversations, compared to years past. Pretty much every meeting I've had with non-vendor attendees has been about their organization's enterprise collaboration strategy or Information Workplace strategy — or their need to develop one. I've been speaking with information and knowledge management professionals with titles like CIO, VP Emerging Technology, Sr. Project Leader, Dir. Global Strategy and Architecture, and VP of Information Systems. They are coming to 1:1 meetings extremely well-prepared, armed with architecture diagrams, drafts of their collaboration strategy documents, and lists of carefully thought-through questions. What a difference from five years ago when common questions were, "What are other companies doing in the area of collaboration?" or "Which is a better team collaboration tool: eRoom or Groove?"
My mind is a sieve. It can take a few requests before I remember to do something. And even with a few prods, it takes a while for me to get moving. But I've gotten so many requests along the lines of "What does a collaboration strategy document look like? What should it include?" that it's all I'm thinking about these days.
I will be publishing a sample collaboration strategy document in Q2. If you have developed and documented an enterprise collaboration strategy and would be willing to share it with Forrester for the greater good of industry research--with our promise to guard it and not share it with anyone outside the company--we would love to include you in our research. You can find me at email@example.com.
This week, the mainstream press reported that Microsoft made a Wikipedia “no-no”: Microsoft offered to pay an independent contributor — Rick Jelliffe — standards expert and the CTO at an Australian tech company — to investigate the accuracy of, and change, if necessary, technical articles about Open XML and Open Document Format (ODF) on Wikipedia. ODF is an OASIS and ISO standard and Open XML is Microsoft’s alternative, currently an ECMA standard and potential ISO standard. Kyle McNabb and I were talking about this incident. Here are our thoughts: