Meridian Point

The Meridian Point Podcast Episode: Why People Open Up to an AI Coach Faster Than a Human Air Date: September 8,2026 EPISODE SUMMARY Kumar Dattatreyan and his longtime collaborator Glenn Marshall sit down for a fireside chat that starts with a finding Kumar didn't expect. He ran the same product management cohort he's run several times. Same content, same kind of audience. The one new variable was a set of AI agents guiding the asynchronous work with Socratic questions. The AI-enabled group shifted their mindset faster, engaged deeper and produced better artifacts. People admitted to a bot what they wouldn't admit to a human instructor. The conversation works through why that happens. Kumar's working theory is psychological safety: the bot behaves like a peer with a narrow base of knowledge, not a positional expert, so people engage with the fundamentals they're embarrassed to ask about. Glenn's first reaction was closer to terror, and he talks through how he reframed it as the ideal learning partner rather than a threat. The second half turns to the collapse of the iron triangle when one person can vibe-code an application in an afternoon, the rise of the two-slice team of one human and several agents, and the ROI and token-cost questions nobody can answer yet. The recording cut off on a technical glitch before Glenn and Kumar reached two threads they teased at the top: organizational ecosystems and the Strait of Hormuz. Those are queued for a future conversation. KEY TOPICS COVERED The AI-enabled cohort experiment Kumar's team won work to train product managers, product owners, business analysts and product-adjacent roles. They convinced the client that a six-to-ten week cohort beats a two-day certification class. They built AI agents into the asynchronous portions to guide learners through ideation, the why behind the product, customer empathy, journey mapping, OKRs, their COBI variant (Customer Outcomes, Business Impact), and writing epics and stories. The AI didn't do the work. It interrogated, Socratic style, and pushed people to think. Same course, one variable Kumar ran the identical course several times in 2025 without AI. The story maps and journey maps came back rudimentary. With the agents added, the same content produced deeper engagement and real artifacts. Within three weeks, the AI-enabled group's mindset had shifted toward discovery, iteration and hypothesis testing far more than the group that used the agents less. Why psychological safety changes learning The bot doesn't judge, doesn't carry a title and doesn't hold a positional imbalance over the learner. Kumar's read is that people engage with a bot the way they'd engage with a trusted peer who happens to know a little more about one narrow thing. Glenn connected it to the ideal one-on-one teacher you could never afford to staff twenty times over. Gamification on steroids, or something more Kumar pushed back on calling it gamification. No badges, no quizzes, no points. The payoff is the artifact appearing through collaboration with the agent. Glenn granted the label "gamification on steroids" while Kumar argued it goes past that into personalized coaching. The listener bot and feedback at scale Part of the course used a listener bot that reads a submitted assignment, identifies the module and lesson, and returns feedback automatically. Some feedback came from Kumar and his colleagues, most from the agent. Learners couldn't tell the difference and took the feedback well either way. Because AI runs at a flat monthly rate rather than by the hour, that kind of one-on-one assessment scales in a way a human team can't match. The iron triangle collapse and the two-slice team Anyone can vibe-code an application in an afternoon with very little budget. Cost, scope and budget stop behaving like real constraints. Kumar floated the shift from the two-pizza team to the two-slice team: one human as the master brain, augmented by five or six agents. The open questions are ROI, token cost and where humans still belong. He noted Microsoft limiting Claude Code use over token costs and a client moving cautiously toward AI for fear of runaway spend. The five-year horizon Glenn split his outlook. The next couple of years look amazing and very useful. The next five look terrifying if the technology isn't managed well, and in his view it isn't being managed well so far. Kumar agreed the shape of future work is unclear, including which new jobs it creates. MEMORABLE QUOTES Kumar: "The bot was better at getting these people to engage with the basics, the fundamentals that maybe they were embarrassed to admit that they didn't know." Kumar: "It takes many sessions before the coachee will trust me enough to tell me things I think they might tell a bot in visit one." Glenn: "Emotions by definition don't make sense." (on why people feel safer with a bot that records everything) Kumar: "Instead of a two-pizza team, it's going to be a two-slice team. One human with several agents helping them do their work." Kumar: "The human is still going to be the master brain, aided and augmented by agents around them in whatever they do." Glenn: "It's amazing and terrifying. In five years, if we're not managing this properly, and so far we're not, this could very easily go to a very bad place." Peter Merel (quoted by Glenn): "AI is going to do all jobs, all work, except for the stuff that we want to do ourselves." KEY TAKEAWAYS Mindset shift is hard, and adding AI agents to existing course content produced one faster than the same course had before Psychological safety is the likely mechanism: people engage with a non-judging peer more openly than with a positional expert The value is additive, not a replacement. The agent gave learners something they never had, then the live sessions got better AI feedback scales one-on-one assessment that a human team can't afford to deliver at the same volume The iron triangle loses its grip when one person can build a working app in an afternoon The two-slice team is a real design question: how many agents per human, and what's the ROI once token costs are counted The near term looks useful, the five-year horizon looks risky, and the new jobs this creates aren't visible yet RESOURCES & LINKS Kumar's Work: The Disruptor Method: disruptormethod.com Take the quiz (disruptor or disrupted): thedisruptormethod.com/quiz Agile Meridian: agilemeridian.com Book a 30-minute conversation Referenced in the Episode: Peter Merel and the XSCALE Alliance: xscalealliance.org Next Level Co-Creation (Glenn's framework) CONNECT WITH GLENN Glenn Marshall is an XSCALE Business Agility coach and trainer based in Toronto. Reach him here: XSCALE Alliance coach profile LinkedIn ABOUT THE CO-HOST Glenn Marshall is an agile coach, Certified Scrum Master and XSCALE Business Agility coach and trainer with a software architecture and development background. He's certified across Kanban, Disciplined Agile, LeSS, SAFe and Management 3.0, and trained as a professional coach. He's the creator of Next Level Co-Creation, a bottom-up transformation method, and a frequent Meridian Point collaborator on XSCALE, permaculture and ecosystem thinking. SUBSCRIBE 🎙️ Spotify | Apple Podcasts | YouTube | LinkedIn 🔔 Weekly episodes on disruption, innovation and transformation 💬 Leave a comment: do you trust AI with things you wouldn't tell a person? #AICoaching #FutureOfWork #Leadership #AgileCoaching #ProductManagement #DigitalTransformation #Disruption #XSCALE

Why 80% of Features Go Unused: Gary Cohen on Building the Right Thing The Meridian Point with Kumar Dattatreyan Episode overview Gary Cohen spent twenty years building a delivery machine that shipped software on schedule almost every time. Customers liked the features. They showed up to every sprint review. Then a private equity board member asked one question that reframed his career: what additional revenue do we expect from all these features? The honest answer exposed a hard truth. The team had optimized for delivery instead of impact. In this episode Gary and Kumar get into why building the right thing is harder than building the thing right. They cover embracing uncertainty as a strategy, continuous discovery, why red, yellow, green status meetings turn into theater, and where product management goes once AI makes the build cheap. About Gary Cohen Gary Cohen is Principal Consultant at Practical Agility. He is an engineering and product leader who ran product and engineering groups in software product companies for two decades. He led an agile transformation for one of Google's customer support groups. Today he helps teams shift from optimizing delivery to practicing real product discovery, drawing on continuous discovery work and a hard-won view of how organizational change actually sticks. What you'll learn Why great delivery can still hide a bigger problem, and the board question that surfaced it Why teams get too incremental, and how the innovator's dilemma quietly caps ambition What embracing uncertainty means, and why uncertainty is where differentiation lives The poker trap of going all in on one solution at the moment you know the least How to hold multiple solutions open and test the critical assumptions behind each Why red, yellow, green status meetings become theater, and the watermelon project problem The generative questions that turn a status interrogation into real discovery How one question, "how can I help," changes the tone of the room Where product discovery goes when AI makes shipping code cheap, and the two levers that still create differentiation Key takeaways Delivery is not the same as impact. You can ship efficiently and still fail to move revenue or usage. Language matters. Until someone asks about business outcomes, teams optimize for the schedule they are measured against. Uncertainty is an advantage. When everyone can execute, execution becomes a commodity. The edge goes to whoever reduces uncertainty fastest. Kill solutions early. The faster you invalidate a weak idea, the sooner you reach the one worth building. Status meetings can be redesigned. Swap "why are we not green" for "are we still convinced this is the right opportunity." Cheaper building raises the stakes on discovery, not lowers them. More competition means finding the valuable thing matters more than ever. Memorable quotes "We can ship stuff people don't want a lot faster." — Gary Cohen "This is the beginning, when you just start working in an area, and it is when you know the least about it. So you are making a decision way too early." — Gary Cohen "You get these watermelon projects, which are green on the outside but really red inside. It is essentially theater." — Gary Cohen "It is that presence of uncertainty that creates the opportunity for differentiation in the marketplace." — Gary Cohen "When something gets cheaper, people do more of it. So product discovery becomes more important, not less." — Gary Cohen Resources and books mentioned Continuous Discovery Habits by Teresa Torres Opportunity Solution Trees, a framework from Teresa Torres The Lean Startup by Eric Ries Jardena London's leadership circle, and her work on polarities and organizational change The "how can I help" reframing, inspired by Max Goodwin on the NBC show New Amsterdam Connect with Gary Cohen LinkedIn Practical Agility Gary would love to hear from listeners. Reach out on LinkedIn to continue the conversation on product discovery and leadership. Connect with the show Host: Kumar Dattatreyan LinkedIn: https://www.linkedin.com/in/coachkdat Agile Meridian: https://www.agilemeridian.com The Meridian Point airs live every two weeks on LinkedIn, YouTube and Facebook, then posts to Apple Podcasts and Spotify. SUBSCRIBE Spotify | Apple Podcasts | YouTube | LinkedIn Weekly episodes on disruption, innovation, and transformation Leave comments and share your experiences #AIStrategy #CommunityBuilding #ProductManagement #Leadership #DigitalTransformation

The Meridian Point Podcast Episode: Community Beats Content: Why Circle Aimed AI at the Admins and Left the Members Human Air Date: August 11, 2026 Episode Number: 177 EPISODE SUMMARY Circle just went fully AI-native with a launch called Eclipse. Kumar Dattatreyan sits down with Rene Rosendahl, Head of Product for Email Hub and CRM at Circle, to unpack a decision most AI-native product teams don't make: pointing the AI at the admins and deliberately keeping it out of the member experience. Rene walks through why content alone stopped being enough once AI made it cheap and abundant, and why community and human connection are what actually drive transformation. He explains where Circle applies AI (setup, moderation, retention, the operational drag that eats a community admin's day) and where it draws a hard line (member to member conversation, the part people showed up for). The conversation closes with how Rene runs product and engineering as a single seat instead of two, and how Circle keeps shipping fast without turning into a Frankenstein of one-off features. KEY TOPICS COVERED From Consulting to Building Rene left ERP systems, project management, and agile coaching because consulting felt mercenary: teach a team something and move on, with no long-term stake in the outcome. Product management gave him ownership of a problem over time instead of a framework handed off and walked away from. Content Versus Transformation Content is cheap now and getting cheaper, with AI generating or influencing much of it. Rene's argument: people don't want content, they want transformation, and reading a book or taking a solo course doesn't move anyone's life. A cohort going through the same journey together, with accountability built in, does. Where Circle Draws the AI Line Circle's Eclipse launch is AI-native, but Rene aimed that AI at the admin side: community setup, pricing and membership structure, content moderation, onboarding, and the repetitive questions that eat an admin's day. The member side stays human, with AI limited to narrow, obvious assists like summarizing long threads. Why "AI Slop" Kills Communities People come to a community for authenticity and connection. Rene's read: when AI starts running the conversation instead of assisting behind the scenes, members sense it and disengage. The line isn't "AI everywhere," it's AI where it removes drag and nowhere near the reason people joined. One Seat, Not Two Rene fuses product and engineering into a single line of ownership at Circle. His take: agreement without alignment is surface level, it doesn't surface the conflict underneath. Owning both roles forces him to hold user value, technical feasibility, and design usability at the same time instead of negotiating them after the fact. Shipping Fast Without Building a Frankenstein Circle's speed comes from a specific combination: leadership that blends technical, product, and design judgment, a shared architecture and design system across teams, a refusal to build one-off features for a single customer, and macro product cycles (Circle 3.0, Circle 4.0) that act as reset points before drift sets in. Measuring Product Velocity as Impact Circle runs quarterly planning built around cross-team priorities, customer feedback, and usage data, not a rigid framework. For efforts that cut across the whole engineering org, like Eclipse, the quarter's plan gets built so every team is pointed at the same outcome at the same time. Where a Community Leader Should Start with AI Rene's advice: use AI first to reduce admin: structure, pricing, and membership setup, plus the operational drag of moderation and onboarding. Then use it as a consultative thought partner for patterns and next moves. The human side of the community, the reason people join and stay, is not the place to automate. MEMORABLE QUOTES Quotes pulled directly from the recorded interview. Flag for a final check against the aired recording before reuse in any other content. "Content alone is not sufficient. Imagine you're reading a book, and you're walking away from that book, not applying anything. It's not necessarily making you or your life any better." "What people are looking for is authenticity and connection, not more AI slop." "If the robots were to take over a community, a place, I think people ultimately sense that and they will find less value or be so annoyed that they disengage from it." "You can agree on any number of things, but if you're not aligned, the agreement is just surface level because it doesn't surface the conflict that may be underneath." "We're not building one-off features just for one customer. That's probably the quickest road to a Frankenstein." "It's almost like you're asking a high performing basketball team to describe the chemistry that they have in order to make it repeatable for other teams." KEY TAKEAWAYS Content is commoditized, transformation isn't. AI made content cheap, but people still need other humans to actually change anything. Aim AI at drag, not at connection. Admin operations are fair game. Member conversations are not. Alignment beats agreement. Two people nodding at the same meeting doesn't mean they're headed the same direction. Speed without a Frankenstein takes structure. Shared architecture, shared design system, and a refusal to build for one customer at a time. Reset points prevent drift. Macro product cycles give a team a chance to correct course before small compromises pile up. AI's best early use for a community leader is time back, not member-facing automation. RESOURCES & LINKS Circle: Platform: circle.so Circle AI / Eclipse: circle.so (AI-native community platform launch) Connect with Rene: LinkedIn: linkedin.com/in/rrosendahl Personal site: agileapplied.com ABOUT THE GUEST Rene Rosendahl is Head of Product for Email Hub and CRM at Circle, the all-in-one platform for community-led businesses. He came up through ERP systems development, project management, and agile coaching before moving into product leadership roles at Kajabi and SamCart, and now leads a role at Circle that fuses product and engineering into a single line of ownership. Based in Irvine, California. ABOUT THE HOST Kumar Dattatreyan is co-founder of Agile Meridian and co-creator of The Disruptor Method™. The Meridian Point explores disruption and innovation through conversations with transformation leaders and entrepreneurs. Connect: linkedin.com/in/coachkdat | Book a conversation: tidycal.com/coachkumar/30-minute-meeting SUBSCRIBE Spotify | Apple Podcasts | YouTube | LinkedIn Weekly episodes on disruption, innovation, and transformation Leave comments and share your experiences #AIStrategy #CommunityBuilding #ProductManagement #Leadership #DigitalTransformation

Two Markets Shifted at Once: Surviving the Trough of Disruption Guest: Jeff Giesen Air Date: July 28, 2026 EPISODE SUMMARY Most disruption stories get told after the person makes it out the other side. Jeff Giesen is still in the middle of his, and that's what makes this conversation different. Jeff spent his career as an engineering leader and agile transformation practitioner. He built and led teams of Release Train Engineers, taught SAFe courses, and drove enterprise-scale change at a company in the travel reservation space. Then COVID flattened airline travel, the layoffs started coming every six months to a year, and eventually his group got hit. The scaled agile transformation that had helped the company deliver started to look like overhead, and the roles went with it. Instead of waiting for the next job to appear, Jeff went bigger on a real estate business he'd been building since 2011. He moved from small multifamily investing into ground-up townhome development, and he's now got eight units finishing in late August. Then the second disruption arrived: the Denver market softened, rates climbed, and units that were built to sell had to be converted to rentals while he waits for the numbers to work. So Jeff is carrying two disruptions at once, a contracted tech job market and a softened real estate market, both tying up his capital and his direction. Kumar calls this space the trough of disruption, the gap between what was and what's next. This episode is an honest look at what that gap feels like from the inside, and what it teaches you that you can't see when everything's going smoothly. KEY TOPICS COVERED Why Agile Didn't Save the Company Jeff's company ran a full scaled agile implementation, and it helped, but not enough to change the outcome. In a slow-moving business tied to the airlines, the transformation delivered improvements that weren't large or fast enough to justify the overhead once economic pressure hit. Kumar and Jeff both name the real lesson: transformation without clear outcomes measured along the way starts to look like cost, not value. Transformation Is a Journey, Not an End State The two agree that transformation has no finish line. It's constant improvement, constant attention to the market and the product, deeply iterative. The failure mode isn't the framework. It's treating the framework as the goal. From Side Hustle to Main Hustle Jeff bought his first rental in 2011 and managed it in his spare time. Watching scrape-and-build projects go up around his Denver duplex pulled at him for years. He couldn't act on it with a full-time job until he found a one-stop development partner who could source land, entitle it, design, and build. That relationship is what let a non-GC get into ground-up construction. When Two Markets Shift at Once Denver softened. Rates shocked upward. Rate buy-downs on completed units didn't move them. Jeff's read is that it isn't only rates: prices are high, everything costs more, and the political and economic backdrop adds friction. The pivot has been to convert unsold builds into rentals to cover expenses while waiting for sale numbers to make sense. Life in the Trough Jeff doesn't feel like the sky is falling, but he feels his hands are tied. His capital is locked in projects that haven't returned, so the commercial multifamily moves he wants to make are on hold. What the limbo has taught him is less tactical and more personal: trust, confidence, and managing fear before fear runs the show. Applying What He Taught to His Own Situation The transformation principles don't transfer to construction management, since Jeff is intentionally hands-off there and defers to operators who know permitting, cities, and counties. What does transfer is relationship-building. He vetted his development partner through his real estate network, and those relationships have carried him through a stretch where builders are struggling. The Job Search Reality Getting back into technology has been hard. AI-driven applicant tracking systems screen him out fast, and he hasn't cracked what they're looking for despite reworking resumes and cover letters with AI. His honest take: networking is still how experienced people actually find work, and he's lost roles to internal candidates the interviewers already knew. Where He's Headed No polished answer. Jeff stays open: technology roles, a real estate tangent that uses his program management skills, maybe something he starts. He describes the discomfort of feeling like he's wandering rather than pointed in one direction, and he's holding the tension between focus and optionality on purpose. MEMORABLE QUOTES Note: this was a live broadcast. Verify each quote against the final recording before reuse in blog or promo copy. "I didn't quit the company. They quit me." "I absolutely feel like I'm in limbo." "What I liked about it is the creation." "The investments you make sometimes don't return when you expect." "I think there's more to it. I think the prices are high." "These AI, ATS systems really pull you out real quickly, and I haven't mastered what they're looking for." "I've mainly found jobs networking, and I think the networking is still huge." "You can just really get yourself going if you'll allow it to." KEY TAKEAWAYS Transformation without measured outcomes becomes overhead. When leadership can't see the value, the roles are first to go in a downturn. There's no end state. Transformation is constant improvement or it's nothing. A pivot doesn't have to be a clean escape. Jeff converted unsold builds to rentals to survive the softening, not to win it. The disruption you plan for is rarely the only one. Two markets can turn at the same time and lock up your options. Relationships are the portable skill. The domain changed from tech to construction. Vetting people and building trust carried over. AI has changed the job search more than the job. Networking still beats the applicant tracking system. The trough teaches something you can't learn on the way up: how to manage fear before it manages you. CONNECT WITH JEFF Real estate and development work: giesenhouse.org YouTube: Jeff shares content on real estate and his development journey (search "Jeff Giesen" on YouTube) LinkedIn: Connect with Jeff Giesen on LinkedIn Jeff is open to hearing from anyone with questions on real estate, or from people who think he might be a fit for a technology or transformation role. If you're navigating your own trough, this is a good person to reach out to. ABOUT THE HOST Kumar Dattatreyan is an ICF PCC executive coach, co-founder of Agile Meridian, and creator of The Disruptor Method™. The Meridian Point explores disruption and innovation through conversations with transformation leaders and entrepreneurs living through change. Connect: LinkedIn | agilemeridian.com | disruptormethod.com SUBSCRIBE 🎙️ Spotify | Apple Podcasts | YouTube | LinkedIn 🔔 Weekly episodes on disruption, innovation, and transformation 💬 Leave comments and share where you are in your own disruption #Disruption #CareerPivot #AgileTransformation #Leadership #RealEstateDevelopment #JobSearch #Resilience

