Leadership Without Authority I Kevin Dias

In this episode of the 40% Better Podcast, Bill Lennan sits down with Kevin Dias, Founder of Ambiki, to explore leadership, remote teams, customer-driven product development, and the unexpected paths that lead to leadership in technology. Kevin shares how his leadership journey began by starting a college ski team and how that early experience shaped his approach to solving problems, building relationships, and taking initiative without waiting for authority or permission. The conversation covers practical leadership lessons, including why leadership is about trust and relationships, how to make better decisions, the importance of Nemawashi, and why great leaders don't always need to have all the answers. Kevin also discusses leading a 100% remote and distributed team, managing communication across time zones, building psychological safety, and using async communication effectively. He explains how his team uses video in GitHub pull requests to improve communication and even catch bugs before they reach production. A major focus of the conversation is the importance of listening to customers. Kevin shares how Coffee with Kevin helped his development team work directly with speech-language pathologists and how staying close to customers shaped Ambiki's product development. He also explains why teams should understand the problem behind a customer request instead of immediately building the requested solution. Bill and Kevin also explore the value of human customer support, why companies should not rush to replace customer service with chatbots, and how exceptional customer experiences can create loyal customers and long-term business value. Topics covered in this episode: * Leadership in technology * Kevin Dias' leadership journey * Building leadership skills through problem solving * Leading without formal authority * Trust and relationships in leadership * One-way and two-way door decisions * Nemawashi and building team buy-in * The importance of internal networking * Helping teams solve problems without giving all the answers * Building ownership within engineering teams * Managing 100% remote and distributed teams * Async communication and time zone management * Psychological safety in remote teams * Over-communicating in distributed teams * Video pull requests and better developer communication * Software quality and QA * AI and the future of software development * Voice of the customer * Customer-driven product development * Talking directly to custom