This is from a product I use daily. Who wrote this code and thought they were done? Who approved these two button styles next to one another? I have this vision of a developer choosing a library that made their development life easier. I picture this code going straight into production use without review. Next, I picture the designer who works there rolling their eyes, checking out, and heading to LinkedIn to see what other opportunities exist. I'm being unfairly harsh, but it makes me wonder what other sloppiness is happening inside this product.
Popular posts from this blog
When I started this blog, Agile was not yet the lingua franca of product development. I was passionate about teaching the Chicago community about Agile. I helped start the Chicago Agile Project Managers Meet Up. I presented at the international Agile conference. I was coaching organizations to use Agile practices and how to integrate user centered design into product development. Good times. Based on this blog’s old google analytics data I can see that I was able to help a lot of people. Today I find myself spending very little time on blogs - reading or creating. My go to places to find content to learn and grow professionally didn’t exist when I started Planning for Improvisation. This blog isn’t needed anymore. As I have moved on, this blog can too. -Kal
A few months back I was working on a large, ground-up redesign for a product I own. I had a little trouble getting started. I realized I needed a playbook to remind me of the basics. I am sharing my playbook for those who are having trouble and procrastinating getting started. Enjoy. Before you start At the highest level, in one paragraph, what is a representative user's goal and the problem you are solving for them? If you can't answer this succinctly you have many, many features or you don't know your users well enough to continue. Slow down, answer #1 for each feature set before you go to #2. What's working for them now? What's not? What you need to design for them Verify you are building all the tools they need. Show the process they will use to reach goal - give them a map or trail to follow. Indication of progress toward the user's goal - "You are here" Make sure you build in escape hatches because they find a better way.