Share:|

I remember reading an article back in 2009 suggesting that Twitter would make a great place for teams to monitor error logs for web applications. The argument went that you could use PHP to post errors as they happened to a Twitter feed, which entire teams could monitor.

 

Clearly, with Twitter being such a public venue - and a notoriously unstable one, at that - the idea was dead in the water the moment it was had.

 

But it was interesting. From pretty much the day I started using Chatter from Salesforce.com internally at BMC, I have noticed great value. I not only communicate better with my employees, but with the members of many "virtual teams" I am a member of - and through conversations I have stumbled onto, I have had a seat at the table in dialogues I would never have known were happening. As a marketing guy, it's cool to suddenly find yourself talking with a bunch of R&D guys and trading ideas, or fielding a question from the sales team.

 

Since Chatter is basically an internal-only version of Twitter, and is therefore a bit more secure, I started thinking about revisiting the brainstorming session about ways to use it. Could web apps or IT services or even hardware each have a Chatter account where they post their goings on? Certainly, they could just maintain their own feeds - logging error messages to a place where larger teams could see them, comment to each other, and collaborate on resolutions.

 

I don't think it's about changing what our technology is saying - to itself or to other technologies. It's about bringing that communication into the most robust and usable communication platform. BSM does that in so many ways, bringing all IT disciplines into a common platform which can dramatically simplify IT management. At the center is the CMDB, which in so many ways is an internal Chatter feed, but unless I am mistaken (again, I am a marketing guy with enough tech knowledge to be fooolishly passionate and clumsy), it's a one-way, 1:1 feed of information.

 

I'm interested in ideas for one-to-many communication, and more importantly, how those conversations - among people, processes, and assets - get brought to the forefront, where problems can get solved, new ideas hatched, and efficiencies gained in the same way the Chatter dialogues I have had over the past few weeks have done for me personally.

 

What are your thoughts? What already exists, and how can we push it?