“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 moreBeware the dreaded “reporting section” in your analytics service
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 moreWhat’s my #1 engineering bias to overcome when designing good analytics products?
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“Post-truth,” data analytics, and omissions–are these design considerations?
We’ve all heard about information overload, and the paradox of choice. Don’t you love those thai menus with every type of sauce, noodle, and protein, all written out as separate dishes? “I’ll have item D132 with no water chestnuts….no, I mean the one with chicken on page 12….yeah, that one.” There’s a ton of data … Read moreMaybe your product’s problem is information *underload*