{"version":1,"type":"rich","provider_name":"Libsyn","provider_url":"https:\/\/www.libsyn.com","height":90,"width":600,"title":"307. How to lead a development team when you're not technical","description":" You're paying for developer time. But you can't evaluate the work yourself. So you're left wondering \u2014 are they actually building, or just going through the motions?  Most founders figure this out the hard way. In this episode, we break down the framework that lets you lead technical teams without being technical \u2014 and why trying to implement it alone often fails.  Key takeaways:   The invisible accountability trap: Why hours-driven management doesn't work (and why output-driven does).  The Monday morning meeting: The exact structure that keeps developers accountable without micromanaging.  Prioritization as a business skill: How to make tradeoffs \u2014 understanding that building feature X means NOT building feature Y.  Technical oversight: Why having a senior engineer validating your developers' work prevents expensive mistakes \u2014 and how we act as that advisor for you.&amp;nbsp;   The implementation gap  Knowing this framework and actually implementing it with your team are two different things. Without someone technical validating your developers' estimates, you won't know if they're being realistic.  Without someone who's done this before, you won't know how to troubleshoot when things go wrong.  Lead your team with confidence  If you want to set up this system properly \u2014 or fix it if you're already struggling \u2014 book a call with us.&amp;nbsp;  Our CTO will validate your developers' estimates. Sophia will help you run the meetings.  We'll help you avoid the expensive mistakes along the way.  Book a call: https:\/\/calendly.com\/sophia-matveeva\/new-meeting Timestamps:  00:00 - Introduction: How to manage a technical team without being technical 02:34 - Output-driven vs input-driven management 04:51 - How to run your Monday morning developer meeting 07:13 - Come with sketches and designs, not just words 09:27 - Real example: The video feature trade-off 11:50 - Why junior developers won't tell you about trade-offs 13:30 - Building your prioritization framework 14:11 - What is a sprint and how to use it 17:30 - How to know if developer estimates are reasonable 20:30 - Summary and closing  Free AI Mini-Workshop for Non-Technical Founders: Learn how to go from idea to a tested product using AI \u2014 in under 30 minutes. Get free access here:&amp;nbsp;https:\/\/www.techfornontechies.co\/aiclass  Follow and Review: We\u2019d love for you to follow us if you haven\u2019t yet. Click that purple '+' in the top right corner of your Apple Podcasts app. We\u2019d love it even more if you could drop a review or 5-star rating over on&amp;nbsp;Apple Podcasts. Simply select \u201cRatings and Reviews\u201d and \u201cWrite a Review\u201d then a quick line with your favorite part of the episode. It only takes a second and it helps spread the word about the podcast.  Listen to our podcast on:   Apple   Spotify   YouTube    Audible    Pandora  Transcript: https:\/\/www.techfornontechies.co\/blog\/307-how-to-lead-a-development-team-when-you-are-not-technical ","author_name":"Tech for Non-Techies \u2014 Product Thinking &amp; Innovation for Business Leaders","author_url":"https:\/\/www.techfornontechies.co\/","html":"<iframe title=\"Libsyn Player\" style=\"border: none\" src=\"\/\/html5-player.libsyn.com\/embed\/episode\/id\/41595510\/height\/90\/theme\/custom\/thumbnail\/yes\/direction\/forward\/render-playlist\/no\/custom-color\/88AA3C\/\" height=\"90\" width=\"600\" scrolling=\"no\"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen><\/iframe>","thumbnail_url":"https:\/\/assets.libsyn.com\/secure\/content\/202831965"}