Skip to content

What You Can Do to Simplify Your Products

This article from Ameet Ranadive was so compelling and spot-on that I was able to overlook its inclusion of a Dilbert cartoon. Keep it simple folks! I came across a Tweetstorm from Mark Suster last weekend that got me… 

5 techniques for prioritizing features (or user stories)

Prioritizing features is a pretty important step when designing and building any product, from websites and mobile apps to toasters and lawn mowers. Here are 5 great techniques for prioritizing features (or user stories) to… 

Are We Mining Data Instead Of Answering Questions?

How the focus on applying algorithms to data is not the same as actually answering questions…. One of the most striking things about the “big data” world of today is the focus on mining data over answering… 

What question are you trying to answer?

Tamara Adlin from Fell Swoop ( a UX consulting firm in Seattle, WA) wrote a revelatory article about how important it is to know what problem you are trying to solve .  Her client(Client X) was having all sorts of problems with their UI, including an inordinate number of users asking “why can’t I do X with your product”.

Client X asked how they should avoid creating such confusion. Instead of just jumping in to solve the (rather obvious & severe) problems with Client X’s UI, she realized the answer was much more basic: she needed to establish exactly what question their product was trying to answer. What problem was the product/website trying to solve?

Ms. Adlin explained that to properly answer that seemingly simple question  you have to figure out: