UX for Development Shops is "the ebook" on digital UX strategy for developers and other technical people. It is available now at a 20% launch discount from October 4 through October 6, 2017. Prices go up on October 7. You can read the first 2 chapters for free at davidp.io/ebook. Please share this with anyone who would find it useful.
Website teardowns tend to focus too much on the evaluator's own perspective. They can include misapplied best practices or long lists of unprioritized recommendations, which can waste your effort and cost you real conversions and revenue. In this guest post for Business2Community, I introduce a way to overcome this using method acting.
Before you design a product, you ought to learn about the people who might use it. In this guest post for The Product Guy, I describe how to navigate around 5 pitfalls in user research, so that you can learn what you need to know about your users and use that knowledge to create great products for them.
Development teams in organizations with developer-centered user experience often find that they have no access to their users. By taking some cues from remote work, these teams can use these 3 techniques to learn information about their users that will be vital to feature decisions.
Does your development team believes that they always know best? Or do usability studies just get cut because of time and budget? Either way, waiting to present a finished release can hurt your user retention. In this guest post for Speckyboy, I explain how to overcome this hurdle using a little-known rule.
What do you do when people give you feedback on your product? Do you rush to implement everything you can, let any issue sit in your bug tracker, or decide what to do in a meeting? In this guest post for Brainleaf, I review some of these options and describe what may be the best system I have ever seen for prioritizing UX bugs.