Technically Lit

You Don’t Need to Code, But You Must Think in Code - Josh Armantrout

In this conversation, Josh Armantrout shares his unique journey into the design field, emphasizing the importance of coding knowledge for designers and how it enhances collaboration with developers. He discusses the evolution of his workflow in different organizational contexts, the significance of learning from past collaboration mistakes, and the value of embracing various design disciplines beyond traditional product design. Josh also reflects on his current projects and aspirations in the rapidly changing landscape of design, particularly with the integration of AI.Chapters00:24 Josh's Design Journey06:00 The Importance of Coding Knowledge for Designers12:37 Fostering Collaboration with Developers21:04 Navigating Different Organizational Contexts26:20 Current Workflow and Feature Development26:47 Evolving Design and Engineering Collaboration30:24 AI Integration in Design Workflows36:33 Learning Through Diverse Design Experiences49:17 The Joy of Being a Versatile Designer💻⚡️Become a product designer who codes with confidence.🌐 https://technicallylit.com📨 Want fewer bottlenecks, better handoffs, and smoother releases? Join the Technically Lit newsletter for practical coding lessons & tips for product designers: https://technicallylit.beehiiv.com/subscribeConnect with Nick:🦋 https://bsky.app/profile/nick-basile.com👨‍💼 https://linkedin.com/in/nickbasile/🆇 https://x.com/nickjbasile

Balancing execution, strategy, and AI: the expanding role of product designers - Sylvia Nguyen Dang

In this conversation, Sylvia Nguyen Dang, a Principal Product Designer at DIG, shares insights into her daily responsibilities, the evolving skill set required in product design, and the integration of AI in healthcare. She discusses the importance of collaboration between designers and engineers, the challenges of user research, and the balance between business goals and user needs. Sylvia also offers advice for aspiring designers and highlights the significance of community in the design field.Chapters00:46 A Day in the Life of a Principal Product Designer03:12 Navigating Skills and Learning in Product Design05:11 The Role of AI in Product Design07:10 Technical Literacy and Collaboration with Engineers09:01 Building Tools for Clinical Workers11:17 Collaborative Design Processes12:20 Team Structure and Roles14:32 Balancing User Research and Design15:52 Collaborative Dynamics with Product Managers18:42 Effective Developer Collaboration20:18 Adapting Collaboration Styles21:55 Empathy in Collaboration23:19 AI's Impact on Design Work24:33 Exploring AI in Design Systems28:40 Navigating User Research with AI30:47 Trust and Transparency in AI Applications35:23 Balancing Innovation and Compliance in Healthcare40:41 Collaboration Between Product and Design43:36 Advice for Aspiring Product Designers💻⚡️Become a product designer who codes with confidence.🌐 https://technicallylit.com📨 Want fewer bottlenecks, better handoffs, and smoother releases? Join the Technically Lit newsletter for practical coding lessons & tips for product designers: https://technicallylit.beehiiv.com/subscribeConnect with Nick:🦋 https://bsky.app/profile/nick-basile.com👨‍💼 https://linkedin.com/in/nickbasile/🆇 https://x.com/nickjbasile

Selling optimism and other lessons from being a Microsoft product manager - Adam Wilson

