Podcasts about Principle

Want more joy and a closer walk with God? Chip shares the game plan for personal satisfaction and intimacy with Him.Breakthrough Concept #2: God owns everything. I am His money manager.The “Oikonomia” Principle: All that we are, and all that we have belongs to God and has been temporarily entrusted to us to manage according to His wishes. -1 Cor. 4:1-2The Setting: Correction of the Pharisees and instruction of His disciples concerning wealth.The Story: Luke 16:1-11Mismanagement occurs and dismissal soon follows.Two options are considered and a third is taken.A commendation by the owner, a good lesson from a bad example, “he was shrewd.”The Teaching: Faithfulness with material wealth is a prerequisite to being entrusted with spiritual wealth and rewards.The Test: Two basic financial practices that demonstrate God is our #1 priority.1. Generous stewards give the FIRST and BEST to God. -Pr. 3:9-102. Generous stewards give REGULARLY and SYSTEMATICALLY. -1 Cor. 16:2Three questions wise stewards regularly ask1. Am I using the money entrusted to me in accordance with the Owner's wishes?2. Am I carefully keeping account of where all the Owner's funds are going?3. Am I becoming “best friends” with the “Owner” by the privilege and opportunity of managing His resources?Broadcast ResourceSeries ResourcesMessage NotesYear End MatchDouble Your Gift TodayMinistry ReportConnect888-333-6003WebsiteChip Ingram AppInstagramFacebookTwitterPartner With UsDonate Online888-333-6003

BONUS: The Operating System for Software-Native Organizations - The Five Core Principles In this BONUS episode, the final installment of our Special Xmas 2025 reflection on Software-native businesses, we explore the five fundamental principles that form the operating system for software-native organizations. Building on the previous four episodes, this conversation provides the blueprint for building organizations that can adapt at the speed of modern business demands, where the average company lifespan on the S&P 500 has dropped from 33 years in the 1960s to a projected 12 years by 2027. The Challenge of Adaptation "What we're observing in Ukraine is adaptation happening at a speed that would have been unthinkable in traditional military contexts - new drone capabilities emerge, countermeasures appear within days, and those get countered within weeks." The opening draws a powerful parallel between the rapid adaptation we're witnessing in drone warfare and the existential threats facing modern businesses. While our businesses aren't facing literal warfare, they are confronting dramatic disruption. Clayton Christensen documented this in "The Innovator's Dilemma," but what he observed in the 1970s and 80s is happening exponentially faster now, with software as the accelerant. If we can improve businesses' chances of survival even by 10-15%, we're talking about thousands of companies that could thrive instead of fail, millions of jobs preserved, and enormous value created. The central question becomes: how do you build an organization that can adapt at this speed? Principle 1: Constant Experimentation with Tight Feedback Loops "Everything becomes an experiment. Not in the sense of being reckless or uncommitted, but in being clear about what we're testing and what we expect to learn. I call this: work like a scientist: learning is the goal." Software developers have practiced this for decades through Test-Driven Development, but now this TDD mindset is becoming the ruling metaphor for managing products and entire businesses. The practice involves framing every initiative with three clear elements: the goal (what are we trying to achieve?), the action (what specific thing will we do?), and the learning (what will we measure to know if it worked?). When a client says "we need to improve our retrospectives," software-native organizations don't just implement a new format. Instead, they connect it to business value - improving the NPS score for users of a specific feature by running focused retrospectives that explicitly target user pain points and tracking both the improvements implemented and the actual NPS impact. After two weeks, you know whether it worked. The experiment mindset means you're always learning, never stuck. This is TDD applied to organizational change, and it's powerful because every process change connects directly to customer outcomes. Principle 2: Clear Connection to Business Value "Software-native organizations don't measure success by tasks completed, story points delivered, or features shipped. Or even cycle time or throughput. They measure success by business outcomes achieved." While this seems obvious, most organizations still optimize for output, not outcomes. The practice uses Impact Mapping or similar outcome-focused frameworks where every initiative answers three questions: What business behavior are we trying to change? How will we measure that change? What's the minimum software needed to create that change? A financial services client wanted to "modernize their reporting system" - a 12-month initiative with dozens of features in project terms. Reframed through a business value lens, the goal became reducing time analysts spend preparing monthly reports from 80 hours to 20 hours, measured by tracking actual analyst time, starting with automating just the three most time-consuming report components. The first delivery reduced time to 50 hours - not perfect, but 30 hours saved, with clear learning about which parts of reporting actually mattered. The organization wasn't trying to fulfill requirements; they were laser focused on the business value that actually mattered. When you're connected to business value, you can adapt. When you're committed to a feature list, you're stuck. Principle 3: Software as Value Amplifier "Software isn't just 'something we do' or a support function. Software is an amplifier of your business model. If your business model generates $X of value per customer through manual processes, software should help you generate $10X or more." Before investing in software, ask whether this can amplify your business model by 10x or more - not 10% improvement, but 10x. That's the threshold where software's unique properties (zero marginal cost, infinite scale, instant distribution) actually matter, and where the cost/value curve starts to invert. Remember: software is still the slowest and most expensive way to check if a feature would deliver value, so you better have a 10x or more expectation of return. Stripe exemplifies this principle perfectly. Before Stripe, accepting payments online required a merchant account (weeks to set up), integration with payment gateways (months of development), and PCI compliance (expensive and complex). Stripe reduced that to adding seven lines of code - not 10% easier, but 100x easier. This enabled an entire generation of internet businesses that couldn't have existed otherwise: subscription services, marketplaces, on-demand platforms. That's software as amplifier. It didn't optimize the old model; it made new models possible. If your software initiatives are about 5-10% improvements, ask yourself: is software the right medium for this problem, or should you focus where software can create genuine amplification? Principle 4: Software as Strategic Advantage "Software-native organizations use software for strategic advantage and competitive differentiation, not just optimization, automation, or cost reduction. This means treating software development as part of your very strategy, not a way to implement a strategy that is separate from the software." This concept, discussed with Tom Gilb and Simon Holzapfel on the podcast as "continuous strategy," means that instead of creating a strategy every few years and deploying it like a project, strategy and execution are continuously intertwined when it comes to software delivery. The practice involves organizing around competitive capabilities that software uniquely enables by asking: How can software 10x the value we generate right now? What can we do with software that competitors can't easily replicate? Where does software create a defensible advantage? How does our software create compounding value over time? Amazon Web Services didn't start as a product strategy but emerged from Amazon building internal capabilities to run their e-commerce platform at scale. They realized they'd built infrastructure that was extremely hard to replicate and asked: "What if we offered it to others?" AWS became Amazon's most profitable business - not because they optimized their existing retail business, but because they turned an internal capability into a strategic platform. The software wasn't supporting the strategy - the software became the strategy. Compare this to companies that use software just for cost reduction or process optimization - they're playing defense. Software-native companies use software to play offense, creating capabilities that change the competitive landscape. Continuous strategy means your software capabilities and your business strategy evolve together, in real-time, not in annual planning cycles. Principle 5: Real-Time Observability and Adaptive Systems "Software-native organizations use telemetry and real-time analytics not just to understand their software, but to understand their entire business and adapt dynamically. Observability practices from DevOps are actually ways of managing software delivery itself. We're bootstrapping our own operating system for software businesses." This principle connects back to Principle 1 but takes it to the organizational level. The practice involves building systems that constantly sense what's happening and can adapt in real-time: deploy with feature flags so you can turn capabilities on/off instantly, use A/B testing not just for UI tweaks but for business model experiments, instrument everything so you know how users actually behave, and build feedback loops that let the system respond automatically. Social media companies and algorithmic trading firms already operate this way. Instagram doesn't deploy a new feed algorithm and wait six months to see if it works - they're constantly testing variations, measuring engagement in real-time, adapting the algorithm continuously. The system is sensing and responding every second. High-frequency trading firms make thousands of micro-adjustments per day based on market signals. Imagine applying this to all businesses: a retail company that adjusts pricing, inventory, and promotions in real-time based on demand signals; a healthcare system that dynamically reallocates resources based on patient flow patterns; a logistics company whose routing algorithms adapt to traffic, weather, and delivery success rates continuously. This is the future of software-native organizations - not just fast decision-making, but systems that sense and adapt at software speed, with humans setting goals and constraints but software executing continuous optimization. We're moving from "make a decision, deploy it, wait to see results" to "deploy multiple variants, measure continuously, let the system learn." This closes the loop back to Principle 1 - everything is an experiment, but now the experiments run automatically at scale with near real-time signal collection and decision making. It's Experiments All The Way Down "We established that software has become societal infrastructure. That software is different - it's not a construction project with a fixed endpoint; it's a living capability that evolves with the business." This five-episode series has built a complete picture: Episode 1 established that software is societal infrastructure and fundamentally different from traditional construction. Episode 2 diagnosed the problem - project management thinking treats software like building a bridge, creating cascade failures throughout organizations. Episode 3 showed that solutions already exist, with organizations like Spotify, Amazon, and Etsy practicing software-native development successfully. Episode 4 exposed the organizational immune system - the four barriers preventing transformation: the project mindset, funding models, business/IT separation, and risk management theater. Today's episode provides the blueprint - the five principles forming the operating system for software-native organizations. This isn't theory. This is how software-native organizations already operate. The question isn't whether this works - we know it does. The question is: how do you get started? The Next Step In Building A Software-Native Organization "This is how transformation starts - not with grand pronouncements or massive reorganizations, but with conversations and small experiments that compound over time. Software is too important to society to keep managing it wrong." Start this week by doing two things.  First, start a conversation: pick one of these five principles - whichever resonates most with your current challenges - and share it with your team or leadership. Don't present it as "here's what we should do" but as "here's an interesting idea - what would this mean for us?" That conversation will reveal where you are, what's blocking you, and what might be possible.  Second, run one small experiment: take something you're currently doing and frame it as an experiment with a clear goal, action, and learning measure. Make it small, make it fast - one week maximum, 24 hours if you can - then stop and learn. You now have the blueprint. You understand the barriers. You've seen the alternatives. The transformation is possible, and it starts with you. Recommended Further Reading Tom Gilb and Simon Holzapfel episodes on continuous strategy  The book by Christensen, Clayton: "The Innovator's Dilemma"  The book by Gojko Adzic: Impact Mapping  Ukraine drone warfare Company lifespan statistics: Innosight research on S&P 500 turnover  Stripe's impact on internet businesses Amazon AWS origin story DevOps observability practices About Vasco Duarte Vasco Duarte is a thought leader in the Agile space, co-founder of Agile Finland, and host of the Scrum Master Toolbox Podcast, which has over 10 million downloads. Author of NoEstimates: How To Measure Project Progress Without Estimating, Vasco is a sought-after speaker and consultant helping organizations embrace Agile practices to achieve business success. You can link with Vasco Duarte on LinkedIn.

