It Is 2009. Why Is "Groupware" Still So Hard?
continuations.com
continuations.com
I guess the title was a rhetorical question!
It's hard for a small design group to understand the universe; the imagined 'solutions' are limited. And it's hard to design a set of tools that people can use to evolve their own solutions. But it's a hard problem. Simplistic 'answers' will fail.
I'm reminded of many attempts at educational software. Too often the programmers clearly had a limited view of what constitutes education. You can't design your way out of your own limited perspective. Research has to precede theory; else you wind up with solutions to the wrong problems.
Proprietary solutions tend to be more passionate about making money than at helping people. Bass-ackwards.
With ShopTalk, we're trying to solve just one (very important) piece of the puzzle: real-time communication. We don't want to own the group, though, as the article says. Since most organizations have some sort of LDAP server (MS Active Directory being the most common), we'll be rolling out LDAP integration soon, so that you only have to add/remove/update users in one place and they only have to remember one password. SSO ftw.
Salient point: If you want to do something that's going to change the world, build software that people want to use instead of software that managers want to buy