In this conversation, Adam Wilson (https://www.linkedin.com/in/adam-wilson-canada/), a Senior Product Manager at Microsoft, shares insights into his daily responsibilities, contrasting experiences between working at a large tech company and a startup, and the importance of user research and customer feedback. He discusses the dynamics of product teams, the challenges of managing developer productivity, and the significance of building trust within engineering teams. Adam emphasizes the need for technical literacy, the value of optimism in product management, and the necessity of knowledge sharing within organizations. He also offers advice for new product managers on navigating their careers effectively.Chapters00:31 A Day in the Life of a Senior Product Manager03:49 Contrasting Startup and Corporate Product Management06:46 User Research and Customer Feedback10:47 Team Dynamics and Developer Productivity17:41 Navigating Large Initiatives and Coordination20:45 The Art of Selling Ideas and Generating Buy-In28:12 The Journey of a Product Manager31:59 Learning to Code: A Practical Approach34:05 Navigating the Microsoft Way35:58 Cultivating Visibility in a Large Organization38:13 Maximizing Developer Productivity45:30 Creating an Ideal Product Environment47:44 The Evolution of a Tech Career50:36 Advice for Aspiring Product Managers📨 Want fewer bottlenecks, better handoffs, and smoother releases?Join the Technically Lit newsletter for weekly insights on product collaboration:https://technicallylit.beehiiv.com/subscribe💻⚡️ Become your dev team's favorite collaborator, without learning to code🌐 https://technicallylit.comConnect with Nick:🦋 https://bsky.app/profile/nick-basile.com👨‍💼 https://linkedin.com/in/nickbasile/🆇 https://x.com/nickjbasile

Why Good Code Isn’t Enough for a Good Product - James Pacheco

In this conversation, James Pacheco (https://www.linkedin.com/in/jamesrpacheco/) shares his unique career journey from finance to technology, emphasizing the importance of adaptability and continuous learning in the tech industry. He discusses the differences between agency life and in-house work, the transition to product management, and the significance of fostering a collaborative culture within teams. James also addresses the challenges of client relationships, the common underestimations in product development, and the need for cross-functional teams. He reflects on how his perspective on what constitutes a good product has evolved over time, highlighting the balance between visionary ideas and user needs.Chapters00:23 James' Career Journey02:37 The Importance of Technology06:23 Learning New Technologies09:29 Advice for Junior Developers13:02 Agency Life vs In-House Work13:53 Transitioning to Product Management16:51 Building Trust in Teams24:22 Cultivating Company Culture28:00 Coaching Startups on Product Development31:52 Building In-House Product Teams33:10 Underestimating Product Development Challenges35:01 The Importance of Iteration in Product Design37:15 Friction Between Product, Design, and Engineering40:18 Creating Cross-Functional Teams42:30 Evolving Perspectives on Good Product46:19 Negotiating Client Expectations50:48 Reconciling Visionary Ideas with User Needs54:19 Wishing for a Magic Wand in Client Relationships📨 Want fewer bottlenecks, better handoffs, and smoother releases?Join the Technically Lit newsletter for weekly insights on product collaboration:https://technicallylit.beehiiv.com/subscribe💻⚡️ Become your dev team's favorite collaborator, without learning to code🌐 https://technicallylit.comConnect with Nick:🦋 https://bsky.app/profile/nick-basile.com👨‍💼 https://linkedin.com/in/nickbasile/🆇 https://x.com/nickjbasile

Why Most Product Teams Get Culture Completely Wrong - Ryan Holdaway

In this conversation, Holdy (https://www.linkedin.com/in/rholdy/) shares his unique journey from a music background to a successful career in technology. He emphasizes the importance of mentorship, overcoming fear in learning, and building effective collaboration among developers. The discussion also covers the role of product management, fostering a culture of experimentation, and the balance between process and flexibility in engineering teams. Holdy highlights the need for system-level thinking and effective communication within engineering, ultimately advocating for a culture that encourages innovation and collaboration.Chapters00:00 Intro03:24 The Importance of Mentorship in Tech06:25 Overcoming Fear and Embracing Learning09:16 Building Effective Developer Collaboration12:15 The Role of Engineers in Product Development15:17 Creating a Culture of Inquiry and Feedback18:21 Navigating Early Career Challenges21:10 The Power of Relationships in Engineering24:03 Collaboration Across Teams: Product, Design, and Engineering28:19 The Power of Accountability in Team Dynamics31:47 Creating a Safe Space for Ideas32:51 Encouraging Experimentation and Learning35:45 Incentivizing Innovation in Product Teams39:29 Understanding Process vs. Culture40:46 Quality Control in Rapid Growth44:54 Bridging the Gap Between Engineering and Non-Technical Teams📨 Want fewer bottlenecks, better handoffs, and smoother releases? Join the Technically Lit newsletter for weekly insights on product collaboration: https://technicallylit.beehiiv.com/subscribe💻⚡️ Become your dev team's favorite collaborator, without learning to code🌐 https://technicallylit.comConnect with Nick:🦋 https://bsky.app/profile/nick-basile.com👨‍💼 https://linkedin.com/in/nickbasile/🆇 https://x.com/nickjbasile