The items below are things DJ Patil said in a Stanford seminar about building data products. — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "The here is that being opportunistic opened up an entire space of things that you could build with the data". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "When you expose data and you put data out there in different forms, you really run into a set of unique challenges". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "The second one that I encourage you to think about is use this analogy of make superpowers". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "It's also, which is another really important thing, products that work, people fall in love with". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "We were trying to go after the problem that we felt was in a striking distance for us". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "We are taking the commonalities and we're translating that into systems that we can then build". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "A portfolio of products that built on top of each other to get us to that Mount Everest cycle". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
On Stanford Online, Patil said: "Stories or narrative have been shared in every culture as a means of entertainment, education, cultural preservation, and to instill moral values". — DJ Patil on Stanford Online, Stanford Seminar: The Things I Wish I Knew, Lessons Learned from Making Data Products (October 2026).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "meeting big problems head-on usually isn’t the winning approach". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "Smart data scientists don’t just solve big, hard problems; they also have an instinct for making big problems small". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "a good definition of a data product is a product that facilitates an end goal through the use of data". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "meeting the problem head-on is a recipe for disaster". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "Does anyone want or need your product". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "you shouldn’t solve the whole problem at once". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2012 O'Reilly piece on Data Jujitsu, Patil wrote: "It doesn’t have to be a great solution; it just has to be good enough to let you know whether it’s worth going further". — DJ Patil, Data Jujitsu: The Art of Turning Data into Product, O'Reilly (July 16, 2012).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "a desire to go beneath the surface and discover and distill a problem down into a very clear set of hypotheses that can be tested". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "the ability to use data to tell a story and to be able to communicate it effectively". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "Our solution was to make the data group a full product team responsible for designing, implementing, and maintaining products". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "The silos that have traditionally separated data people from engineering, from design, and from marketing, don’t work when you’re building data products". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "Every data project is a new experiment, and design is a critical part of that experiment". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "To ensure agility, we build small groups to work on specific products, projects, or analyses". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "Tools are important because they allow you to automate". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "Everything can’t be urgent". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
In a 2015 O'Reilly piece on building data science teams, Patil wrote: "you’ll see data products appearing everywhere". — DJ Patil, Building Data Science Teams, O'Reilly (March 4, 2015).
