SummaryMachine learning is a transformative tool for the organizations that can take advantage of it. While the frameworks and platforms for building machine learning applications are becoming more powerful and broadly available, there is still a significant investment of time, money, and talent required to take full advantage of it. In order to reduce that barrier further Adam Oliner and Brian Calvert, along with their other co-founders, started Graft. In this episode Adam and Brian explain how they have built a platform designed to empower everyone in the business to take part in designing and building ML projects, while managing the end-to-end workflow required to go from data to production.Announcements
Interview
Introduction
How did you get involved in machine learning?
Can you describe what Graft is and the story behind it?
What is the core thesis of the problem you are targeting?
How does the Graft product address that problem?
Who are the personas that you are focused on working with both now in your early stages and in the future as you evolve the product?
What are the capabilities that can be unlocked in different organizations by reducing the friction and up-front investment required to adopt ML/AI?
What are the user-facing interfaces that you are focused on providing to make that adoption curve as shallow as possible?
What are some of the unavoidable bits of complexity that need to be surfaced to the end user?
Can you describe the infrastructure and platform design that you are relying on for the Graft product?
What are some of the emerging "best practices" around ML/AI that you have been able to build on top of?
As new techniques and practices are discovered/introduced how are you thinking about the adoption process and how/when to integrate them into the Graft product?
What are some of the new engineering challenges that you have had to tackle as a result of your specific product?
Machine learning can be a very data and compute intensive endeavor. How are you thinking about scalability in a multi-tenant system?
Different model and data types can be widely divergent in terms of the cost (monetary, time, compute, etc.) required. How are you thinking about amortizing vs. passing through those costs to the end user?
Can you describe the adoption/integration process for someone using Graft?
Once they are onboarded and they have connected to their various data sources, what is the workflow for someone to apply ML capabilities to their problems?
One of the challenges about the current state of ML capabilities and adoption is understanding what is possible and what is impractical. How have you designed Graft to help identify and expose opportunities for applying ML within the organization?
What are some of the challenges of customer education and overall messaging that you are working through?
What are the most interesting, innovative, or unexpected ways that you have seen Graft used?
What are the most interesting, unexpected, or challenging lessons that you have learned while working on Graft?
When is Graft the wrong choice?
What do you have planned for the future of Graft?
Contact Info
Parting Question
Closing Announcements
Links
The intro and outro music is from Hitman’s Lovesong feat. Paola Graziano) by The Freak Fandango Orchestra)/CC BY-SA 3.0