How can good design help you avoid product bloat and drift?

Let’s talk about your product’s drift and keeping it in check. As your product evolves, it will likely grow in size, and get more complex over time. You’ll listen to customers, adapt to their needs, and over time will begin to encounter situations where different segments’ needs are in conflict, and you either dissatisfy one … Read more

What’s the #1 way you can simplify your service?

Ok, you probably know this one, but let’s dig in a little farther. I recently started to explore using the TORBrowser when surfing on public wi-fi for more security (later finding out that using a VPN, and not TOR, is what will enable safer surfing). However, in the process of downloading and trying the TORBrowser … Read more

(4) Reasons reverse-engineering data into use cases for data products is costly and risky

Toilet bowl with cash money in it

On a lot of analytics-driven projects, I am told by my clients that there are many possible use cases or user stories that the design needs to support. Why so many? I think it stems from the fact that products and companies are collecting more and more data, and so the logical assumption is that there … Read more

Beware the dreaded “reporting section” in your analytics service

“That stuff probably belongs in the reporting section.” I’ve heard that one before. There’s probably a better approach. Remember: it’s not really about “analytics” — it’s about providing information to help your customers make better decisions. Shoveling your analytics into the “reporting section” can easily become a dumping ground for “stuff that might be useful” … Read more

What’s my #1 engineering bias to overcome when designing good analytics products?

I’ve worked with a lot of talented engineers in my 20+ years of designing websites and software. One of the things about analytics that can trip up some engineers: imperfect data, conclusions, and evidence. Analytics tools rarely provide exact answers, but this doesn’t mean there isn’t value to your customers. If your data, analytics, or … Read more

“Post-truth,” data analytics, and omissions–are these design considerations?

Post-truth. The 2016 word of the year. Yikes for some of us. This got me thinking about UX around data, analytics, and information, and what it means when we present conclusions or advice based on quantitative data. Are those “facts”? If your product generates actionable information for customers, then during your design phase, your team … Read more

Does your data answer real customer questions, or the ones your data model supports?

I worked on a project with two sociologists from the Future of Music Coalition a couple years ago. They conducted the first large-scale formal survey on musicians’ revenue streams to help answer the question “how do working musicians make a living?” It was a really fantastic project funded in part by the Doris Duke Charitable … Read more

How can good design help you raise investment capital and increase monthly SAAS revenue?

At some point, you probably visited designingforanalytics.com if you’re on my mailing list, and you might have read a cast study about one of my startup clients, Apptopia.com. Apptopia hired me to help them turn a suffering marketplace business into a thriving mobile app intelligence platform based on analytics. If you aren’t familiar with this company, Apptopia … Read more

Want a Silver-quality analytics product? Use Agile. Want Gold? Read on.

Agile software development is everywhere. You’re probably using some form of it yourself. And, that’s probably good, assuming you’re actually delivering value with agility. These days, I constantly hear about how “shipping working code” sooner trumps everything else. When it comes to designing for analytics though, I don’t always agree. It’s hard to build and ship … Read more

The #1 problem I see with clients trying to design good analytics products

When it comes to analytics products that need to show data to customers, one of the biggest misconceptions I see with clients is the believe that their trove of data is actually ​information, by default. Your data is not informative until it has been presented–i.e. designed–in a way that customers can inform their future decisions or actions. … Read more