Wondering why faith feels like a duty? Chip explains the secret to finding lasting joy and a deeper relationship with God.Breakthrough Concept #2: God owns everything. I am His money manager.The “Oikonomia” Principle: All that we are, and all that we have belongs to God and has been temporarily entrusted to us to manage according to His wishes. -1 Cor. 4:1-2The Setting: Correction of the Pharisees and instruction of His disciples concerning wealth.The Story: Luke 16:1-11Mismanagement occurs and dismissal soon follows.Two options are considered and a third is taken.A commendation by the owner, a good lesson from a bad example, “he was shrewd.”The Teaching: Faithfulness with material wealth is a prerequisite to being entrusted with spiritual wealth and rewards.The Test: Two basic financial practices that demonstrate God is our #1 priority.1. Generous stewards give the FIRST and BEST to God. -Pr. 3:9-102. Generous stewards give REGULARLY and SYSTEMATICALLY. -1 Cor. 16:2Three questions wise stewards regularly ask1. Am I using the money entrusted to me in accordance with the Owner's wishes?2. Am I carefully keeping account of where all the Owner's funds are going?3. Am I becoming “best friends” with the “Owner” by the privilege and opportunity of managing His resources?Broadcast ResourceSeries ResourcesMessage NotesYear End MatchDouble Your Gift TodayMinistry ReportConnect888-333-6003WebsiteChip Ingram AppInstagramFacebookTwitterPartner With UsDonate Online888-333-6003

Two things this episode. A huge thanks to the amazing lovefly community. Also, discussing the psychological principle of the Progress Principle and how it links to fear of flying. Lovefly Courses  FB - Lovefly Insta @loveflyhelp #fearofflying #flyingwithout fear #anxiety #aviation #lovefly #pilots #turbulence #claustrophobia #progressprinciple  Private Members Group https://lovefly.podia.com Intro and outro music 'Fearless' Daniel King Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Head over to ⁠8020BASEBALL.com⁠⁠⁠⁠⁠⁠⁠⁠⁠ and get the full COACHING PLAN and the free 21-page Drill Design Guide PDF.IN THIS WEEK'S EPISODE: We discuss the optimal baserunning mindset, while underscoring the value of tailored scrimmages to enhance baserunning production. Additionally, Coach Bo cautions against a hitting tip he read recently.ABOUT:Welcome to the 8020 Baseball Podcast, where Coach Bo shares a direct path to becoming a great youth baseball coach by combining his 20+ years of baseball coaching experience with his 20+ years of unique teaching experience, while also drawing on his experiences playing youth, HS, collegiate, and professional baseball.A deep level of baseball knowledge, combined with universal strategies such as the 80/20 Principle, gives this podcast a uniquely advanced approach to mastering all the key parts of coaching youth baseball.The podcast combines solo episodes with high-quality interviews featuring individuals who share specific, actionable strategies for youth baseball coaches. New episodes every Tuesday!

Principle 4 – Colossians 1:15-20A Principle to Live By – Putting Christ FirstTo walk in God's will, Jesus Christ must always be the central focus in our personal and corporate lives.NEW! - Let us know what you think of the program! Support the show

Kevin Prentice is a former Professional Golfer, and Golf Instructor. His journey in golf is incredible and reads like a movie-script. From working in a Lumber Mill to playing in the US Open alongside Johnny Miller and Raymond Floyd two years later, Kevin's story is one of resilience, hard work, serendipitous meetings, and an open and curious mind. He joins #OntheMark to tell his story and share lessons he learned from legendary golf instructors like Henry Picard, Gardner Dickinson and Alex Morrison. Stay tuned for golf-swing insights and lessons on how Ben Hogan swung the golf-club. Insights include: A lesson from Tony Pena on Alignment and Swing Path A lesson from Jack Grout, Jack Nicklaus's teacher, on Footwork and a Steady Head Lessons from Henry Picard on - Shaft Lean, Hitting Irons Softly, Self-discovery and Asking Good Technique Questions, and Principle-based Teaching, and Golf Lessons from Gardner Dickinson and David Lee of Gravity Golf. Kevin's experience and anecdotes share age-old truths about game improvement, and his goal is to share his treasure trove of insights from some of the brightest minds in the game. He will regale you with stories laden with golf nuggets while dispelling some of the "internet golf instruction" from the “Golf Swing Charlatans” as he calls them. This podcast is also available as a vodcast on YouTube - search and subscribe to Mark Immelman.

In this episode, we sit down with a top entrepreneur and filmmaker Stewart Cohen, an expert and business owner of nearly 20 years, to unpack how to build genuine credibility and lasting success in an age of overwhelming digital noise ("cyber noise").Stewart shares timeless principles from his entrepreneurial journey, shaped by a family legacy of business ownership, and contrasts the foundational strategies of the past with the unique challenges of today.Stewart argues that in a world where “social media lies, websites lie,” the most valuable currency is in-person credibility. He provides a masterclass in turning client relationships into your most powerful marketing engine and explains why protecting your audience's attention is the ultimate business discipline.

In this episode, Dr. Killeen shares a simple (and funny) story about a donkey, a tiger, and a lion that carries a surprisingly powerful lesson. He connects it to modern life, especially social media, where arguments are loud, endless, and often pointless. The takeaway is a reminder that wisdom isn't about winning every debate—it's about protecting your peace and knowing when to disengage. A calm, grounded listen for anyone feeling worn down by noise, negativity, or online drama.

Dr. Ted Traylor delivers a message based in John 3:22-30, especially John's words, "He must increase, but I must decrease," speaking of the humility we must all have as we lift up the name of Jesus. 00:00 - Introduction 07:50 - The Danger of Exalting Self 14:09 - The Delight of Exalting Jesus 24:10 - Mr. Everything Visit olivebaptist.org for more information.

Apply for coaching here Whatsapp Emma with any questions hereChapters00:00 Introduction and Client Success Story04:45 Setting Holiday Goals and Intentions09:39 The Power of Imperfect Action10:16 The 'F*ck Yes or No' Principle

Before you scroll through Rightmove, fall in love with "the one," or even book your first viewing… there's one crucial step every first-time buyer needs - and hardly anyone explains it properly. In this episode of On The Ladder, we're breaking down the Decision in Principle (also known as an Agreement in Principle, Mortgage in Principle, or simply a DIP). This simple document is your very first green light from a lender, proving they're willing - in principle - to lend you money for your new home. We'll walk you through:  What a Decision in Principle actually is Why you should get one before you start house-hunting How a mortgage adviser helps you find the lender that suits your situation The truth about credit checks (and why you shouldn't apply for DIPs everywhere online) How long a DIP lasts — and what to do if it expires Why you should never reveal your full DIP amount to an estate agent Whether you can have more than one DIP  How your DIP becomes a full mortgage application when you find "the one" By the end of this episode, you'll understand exactly why a DIP is the difference between hoping you can buy a home… and knowing you can. If you're a first-time buyer, self-employed, on maternity leave, or simply unsure where to start, this episode will give you the clarity and confidence you need to take the next step. Watch the full episode on YouTube: How to Save for a House Deposit UK | On The Ladder Ep. 1 Follow on Instagram: @the_mortgage_mum 

(Note: We have adjusted the series order to cover Christian Liberty in Session 8 last week, with The Regulative Principle of Worship following this week in Session 9.)In this lesson, we explore the biblical regulative principle of worship: God alone determines how He is to be worshiped, and only those elements explicitly commanded or exemplified in Scripture are permitted. Following chapter 8 of Dr. Hicks' book, we will examine the key elements of corporate worship (such as the reading and preaching of the Word, prayer, singing of psalms/hymns/spiritual songs, and the ordinances of baptism and the Lord's Supper), while rejecting human inventions or additions that lack biblical warrant—all to ensure worship that is simple, pure, and God-glorifying.This series works to provide a positive, biblical case for key beliefs, including the sufficiency of Scripture, salvation by grace alone, justification by faith, covenant theology, Calvinism, the regulative principle of worship, and more—tracing their roots from the early church through the Reformation and Puritan eras.Our weekly Sunday School live stream begins every Lord's Day at 9:30 AM (US Central Time).About Reformed Baptist Church of McKinneyWe are a Christ-centered, Bible-believing church in McKinney, Texas, committed to the glory of God through expository preaching, sound doctrine, and vibrant fellowship. For more details on our beliefs, ministries, and events, visit our website: https://rbcmckinney.comConnect with UsFacebook/Instagram/X: @rbcmckinneySupport Our MinistryYour generous tithes and offerings help sustain our work in proclaiming the gospel. Give securely online: https://rbcmckinney.churchcenter.com/givingDisclaimerWe do not own the rights to “What Is a Reformed Baptist? An Overview of Doctrinal Distinctives” by Tom Hicks (Founders Press, 2024). This book is used solely as a teaching guide for our series. For more on the author, the book, or Founders Ministries, visit: https://press.founders.org/shop/what-is-a-reformed-baptist/SOLI DEO GLORIA

Watch the YouTube version of this episode HEREAre you a firm owner struggling with hiring top talent? In this episode, Tyson shares a personal story about hiring and professionalism. Tyson encourages listeners to look beyond surface-level traits and trust their intuition, highlighting that true professionalism is revealed in small, everyday actions.After buying a new car, Tyson provides some insights on first impressions for the hiring process. When Tyson called the dealership, he encountered an individual who had amazing phone training. This individual asked him all the right questions, anticipated his answers and overall showed Tyson what smooth, client interactions can look like. After receiving a text from this person asking about a job at his firm, Tyson reflects on professionalism and what to look for when hiring good talent.When it comes to hiring for a firm, it is important to assess fit and look at certain qualities in a candidate. When looking to hire, sometimes you might find someone that checks all of your boxes and might actually be a really good fit. But, it is important to find someone that takes it to the next level. To determine this, you look at those deeper qualities. Do they have the character needed to do well and represent your firm well? This might be the most important quality, so if someone does not have it, you need to re-evaluate.Take a listen!4:12 Reflection on First Impressions and Hiring Process5:42 Cialdini's Principle and Breach of Professionalism10:21 Employer-Employee Relationship and Professional Courtesy12:29 Timing and Judgment in Professional Interactions15:43 Assessing Fit and Deeper Qualities in HiringTune in to today's episode and checkout the full show notes here. 

Principle 5 – Oneness in Christ   Ephesians 2:11-22Regardless of our ethnic backgrounds, social statuses, genders, or races, when we become believers we are to function as members of one family. NEW! - Let us know what you think of the program! Support the show

Growth often looks like adding more products, more offers, and more activity. In reality, it is usually the opposite that creates profit.

Former pro surfer Nicole Grodesky sits down with us to chat about her surf journey, the nuances of women's professional surfing, and how we can leverage different mentalities to help push us to believe in ourselves more and succeed. We chat about how setbacks can be viewed as life redirects, rather than failures, that lead us down more fulfilling paths, why it is essential to speak up for ourselves, and some insight into dealing with the emotional rollercoaster that is surfing. Nicole's story emphasizes that that every life experience provides extra leverage and greater benefit moving forward.

