Archive for the ‘wiki’ Tag

Why in the world are we paying for Social Text? « DC’s Blog

Why in the world are we paying for Social Text? « DC’s Blog

There’s a good string of comments here.  Mine is as follows:

I both agree and disagree with Alan here.  Disagree in the sense that I think some “free” sites are competition – namely, Google.  Many companies have precisely moved away from enterprise level email hosting, and routing their corporate email through Gmail.  I think there is a real danger here that Google sites (Google’s free wiki platform) could morph into a similar competitor.

On the other hand, my experience with SocialText is that they tend to be fairly proactive in platform development.  Just as I wish that ST had a feature, it’s not long before it appears (of course, I’ve been asking for the ability to “rate” pages for years now to no avail).  I also agree that ST is a very “user friendly” experience.  They do a good job at hand-holding, which is required for the short term adoption of these tools.  If ST continues to hand hold and use those opportunities to respond to customer concerns by adding new features, then they could stay one step ahead of the Googles of the world.

It might never become a $50B company, but by pushing the envelope on group collaboration they can might find a good niche that they can ride for many years.  We’ll see.

What they really need to do is hire me as a consultant to go into companies and give my dog and pony show on group collaboration.  Maybe if they reach their first billion.

Socialtext – more than a facelift

Tech Joy

I’ve seen both Claire and Joy discuss the so-called “facelift” that has happened in our socialtext platform that we use for class.  I have been interested in this discussion, mainly for the implications that the conversation suggests.

My first response is that these changes are far more than just a “facelift.”  It represents a fundamental redesign (or at least powerful new functionality) to the way Socialtext operates.  “But wait” I hear you saying, I don’t see any fancy new technology…it works the same but just looks different.  Well, yes and no.

I have been very excited about the potential of the new ST 3.0 platform, and I have been following release notes closely.  A year ago I met with ST developers and told them that I thought this was the direction the platform should go (only to find out that their CEO had expressed the same sentiment two weeks earlier…great minds may think alike but this mind gets paid alot less!)

So, I went to try out this new functionality, and use this as a teachable moment for Joy and Claire to not judge a book by its cover, only to find out that the new features were not yet turned on.  Why on earth would ST do this?  These cool new toys and I have to ask for permission to play with them.

After further thought, however, it makes alot of sense.  We’ve been talking in class lately about computing as a service.  Companies who offer software as a service have to contend with an issue that I had not previously considered – upgrading the software without the user’s permission or knowledge.  It would have been a rude awakening not to just have ST look different but act different without any real advance warning.  So, their approach was to make the tools available if we want them.  Prety smart, if you ask me.

I’m tentatively planning on having ST’s director of marketing in class sometime over the next few weeks to discuss the changes.  I’ll give you a heads up so we can all be ready to explore the new functionality and decide (as a class) if we want to adopt it.  Could be interesting for us all.