INFORMAZIONI SU QUESTO EPISODIO
Mohit Aron has built 2 companies to $10B+ (Nutanix & Cohesity) by telling his engineers to ignore "minimum viable product" and build what customers actually love. He says you can NOT build a billion-dollar business by using the same strategy as everybody else — like giving points to engineers for building their favorite features. Instead, you need a Minimum Lovable Product.
We cover:
- Why "Minimum Lovable Products" beat MVPs
- How Amazon Fire Phone proved viable isn't enough
- Making engineers think "will customers love this?" not "does it work?"
- Why viability is whatever internal teams decide (the problem)
- When you know it's actually lovable (customers buy with their money)
Check out Suresh's idea: The Self-Driving Cloud™
Learn how Sedai can make your cloud autonomous → https://www.sedai.io/
Inglese
Stati Uniti
TRASCRIZIONE 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
CERCA TRA GLI EPISODI PASSATI
Cerca gli episodi passati di 1 IDEA.
ALTRI EPISODI IN QUESTO PODCAST
Salesforce needed a faster UI runtime, but rewriting everything without forcing customers to migrate seemed impossible.
On this episode of 1 IDEA, Kevin Hill (VP of Engineering @ Salesforce) shares how backing his team’s “impossible” ideas led to the one idea that unlocked Salesforce’s UI overhaul…
Manish (VP of Engineering @ Cisco) watched AI write perfect code that created a disaster. When his team asked AI to add traceability, it invented a brand new framework instead of using the one they already had. Multiply that across 1,100 engineers, and suddenly you have dozens of competing implemen…
Vinay Perneti, VP of Engineering at Augment, learned the hard way that being the go-to problem solver was actually "diminishing the intelligence" of his team.
Years ago at Pure Storage, his manager's brutal feedback forced him to develop the "Bottleneck Test": a framework he uses to scale teams a…
Rachit Lohani (fmr. CTO @ Paylocity) has seen the same pattern everywhere: engineering leaders getting hammered with "Why aren't we more productive with AI?"
Teams are using AI. They're writing more code. But nobody can answer whether it actually matters.
For his one idea, Rachit breaks down why …
Dichiarazione di non responsabilità: Il podcast e la grafica incorporati in questa pagina provengono da Sedai, che è di proprietà del suo proprietario e non è affiliato o approvato da Listen Notes, Inc.
MODIFICA
Grazie, ci hai aiutato a mantenere aggiornato il database dei podcast.
