 |
Experiencing Data w/ Brian T. ONeill (UX for AI Data Products, SAAS Analytics, Data Product Management)Author: Brian T. ONeill from Designing for Analytics
Is the value of your enterprise analytics SAAS or AI product not obvious through its UI/UX? Got the data and ML models right...but user adoption of your dashboards and UI isnt what you hoped it would be?While it is easier than ever to create AI and analytics solutions from a technology perspective, do you find as a founder or product leader that getting users to use and buyers to buy seems harder than it should be?If you lead an internal enterprise data team, have you heard that a data product approach can helpbut youre concerned its all hype?My name is Brian T. ONeill, and on Experiencing Dataone of the top 2% of podcasts in the worldI share the stories of leaders who are leveraging product and UX design to make SAAS analytics, AI applications, and internal data products indispensable to their customers. After all, you cant create business value with data if the humans in the loop cant or wont use your solutions.Every 2 weeks, I release interviews with experts and impressive people Ive met who are doing interesting work at the intersection of enterprise software product management, UX design, AI and analyticswork that you need to hear about and from whom I hope you can borrow strategies.I also occasionally record solo episodes on applying UI/UX design strategies to data productsso you and your team can unlock financial value by making your users and customers lives better.Hashtag: #ExperiencingData. JOIN MY INSIGHTS LIST FOR 1-PAGE EPISODE SUMMARIES, TRANSCRIPTS, AND FREE UX STRATEGY TIPShttps://designingforanalytics.com/edABOUT THE HOST, BRIAN T. ONEILL:https://designingforanalytics.com/bio/ Language: en-us Genres: Business, Management, Technology Contact email: Get it Feed URL: Get it iTunes ID: Get it |
Listen Now...
188 - Can’t Close the Sale? Why Your Product’s UX and Workflow Misalignment Are Killing Sales (Part 2)
Episode 188
Tuesday, 17 February, 2026
I’m continuing my exploration of a hard truth many leaders of analytics software companies run into: deals don’t stall because the tech is weak. Instead, they stall because prospects can’t see the value soon enough or the risk of changing the status quo is too high. This is often a product problem, not a sales one, and obtaining Flow-of-Work Alignment (FOWA) may help you start closing more evals and deals. So what is FOWA? The idea is simple, but demanding: stop showcasing features and start designing experiences that fit into how customers already do their work, create value, and add delight when your product is added into the loop. Getting to FOWA means tailoring demos with realistic, industry-specific data, reducing mental translation, and minimizing behavior change. In this scenario, improvements become small, testable bets tied to outcomes, not feature checklists. UX and usability are not cosmetic; they should shape trust, adoption, and buyability. When prospects can clearly see themselves succeeding with your product, value feels obvious, evals progress, and deals close. Highlights/ Skip to: Steps to implementing Flow-of-Work Alignment (FOWA): Tailor your demo or POC to map to the prospects' world and their workflow (1:53) Treat product improvements as bets that have to be tested so that observable outcomes are what you’re holding your product team accountable for (3:57) Reducing perceived behavior change (6:39) Realize that your product’s visual design are likely impacting your product’s clarity and its desirability (12:29) Aligning your sales and product teams around customer outcomes and not feature gaps (18:03) Why you might think FOWA won’t work for your product—and how to reframe those objections (24:22)