Principle 4 – God's Gift   Ephesians 1:20-2:10When we present the message of hope in Christ, we must make sure that all people understand that good works do not contribute in any way to their salvation experience. NEW! - Let us know what you think of the program! Support the show

A study of the Gospel of Matthew by the Theology of Work Project notes that Matthew 6:21 is worded somewhat counter-intuitively. Jesus instructed his listeners to store up treasures in heaven instead of on earth, where those treasures are subject to loss. He then said, “For where your treasure is, there your heart will be ... The post Treasure Principle appeared first on Unconventional Business Network.

Principle 3 – Measuring Corporate Maturity   Ephesians 1:15-19When we evaluate the maturity of any local church, we should look for the ways believers are manifesting faith, hope, and love in their relationships with God and one another.NEW! - Let us know what you think of the program! Support the show

In this episode, Bryan Dawson applies the “Dutton Principle” to immigration and explains why anything worth having must be defended—or it will be lost. Dawson connects faith, history, and current events to argue that immigration is the most urgent political issue facing America today. Building on themes from recent episodes, he explains why immigration without assimilation is not compassion, but invasion, and how it fits into a broader cultural and ideological struggle. Dawson frames America as an inherited garden, built through sacrifice and faith, and warns that stewardship requires the courage to protect what previous generations handed down. From overwhelmed hospitals and public schools to rising housing costs, infrastructure strain, public safety concerns, and compromised elections, he lays out how mass legal and illegal immigration is reshaping the nation's economy, culture, and future. In a viral personal story sparked by a routine trip to buy stamps, Dawson exposes what he calls “toxic empathy”—a mindset that prioritizes the feelings of lawbreakers over responsibility to citizens and future generations. The backlash he received online, filled with accusations of racism and fascism, becomes a case study in how dissent is silenced and resistance discouraged. The episode also addresses a controversial but direct claim: while abortion remains a grave moral evil, a nation must exist in order to outlaw it. Without borders, assimilation, and moral clarity, no long-term political victories are possible. Dawson closes with a call to reject propaganda, embrace courage, and accept that defending something worth having always comes at a cost.

In this episode, Bryan Dawson applies the “Dutton Principle” to immigration and explains why anything worth having must be defended—or it will be lost. Dawson connects faith, history, and current events to argue that immigration is the most urgent political issue facing America today. Building on themes from recent episodes, he explains why immigration without assimilation is not compassion, but invasion, and how it fits into a broader cultural and ideological struggle. Dawson frames America as an inherited garden, built through sacrifice and faith, and warns that stewardship requires the courage to protect what previous generations handed down. From overwhelmed hospitals and public schools to rising housing costs, infrastructure strain, public safety concerns, and compromised elections, he lays out how mass legal and illegal immigration is reshaping the nation's economy, culture, and future. In a viral personal story sparked by a routine trip to buy stamps, Dawson exposes what he calls “toxic empathy”—a mindset that prioritizes the feelings of lawbreakers over responsibility to citizens and future generations. The backlash he received online, filled with accusations of racism and fascism, becomes a case study in how dissent is silenced and resistance discouraged. The episode also addresses a controversial but direct claim: while abortion remains a grave moral evil, a nation must exist in order to outlaw it. Without borders, assimilation, and moral clarity, no long-term political victories are possible. Dawson closes with a call to reject propaganda, embrace courage, and accept that defending something worth having always comes at a cost.

Today I'm joined by Scott Simons, Dealer Principle of Simons Chevrolet GMC. Scott breaks down the leap from corporate leadership to dealership ownership — the money discipline, personal brand, and network it actually takes. He lays out the unexpected challenges of buying his first store, how he navigated a sub-$10M investment, and why adaptability became his biggest edge. Dealers will walk away with clear, tactical insights on evaluating opportunities, managing risk, and jump-starting early growth. This episode is brought to you by: 1. vAuto - Join us at the Cox Automotive Village during NADA. See the latest vAuto innovations and talk to our experts. Reserve your spot now at https://www.coxautoinc.com/nada/vauto. Don't miss it—your next big advantage starts here. Visit @ https://www.coxautoinc.com/nada/vauto 2. Lotlinx - What if ChatGPT actually spoke dealer? Meet LotGPT — the first AI chatbot built just for car dealers. Fluent in your market, your dealership, and your inventory, LotGPT delivers instant insights to help you merchandise smarter, move inventory faster, and maximize profit. It pulls from your live inventory, CRM, and Google Analytics to give VIN-specific recommendations, helping dealers price vehicles accurately, spot wasted spend, and uncover the hottest opportunities — all in seconds. LotGPT is free for dealers, but invite-only. Join the waitlist now @ http://www.Lotlinx.com/LotGPT 3. Nomad Content Studio - Most dealers still fumble social—posting dry inventory pics or handing it off without a plan. Meanwhile, the store down the street is racking up millions of views and selling / buying cars using video. That's where Nomad Content Studio comes in. We train your own videographer, direct what to shoot, and handle strategy, to posting, to feedback. Want in with the team behind George Saliba, EV Auto, and top auto groups? Book a call @ http://www.trynomad.co Check out Car Dealership Guy's stuff: For dealers: CDG Circles ➤ ⁠https://cdgcircles.com/⁠ Industry job board ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://jobs.dealershipguy.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Dealership recruiting ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.cdgrecruiting.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Fix your dealership's social media ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.trynomad.co⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Request to be a podcast guest ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.cdgguest.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ For industry vendors: Advertise with Car Dealership Guy ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.cdgpartner.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Industry job board ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://jobs.dealershipguy.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Request to be a podcast guest ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://www.cdgguest.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Topics: 03:10 Key to acquiring the dealership? 06:24 How does family drive your motivation? 11:42 Biggest operational challenge and strategy? 14:13 Most crucial vendor relationship lesson? 24:59 Securing OEM approval: hardest part? 28:42 How to build a strong team? 29:52 How does networking drive career growth? 49:27 What is your ultimate legacy goal? Car Dealership Guy Socials: X ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠x.com/GuyDealership⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠instagram.com/cardealershipguy/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ TikTok ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠tiktok.com/@guydealership⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠linkedin.com/company/cardealershipguy⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Threads ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠threads.net/@cardealershipguy⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Facebook ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠facebook.com/profile.php?id=100077402857683⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Everything else ➤ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠dealershipguy.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

In this episode, Ernie explains how the American Arbitration Association is now using AI to draft decisions, subject to human review. The discussion covers the importance of transparency, control, and human oversight in the arbitration process, as well as the potential for AI to improve access to justice by making dispute resolution faster and more cost-effective. Key Takeaways AI is not about replacing humans but enhancing their capabilities. The American Arbitration Association is pioneering AI in legal disputes. AI can draft decisions, but humans retain final authority. Transparency and control are crucial in the arbitration process. Party validation ensures fairness and understanding in disputes. Governed AI operates within strict guidelines to ensure accuracy. The system learns from human edits to improve over time. Speed and cost savings are significant benefits of AI arbitration. AI can open doors to justice for underserved populations. This technology may signal a fundamental shift in legal processes. Resource Links ChatGPT Lab (a weekly AI workshop for lawyers) Apply to join the ChatGPT Lab The 80/20 Principle (my techlaw newsletter) The Inner Circle (my online community for lawyers) Follow and Review: I'd love for you to follow me if you haven't yet. Click that purple '+' in the top right corner of your Apple Podcasts app. I'd love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select "Ratings and Reviews" and "Write a Review" 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. Thanks to the sponsor: Smith.ai Smith.ai is an amazing virtual receptionist service that specializes in working with solo and small law firms. When you hire Smith.ai, you're hiring well-trained, friendly receptionists who can respond to callers in English or Spanish. And they have a special offer for podcast listeners where you can get an extra $100 discount with promo code ERNIE100. Sign up for a risk-free start with a 14-day money-back guarantee now (and learn more) at smith.ai.    

Head over to ⁠8020BASEBALL.com⁠⁠⁠⁠⁠⁠⁠⁠⁠ and get the “COACHING PLAN” and the free 21-page Drill Design Guide PDF.ABOUT:Welcome to the 8020 Baseball Podcast, where Coach Bo shares a direct path to becoming a great youth baseball coach by combining his 20+ years of baseball coaching experience with his 20+ years of unique teaching experience, while also drawing on his experiences playing youth, HS, collegiate, and professional baseball.A deep level of baseball knowledge, combined with universal strategies such as the 80/20 Principle, gives this podcast a uniquely advanced approach to mastering all the key parts of coaching youth baseball.The podcast combines solo episodes with high-quality interviews featuring individuals who share specific, actionable strategies for youth baseball coaches. New episodes every Tuesday!

Principle 2 – Our Position in Christ   Ephesians 1:3-14Because of our eternal hope and secure relationship with God through Jesus Christ and the Holy Spirit, we should never cease to praise and worship him. NEW! - Let us know what you think of the program! Support the show

① Saudi Arabia strongly reaffirms the one-China principle during Wang Yi's Middle East visit. What message does it send? (00:45) ② China denounces Japan for hyping up its regular military training. What's behind Tokyo's provocation? (11:55) ③ IMF official on China's economic outlook: what forces will shape the country's future? (27:05) ④ Far-right candidate Kast wins Chile's presidential election. What does it mean for the country and the region? (36:41) ⑤ China grants the first Level 3 autonomous driving vehicle permits. What's next? (45:08)

ABOUT THE EPISODEListen in as David Schrock and Stephen Wellum interview Levi Secord on his COA Longform Essay: "Law is King: How the BIble Shapes Our View of Law & Civil Government"Timestamps00:30 – Intro03:38 – The Background Behind Servant Not Savior05:11 – What are Some Things that Need to be On Our Radar as We Discuss This Subject?08:15 – Walking Us Through the History from the King to the Law10:27 – The Place of Natural Law13:15 – Where in the Bible Do We Encounter Rutherford's Ideas?15:49 – Nations Making Covenants21:00 – What is the Responsibility of Christians to Remind the Government of Their Role Before God?22:57 – Who's Role is it to Preach Before the Government?29:00 – Political Theology is not Just from the Old Testament31:32 – How Should We Read the OT Law to the King and Apply It Today?36:50 – How Does Progressive Covenantalism Apply the Law?40:22 – The Principle of General Equity42:03 – What Can Nations Learn from Israel? From the Church?47:20 – Good Government is the Exception to the Rule51:25 – The Case for Bringing the Bible to the Public Square54:50 – Natural Law is Not Devoid of Special Revelation56:10 – Levi Secord's Final Encouragements57:40 – OutroResources to Click“Law is King: How the Bible Shapes Our View of Law & Civil Government” – Levi Secord136: Political Islam – Just Thinking Podcast2026 National Founders Conference: Make DisciplesTheme of the Month: Christmas BuffetGive to Support the WorkBooks to ReadServant Not Savior: An Introduction to the Bible's Teaching about Civil Government – Levi SecordDefending the Declaration: How the Bible and Christianity Influenced the Writing of the Declaration of Independence – Gary AmosA Christian Manifesto – Francis SchaefferHow Should We Then Live? – Francis SchaefferHe Is There and He Is Not Silent – Francis SchaefferLex Rex: The Law is King – Samuel RutherfordThe Origins of American Constitutionalism – Donald LutzColossians and Philemon (ZECotNT) – David W. PaoThe Gospel of Matthew (NICNT) – R.T. FranceThe Mission of God: A Manifesto of Hope for Society – Joseph BootThe Emergence of Liberty in the Modern World – Douglas F. KellyDominion – Tom HollandThe Book that Made Your World: How the Bible Created the Soul of Western Civilization – Vishal MangalwadiMere Christendom – Douglas Wilson