The Meridian Point Podcast Episode 175: Bloated Teams, Broken Delivery: The Case for De-Scaling with Nawaz Butt EPISODE SUMMARY Most organizations hired to scale Agile are solving the wrong problem. They add teams, stack committees, multiply hand-offs and approval gates, then wonder why delivery is slower than it was three years ago. Nawaz Butt has spent years inside some of Canada's largest organizations, including Canada Life, and his diagnosis runs counter to almost everything the transformation industry sells: the goal isn't more teams. It's fewer, right-sized, autonomous teams aligned to a purpose they actually own. In this conversation, Nawaz and Kumar Dattatreyan cover what de-scaling actually means in practice, why Conway's Law predicts most of the complexity practitioners are hired to untangle, how psychological safety (not talent) is the real differentiator between high and low performing teams, and why the word "team" gets thrown around to describe groups of people who have never truly pulled for each other. They also get into the future of coaching, the limits of AI in human-centered practice, and what ikigai has to do with leaving a mark on the world. KEY TOPICS COVERED Conway's Law as a Diagnostic Tool Organizations design systems that mirror their communication structures. As companies grow, they add hierarchy, committees and approval gates. The result is a compounding dependency problem that no amount of scaling Agile will fix. De-scaling starts with simplifying decision-making, not multiplying teams. What "Team" Actually Means People throw the word team around to describe groups sharing a Jira board. A real team is small, knows each member's skills and abilities, backs each other up without being asked, and pulls toward the same goal. Most large organizations have groups, not teams. That distinction matters for delivery. The Formula One Model for Alignment Ferrari and Red Bull each have 1,200 to 1,500 people on their Formula One teams. The question isn't how many people, it's whether leadership has done enough work to define the goal so clearly that everyone, from aerodynamics to pit crew, knows their role in winning. Common purpose is the only thing that makes scale work. De-scaling in Practice: Delegation Poker Moving teams from a "telling" stance to an "owning" stance is not a single move. Delegation poker maps the spectrum from directive to fully autonomous. The aim is always to move right, toward autonomy, but most teams start somewhere in the middle. The key is making the conversation about trust explicit. Bring the Work to the Team Too often, people are moved to the work rather than the work coming to the team. Long-lived teams with fixed capacity and clear commitments need ownership over what they build. When that ownership is missing, virtual teams get stood up by borrowing capacity from existing teams, initiatives clash, branches can't merge, and nobody is tracking the true cost of the fragmentation. Psychological Safety as the Prerequisite Google's Project Aristotle identified psychological safety as the single biggest predictor of high-performing teams, above talent, above technical skill, above everything else. Nawaz opens every coaching engagement by asking how much safety exists before asking anything about process. When a Team Doesn't Need a Coach Nawaz walked into an engagement, spent two weeks with a self-organized, nimble team that had been without a manager for over a year and was thriving. He went back to leadership and told them the team didn't need him. His coaching hours are limited. The job is to create conditions for self-sufficiency, not to preserve the coaching role. AI in Coaching: What the Machine Misses Kumar packaged his own coaching knowledge into an AI agent named E. Kumar for a client to use between sessions. Nawaz asked organizations what the AI got wrong and got surface-level answers about abbreviations and misspelled names. His deeper point: AI can't feel the tension in a room, see the rolling eyes, or sense when someone is shutting down. Those are the signals that coaching actually runs on. The Future of Coaching Coaching as a title may fade. The function matters more than the label. The real shift Nawaz wants to see is coaching and mentoring baked into leadership competency models so that every leader develops people as a core part of the job, not as a nice-to-have. MEMORABLE QUOTES "The aim has to be not to have more teams, but to have fewer teams in the organization." "I don't see people as Agile or non-Agile. I meet the team where they are." "This team doesn't need me. I went back to leadership and told them that. My job as a coach is not to preserve my role. It's to create conditions where people become self-organized and self-sufficient." "If somebody says to person one in the morning that you are an a-hole, and to person two in the afternoon, and to person three in the evening, you know who the a-hole is. It's your reflection you see." "AI doesn't have any feeling. It won't feel the tension in the room. It won't see the visual cues. At least not yet." "Do what you like to do. Or at least do more of it if you can't do only that." KEY TAKEAWAYS Conway's Law predicts your delivery problems: your systems mirror your communication structures. Fix the structure before adding more teams. De-scaling means simplifying decision-making, not just cutting headcount. Localized, autonomous decision-making bodies are the goal. The word "team" is overused. Most organizations have groups. Real teams are small, mutually accountable and purpose-driven. Bring the work to the team. Moving people to the work destroys team coherence and creates virtual team debt that nobody is measuring. Psychological safety is not a culture outcome. It's a prerequisite for everything else. A good coach works themselves out of a job. Creating conditions for self-sufficiency is the measure of success, not the length of the engagement. AI augments coaching but can't replace the human capacity to read a room, feel tension or hold space for disagreement. RESOURCES MENTIONED Conway's Law: organizational design principle linking communication structures to system design Project Aristotle (Google): research identifying psychological safety as the top predictor of team performance Delegation Poker: management tool for mapping the spectrum from directive to autonomous decision-making Collaborative Intelligence by J. Richard Hackman: six conditions for effective teams Ikigai: Japanese concept for finding purpose at the intersection of what you love, what you're good at, what the world needs and what you can be paid for XSCALE: de-scaling framework referenced by Kumar Dattatreyan throughout the conversation BetterUp: coaching platform deploying AI agents alongside human coaches CONNECT WITH NAWAZ BUTT LinkedIn: https://www.linkedin.com/in/nawazbutt/ Nawaz runs an Agile and leadership meetup group in Toronto. Connect with him on LinkedIn to follow his thinking on organizational design, de-scaling and people-first coaching. CONNECT WITH KUMAR DATTATREYAN LinkedIn: https://www.linkedin.com/in/coachkdat/ Book a strategy call: https://tidycal.com/coachkumar/30-minute-meeting Learn more about Agile Meridian: https://www.agilemeridian.com Learn more about The Disruptor Method™: https://thedisruptormethod.com/quiz ABOUT THE GUEST Nawaz Butt is an Agile coach and transformation practitioner based in Toronto, Canada. He works inside large organizations helping leadership teams navigate complexity without losing their people in the process. He currently serves as Program Steward at Canada Life, one of Canada's largest insurance providers. He runs a long-standing Agile and leadership meetup group with over 5,000 followers and brings a people-first, framework-agnostic approach to every coaching engagement. ABOUT THE HOST Kumar Dattatreyan is an ICF PCC executive coach and co-founder of Agile Meridian. He is co-creator of The Disruptor Method™, a framework that helps leadership teams disrupt themselves to drive organizational transformation. The Meridian Point explores disruption, innovation and the leadership it takes to navigate both. SUBSCRIBE Spotify | Apple Podcasts | YouTube | LinkedIn New episodes broadcast live every other Tuesday at 12:30 PM Eastern. Leave a review if this episode added value. #DescalingAgile #OrganizationalDesign #AgileCoaching #LeadershipDevelopment #TeamDynamics #ConwaysLaw #BusinessAgility #DeliveryExcellence #ExecutiveCoaching #TheMeridianPoint #Disruption #Innovation #FutureOfWork #PsychologicalSafety #AgileTransformation