May 2008 Archives
There is always tension between usability for a specific task, and power for a broad range of tasks. As software matures, it tends to get an "everything but the kitchen sink" feel that reduces it's appeal, even though it may increase it's utility.
I have resisted and delayed adding some things to FUNDimensions, focusing instead on refining existing interfaces and capabilities, just to avoid the ruination to elegance, appeal and enjoyment in use, that software maturation usually brings. By improving existing functionality, condensing it, and generalizing it where possible, I hoped to extend the utility of what was already there, so that whole new chunks wouldn't be needed. One tradeoff with this approach is that sometimes generalized tools cannot work as well or be as elegant as tools specifically made for a task.
Another approach is to hide big chunks behind something simpler. The last upgrade (7.0) featured an Event Manager module, which was a large set of tools contained completely inside the Calendar: you don't see or have access to the Event Manager until you create a calendar item and explicitly invoke the event manager for it. The Event Manger does link to existing donor and gift modules, so it is integrated with the rest of the software, but not in any way that requires you to know anything about the Event Manager to use those other modules.
This means you can use all the other parts of the software, except the calendar, and never even know the Event Manager exists. And if you never click the Management tab in a calendar event, you can even use that module without knowing anything about the Event Manager. In this way, the Event Manager does not contribute to any overall "kitchen sink" feel to the software, while still giving a very specialized, focused toolset to fundraisers who can benefit from it.
One disadvantage to this approach is that fundraisers looking over the demo might never see it, and conclude their survey of FUNDimensions without including the Event Manager in their consideration of whether to purchase the software. This might cause a few organizations that wold really like and benefit from using FUNDimensions, to miss out.
Another disadvantage is that regular users of the software will never discover the Event Manager, or will forget it is there and use some other tool for managing their events. Then, if they are reminded of the tool later, they figure they already have a working system, and it is too much trouble to change it, even though there would be benefits from doing so. This resistance to changing tools can also happen at the outset of a new installation, even if the intention was to switch to the new tool.
But if users repeatedly encounter the presence of the tool as they do other routine tasks, they might be more inclined to try it out when the time comes, even though the repeated encounters with it earlier were essentially a distraction or obstacle to the current task.
It is a very delicate balance. I have definitely leaned toward an approach that preserves a lean, fast, welcoming interface. What might partially compensate for the disadvantages of this approach is more communication with fundraisers, both current users and prospective ones. For example, Webex-style demos or seminars of the Event Manager, to keep it's considerable power and elegance in the consciousness of those who might benefit from it the most. For those who don't know, a Webex demo is an online meeting where I can share my screen with you over the internet, while on a conference call that allows for you to interact with me by asking questions and participating in a conversation.
