Prompt and Circumstance cover art

Prompt and Circumstance

Prompt and Circumstance

By: Mike Richardson Mark Redgrave Ryan Neimann & Tom Adams
Listen for free

It’s human-friendly banter about code, culture, and CEO reality checks—served up by Mike Richardson, Ryan Niemann, Mark Redgrave, and Tom Adams. No jargon. No hype. Just real talk from four guys who’ve seen it all, and aren’t afraid to say what everyone’s thinking.Flourish Press Inc. Economics Management Management & Leadership
Episodes
  • From Pilots to Product: Making AI a Strategic Advantage

    From Pilots to Product: Making AI a Strategic Advantage
    Jun 28 2026
    Most leaders still feel AI is a technical maze they don’t understand—and that keeps them stuck in pilot purgatory: scattered experiments, nothing in production, and no real business value. This episode tackles that head‑on and reframes AI as a people, data, and strategy problem long before it’s a tech problem.You’ll hear how mid‑market CEOs visibly relax when they realize they don’t need to “get the tech” to lead effectively in AI; they need to orchestrate change, align projects to strategy, and mobilize their people around real business outcomes. The conversation unpacks why data—structured and unstructured—is now the primary constraint, and why your biggest challenge is often just finding, cleaning, and connecting what you already have in CRMs, ERPs, email, call transcripts, and document stores.Tom shares an emerging approach he’s building around “conversational intelligence”: multi‑agent AI systems that simulate advisory boards and multi‑voice conversations, complete with auditors and supervisors to make reasoning auditable and enterprise‑ready. This leads into a broader discussion about internal advisory boards, IP, and how individuals might someday curate their own AI “councils” based on the thinkers and operators who’ve influenced them.You’ll also hear concrete examples from local AI summits and peer forums: how leaders are using AI to avoid linear headcount growth, where smaller firms are finding affordable “AI accelerants,” and why Microsoft‑centric companies may have a structural edge because their data is already inside one secure ecosystem. The episode closes with very practical next steps: how to inventory your data, who to involve, how to test offerings with real customers, and why you must be willing to hear “you’re not ready” if you want to move fast and build something that matters.HighlightsReframe AI as a change‑leadership and data challenge, not a technical mystery only engineers can solve.Escape AI pilot purgatory by tying every experiment directly to strategic business outcomes and value creation.Treat data (structured and unstructured) as your main AI bottleneck; inventory and centralize before you scale.Use AI to avoid linear headcount growth as you scale, not as a blunt instrument for layoffs.Explore conversational intelligence: multi‑agent AI “advisory boards” that debate, audit, and document decisions.Leverage existing ecosystems like Microsoft 365 to unlock emails, documents, and transcripts securely with AI.Expect emotional resistance; leaders must tolerate “you’re not ready” feedback to refine real-world propositions.Build human peer forums as an antidote to AI‑driven isolation for CEOs who suddenly “don’t know the top.” Important Concepts and FrameworksPilot Purgatory - Multiple unconnected AI pilots that never reach production or meaningful business impact.“No Data, No AI” Principle - The idea that usable, connected data—more than algorithms—is the real constraint.Structured vs. Unstructured Data Structured: rows/columns in CRMs, ERPs, financial systems. Unstructured: documents, emails, call/meeting transcripts, notes, shared drives.Conversational Intelligence - Multi‑agent AI systems that simulate real multi‑voice conversations, with agents that consult each other and an auditor to enforce constraints and maintain an auditable chain of thought.Headcount Non‑Linearity - Using AI to grow revenue 2–3x without equivalent growth in support, sales, and operations headcount.Data Lakes and Plumbing - The architectural need to connect disparate data sources (data lakes, warehouses, APIs) as the foundation of any serious AI effort.AI Peer and Advisory Models - Using AI to mirror advisory boards or peer groups where multiple “voices” debate, refine, and contextualize advice.Embedded Ecosystem Advantage (Microsoft 365 + Copilot) - Organizations with email, documents, and collaboration already inside one secure ecosystem can unlock cross‑system insights faster with embedded AI tools like Microsoft Copilot — if properly governed. Strategic Alignment of AI Portfolios - Ensuring dozens of in‑flight AI projects map directly to macro business objectives, not just “interesting” use cases.Tools & Resources MentionedCadre AI — AI company providing applied AI solutions; referenced via insights from a lead practitioner (Riley Strickland). Strategic Coach — Entrepreneurial coaching program (Dan Sullivan) that shapes how leaders think about growth and leverage. Alex Hormozi / Acquisition.com — Example of a modern content‑driven business/marketing playbook and associated IP questions in the AI era. Microsoft Copilot — Embedded AI assistant across Microsoft 365, with deep access to emails, documents, and collaboration data. Airtable — Flexible database/spreadsheet used by some firms to replicate and free up structured data locked in legacy systems. Google ...
    Show More Show Less
    47 mins
  • Why AI Value Depends on People, Strategy, and Escaping the Activity Trap

    Why AI Value Depends on People, Strategy, and Escaping the Activity Trap
    Jun 15 2026
    Most organizations are pouring hundreds of thousands of dollars into AI experimentation with little to show for it. They are trapped in what advisor Mark Redgrave calls the "AI activity trap"—lots of movement, no strategic impact. The problem isn't the technology; the tools will reach parity quickly. The real bottleneck is getting people to adopt, adapt, and change. Without a clear CEO mandate that ties AI directly to business strategy, initiatives remain stuck at the director level where budgets get cut and momentum fizzles.This conversation dismantles the common belief that AI adoption is a technical challenge. Instead, it reframes success around two pivotal concepts: strategy-first AI alignment and cross-functional team design. Leaders learn why functional silos kill innovation—70% of project time is wasted in handoffs between departments—and how small cross-functional "skunkworks" teams can deliver results in weeks instead of months. The episode offers a practical path forward for mid-market CEOs who need to stop frenetic experimentation and start connecting AI investment to the metrics that actually matter.HighlightsTie every AI initiative directly to your company's core strategic priorities.Understand employee "why" before introducing AI-driven change.Stop experimenting without strategic alignment to escape the activity trap.Move AI from director-level pilots to an explicit CEO mandate.Break functional silos with cross-functional teams for faster execution.Recognize that 70% of project time is lost in departmental handoffs.Start with small cross-functional teams instead of restructuring the entire company.Treat AI value creation as a people and change management challenge.Important Concepts and FrameworksAI Activity Trap — The frenzy of experimentation without measurable strategic outcomes. Leaders mistake motion for progress, leading to "pilot purgatory."CEO Mandate for AI — The explicit declaration from the C-suite about what AI is and is not for the business, creating organizational alignment and investment clarity.Theory of Constraints — A management framework for identifying the bottleneck in any process. Applied here to show how departmental handoffs consume 70% of elapsed project time.Cross-Functional Team Design / Skunkworks — Organizing people from different functions around a single mission to eliminate handoff delays and accelerate delivery.Ready, Fire, Aim — A business metaphor describing the common mistake of rushing to action without strategic clarity. The antidote: "ready, aim, fire."Simon Sinek "Start with Why" — Referenced and contrasted as a different kind of "why" than the organizational change motivation discussed in this episode.Tools & Resources MentionedClaude / Anthropic (Claude Code, Opus 4.8)** — AI coding and reasoning model; noted for verbosity and shifting personality across versions.ChatGPT / OpenAI Codex — AI coding model; noted for concise, action-oriented responses in terminal.Google Gemini — AI assistant; described as sitting between Claude and Codex in communication style.McKinsey & Company — Global consulting firm where Mark serves as a senior advisor on large-scale transformation.Shift — Mark Redgrave's mid-market consulting practice focused on strategy, innovation, and AI adoption. | https://www.shift-transform.comCalls to ActionSchedule a leadership team conversation focused on one question: How do our current AI initiatives support our business strategy?Identify the key metrics the CEO actually cares about and audit whether your AI projects connect to those metrics.Choose one high-priority strategic pillar and launch an 8-week cross-functional team to prove AI value, rather than funding multiple scattered pilots.Stop any AI experimentation that cannot be clearly tied to a strategic outcome—redirect that budget toward aligned initiatives.Create explicit CEO-level accountability for AI workstreams, with owners and milestones tied to business results.Key Quotes"AI is a people problem, not a technology problem." — Mark Redgrave"If something is important, make it important." — Mark Redgrave"70% of the elapsed time of any project is in someone's inbox." — Mark Redgrave"We're ready, fire, aiming right now. Stop pulling triggers." — Mark Redgrave"The tools will reach parity quickly. The difference is how you leverage them." — Mark RedgraveChapters00:28 — Why AI Model Personalities Impact Your Daily Work 01:20 — The Frenzy of New AI Releases and IPO Mania 07:01 — AI Is a People Problem, Not a Technology Problem 11:26 — Earning Employee Buy-In Through the Strategic "Why" 14:23 — The AI Activity Trap: Motion Without Results 16:19 — Performance vs. Activity: Strategy Must Lead AI 22:28 — Making AI a CEO Mandate, Not a Director Experiment 30:53 — Operating Model as the Hidden Bottleneck to AI Value 39:10 — Cross-Functional Teams That Deliver in Weeks, Not Months 46:43 — Final Advice: Ready, ...
    Show More Show Less
    49 mins
  • Why Your Team Is Resisting AI (And How to Lead Through It)

    Why Your Team Is Resisting AI (And How to Lead Through It)
    Jun 1 2026
    Is your workforce pushing back against AI, even as you're told you must embrace it or fall behind? You're not alone—and the resistance isn't a problem to solve; it's data to act on.In this episode, the hosts confront the growing tension between AI acceleration and the people who are supposed to adopt it. Students booing AI references at graduation ceremonies. Workers quietly undermining AI rollouts. Communities fighting data center development. And leaders caught between "AI is inevitable" and "we're waiting to see how this plays out."The core argument: this is not a technology challenge—it's a people challenge. All major AI tools are approaching parity. The differentiating factor isn't which model you pick. It's whether your people trust you enough to come along on the journey.Mark introduces the trust triangle—capability, consistency, and selflessness—and asks a hard question: in an era where stock prices rise on layoff announcements, can you credibly claim selflessness? Mike connects the resistance to something deeper: employees and new graduates feel hopeless, and nobody is giving them a compelling vision of a future they can build toward.The conversation surfaces the IKEA call center case study, where AI removed mundane work but inadvertently left employees handling only high-difficulty calls—creating unsustainable cognitive load. The takeaway: removing the easy work doesn't automatically make the hard work easier.The hosts offer a practical framework for leaders: be truthful, create agency (which is the antidote to fear), and ensure shared benefit. And on Monday morning? Start by listening—not by telling. Find three ways to engage your team about their AI fears and actually hear what they say.HighlightsResistance to AI isn't an obstacle—it's feedback. Start listening instead of dismissing.AI tools are reaching "awesomeness parity" quickly; the winner will be the organization that builds trust, not the one that picks the best model.Removing mundane work with AI can backfire if employees are left with only cognitively demanding tasks.Agency is the antidote to fear—let your people build, don't do it to them.The only sustainable competitive advantage left is culture, and it must now be an AI-powered culture.Leaders must go on their own learning journey before they can expect their teams to adopt AI.Super-triage is the most critical leadership skill in an era of exponential change.Important Concepts and FrameworksTrust Triangle (Capability, Consistency, Selflessness) — A leadership framework for rebuilding trust during AI transitions. Capability asks "Can you do this?" Consistency asks "Do you do what you say?" Selflessness asks "Are you doing this for the team or for yourself?"Hype Cycle / Trough of Disillusionment — Gartner's model describing how technologies go from peak inflated expectations to a trough before productive adoption. The hosts argue AI is entering the trough of disillusionment as organizations realize the frenzy created overhead, not value.Dunning-Kruger Effect — The cognitive bias where people overestimate their competence early in a learning curve. Referenced as "Mount Stupid"—the peak many organizations reached before realizing they were "busy fools."Flow (in Agile / Lean) — A state of balanced delivery: not too much/too fast/too scattered, and not too little/too slow/too narrow. The antidote to both disorganized chaos and analysis paralysis.Leader-Led Transformation — The principle that AI transformation cannot be delegated. Leaders must be on the learning journey themselves, not just directing from a distance.IKEA Call Center Case Study — When IKEA deployed AI to handle routine call center work, employees were redeployed to handle only complex problems. The unintended consequence was unsustainable cognitive load from 100% hard problems.Kanban Method — A workflow management method for defining, managing, and improving services that deliver knowledge work."In Search of Excellence" by Tom Peters — Classic business book referenced for the quote "Leaders are dealers in hope."Tools & Resources MentionedClaude (by Anthropic) — AI assistant that one host describes as having a "semi love affair" with, noting it's replaced ChatGPT as their primary toolChatGPT (by OpenAI) — AI assistant referenced as the initial tool that brought AI into mainstream awareness for most peopleMicrosoft Copilot — Microsoft's AI assistant, referenced in the context of Satya Nadella restricting Claude usage to refocus on Copilot due to cost overrunsClaude CoWork (by Anthropic) — A feature/usage pattern for collaborative AI work that one host introduced to their groups, noting a measurable shift in AI adoption across the bell curveCalls to ActionOn Monday morning, start a listening campaign. Find three ways to engage your team about their views on AI and their fears—and just listen. Do not pitch, defend, or reassure. Just listen.Go on your own learning journey. Before ...
    Show More Show Less
    48 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet