Experiencing Data w/ Brian T. O’Neill · 2026-04-28 · 24 min
Speed is often confused with good product thinking. The idea is that if teams can ship prototypes, dashboards, and models faster, they will automatically learn faster. But execution speed alone doesn’t ensure a clearer understanding of what’s actually worth building. Instead, teams often fall into a loop driven by demo feedback. They present working prototypes, and users respond to what they can see in the form of interface design, visualizations, or surface-level data behavior. While this feedback feels positive, it’s often misleading. Teams can end up reacting to presentation (UI) feedback only to find it does not change propensity to buy or increase user adoption. The key idea today is that prototypes can either be used to clarify the problem space and user needs or to validate the solution presented. Where I see most teams fail is that every artifact or prototype is seen as a solution to validate, and they can miss the forest for the trees. Another approach borrows from blue ocean thinking, which focuses on creating value by looking for overlooked opportunities in the empty space - beyond the known “problem space” your customer knowingly lives in now.
197 - Agentic AI Isn’t a Moat for Analytics Products. This is56 / 100196 - The Unique Challenges and Solutions to Selling API-based Analytics and Intelligence Products195 - Buyers Block: Why Your B2B Analytics or AI Product's POC Didn't Close194 - AI for BI: Juan Sequeda on Preparing Your Analytics to Work With LLMs192 - Product Usage Does Not = Value: Why “Adoption” Metrics Are Misleading You