Something old vs. something new?
By pdiamond on Aug 21, 2007
Today I am reminded how hard it is to communicate, and how much work there is in supporting communities. We are working on improving the support for several of our technical communities at Sun, and yet we are struggling with how best to communicate and collaborate within our own team.
Combined with that is the challenge to prioritize between bringing improved functionality (aka web 2.0) vs. addressing the "boring" old issues our users face every day - how do we help them do what they are doing today, while trying to also show them new ways which will some day be more useful?
My concern is that it is very easy to see how much new exciting technology is out there, while losing sight of the users' everyday concerns. It's a version of the old "win the battle, lose the war" - we can successfully deploy new stuff which gets ignored or rejected because there is no obvious relationship to the old problems.
Maybe this will all look better after some lunch...