Anyone can follow a list of procedures, when do I get to make a difference? Can’t I just spend my time automating this?
Today’s XKCD comic (4/29/2013) asked the question, “How long can you work on making a routine task more efficient before you’re spending more time than you save?”
Create a sound solution and let the user accomplish what they set out to do. In order to do that I have a set of key points I hold up and get others to buy-into as the development process starts.
Picking a smart phone really requires yourself to not pick sides, but rather ask yourself, do I want to live in the Google or Apple ecosystem?
I preach the benefits of change, but when it takes over a year to adjust to a new method, something is broken. Something is flawed.
Adding new features is like getting a pet. Feature ownership can be very rewarding, but do you have the support and resources to take on such a commitment?
I, and many users, get frustrated when features are added, but no devotion is dedicated to making it totally great or usable. There needs to be carry through from just adding another feature to the feature list to one that is actually usable.
I have a suggestion for a popular calendar application when it comes to recurring events. Allow the user to select a third option: designate a day of the week in the nth full week of the month. As you can see in my screenshot I have the ability to select two options in date selection […]