Principle 12 – Pure Motives in Ministry   Galatians 6:11-17To counter false teaching in the church, we must keep our motives pure.NEW! - Let us know what you think of the program! Support the show

TLDR: It was Claude :-)When I set out to compare ChatGPT, Claude, Gemini, Grok, and ChatPRD for writing Product Requirement Documents, I figured they'd all be roughly equivalent. Maybe some subtle variations in tone or structure, but nothing earth-shattering. They're all built on similar transformer architectures, trained on massive datasets, and marketed as capable of handling complex business writing.What I discovered over 45 minutes of hands-on testing revealed not just which tools are better for PRD creation, but why they're better, and more importantly, how you should actually be using AI to accelerate your product work without sacrificing quality or strategic thinking.If you're an early or mid-career PM in Silicon Valley, this matters to you. Because here's the uncomfortable truth: your peers are already using AI to write PRDs, analyze features, and generate documentation. The question isn't whether to use these tools. The question is whether you're using the right ones most effectively.So let me walk you through exactly what I did, what I learned, and what you should do differently.The Setup: A Real-World Test CaseHere's how I structured the experiment. As I said at the beginning of my recording, “We are back in the Fireside PM podcast and I did that review of the ChatGPT browser and people seemed to like it and then I asked, uh, in a poll, I think it was a LinkedIn poll maybe, what should my next PM product review be? And, people asked for ChatPRD.”So I had my marching orders from the audience. But I wanted to make this more comprehensive than just testing ChatPRD in isolation. I opened up five tabs: ChatGPT, Claude, Gemini, Grok, and ChatPRD.For the test case, I chose something realistic and relevant: an AI-powered tutor for high school students. Think KhanAmigo or similar edtech platforms. This gave me a concrete product scenario that's complex enough to stress-test these tools but straightforward enough that I could iterate quickly.But here's the critical part that too many PMs get wrong when they start using AI for product work: I didn't just throw a single sentence at these tools and expect magic.The “Back of the Napkin” Approach: Why You Still Need to Think“I presume everybody agrees that you should have some formulated thinking before you dump it into the chatbot for your PRD,” I noted early in my experiment. “I suppose in the future maybe you could just do, like, a one-sentence prompt and come out with the perfect PRD because it would just know everything about you and your company in the context, but for now we're gonna do this more, a little old-school AI approach where we're gonna do some original human thinking.”This is crucial. I see so many PMs, especially those newer to the field, treat AI like a magic oracle. They type in “Write me a PRD for a social feature” and then wonder why the output is generic, unfocused, and useless.Your job as a PM isn't to become obsolete. It's to become more effective. And that means doing the strategic thinking work that AI cannot do for you.So I started in Google Docs with what I call a “back of the napkin” PRD structure. Here's what I included:Why: The strategic rationale. In this case: “Want to complement our existing edtech business with a personalized AI tutor, uh, want to maintain position industry, and grow through innovation. on mission for learners.”Target User: Who are we building for? “High school students interested in improving their grades and fundamentals. Fundamental knowledge topics. Specifically science and math. Students who are not in the top ten percent, nor in the bottom ten percent.”This is key—I got specific. Not just “students,” but students in the middle 80%. Not just “any subject,” but science and math. This specificity is what separates useful AI output from garbage.Problem to Solve: What's broken? “Students want better grades. Students are impatient. Students currently use AI just for finding the answers and less to, uh, understand concepts and practice using them.”Key Elements: The feature set and approach.Success Metrics: How we'd measure success.Now, was this a perfectly polished PRD outline? Hell no. As you can see from my transcript, I was literally thinking out loud, making typos, restructuring on the fly. But that's exactly the point. I put in maybe 10-15 minutes of human strategic thinking. That's all it took to create a foundation that would dramatically improve what came out of the AI tools.Round One: Generating the Full PRDWith my back-of-the-napkin outline ready, I copied it into each tool with a simple prompt asking them to expand it into a more complete PRD.ChatGPT: The Reliable GeneralistChatGPT gave me something that was... fine. Competent. Professional. But also deeply uninspiring.The document it produced checked all the boxes. It had the sections you'd expect. The writing was clear. But when I read it, I couldn't shake the feeling that I was reading something that could have been written for literally any product in any company. It felt like “an average of everything out there,” as I noted in my evaluation.Here's what ChatGPT did well: It understood the basic structure of a PRD. It generated appropriate sections. The grammar and formatting were clean. If you needed to hand something in by EOD and had literally no time for refinement, ChatGPT would save you from complete embarrassment.But here's what it lacked: Depth. Nuance. Strategic thinking that felt connected to real product decisions. When it described the target user, it used phrases that could apply to any edtech product. When it outlined success metrics, they were the obvious ones (engagement, retention, test scores) without any interesting thinking about leading indicators or proxy metrics.The problem with generic output isn't that it's wrong, it's that it's invisible. When you're trying to get buy-in from leadership or alignment from engineering, you need your PRD to feel specific, considered, and connected to your company's actual strategy. ChatGPT's output felt like it was written by someone who'd read a lot of PRDs but never actually shipped a product.One specific example: When I asked for success metrics, ChatGPT gave me “Student engagement rate, Time spent on platform, Test score improvement.” These aren't wrong, but they're lazy. They don't show any thinking about what specifically matters for an AI tutor versus any other educational product. Compare that to Claude's output, which got more specific about things like “concept mastery rate” and “question-to-understanding ratio.”Actionable Insight: Use ChatGPT when you need fast, serviceable documentation that doesn't need to be exceptional. Think: internal updates, status reports, routine communications. Don't rely on it for strategic documents where differentiation matters. If you do use ChatGPT for important documents, treat its output as a starting point that needs significant human refinement to add strategic depth and company-specific context.Gemini: Better Than ExpectedGoogle's Gemini actually impressed me more than I anticipated. The structure was solid, and it had a nice balance of detail without being overwhelming.What Gemini got right: The writing had a nice flow to it. The document felt organized and logical. It did a better job than ChatGPT at providing specific examples and thinking through edge cases. For instance, when describing the target user, it went beyond demographics to consider behavioral characteristics and motivations.Gemini also showed some interesting strategic thinking. It considered competitive positioning more thoughtfully than ChatGPT and proposed some differentiation angles that weren't in my original outline. Good AI tools should add insight, not just regurgitate your input with better formatting.But here's where it fell short: the visual elements. When I asked for mockups, Gemini produced images that looked more like stock photos than actual product designs. They weren't terrible, but they weren't compelling either. They had that AI-generated sheen that makes it obvious they came from an image model rather than a designer's brain.For a PRD that you're going to use internally with a team that already understands the context, Gemini's output would work well. The text quality is strong enough, and if you're in the Google ecosystem (Docs, Sheets, Meet, etc.), the integration is seamless. You can paste Gemini's output directly into Google Docs and continue iterating there.But if you need to create something compelling enough to win over skeptics or secure budget, Gemini falls just short. It's good, but not great. It's the solid B+ student: reliably competent but rarely exceptional.Actionable Insight: Gemini is a strong choice if you're working in the Google ecosystem and need good integration with Docs, Sheets, and other Google Workspace tools. The quality is sufficient for most internal documentation needs. It's particularly good if you're working with cross-functional partners who are already in Google Workspace. You can share and collaborate on AI-generated drafts without friction. But don't expect visual mockups that will wow anyone, and plan to add your own strategic polish for high-stakes documents.Grok: Not Ready for Prime TimeLet's just say my expectations were low, and Grok still managed to underdeliver. The PRD felt thin, generic, and lacked the depth you need for real product work.“I don't have high expectations for grok, unfortunately,” I said before testing it. Spoiler alert: my low expectations were validated.Actionable Insight: Skip Grok for product documentation work right now. Maybe it'll improve, but as of my testing, it's simply not competitive with the other options. It felt like 1-2 years behind the others.ChatPRD: The Specialized ToolNow this was interesting. ChatPRD is purpose-built for PRDs, using foundational models underneath but with specific tuning and structure for product documentation.The result? The structure was logical, the depth was appropriate, and it included elements that showed understanding of what actually matters in a PRD. As I reflected: “Cause this one feels like, A human wrote this PRD.”The interface guides you through the process more deliberately than just dumping text into a general chat interface. It asks clarifying questions. It structures the output more thoughtfully.Actionable Insight: If you're a technical lead without a dedicated PM, or you're a PM who wants a more structured approach to using AI for PRDs, ChatPRD is worth the specialized focus. It's particularly good when you need something that feels authentic enough to share with stakeholders without heavy editing.Claude: The Clear WinnerBut the standout performer, and I'm ranking these, was Claude.“I think we know that for now, I'm gonna say Claude did the best job,” I concluded after all the testing. Claude produced the most comprehensive, thoughtful, and strategically sound PRD. But what really set it apart were the concept mocks.When I asked each tool to generate visual mockups of the product, Claude produced HTML prototypes that, while not fully functional, looked genuinely compelling. They had thoughtful UI design, clear information architecture, and felt like something that could actually guide development.“They were, like, closer to, like, what a Lovable would produce or something like that,” I noted, referring to the quality of low-fidelity prototypes that good designers create.The text quality was also superior: more nuanced, better structured, and with more strategic depth. It felt like Claude understood not just what a PRD should contain, but why it should contain those elements.Actionable Insight: For any PRD that matters, meaning anything you'll share with leadership, use to get buy-in, or guide actual product development, you might as well start with Claude. The quality difference is significant enough that it's worth using Claude even if you primarily use another tool for other tasks.Final Rankings: The Definitive HierarchyAfter testing all five tools on multiple dimensions: initial PRD generation, visual mockups, and even crafting a pitch paragraph for a skeptical VP of Engineering, here's my final ranking:* Claude - Best overall quality, most compelling mockups, strongest strategic thinking* ChatPRD - Best for structured PRD creation, feels most “human”* Gemini - Solid all-around performance, good Google integration* ChatGPT - Reliable but generic, lacks differentiation* Grok - Not competitive for this use case“I'd probably say Claude, then chat PRD, then Gemini, then chat GPT, and then Grock,” I concluded.The Deeper Lesson: Garbage In, Garbage Out (Still Applies)But here's what matters more than which tool wins: the realization that hit me partway through this experiment.“I think it really does come down to, like, you know, the quality of the prompt,” I observed. “So if our prompt were a little more detailed, all that were more thought-through, then I'm sure the output would have been better. But as you can see we didn't really put in brain trust prompting here. Just a little bit of, kind of hand-wavy prompting, but a little better than just one or two sentences.”And we still got pretty good results.This is the meta-insight that should change how you approach AI tools in your product work: The quality of your input determines the quality of your output, but the baseline quality of the tool determines the ceiling of what's possible.No amount of great prompting will make Grok produce Claude-level output. But even mediocre prompting with Claude will beat great prompting with lesser tools.So the dual strategy is:* Use the best tool available (currently Claude for PRDs)* Invest in improving your prompting skills ideally with as much original and insightful human, company aware, and context aware thinking as possible.Real-World Workflows: How to Actually Use This in Your Day-to-Day PM WorkTheory is great. Here's how to incorporate these insights into your actual product management workflows.The Weekly Sprint Planning WorkflowEvery PM I know spends hours each week preparing for sprint planning. You need to refine user stories, clarify acceptance criteria, anticipate engineering questions, and align with design and data science. AI can compress this work significantly.Here's an example workflow:Monday morning (30 minutes):* Review upcoming priorities and open your rough notes/outline in Google Docs* Open Claude and paste your outline with this prompt:“I'm preparing for sprint planning. Based on these priorities [paste notes], generate detailed user stories with acceptance criteria. Format each as: User story, Business context, Technical considerations, Acceptance criteria, Dependencies, Open questions.”Monday afternoon (20 minutes):* Review Claude's output critically* Identify gaps, unclear requirements, or missing context* Follow up with targeted prompts:“The user story about authentication is too vague. Break it down into separate stories for: social login, email/password, session management, and password reset. For each, specify security requirements and edge cases.”Tuesday morning (15 minutes):* Generate mockups for any UI-heavy stories:“Create an HTML mockup for the login flow showing: landing page, social login options, email/password form, error states, and success redirect.”* Even if the HTML doesn't work perfectly, it gives your designers a starting pointBefore sprint planning (10 minutes):* Ask Claude to anticipate engineering questions:“Review these user stories as if you're a senior engineer. What questions would you ask? What concerns would you raise about technical feasibility, dependencies, or edge cases?”* This preparation makes you look thoughtful and helps the meeting run smoothlyTotal time investment: ~75 minutes. Typical time saved: 3-4 hours compared to doing this manually.The Stakeholder Alignment WorkflowGetting alignment from multiple stakeholders (product leadership, engineering, design, data science, legal, marketing) is one of the hardest parts of PM work. AI can help you think through different stakeholder perspectives and craft compelling communications for each.Here's how:Step 1: Map your stakeholders (10 minutes)Create a quick table in a doc:Stakeholder | Primary Concern | Decision Criteria | Likely Objections VP Product | Strategic fit, ROI | Company OKRs, market opportunity | Resource allocation vs other priorities VP Eng | Technical risk, capacity | Engineering capacity, tech debt | Complexity, unclear requirements Design Lead | User experience | User research, design principles | Timeline doesn't allow proper design process Legal | Compliance, risk | Regulatory requirements | Data privacy, user consent flowsStep 2: Generate stakeholder-specific communications (20 minutes)For each key stakeholder, ask Claude:“I need to pitch this product idea to [Stakeholder]. Based on this PRD, create a 1-page brief addressing their primary concern of [concern from your table]. Open with the specific value for them, address their likely objection of [objection], and close with a clear ask. Tone should be [professional/technical/strategic] based on their role.”Then you'll have customized one-pagers for your pre-meetings with each stakeholder, dramatically increasing your alignment rate.Step 3: Synthesize feedback (15 minutes)After gathering stakeholder input, ask Claude to help you synthesize:“I got the following feedback from stakeholders: [paste feedback]. Identify: (1) Common themes, (2) Conflicting requirements, (3) Legitimate concerns vs organizational politics, (4) Recommended compromises that might satisfy multiple parties.”This pattern-matching across stakeholder feedback is something AI does really well and saves you hours of mental processing.The Quarterly Planning WorkflowQuarterly or annual planning is where product strategy gets real. You need to synthesize market trends, customer feedback, technical capabilities, and business objectives into a coherent roadmap. AI can accelerate this dramatically.Six weeks before planning:* Start collecting input (customer interviews, market research, competitive analysis, engineering feedback)* Don't wait until the last minuteFour weeks before planning:Dump everything into Claude with this structure:“I'm creating our Q2 roadmap. Context:* Business objectives: [paste from leadership]* Customer feedback themes: [paste synthesis]* Technical capabilities/constraints: [paste from engineering]* Competitive landscape: [paste analysis]* Current product gaps: [paste from your analysis]Generate 5 strategic themes that could anchor our Q2 roadmap. For each theme:* Strategic rationale (how it connects to business objectives)* Key initiatives (2-3 major features/projects)* Success metrics* Resource requirements (rough estimate)* Risks and mitigations* Customer segments addressed”This gives you a strategic framework to react to rather than starting from a blank page.Three weeks before planning:Iterate on the most promising themes:“Deep dive on Theme 3. Generate:* Detailed initiative breakdown* Dependencies on platform/infrastructure* Phasing options (MVP vs full build)* Go-to-market considerations* Data requirements* Open questions requiring research”Two weeks before planning:Pressure-test your thinking:“Play devil's advocate on this roadmap. What are the strongest arguments against each initiative? What am I likely missing? What failure modes should I plan for?”This adversarial prompting forces you to strengthen weak points before your leadership reviews it.One week before planning:Generate your presentation:“Create an executive presentation for this roadmap. Structure: (1) Market context and strategic imperative, (2) Q2 themes and initiatives, (3) Expected outcomes and metrics, (4) Resource requirements, (5) Key risks and mitigations, (6) Success criteria for decision. Make it compelling but data-driven. Tone: confident but not overselling.”Then add your company-specific context, visual brand, and personal voice.The Customer Research WorkflowAI can't replace talking to customers, but it can help you prepare better questions, analyze feedback more systematically, and identify patterns faster.Before customer interviews:“I'm interviewing customers about [topic]. Generate:* 10 open-ended questions that avoid leading the witness* 5 follow-up questions for each main question* Common cognitive biases I should watch for* A framework for categorizing responses”This prep work helps you conduct better interviews.After interviews:“I conducted 15 customer interviews. Here are the key quotes: [paste anonymized quotes]. Identify:* Recurring themes and patterns* Surprising insights that contradict our assumptions* Segments with different needs* Implied needs customers didn't articulate directly* Recommended next steps for validation”AI is excellent at pattern-matching across qualitative data at scale.The Crisis Management WorkflowSomething broke. The site is down. Data was lost. A feature shipped with a critical bug. You need to move fast.Immediate response (5 minutes):“Critical incident. Details: [brief description]. Generate:* Incident classification (Sev 1-4)* Immediate stakeholders to notify* Draft customer communication (honest, apologetic, specific about what happened and what we're doing)* Draft internal communication for leadership* Key questions to ask engineering during investigation”Having these drafted in 5 minutes lets you focus on coordination and decision-making rather than wordsmithing.Post-incident (30 minutes):“Write a post-mortem based on this incident timeline: [paste timeline]. Include:* What happened (technical details)* Root cause analysis* Impact quantification (users affected, revenue impact, time to resolution)* What went well in our response* What could have been better* Specific action items with owners and deadlines* Process changes to prevent recurrence Tone: Blameless, focused on learning and improvement.”This gives you a strong first draft to refine with your team.Common Pitfalls: What Not to Do with AI in Product ManagementNow let's talk about the mistakes I see PMs making with AI tools. Pitfall #1: Treating AI Output as FinalThe biggest mistake is copy-pasting AI output directly into your PRD, roadmap presentation, or stakeholder email without critical review.The result? Documents that are grammatically perfect but strategically shallow. Presentations that sound impressive but don't hold up under questioning. Emails that are professionally worded but miss the subtext of organizational politics.The fix: Always ask yourself:* Does this reflect my actual strategic thinking, or generic best practices?* Would my CEO/engineering lead/biggest customer find this compelling and specific?* Are there company-specific details, customer insights, or technical constraints that only I know?* Does this sound like me, or like a robot?Add those elements. That's where your value as a PM comes through.Pitfall #2: Using AI as a Crutch Instead of a ToolSome PMs use AI because they don't want to think deeply about the product. They're looking for AI to do the hard work of strategy, prioritization, and trade-off analysis.This never works. AI can help you think more systematically, but it can't replace thinking.If you find yourself using AI to avoid wrestling with hard questions (”Should we build X or Y?” “What's our actual competitive advantage?” “Why would customers switch from the incumbent?”), you're using it wrong.The fix: Use AI to explore options, not to make decisions. Generate three alternatives, pressure-test each one, then use your judgment to decide. The AI can help you think through implications, but you're still the one choosing.Pitfall #3: Not IteratingGetting mediocre AI output and just accepting it is a waste of the technology's potential.The PMs who get exceptional results from AI are the ones who iterate. They generate an initial response, identify what's weak or missing, and ask follow-up questions. They might go through 5-10 iterations on a key section of a PRD.Each iteration is quick (30 seconds to type a follow-up prompt, 30 seconds to read the response), but the cumulative effect is dramatically better output.The fix: Budget time for iteration. Don't try to generate a complete, polished PRD in one prompt. Instead, generate a rough draft, then spend 30 minutes iterating on specific sections that matter most.Pitfall #4: Ignoring the Political and Human ContextAI tools have no understanding of organizational politics, interpersonal relationships, or the specific humans you're working with.They don't know that your VP of Engineering is burned out and skeptical of any new initiatives. They don't know that your CEO has a personal obsession with a specific competitor. They don't know that your lead designer is sensitive about not being included early enough in the process.If you use AI-generated communications without layering in this human context, you'll create perfectly worded documents that land badly because they miss the subtext.The fix: After generating AI content, explicitly ask yourself: “What human context am I missing? What relationships do I need to consider? What political dynamics are in play?” Then modify the AI output accordingly.Pitfall #5: Over-Relying on a Single ToolDifferent AI tools have different strengths. Claude is great for strategic depth, ChatPRD is great for structure, Gemini integrates well with Google Workspace.If you only ever use one tool, you're missing opportunities to leverage different strengths for different tasks.The fix: Keep 2-3 tools in your toolkit. Use Claude for important PRDs and strategic documents. Use Gemini for quick internal documentation that needs to integrate with Google Docs. Use ChatPRD when you want more guided structure. Match the tool to the task.Pitfall #6: Not Fact-Checking AI OutputAI tools hallucinate. They make up statistics, misrepresent competitors, and confidently state things that aren't true. If you include those hallucinations in a PRD that goes to leadership, you look incompetent.The fix: Fact-check everything, especially:* Statistics and market data* Competitive feature claims* Technical capabilities and limitations* Regulatory and compliance requirementsIf the AI cites a number or makes a factual claim, verify it independently before including it in your document.The Meta-Skill: Prompt Engineering for PMsLet's zoom out and talk about the underlying skill that makes all of this work: prompt engineering.This is a real skill. The difference between a mediocre prompt and a great prompt can be 10x difference in output quality. And unlike coding or design, where there's a steep learning curve, prompt engineering is something you can get good at quickly.Principle 1: Provide Context Before InstructionsBad prompt:“Write a PRD for an AI tutor”Good prompt:“I'm a PM at an edtech company with 2M users, primarily high school students. We're exploring an AI tutor feature to complement our existing video content library and practice problems. Our main competitors are Khan Academy and Course Hero. Our differentiation is personalized learning paths based on student performance data.Write a PRD for an AI tutor feature targeting students in the middle 80% academically who struggle with science and math.”The second prompt gives Claude the context it needs to generate something specific and strategic rather than generic.Principle 2: Specify Format and ConstraintsBad prompt:“Generate success metrics”Good prompt:“Generate 5-7 success metrics for this feature. Include a mix of:* Leading indicators (early signals of success)* Lagging indicators (definitive success measures)* User behavior metrics* Business impact metricsFor each metric, specify: name, definition, target value, measurement method, and why it matters.”The structure you provide shapes the structure you get back.Principle 3: Ask for Multiple OptionsBad prompt:“What should our Q2 priorities be?”Good prompt:“Generate 3 different strategic approaches for Q2:* Option A: Focus on user acquisition* Option B: Focus on engagement and retention* Option C: Focus on monetizationFor each option, detail: key initiatives, expected outcomes, resource requirements, risks, and recommendation for or against.”Asking for multiple options forces the AI (and forces you) to think through trade-offs systematically.Principle 4: Specify Audience and ToneBad prompt:“Summarize this PRD”Good prompt:“Create a 1-paragraph summary of this PRD for our skeptical VP of Engineering. Tone: Technical, concise, addresses engineering concerns upfront. Focus on: technical architecture, resource requirements, risks, and expected engineering effort. Avoid marketing language.”The audience and tone specification ensures the output will actually work for your intended use.Principle 5: Use Iterative RefinementDon't try to get perfect output in one prompt. Instead:First prompt: Generate rough draft Second prompt: “This is too generic. Add specific examples from [our company context].” Third prompt: “The technical section is weak. Expand with architecture details and dependencies.” Fourth prompt: “Good. Now make it 30% more concise while keeping the key details.”Each iteration improves the output incrementally.Let me break down the prompting approach that worked in this experiment, because this is immediately actionable for your work tomorrow.Strategy 1: The Structured Outline ApproachDon't go from zero to full PRD in one prompt. Instead:* Start with strategic thinking - Spend 10-15 minutes outlining why you're building this, who it's for, and what problem it solves* Get specific - Don't say “users,” say “high school students in the middle 80% of academic performance”* Include constraints - Budget, timeline, technical limitations, competitive landscape* Dump your outline into the AI - Now ask it to expand into a full PRD* Iterate section by section - Don't try to perfect everything at onceThis is exactly what I did in my experiment, and even with my somewhat sloppy outline, the results were dramatically better than they would have been with a single-sentence prompt.Strategy 2: The Comparative Analysis PatternOne technique I used that worked particularly well: asking each tool to do the same specific task and comparing results.For example, I asked all five tools: “Please compose a one paragraph exact summary I can share over DM with a highly influential VP of engineering who is generally a skeptic but super smart.”This forced each tool to synthesize the entire PRD into a compelling pitch while accounting for a specific, challenging audience. The variation in quality was revealing—and it gave me multiple options to choose from or blend together.Actionable tip: When you need something critical (a pitch, an executive summary, a key decision framework), generate it with 2-3 different AI tools and take the best elements from each. This “ensemble approach” often produces better results than any single tool.Strategy 3: The Iterative Refinement LoopDon't treat the AI output as final. Use it as a first draft that you then refine through conversation with the AI.After getting the initial PRD, I could have asked follow-up questions like:* “What's missing from this PRD?”* “How would you strengthen the success metrics section?”* “Generate 3 alternative approaches to the core feature set”Each iteration improves the output and, more importantly, forces me to think more deeply about the product.What This Means for Your CareerIf you're an early or mid-career PM reading this, you might be thinking: “Great, so AI can write PRDs now. Am I becoming obsolete?”Absolutely not. But your role is evolving, and understanding that evolution is critical.The PMs who will thrive in the AI era are those who:* Excel at strategic thinking - AI can generate options, but you need to know which options align with company strategy, customer needs, and technical feasibility* Master the art of prompting - This is a genuine skill that separates mediocre AI users from exceptional ones* Know when to use AI and when not to - Some aspects of product work benefit enormously from AI. Others (user interviews, stakeholder negotiation, cross-functional relationship building) require human judgment and empathy* Can evaluate AI output critically - You need to spot the hallucinations, the generic fluff, and the strategic misalignments that AI inevitably producesThink of AI tools as incredibly capable interns. They can produce impressive work quickly, but they need direction, oversight, and strategic guidance. Your job is to provide that guidance while leveraging their speed and breadth.The Real-World Application: What to Do Monday MorningLet's get tactical. Here's exactly how to apply these insights to your actual product work:For Your Next PRD:* Block 30 minutes for strategic thinking - Write your back-of-the-napkin outline in Google Docs or your tool of choice* Open Claude (or ChatPRD if you want more structure)* Copy your outline with this prompt:“I'm a product manager at [company] working on [product area]. I need to create a comprehensive PRD based on this outline. Please expand this into a complete PRD with the following sections: [list your preferred sections]. Make it detailed enough for engineering to start breaking down into user stories, but concise enough for leadership to read in 15 minutes. [Paste your outline]”* Review the output critically - Look for generic statements, missing details, or strategic misalignments* Iterate on specific sections:“The success metrics section is too vague. Please provide 3-5 specific, measurable KPIs with target values and explanation of why these metrics matter.”* Generate supporting materials:“Create a visual mockup of the core user flow showing the key interaction points.”* Synthesize the best elements - Don't just copy-paste the AI output. Use it as raw material that you shape into your final documentFor Stakeholder Communication:When you need to pitch something to leadership or engineering:* Generate 3 versions of your pitch using different tools (Claude, ChatPRD, and one other)* Compare them for:* Clarity and conciseness* Strategic framing* Compelling value proposition* Addressing likely objections* Blend the best elements into your final version* Add your personal voice - This is crucial. AI output often lacks personality and specific company context. Add that yourself.For Feature Prioritization:AI tools can help you think through trade-offs more systematically:“I'm deciding between three features for our next release: [Feature A], [Feature B], and [Feature C]. For each feature, analyze: (1) Estimated engineering effort, (2) Expected user impact, (3) Strategic alignment with making our platform the go-to solution for [your market], (4) Risk factors. Then recommend a prioritization with rationale.”This doesn't replace your judgment, but it forces you to think through each dimension systematically and often surfaces considerations you hadn't thought of.The Uncomfortable Truth About AI and Product ManagementLet me be direct about something that makes many PMs uncomfortable: AI will make some PM skills less valuable while making others more valuable.Less valuable:* Writing boilerplate documentation* Creating standard frameworks and templates* Generating routine status updates* Synthesizing information from existing sourcesMore valuable:* Strategic product vision and roadmapping* Deep customer empathy and insight generation* Cross-functional leadership and influence* Critical evaluation of options and trade-offs* Creative problem-solving for novel situationsIf your PM role primarily involves the first category of tasks, you should be concerned. But if you're focused on the second category while leveraging AI for the first, you're going to be exponentially more effective than your peers who resist these tools.The PMs I see succeeding aren't those who can write the best PRD manually. They're those who can write the best PRD with AI assistance in one-tenth the time, then use the saved time to talk to more customers, think more deeply about strategy, and build stronger cross-functional relationships.Advanced Techniques: Beyond Basic PRD GenerationOnce you've mastered the basics, here are some advanced applications I've found valuable:Competitive Analysis at Scale“Research our top 5 competitors in [market]. For each one, analyze: their core value proposition, key features, pricing strategy, target customer, and likely product roadmap based on recent releases and job postings. Create a comparison matrix showing where we have advantages and gaps.”Then use web search tools in Claude or Perplexity to fact-check and expand the analysis.Scenario Planning“We're considering three strategic directions for our product: [Direction A], [Direction B], [Direction C]. For each direction, map out: likely customer adoption curve, required technical investments, competitive positioning in 12 months, and potential pivots if the hypothesis proves wrong. Then identify the highest-risk assumptions we should test first for each direction.”This kind of structured scenario thinking is exactly what AI excels at—generating multiple well-reasoned perspectives quickly.User Story GenerationAfter your PRD is solid:“Based on this PRD, generate a complete set of user stories following the format ‘As a [user type], I want to [action] so that [benefit].' Include acceptance criteria for each story. Organize them into epics by functional area.”This can save your engineering team hours of grooming meetings.The Tools Will Keep Evolving. Your Process Shouldn'tHere's something important to remember: by the time you read this, the specific rankings might have shifted. Maybe ChatGPT-5 has leapfrogged Claude. Maybe a new specialized tool has emerged.But the core principles won't change:* Do strategic thinking before touching AI* Use the best tool available for your specific task* Iterate and refine rather than accepting first outputs* Blend AI capabilities with human judgment* Focus your time on the uniquely human aspects of product managementThe specific tools matter less than your process for using them effectively.A Final Experiment: The Skeptical VP TestI want to share one more insight from my testing that I think is particularly relevant for early and mid-career PMs.Toward the end of my experiment, I gave each tool this prompt: “Please compose a one paragraph exact summary I can share over DM with a highly influential VP of engineering who is generally a skeptic but super smart.”This is such a realistic scenario. How many times have you needed to pitch an idea to a skeptical technical leader via Slack or email? Someone who's brilliant, who's seen a thousand product ideas fail, and who can spot b******t from a mile away?The quality variation in the responses was fascinating. ChatGPT gave me something that felt generic and safe. Gemini was better but still a bit too enthusiastic. Grok was... well, Grok.But Claude and ChatPRD both produced messages that felt authentic, technically credible, and appropriately confident without being overselling. They acknowledged the engineering challenges while framing the opportunity compellingly.The lesson: When the stakes are high and the audience is sophisticated, the quality of your AI tool matters even more. That skeptical VP can tell the difference between a carefully crafted message and AI-generated fluff. So can your CEO. So can your biggest customers.Use the best tools available, but more importantly, always add your own strategic thinking and authentic voice on top.Questions to Consider: A Framework for Your Own ExperimentsAs I wrapped up my Loom, I posed some questions to the audience that I'll pose to you:“Let me know in the comments, if you do your PRDs using AI differently, do you start with back of the envelope? Do you say, oh no, I just start with one sentence, and then I let the chatbot refine it with me? Or do you go way more detailed and then use the chatbot to kind of pressure test it?”These aren't rhetorical questions. Your answer reveals your approach to AI-augmented product work, and different approaches work for different people and contexts.For early-career PMs: I'd recommend starting with more detailed outlines. The discipline of thinking through your product strategy before touching AI will make you a stronger PM. You can always compress that process later as you get more experienced.For mid-career PMs: Experiment with different approaches for different types of documents. Maybe you do detailed outlines for major feature PRDs but use more iterative AI-assisted refinement for smaller features or updates. Find what optimizes your personal productivity while maintaining quality.For senior PMs and product leaders: Consider how AI changes what you should expect from your PM team. Should you be reviewing more AI-generated first drafts and spending more time on strategic guidance? Should you be training your team on effective AI usage? These are leadership questions worth grappling with.The Path Forward: Continuous ExperimentationMy experiment with these five AI tools took 45 minutes. But I'm not done experimenting.The field of AI-assisted product management is evolving rapidly. New tools launch monthly. Existing tools get smarter weekly. Prompting techniques that work today might be obsolete in three months.Your job, if you want to stay at the forefront of product management, is to continuously experiment. Try new tools. Share what works with your peers. Build a personal knowledge base of effective prompts and workflows. And be generous with what you learn. The PM community gets stronger when we share insights rather than hoarding them.That's why I created this Loom and why I'm writing this post. Not because I have all the answers, but because I'm figuring it out in real-time and want to share the journey.A Personal Note on Coaching and ConsultingIf this kind of practical advice resonates with you, I'm happy to work with you directly.Through my pm coaching practice, I offer 1:1 executive, career, and product coaching for PMs and product leaders. We can dig into your specific challenges: whether that's leveling up your AI workflows, navigating a career transition, or developing your strategic product thinking.I also work with companies (usually startups or incubation teams) on product strategy, helping teams figure out PMF for new explorations and improving their product management function.The format is flexible. Some clients want ongoing coaching, others prefer project-based consulting, and some just want a strategic sounding board for a specific decision. Whatever works for you.Reach out through tomleungcoaching.com if you're interested in working together.OK. Enough pontificating. Let's ship greatness. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit firesidepm.substack.com

Crown Ignorant Kings — Reclaiming Truth, Authority, and the KingdomWhat if ignorance isn't an insult—but a wake-up call?In this unapologetically bold podcast, we challenge the misunderstood meaning of “ignorance” and uncover how misinformation, withheld truth, and spiritual misdirection have robbed humanity of its divine inheritance. Here, truth isn't just facts—it's original, eternal knowledge that transcends the senses.We delve into the profound message that every human being was created as a king, not by gender, but by divine authority. Through powerful revelations, we explore why God came in human form: to restore what was lost, to reconnect us to the Kingdom, and to reclaim the crowns forfeited through disobedience. This isn't your typical Gospel conversation. We go beyond “What Would Jesus Do” and ask the real question: What Did Jesus Say? Because the true Good News isn't just about the cross—it's about the crown beyond it. Join us as we confront spiritual misconceptions, awaken dormant authority, and do the work to Crown Ignorant Kings—one truth at a time. Now, Let's Adjust Our Crowns!Become a supporter of this podcast: https://www.spreaker.com/podcast/crowning-ignorant-kings--2714790/support.Crowning Ignorant Kings: The Online Kingdom AcademyFollow this FREE plan to gather the resources that you need to learn more about experiencing the Kingdom of God on earth.Crowning Ignorant Kings: BLOGCrowning Ignorant Kings: The Kingdom AcademyCrowning Ignorant Kings: Online Community

Principle 10 – Walking in Newness of Life   Ephesians 4:17-24Since God chose each one of us to live holy lives, we are to become what he created us to be. NEW! - Let us know what you think of the program! Support the show

Mark Raffles, from Scottsdale, Arizona, USALearn what we look for in a Daily Lift by listening to our webinar at christianscience.com/dailylift and submit your own healing message. We'd love to hear from you!

Principle 9 – Building Up One Another  Ephesians 4:7-16To become mature in Christ as local communities of faith, we must all function as members of one another. NEW! - Let us know what you think of the program! Support the show

I just had dinner with four really successful business owners—all running businesses bigger than mine—and we got talking about sales compensation plans. Once I started sharing things I honestly take for granted after 20 years in sales leadership, they were like "we hadn't thought about that." These are very smart, very successful guys, just not from the sales world. So if they found it helpful, maybe you will too. Here's the foundation: the only purpose of your comp plan is to change behavior. Charlie Munger said it perfectly: "Show me the incentive and I will show you the outcome." This episode breaks down three critical comp plan mistakes I see constantly: (1) Long-term commissions that look generous to you but don't change behavior next week because salespeople don't think like business owners—they think in cash, not equity or 36-month payouts, (2) Perpetual residuals that create permanent misalignment as your costs go up while their incentive to do the hard work (hunting) goes down, and (3) Having hunters farm instead of separating the roles, which misallocates both money and results. Learn why you need to reward behavior closest to when it happens, why saying "I'll fix it later" is fucked up, and how to align effort, difficulty, and value with what you're actually paying for.//Welcome to Repeatable Revenue, hosted by strategic growth advisor , Ray J. Green.About Ray:→ Former Managing Director of National Small & Midsize Business at the U.S. Chamber of Commerce, where he doubled revenue per sale in fundraising, led the first increase in SMB membership, co-built a national Mid-Market sales channel, and more.→ Former CEO operator for several investor groups where he led turnarounds of recently acquired small businesses.→ Current founder of MSP Sales Partners, where we currently help IT companies scale sales: www.MSPSalesPartners.com→ Current Sales & Sales Management Expert in Residence at the world's largest IT business mastermind.→ Current Managing Partner of Repeatable Revenue Ventures, where we scale B2B companies we have equity in: www.RayJGreen.com//Follow Ray on:YouTube | LinkedIn | Facebook | Twitter | Instagram

In this solo episode, I walk through 10 concrete rules to get way more out of Claude Code and Claude Opus 4.5, based directly on tips Anthropic has shared in their docs and blog posts. I show how to move from vague prompts to architected briefs that use tone, constraints, structure, and power phrases to avoid “AI slop.” I demo examples across writing, research, teaching, and planning so you can see exactly how to apply each rule. By the end, you have a practical playbook for prompting Claude like a teammate and using it as a true thinking partner in your work. Timestamps 00:00 – Intro 00:56 – Rule #1: Tone of collaboration 02:16 – Rule #2: Principle of explicitness (action verbs, quantity, audience) 03:20 – Rule #3: Define the boundaries with clear constraints 04:26 – Rule #4: Draft, plan, then act (outline → refine → execute) 06:39 – Rule #5: Demand structured output (tables, formats, schemas) 08:00 – Rule #6: Explain the “why” behind your request 09:05 – Rule #7: Control brevity vs. verbosity (expert, brief, simplifier) 10:21 – Rule #8: Provide a scaffold and templates 11:21 – Rule #9: Use “power phrases” and expert personas 12:28 – Rule #10: Divide and conquer complex projects 14:09 – Putting it all together with an example For founders doing $50k+ MRR+: https://startup-ideas-pod.link/offline-mode Key Points I share 10 specific prompting rules that come directly from how Anthropic suggests people use Claude. I show how friendly, clear, and firm prompts beat either vague or overly polite requests. I demonstrate how explicit constraints (length, style, audience, banned words) create more creative and focused outputs. I use outlines, scaffolds, and structured formats to turn Claude into a planning and synthesis engine instead of a random text generator. I introduce “power phrases” like “think step by step” and “critique your own response” to unlock more advanced reasoning. I wrap everything into a final Stoicism lecture prompt that combines persona, context, constraints, structure, and tone. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: thevibemarketer.com Startup Empire - get your free builders toolkit to build cashflowing business - https://startup-ideas-pod.link/startup-empire-toolkit Become a member - https://startup-ideas-pod.link/startup-empire FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/

If you've been feeling the call to be around others who get it — this is your chance.Not just daily prompts or prerecorded content — the Circle is INTERACTIVE, alive, real-time, and built on true human connection.

Principle 8 – Walking Worthy  Ephesians 4:1-6When we truly understand what God has done for all of us in Jesus Christ, we should respond by living godly lives in love and unity.NEW! - Let us know what you think of the program! Support the show

Show Notes In this podcast episode, Ernie Svenson interviews Dorna At Gavel, a former attorney turned tech entrepreneur, about her journey in creating Gavel, a legal technology platform. Dorna shares her experiences in building Gavel Workflows and Gavel Exec, tools designed to automate document creation and enhance legal drafting with AI. The conversation explores the integration of these tools with Microsoft Word, the importance of user experience, and the future of AI in the legal field. Dorna addresses common misconceptions about AI, the concept of 'vibe lawyering,' and how these technologies can empower lawyers to focus on more meaningful work while improving efficiency. Takeaways Dorna transitioned from law to tech to help domestic violence survivors. Gavel Workflows automates document creation for legal professionals. Gavel Exec serves as an AI copilot within Microsoft Word. The platform is designed to enhance collaboration and efficiency. AI tools can help lawyers focus on higher-level tasks. Misconceptions about AI include fears of job loss in the legal field. Vibe lawyering encourages creative legal thinking with AI assistance. Training junior associates can be streamlined using AI playbooks. Gavel Exec integrates with existing workflows to improve productivity. The future of legal practice will likely include AI as a standard tool. Resource Links ChatGPT Lab (a weekly AI workshop for lawyers) Apply to join the ChatGPT Lab The 80/20 Principle (my techlaw newsletter) The Inner Circle (my online community for lawyers) Follow and Review: I'd love for you to follow me if you haven't yet. Click that purple '+' in the top right corner of your Apple Podcasts app. I'd love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select "Ratings and Reviews" and "Write a Review" 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. Thanks to the sponsor: Smith.ai Smith.ai is an amazing virtual receptionist service that specializes in working with solo and small law firms. When you hire Smith.ai, you're hiring well-trained, friendly receptionists who can respond to callers in English or Spanish. And they have a special offer for podcast listeners where you can get an extra $100 discount with promo code ERNIE100. Sign up for a risk-free start with a 14-day money-back guarantee now (and learn more) at smith.ai.  

Head over to ⁠8020BASEBALL.com⁠⁠⁠⁠⁠⁠⁠⁠⁠ and get the newly launched COACHING PLAN and the free 21-page Drill Design Guide PDF.Welcome to the 8020 Baseball Podcast, where Coach Bo shares a direct path to becoming a great youth baseball coach by combining his 20+ years of baseball coaching experience with his 20+ years of unique teaching experience, while also drawing on his experiences playing youth, HS, collegiate, and professional baseball.A deep level of baseball knowledge, combined with universal strategies such as the 80/20 Principle, gives this podcast a uniquely advanced approach to mastering all the key parts of coaching youth baseball.The podcast combines solo episodes with high-quality interviews featuring individuals who share specific, actionable strategies for youth baseball coaches. New episodes every Tuesday!The best way to support the podcast is to share it (or leave a review). Thank you.

Join Dan and Stephanie Burke as they discuss how the devil tries to cause trouble in your marriage and how to combat those lies! Resources: Divine Intimacy in Marriage - retreat Finding Peace in the Storm - Dan Burke Into the Deep – Dan Burke Spiritual Warfare and the Discernment of Spirits - Dan Burke The Contemplative Rosary - Dan Burke and Connie Rossini A Catholic Guide to Mindfulness - Susan Brinkmann OCDS Avila-Institute.org/events - website Avila Institute for Spiritual Formation EWTN Religious Catalogue – online

In this episode, we talk about the six foundational principles of strain creation in animal breeding, crucial knowledge for anyone serious about starting or improving a breeding program. Whether you're breeding birds, livestock, or other animals, understanding these principles can help you develop strains that not only represent their breed, but are genetically strong, healthy, and productive.  We start by giving a brief recap of the six principles, Consolidation, Maximization, Fixation, Duplication, Stabilization, and Isolation—and explain how they work together to form the backbone of a successful breeding program. The Principle of Consolidation: Learn how outcrossing and crossbreeding can increase genetic diversity and introduce desirable traits, but if used improperly, it can weaken your strain.  The Principle of Maximization: Discover the power of selective breeding and how to amplify specific traits to continuously improve your strain. The Principle of Fixation: Explore how inbreeding and line-breeding can lock in desirable traits for consistency and reliability. The Principle of Duplication: Understand the importance of creating a strain that is predictable and uniform across generations. The Principle of Stabilization: Find out how to maintain the integrity of your strain, while improving key traits through careful selection and culling. The Principle of Isolation: Learn how to safeguard your strain from contamination, disease, and outside genetic influences to maintain purity and health. We encourage you to put these principles into practice in your own breeding program, whether you're starting from scratch or looking to refine an existing strain. Tune in to discover how mastering these principles can elevate your breeding efforts. This episode is packed with actionable advice, so be sure to grab a notebook and take notes! Don't forget to subscribe for more expert tips and insights into the world of breeding! Just go to www.breedersacademy.com #AnimalBreeding #StrainCreation #BreedingPrinciples #GeneticImprovement #SelectiveBreeding #InbreedingAndLinebreeding #LivestockBreeding #PoultryBreeding #BreedingProgram #GeneticStability #HealthyStrains #BreedersAcademy Join us on Bred to Perfection Live, Friday's at 6pm PST or 9pm EST on YouTube, as we discuss the benefits of creating your own strain. See ya there! Kenny Troiano Founder of "The Breeders Academy"  We specialize in breeding, and breeding related topics. This includes proper selection practices and the use of proven breeding programs. It is our mission to provide our followers and members a greater understanding of poultry breeding, poultry genetics, poultry health care and disease prevention, and how to improve the production and performance ability of your fowl.  If you are interested in creating a strain, or improving your established strain, you are in the right place.  We also want to encourage you to join us at the Breeders Academy, where we will not only help you increase your knowledge of breeding and advance your skills as a breeder, but improve the quality and performance of your fowl. If you would like to learn more, go to: https://www.breedersacademy.com

In this episode, we talk about the six foundational principles of strain creation in animal breeding, crucial knowledge for anyone serious about starting or improving a breeding program. Whether you're breeding birds, livestock, or other animals, understanding these principles can help you develop strains that not only represent their breed, but are genetically strong, healthy, and productive.  We start by giving a brief recap of the six principles, Consolidation, Maximization, Fixation, Duplication, Stabilization, and Isolation—and explain how they work together to form the backbone of a successful breeding program. The Principle of Consolidation: Learn how outcrossing and crossbreeding can increase genetic diversity and introduce desirable traits, but if used improperly, it can weaken your strain.  The Principle of Maximization: Discover the power of selective breeding and how to amplify specific traits to continuously improve your strain. The Principle of Fixation: Explore how inbreeding and line-breeding can lock in desirable traits for consistency and reliability. The Principle of Duplication: Understand the importance of creating a strain that is predictable and uniform across generations. The Principle of Stabilization: Find out how to maintain the integrity of your strain, while improving key traits through careful selection and culling. The Principle of Isolation: Learn how to safeguard your strain from contamination, disease, and outside genetic influences to maintain purity and health. We encourage you to put these principles into practice in your own breeding program, whether you're starting from scratch or looking to refine an existing strain. Tune in to discover how mastering these principles can elevate your breeding efforts. This episode is packed with actionable advice, so be sure to grab a notebook and take notes! Don't forget to subscribe for more expert tips and insights into the world of breeding! Just go to www.breedersacademy.com #AnimalBreeding #StrainCreation #BreedingPrinciples #GeneticImprovement #SelectiveBreeding #InbreedingAndLinebreeding #LivestockBreeding #PoultryBreeding #BreedingProgram #GeneticStability #HealthyStrains #BreedersAcademy Join us on Bred to Perfection Live, Friday's at 6pm PST or 9pm EST on YouTube, as we discuss the benefits of creating your own strain. See ya there! Kenny Troiano Founder of "The Breeders Academy"  We specialize in breeding, and breeding related topics. This includes proper selection practices and the use of proven breeding programs. It is our mission to provide our followers and members a greater understanding of poultry breeding, poultry genetics, poultry health care and disease prevention, and how to improve the production and performance ability of your fowl.  If you are interested in creating a strain, or improving your established strain, you are in the right place.  We also want to encourage you to join us at the Breeders Academy, where we will not only help you increase your knowledge of breeding and advance your skills as a breeder, but improve the quality and performance of your fowl. If you would like to learn more, go to: https://www.breedersacademy.com

Al, Zach, John Luke, and Christian explore the principle of “no kings” and how cultural envy pushed Israel to demand a leader who looked impressive but lacked character and paid for it dearly. The guys  trace the fallout from choosing Saul, contrast it with David's repentant heart, and show how wanting to resemble other nations sent Israel down a destructive path.  In this episode: Genesis 11; Genesis 12; Genesis 3, verse 24; Genesis 4; Exodus 14; Exodus 16; Exodus 17; Exodus 25; Deuteronomy 17; Joshua 2; Joshua 7; Judges 2; Judges 21; 1 Samuel 4, verses 19–22; 1 Samuel 5; 1 Samuel 6; 1 Samuel 8; 1 Samuel 9; 1 Samuel 10; Jonah 1; Hebrews 12, verses 28–29; Psalm 51; Romans 1 Today's conversation is about Lesson 1 of The David Story: Shepherd, Father, King taught by Hillsdale Professor Justin Jackson. Take the course with us at no cost to you! Sign up at ⁠http://unashamedforhillsdale.com/⁠ More about The David Story: Encounter the beauty of the Bible. The David Story: Shepherd, Father, King explores the lives of Israel's first two kings—Saul and David—to discover the Bible's profound lessons about fatherhood, the nature of sin, and the consequences of sin on both a family and a nation. While David suffers great tragedies due to his own transgressions, he models a path to redemption through repentance. Join Professor Justin Jackson in a careful reading of First and Second Samuel to gain a deeper understanding of the meaning and beauty of this story that is not only fundamental to the Christian and Jewish faiths, but also a literary masterpiece. Join us today in this pursuit of a deeper understanding of the Bible in “The David Story.” Sign up at ⁠http://unashamedforhillsdale.com/ Check out At Home with Phil Robertson, nearly 800 episodes of Phil's unfiltered wisdom, humor, and biblical truth, available for free for the first time! Get it on Apple, Spotify, Amazon, and anywhere you listen to podcasts! https://podcasts.apple.com/us/podcast/at-home-with-phil-robertson/id1835224621 Listen to Not Yet Now with Zach Dasher on Apple, Spotify, iHeart, or anywhere you get podcasts. — Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of The Alpha Male Coach Podcast, we nerd all the way out on one of the deepest truths of your spiritual journey: time is always now. Brother, we go right into the heart of what it means to live in a “limited reality” and why your true power only exists in the present moment.I start by introducing The Brotherhood, a new program coming in January 2026 that serves as a half-step into the Academy for Consciousness Expansion - a place for you to step into community, coaching, the Model of Alignment, and eliminating buffering from your life. From there, we move straight into the here and now: why the past and future only exist in perception, why time and space are illusions, and how your consciousness is always operating in the eternal present.We explore monism: there is no separation between inner and outer, mind and body, you and your environment. Your consciousness and your environment are one unified hologram. That means reincarnation is not some linear “next life” in the future - it's about lessons, games, and the spiritual journey. Your consciousness can incarnate “forward” or “backward” in historical time, because it's all the same eternal now.To ground this, we dive into Star Wars - Obi-Wan, Qui-Gon Jinn, Yoda, and the living Force - as metaphors for your awakening. Being “mindful of the future” is useful, but not at the expense of the moment. When your mind is trapped in anxiety about the future or guilt about the past, you lose access to the Force. You lose access to action.So I give you a five-step practical process to return to the now and reclaim your power over flesh:Pause & Elevate Your Alpha – Stop and observe your mind. Where is your consciousness - past, future, or present?Run a Model of Alignment – Put it on paper, in a notebook, on your phone, or even using a tool like ChatGPT. Get your model out of your head so you can see your conditioning.Return to Presence & Feel – Bring your mind into your body. Feel the vibration, the emotion, the energy in motion. Let it move.Look Again at Your Environment – Open your eyes and truly see what's around you - whether it's trees, traffic, or office walls. It's all you. Your environment is your consciousness.Practice Your Intentional Model & Energy Mechanics – From presence, think deliberately. Run your intentional model and experiment with how you manage and move your energy.This episode is an invitation to stop living as a prisoner of time and start operating as a conscious Jedi in the hologram - aligned with the Force, rooted in the now, and fully engaged in your spiritual transformation.

After 27 years, Melvyn Bragg has decided to step down from the In Our Time presenter's chair. With over a thousand episodes to choose from, he has selected just six that capture the huge range and depth of the subjects he and his experts have tackled. In this fifth of his choices, we hear Melvyn Bragg and his guests discuss a key figure from quantum mechanics. Their topic is the life and ideas of Wolfgang Pauli (1900-1958), whose Exclusion Principle is one of the key ideas in quantum mechanics. A brilliant physicist, at 21 Pauli wrote a review of Einstein's theory of general relativity and that review is still a standard work of reference today. The Pauli Exclusion Principle proposes that no two electrons in an atom can be at the same time in the same state or configuration, and it helps explain a wide range of phenomena such as the electron shell structure of atoms. Pauli went on to postulate the existence of the neutrino, which was confirmed in his lifetime. Following further development of his exclusion principle, Pauli was awarded the Nobel Prize in Physics in 1945 for his 'decisive contribution through his discovery of a new law of Nature'. He also had a long correspondence with Jung, and a reputation for accidentally breaking experimental equipment which was dubbed The Pauli Effect. With Frank Close Fellow Emeritus at Exeter College, University of Oxford Michela Massimi Professor of Philosophy of Science at the University of Edinburgh and Graham Farmelo Bye-Fellow of Churchill College, University of Cambridge Producer: Simon Tillotson Spanning history, religion, culture, science and philosophy, In Our Time from BBC Radio 4 is essential listening for the intellectually curious. In each episode, host Melvyn Bragg and expert guests explore the characters, events and discoveries that have shaped our world