Published in OSCON,
barcamp,
barcampportland,
blogging,
blogs,
clearspace,
clearspace x,
collaboration,
community,
conference,
dawn foster,
enterprise 2.0,
forums,
ignite realtime,
im,
jive software,
openfire,
productivity,
spark,
web 2.0 and
wiki .
My first week at Jive has been a whirlwind of activity, and I think that I have been super productive for the first 5 days on the job. I’ve completed a first draft of how we might build Jive’s new developer community on our newly released Clearspace X infrastructure. I am re-working the process for how we give away free licenses of Jive’s Clearspace and Forum products to open source projects. I’ve put together a new demo script for our CEO to use at BarCamp - customized for what I think will be the audience at BarCamp. I was also able to get confirmed speaking engagements at Defrag and OSCON this week. All this while being constantly distracted with last minute BarCamp details as the co-organizer of the BarCamp Portland event this weekend (note to self: next year, do NOT start a new job the week that you are holding BarCamp!)
How was I able to get all of this done while getting up to speed in a new company? It comes down to dogfood, specifically, to eating our own dogfood at Jive. We use the current Clearspace beta product for all of our documents, to hold discussions, for blogging, and more. Most of the information that I needed was already in Clearspace. For new information, I just started discussions in Clearspace where I asked other Jive employees about things like what to name the new developer community, how to promote our new developer community, and more. I posted all of my work as wiki documents in Clearspace, and because everyone uses it, I was able to get feedback and information from across the company.
We are also avid users of our Openfire / Spark IM solution with every Jive employee already populated in our buddy lists from day 1 on the job. I worked with an employee in Canada over IM to help him reproduce an issue that I was seeing in our beta product, discussed our Ignite community with our CTO, negotiated with our web developer on resources to get some web forms completed, and much more.
I have to say that Jive seems to be a great fit for me. I’m working with people who are just insanely smart, who live web 2.0 technologies, and we’re working on some really cool collaboration software. Did I mention that we are hiring?
I was just reading Richard MacManus’ coverage of Forrester’s recent reports about web 2.0 in the enterprise:
“Forrester Research has just released two reports concerning ‘web 2.0′ in the enterprise. Forrester recently surveyed 119 CIOs on the topic and their answers illustrate what IT honchos want – and don’t want – from social software technologies such as blogs, wikis, podcasts, RSS, social networking, and content tagging.
According to the report entitled ‘CIOs Want Suites For Web 2.0′, the enterprise Web 2.0 market “is beginning to consolidate”. Apparently CIOs have a strong desire to purchase web 2.0 products “as a suite, as well as an equally strong desire to purchase these technologies from large, incumbent software vendors.” 61% of respondents indicated that they would prefer both a suite solution and a large, incumbent vendor. According to the report, “integration issues, longevity concerns, and the occasional lack of polish” are counting against small vendors.” (Quote from Richard MacManus on Read/WriteWeb)
The data is interesting, but I am not sure that Forrester was asking the right questions or the right people. My experience with web 2.0, and other innovative technologies (open source, etc.) is that there is a big gap between what many CIOs want / think they have and what is really happening within their organization. Those of us who are passionate about web 2.0 technologies just tend to use them. This often means that we bring things like IM, wikis, and more into our corporate life as productivity tools regardless of whether or not the technology is officially sanctioned. For example, Intelpedia, an internal Intel wiki, was started as a grass roots effort on a test server without “official” buy in because Josh Bancroft and other Intel employees thought that Intel needed an internal wiki to help manage information. A better study might have been to ask people a few levels below the CIO about the web 2.0 technologies currently being used in their organization.
CIOs may want web 2.0 suites from larger, incumbent software providers, but I suspect that the reality of what is actually used within enterprises over the next few years will differ significantly from this CIO vision.
If you are nostalgic for the dot com Super Bowl ads circa 2000, you might want to check out the SuperDotComAds from Meebo, Technorati, and others on YouTube.
Where will I be this weekend instead of watching the Super Bowl? With all of the other geeks at RecentChangesCamp, of course! I just Tivo the game to watch the commercials anyway.
RecentChangesCamp is free, and it runs from Friday morning through Sunday afternoon in Portland. If you are in the area, you should check it out. Proposed topics include wikis, collaboration, identity / OpenID, and more!
I just posted an entry on my Intel Trends in Web 2.0 blog about how “Wikis can be a great collaboration tool for use internally within the corporate environment or externally for use with customers or clients.”
If you want to learn more benefits of using wikis and hear about how I have been recently using wikis for collaboration, please visit my Intel Trends in Web 2.0 blog.