David on the Good in Email
David Maister makes a case for why using email is increasing our abilities to connect with others. He raises 6 valid points. A number of commenters add valued input. David’s take is very much at the business/communication end of the spectrum, rather than the ways in which email as a technology is good. Interesting reflections.
And for the record, David’s book True Professionalism remains one of my all-time-favorite books. It contains very clear and lucid thinking that helped me a lot as I was making a start in business.
White Paper on DM and Team Collaboration with Open Source Solutions
Rivet Logic published a white paper entitled “Seven Keys to Radically Improve Document Management and Team Collaboration with Open Source Solutions”.
Despite the relatively mature state of enterprise software, companies still find it difficult to easily manage the hundreds (and sometimes thousands) of documents generated by collaborative project teams. Because of this difficulty, team members suffer from miscommunication, lost information, and disorganized workflow – all of which result in project delays, wasted time, and redundant work activities, not to mention frustrated employees, partners, and customers.
The need for improvement is prevalent across teams of all sizes, but those feeling the pain most acutely are those teams with three or more people, those handling multiple documents and document types, and groups comprising geographically dispersed team members.
Teams of all types – ranging from cross-functional product development teams to departmental groups that support repeatable business processes – can benefit from a robust yet simplified approach to document management and team collaboration.
I’ve ordered the paper, but just because the software is open source doesn’t mean that document management and team collaboration will be better.
Stowe Wants Federation in Basecamp
Stowe wants 37Signals to add federation capabilities to Basecamp.
… I consider it a basic flaw that Basecamp doesn’t support a federated model of work: that is to say, if I am working with four companies who each have a Basecamp instance, I wind up with four account/login/password combinations, and worst of all, no unified dashboard view to consolidate all my Basecamp information.
Jason from 37signals said that Stowe was abnormal and that “most people only have one account”. Stowe replied that he’s an early adopter and so sees the flaws earlier than others.
However, anyone who is a free agent — working for multiple companies, or across multiple projects in a big company that has more than one Basecamp account — will encounter this problem just as soon as I have, although they may not have the situation that I do, with over a dozen account/login/password triples in the past 12 months.
Jason said they’re working on something that may solve the issue, and then encourages “some enterprising entrepreneur” to build a for-fee capability using the Basecamp API.
Mike Gotta on Sametime 7.5
Mike Gotta from the Burton Group shares his thoughts about Sametime 7.5 in the enterprise IM and presence market.
Since 2003, IBM essentially left the battlefield when it came to RTC, allowing Microsoft to move through the market almost at will. For some time there has not been a vision or coherent strategy around the convergence of audio/video/data conferencing, instant messaging, IP telephony/VoIP, presence, e-mail, and voice mail – what many people are categorizing as Unified Communications today. There have been product updates to Sametime for sure, but no strategic vision and architectural framework or partner business model until recently that paralleled what Microsoft (and even some communication vendors) have been talking about concerning “convergence”.
And that is what’s most important about this release of Sametime. V7.5 signifies IBM’s return to competing with Microsoft when it comes to unified communications. While not a perfect release (I wish it did more to modernize the back-end), it is an initial volley. The question now is whether it is too little too late and whether the rest of the work needed to be delivered happens in a timetable that satisfies client needs and market dynamics.
Mike continues and outlines (a) what he likes about the new release, and (b) what remains a concern.