Is IBM onto something here, ahead of Microsoft? Indeed, Lotus-based organizations should see benefit from the secure enterprise microblogging as described below. Seems organizations based on Exchange would similarly benefit, if the upcoming Exchange 2010 release would include these "publish/subscribe dialogues" within the enterprise, similar to Twitter (but no indication of that from the Exchange 2010 Beta so far). Exchange's unified messaging since Exchange 2007 may be useful and have significant benefits, but IMHO not as simple and easy to use as a Twitter-like service could/should be, if integrated intelligently into the enterprise architecture. Here's further information courtesy of IBM Enterprise Microblogging Debuts - Technology For Change:
"Lotus Connections now boasts a Twitter-like service that lets employees establish and maintain publish/subscribe dialogues within their organizations.
At its Center for Social Software symposium being held this week in Cambridge, Mass., IBM announced the release of a microblogging and file-sharing facility bolstering the Lotus Connections suite of enterprise social networking tools. The Twitter-like service enables employees to establish and maintain publish/subscribe dialogues within their organizations.
Additional features added to Lotus Connections include support for iPhone and Nokia S60 mobile devices, including microbrowser access to Profiles, Activities and the Lotus Connections blogging tool..."
Musings on personal and enterprise technology (of potential interest to professional technoids and others)
Wednesday, September 30, 2009
IBM/Lotus Enterprise Microblogging Debuts: What about Microsoft?
Posted by
dgftest
at
10:44 PM
0
comments
Labels: collaboration, Enterprise-Architecture, ExchangeServer2007, IBM, Microsoft, mobile-computing, Twitter, unified-messaging, Upgrade-Treadmill
Tuesday, August 11, 2009
3 Reasons a CIO Should Care About Twitter — CIOUpdate.com
Senior IT executives / CIO's can also benefit from Twitter, according to CIOUpdate.com . The relevant observations excerpted below are a nice complement to my recent post Re: Should Project Managers Twitter? . So here are some of the potential business benefits of Twitter which (when balanced against the known Twitter security/privacy issues) can make sense for many organizations:
3 Reasons a CIO Should Care About Twitter — CIOUpdate.com: "...If all the buzz in the mass media isn’t enough to get you interested in Twitter, here are three solid business reasons why CIOs should devote some time to learning more:
1. Get Targeted Insights Faster - ... Some of the smartest people I meet haven’t devoted themselves to publishing or publicity that gets them a high Google ranking. But they are willing to share their experience and make themselves available for legitimate conversations.
Enter Twitter. Anyone can post their 140-character question, idea or comment on any topic. While the stream is uncensored and unfiltered, it is highly searchable. And because responses come in real time, it’s a channel that is particularly suited for time-sensitive information.
2. Participate in Social Media Innovation - ... the availability of Twitter’s API may present a direct opportunity for you and your company’s brand and products. Is there a way to utilize Twitter to support customer service (see @ComcastCares), promotions, order tracking, etc?
3. Expand Your Professional Network: ... as Twitter participation stabilizes will a valuable professional community emerge? There are some early signs that a viable CIO community exists on Twitter. At this point, I’ve identified over 70 CIOs across 20 industries. You can keep tabs on the growing community at http://www.ciodashboard.com/cio-twitter-dashboard . ..."
Posted by
dgftest
at
10:28 PM
0
comments
Labels: collaboration, Knowledge-Management, Marketing, mobile-computing, privacy, security, Service-Management, Twitter, wireless, Workflow
Tuesday, July 14, 2009
Secure Enterprise Twitter-like microblogging from Socialtext - Webware.com 14-July-2009
I recently discussed whether project managers should use twitter.
With the new Socialtext corporate appliance that runs a Twitter-like app behind the firewall, business use of Twitter (or a similar type of "microblogging" capability) now appears to be a simpler issue. This solution seems especially relevant for large organizations wishing to enhance their internal communication, messaging and overall knowledge management. Nice to see that the issue of backup / DRP is apparently being addressed as well:
Socialtext offers enterprise microblogging in a box | Web Crawler - CNET News: "As a follow-up to its free, 50-user microblogging product, Socialtext is launching a new paid service for large to enterprise-sized companies that lets them run the Twitter-like service behind the firewall, and with many more users.
Companies that want it can pay $1 per user, per month, alongside a monthly fee that pays for Socialtext's server appliance. This hardware runs the microblogging software locally, and can be connected to a company's backup systems for if something goes wrong, although it makes nightly backups of its own. The appliance fee also covers monthly software updates that will fix bugs and add new features...."
Posted by
dgftest
at
5:59 PM
0
comments
Labels: collaboration, DRP, emergency-communications, ILM, Knowledge-Management, mobile-computing, privacy, security, Twitter, Workflow
Thursday, May 14, 2009
Should Project Managers Twitter?
Some interesting observations from the gantthead blogs about the potential relevance of Twitter to Project Managers:
Why Project Managers Should Twitter: "How many times have you heard that project management is all about communication? Communicating with your team is important, but so is communication with the outside world... you should at least become familiar with Twitter..."
I agree that PM's should become familiar with Twitter... However, the decision for any specific project would of course depend on the audience, sensitivity of the information being transmitted, overall environment and expectations of the customer, etc...
For those of us (including current or aspiring PMP's and CAPM's) familiar with the Project Management Institute's PMBOK, this basic issue is addressed as part of the Project Communications Management knowledge area, e.g. the Communications Planning process, for which the PMI observes that it is critical both to:
- Identify stakeholder information requirements, and
- Determine a "suitable means" to address those requirements.
Similarly, there could be situations in which the risk of not communicating by Twitter is much greater than doing so. Think of an emergency natural-disaster evacuation scenario in which affected parties need to receive extremely urgent information... Some of them may be accessing Twitter on a very regular basis, but their cellphone number for SMS might not be functioning at that particular moment.
Posted by
dgftest
at
10:35 AM
0
comments
Labels: collaboration, emergency-communications, mobile-computing, privacy, Project-Management, security, SMS, Twitter, Web 2.0, wireless
Tuesday, July 1, 2008
SMS robustness: Emergency - The Key is "Communications that work", Robert Paterson's Weblog
Some practical and tested suggestions re: how SMS can be more robust than vanilla cellphone/voice during true emergency scenarios. Security/privacy issues may be different for SMS than standard cell-phone voice calls (let alone SMS per-message charges depending on your carrier)... And SMS let alone Twitter may not be the most common corporate communications tools just yet. However, it is easy to agree that as mentioned by Robert Paterson below (quoting Debi Jones), in those situations, indeed, the key is something for SMS seems to have an edge: Communications that work":
Robert Paterson's Weblog: Emergency - The Key is "Communications that work": "...It is likely in a very bad situation that cell phone networks will get jammed - what we are learning though is that SMS tends to get through - so Twitter as a feed may be the core of a good plan
Advisories have been announced on CNN and local San Diego TV stations asking people to limit their mobile phone use as the networks are saturated. This is a common problem during emergencies as we’ve seen over and over. The one component that continued to provide communication during the London bombings, post Katrina flooding in New Orleans and now in San Diego is text messaging. Twice today my mobile calls have been rejected with the network reporting, “all circuits are busy”. And yet, I’ve continued to be able to send out SMS..."
Posted by
dgftest
at
12:00 PM
0
comments
Labels: collaboration, emergency-communications, SMS, Twitter, wireless
