Twitter...Are We Doing It Wrong?
I should be
spending a little more time preparing for the social software
proof of technology seminar that I am giving the next two days, but instead I'm spending time reading blogs about social software. Hmmm...maybe that actually counts. :-)
There's been quite a bit of buzz about Twitter
in our community lately. Rocky asked what all the fuss was about
a few days ago. I saw Andrew talking about Twitter being used incorrectly on Twitter
yesterday, which I thought was funny and ironic. Today, he elaborates on those short points
and says that we are using Twitter as a chat room and that we shouldn't be doing so. I thought my comment might get a bit long, so I decided to post here.
Looking at Andrew's thoughts and some of the ensuing comments, my initial reaction is that you guys are all spending too much time looking at this from a tool and technology point of view. Social software is about relationships between people. Twitter provides a dead simple mechanism for people to expose bits and pieces about themselves that can lead to a strengthening of those relationships. It has a singular purpose...to let us learn more about others. It may have initially been created to tell your friends what you are doing at this exact moment, but the community that has grown up around Twitter has fashioned a new use for it. This is a hallmark of good technology...it expanded beyond the dreams of its creators. The importance of the 140 character limit can't be understated either. It encourages interesting ebbs and flows within a conversation or a person's thought patterns that you would not otherwise see if they had the ability to type free form. It's a great way to fill in the blanks between e-mails and blog posts.
Twitter works because YOU have the say in what you want to listen to and how you want to participate in the grand conversation. It's easy to filter out the noise and focus on what interests you. With the rapid adoption of this model across other platforms, you are going to be hard pressed to get those who believe in it to leave. I'm not saying that chat rooms don't have their place (they certainly do), but it's just a completely different paradigm. I see Twitter as organized chaos that I'm free to jump in and out of at will, and there's something about that concept that appeals to me. It's not about if we're using it for its intended purpose. What matters is if it strengthens the connections I have to people I am interested in. Does it help me build a feeling of community? So far, the answer is yes. Thus, I think our use of Twitter is just right.
Hey...if you want to follow me, I'm chrisblatnick
on Twitter. See you there!
Labels: social software
permalink | leave a comment
Is Lotus Notes Long In The Tooth?
By now, if you are a member of the Lotus community in any way, shape or form, you've probably seen the great new press release
that articulates the momentum we've been gaining (quarter after quarter) over our competitors. It's so great to see the commitment we've all made to this platform be validated in real world terms. I, for one, welcome our new Lotus Notes
In light of all the great press and positive upswing I've seen out in the wild lately, I thought it was interesting that I had the following conversation the other day. I was at a meeting with a customer...a large financial institution. They are a long-time Lotus customer and really do a great job taking advantage of the Notes platform. After a successful meeting, I was standing out in the hall talking with one of the VPs and he said to me, "We use Lotus Notes for so many things, especially workflow applications, but they are getting pretty long in the tooth
." I was not expecting that comment, but I immediately knew what he was referring to. The thousands of applications this customer has are still providing a lot of business value, but the problem is...many of them look and feel old. In other words, the interface is what makes him think that perhaps it's time to do something new. I've been around long enough to know that this is not a new sentiment, but it's one worth shedding a little light on.
One of Lotus Notes' greatest strengths can also be its bane. With Notes, you can rapidly roll out a solution that addresses a business problem, usually faster than your colleagues that use some other technology. I've seen many of these applications continue providing great value to a company many years after they were initially deployed. The 100% backward compatibility allows these databases to keep on working version after version. This brings us to the problem of the interface, however. If an application was created in...let's say R4...that application is already over a decade old. If changes to the UI haven't been made, then of course it is going to look antiquated. Both the technology and interface conventions have changed a lot in that time and user expectations have greatly morphed in that period as well.
Here's the real truth: As developers, we no longer have the luxury of creating application that work but don't look good. You can't say "I don't do UI" any more, lest you want the Notes platform to disappear. The users of today are computer literate or at least savvy enough to know a good application experience from a bad one. The internet and Web 2.0 has established a precedent when it comes to usability and user interface design and we ignore this precedent at our own peril.
So...is Lotus Notes long in the tooth? Is it a tired platform that we need to send to the old folks home? Of course not. The fact is, the future for Lotus Notes is brighter than it's been for a long time.
It is necessary, however, to start treating it like the modern development platform it is and that means that developers need to take a look at themselves and see if they have the requisite skills to create compelling UIs and usable applications on the Notes platform. If you feel you are deficient in this area, then here's my call to action:
- Start thinking about the user interface at the very beginning of your project. You don't necessarily have to use low-fidelity prototyping
, but the interface shouldn't be an afterthought.
- Read a good book or two on interface design. I'd recommend starting with Don't Make Me Think
or Designing Interfaces: Patterns for Effective Interaction Design
. Getting Real
by the guys at 37Signals is a must read.
- Make usability testing
a part of your standard development methodology. Then actually listen
to what your users have to say and make the appropriate changes.
- Sharpen your technical design skills. Learn how to use a graphics program such as Photoshop or Paint Shop Pro. Really learn
- Stop making all your Notes apps look the same as you did 10 years ago. Yes...I'm talking to you! :-) At a minimum, begin utilizing the User Experience Guidelines for IBM Rich Client Applications
. Better than that, though, is to make clean and simple interfaces that support what your users are doing in your application...no more, no less.
I know many developers think the interface is touchy feely stuff, but the reality is that our software is judged by its looks. Lotus Notes now has a pretty face. Do your applications? If your users think that Lotus Notes is "long in the tooth", then your choice is clear...start fixing those interfaces or put them out to pasture.
Labels: Interface, Lotus Notes, Usability, User Experience
permalink | leave a comment