Episodios

  • Reporting vs Owning

    Reporting vs Owning
    Mar 10 2026
    Reporting vs Owning (Weather Reports vs Action Plans)Hosts: Ed Schaefer and Andy SiegmundEpisode: 17 (Season 2, Episode 3)Runtime: Approximately 55 minutesRelease Date: March 10, 2026Website: leadershipexploredpod.comEpisode DescriptionIn this episode of Leadership Explored, Ed Schaefer and Andy Siegmund unpack a leadership tension most teams feel every week: when is it enough to “report the weather,” and when are you expected to own the outcome?They break down why “Don’t bring me problems, bring me solutions” can backfire, how psychological safety and decision rights shape what people share, and how to move from passive updates to high-value leadership communication—without overstepping your authority.Ed and Andy introduce a practical spectrum (Reporting → Recommending → Owning), share language shifts that make escalation safer, and offer a simple structure for upgrades to your status updates: What / So What / Now What—plus how to consistently coach teams into stronger ownership over time.What Ed & Andy Discuss* Why “weather reports” frustrate leaders (and how to fix them without shaming people)* The difference between owning the decision vs owning the recommendation* When “above my pay grade” is valid—and how to still add value* How fear, past reprimands, and unclear boundaries push people into “safe” reporting* The “recommendation bridge”: observation → implication → options → recommendation → ask* “Strong convictions, loosely held” as the best operating stance for growing leaders* How to coach ownership by being boringly consistent with your questions* Intention-based leadership (“I intend to…”) and why it changes team dynamicsEpisode Highlights⏳ [00:00] – The tension: problems vs solutions, reporting vs owning⏳ [01:02] – Andy’s “weather report” metaphor + the missing “So what / What now?”⏳ [03:34] – Ed’s spectrum: reporting → recommending → owning the outcome⏳ [09:54] – Why “don’t bring me problems” is a trap + “strong convictions, loosely held”⏳ [17:53] – Why smart people still default to weather-reporting (fear, safety, skills gaps)⏳ [23:00] – “Above my pay grade” is real—here’s how to escalate with value anyway⏳ [26:55] – The middle-ground challenge: too early, too much info, or the “wrong” initiative⏳ [34:30] – Intent-based leadership (“I intend to…”) as the ultimate ownership upgrade⏳ [40:06] – The replaceability problem: sensors are easy to find; owners are not⏳ [44:27] – Coaching move: be predictably consistent with the questions you ask⏳ [47:52] – Ed’s 3 tools: What/So What/Now What, recommendation language, clear boundaries⏳ [54:09] – Your challenge this week: how you communicate up and how safe it is to communicate downKey Quotes* “A bad weather report is observation without implication.”* “There’s a spectrum: reporting, recommending, and owning the outcome.”* “Strong convictions, loosely held—bring a point of view, but don’t pretend you know everything.”* “Recommendations give you an off-ramp. Plans imply ‘come hell or high water.’”* “As a leader, if you want people to stop reporting the weather, you have to make it safe to forecast.”* “Be boringly consistent—your team will learn what you’re looking for.”Practical Takeaways (Listener-Ready)1) Upgrade your update with: What / So What / Now What* What: What happened?* So what: Why does it matter? What’s the impact/risk?* Now what: What’s next? What do you recommend? What help do you need?2) Use “recommendations” to reduce fear and increase initiativeAsking for a recommendation invites thinking without forcing people to pretend they have full authority or complete context.3) Make boundaries explicitIf leaders want ownership, they need to define the sandbox:* “You own schedule decisions; I own budget decisions.”* “You can execute within these constraints without checking with me.”4) Coach ownership through predictable questionsWhen leaders ask the same 3–4 questions every time (“So what?” “What now?” “What do you need?”), people adapt fast—and it becomes a habit.Potentially Controversial / Spicy Moments* Calling “Don’t bring me problems, bring me solutions” a BS line (because it can suppress early warnings).* “If you’re afraid to share ideas because you’ll get steamrolled, go find somewhere else to work.”* The implied leadership critique: if teams only report, the environment may be training them to stay “safe,” not useful.Resources Mentioned* Intent-Based Leadership (“I intend to…”) — L. David Marquet* Delegation Poker — Management 3.0* Psychological Safety This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    55 m
  • Projects Always Start Red

    Projects Always Start Red
    Feb 24 2026
    Projects Always Start RedHosts: Ed Schaefer & Andy SiegmundEpisode: 16 (Season 2, Episode 2)Runtime: Approximately 52 minutesRelease Date: February 24, 2026Website: leadershipexploredpod.comEpisode DescriptionYou kick off a new project, nothing has slipped yet, and the first status report goes out… green. But should it? In this episode, Ed and Andy challenge a default that quietly fuels late-stage surprises: treating “not behind yet” as “on track.” They argue that projects don’t start green—they start uncertain, and uncertainty is risk.Ed introduces the idea that projects should “earn their way to green” by reducing unknowns over time, not by waiting until something breaks. Andy pushes on practicality: different project types, organizational culture, and the reality that RAG status is often an escalation trigger—not a learning tool. Together, they land on a more usable approach for real organizations: add trend and confidence signals (and separate “uncertainty” from “needs escalation”) so leaders can see what’s coming before it’s too late.What Ed & Andy discuss* Why “green at kickoff” often means optimism, not true status* The difference between measuring “have we failed yet?” vs. “how confident are we?”* How the cone of uncertainty shows up in real delivery work* Why dependency-heavy work creates an illusion of control* Andy’s “panic meter” analogy (and why it’s a surprisingly practical model)* How to make this usable without starting a culture war in your PMO* The role of psychological safety in honest, early reportingEpisode Highlights (Timestamps)* ⏳ [00:00] The kickoff status report problem: “green” as default* ⏳ [02:00] The core thesis: early projects are high-uncertainty—so why call them green?* ⏳ [05:12] Andy’s pushback: repeatable work vs. true uncertainty* ⏳ [08:23] Ed’s workaround: an “initialization phase” that’s off-RAG* ⏳ [20:25] The big question: if you start red, what’s the escalation mechanism?* ⏳ [28:27] The “panic meter” framing (and why it clicks)* ⏳ [35:11] Dependency math + complexity: why confidence collapses fast* ⏳ [44:03] The practical move: trends, confidence, and unknowns in reporting* ⏳ [51:40] Three tactical actions you can use tomorrowKey Takeaways* Status isn’t just color—it’s signal. Without trend and confidence, green can hide real risk.* Early honesty prevents late drama. If leadership only finds out at “red,” the system trained people to delay truth.* Separate uncertainty from escalation. Not every unknown requires executive intervention—but pretending unknowns don’t exist creates surprises.* Trend beats snapshot. “Amber trending green” is often healthier than “Green trending down.”* Culture is the real constraint. You don’t “implement” better reporting; you co-create it to fit how your organization reacts to bad news.“Your Move This Week” (Listener Challenge)Pick a project that’s early-stage and ask: Is our status green because we’re confident… or because we’re hopeful?Then try one of these:* Add a confidence score (1–5) next to status* Add a trend arrow (improving / flat / worsening)* List the top unknowns explicitly—and what it will take to turn them into knownsKey Quotes* “When we mark it green on week one, we’re not reporting status—we’re reporting optimism.”* “I don’t think it benefits us to manage decline.”* “When the vets start getting stressed out, treat that like a signal.”* “Real leadership isn’t pretending you know the future. It’s reducing what you don’t know—on purpose.”Potentially Spicy / Debate-Worthy Moments* Calling projects “red” at the start sounds like pessimism—Ed argues it’s just math and realism.* The idea that traditional RAG reporting is structurally designed to hide uncertainty until it becomes undeniable.* The critique that many dependency-heavy plans are basically “hope with slideware,” even when everyone reports green.Contact / FeedbackHave a story or a perspective you want to share? Connect with us on LinkedIn or email leadershipexplored@gmail.com This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    55 m
  • Watermelon Projects

    Watermelon Projects
    Feb 10 2026

    Watermelon Projects: Green on the Outside, Red on the Inside

    Hosts: Ed Schaefer and Andy Siegmund

    Episode: 15 (Season 2, Episode 1)

    Runtime: ~54 minutes

    Release Date: February 10, 2026

    Website: leadershipexploredpod.com

    Episode Description

    A watermelon project is green on the outside and red on the inside—everything looks “fine” on dashboards, but the people doing the work know the risks are stacking up. Ed and Andy explore why this happens across organizations of all sizes, why “more reporting” often makes the problem worse, and what actually works: psychological safety, incentives aligned to transparency, and leadership behavior that makes escalation feel like support—not punishment.

    They also dig into nuance: when does a risk warrant flipping to amber/red, and when does escalation become “crying wolf”? You’ll hear practical methods like pre-mortems, blameless postmortems, and “highlight + lowlight” reporting that forces reality into the open—without turning red status into a career-limiting move.

    Episode Highlights (with timestamps)

    ⏳ [00:00] – What a “watermelon project” is—and why it’s rarely a surprise to the team doing the work.⏳ [05:04] – A key smell: the absence of yellow (green → red whiplash).⏳ [05:41] – Andy’s caveat: shifting to amber/red should mean there’s something actionable you can do.⏳ [09:26] – ROAM risks (Resolve/Own/Accept/Mitigate) and why “accepted” risks shouldn’t become performative escalations.⏳ [10:32] – Ed’s real-world example: a major data risk called out early… and ignored anyway.⏳ [15:17] – Why this is everywhere (not just big companies)—but often worse in insecure, low-trust environments.⏳ [20:18] – The psychology and incentives: optimism, fear, and “we always pull out of the nosedive.”⏳ [24:42] – The “nobody wants to tell the boss” chain (plus the Toyota andon cord as the culture counter-example).⏳ [29:28] – Why escalation becomes punishment: meetings, extra reporting, and leaders “gumming up” the work.⏳ [31:12] – The hero trap: working nights/weekends to keep it green… until burnout + surprise red.⏳ [33:19] – Reporting to the plan vs. reporting reality—and why outcome-focus beats “build the widget.”⏳ [37:01] – The bureaucracy trap: “thicker rind” doesn’t fix a red interior; culture does.⏳ [39:47] – Blameless postmortems: system failure vs. people blame.⏳ [44:46] – What leaders should do when it turns red: calm, useful, and action-oriented.⏳ [46:03] – Concrete takeaways: questions to ask, pre-mortems, and rewarding early warning signals.⏳ [47:38] – A practical reporting mechanism: require highlights + lowlights—and block “weakness as a strength” spin.⏳ [53:20] – The challenge: are your projects green because they’re truly on track—or because they have to be?

    Key Takeaways for Leaders

    * Green status is not proof—it’s a signal. If you’ve been burned before, don’t accept green casually—ask one smart question that reveals reality.

    * Escalation must reduce pain, not add overhead. If “red” triggers 13 meetings and more forms, you’ve trained people to hide risk.

    * Reframe red as a request for support (not a verdict of failure). In healthy systems, raising the flag early is a competence move.

    * Stop “reporting to the plan.” Plans are hypotheses. Reality is the data. Strong leaders update plans—not narratives.

    * Culture beats bureaucracy. More process often just thickens the rind while the project stays red underneath.



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    54 m
  • Welcome to Season 2 of Leadership Explored

    Welcome to Season 2 of Leadership Explored
    Feb 10 2026

    Welcome to Season 2 of Leadership Explored — We’re Back

    Hosts: Ed Schaefer and Andy Siegmund

    Episode: Season 2, Episode 0

    Runtime: Approximately 29 minutes

    Release Date: February 10, 2026

    Website: leadershipexploredpod.com

    Episode Description

    Leadership Explored is back for Season 2. After a strategic (and necessary) pause, Ed and Andy return to talk candidly about why they stepped away, what they’re seeing in the workplace right now, and what this next chapter will focus on.

    They unpack the current “wait-and-see” mood across corporate America—driven by volatility, AI hype vs. reality, layoffs, and eroding trust—and make the case for a different kind of leadership content: not polished “highlight reels,” but a practical sanity check for leaders navigating the messy middle.

    You’ll also hear the Season 2 direction: deeper conversations about real-world leadership friction—where best practices break down, politics complicate decisions, and leaders have to adapt without losing their values.

    In This Episode, Ed & Andy Discuss

    * Why taking a break can be a leadership decision, not a failure

    * The “messy middle”: where theory meets real life (and things get complicated fast)

    * Why so many leaders and teams feel stuck in cautious paralysis

    * How layoffs + “record profits” messaging erode trust

    * Why vulnerability and real communication matter more than polished corporate speak

    * A leadership “audit” you can run this month: stop doing what’s performative and draining

    * A simple journaling technique to let your brain solve problems overnight

    Episode Highlights (Timestamps)

    ⏳ [00:00] — Season 2 kickoff: why the pause was strategic and necessary⏳ [02:25] — Season 1 was “exploring the landscape”; Season 2 goes into the messy middle⏳ [03:35] — Plans are useless, planning is useful: where theory bends in the real world⏳ [06:43] — The current mood: cautious, volatile, wait-and-see⏳ [08:29] — Why uncertainty creates decision paralysis (and what it does to teams)⏳ [10:27] — The widening range of “acceptable” leadership behavior and styles⏳ [11:22] — Trust erosion: record profits… then layoffs… and the cultural fallout⏳ [13:26] — The podcast as a “sanity check” for leaders who feel like something’s off⏳ [17:23] — The podcast as a mirror: using episodes to audit your own leadership habits⏳ [19:29] — Season 2 preview: projects, teaching, stoicism (not “broicism”), reading, and more⏳ [21:35] — “Define your season”: push season vs. recovery season vs. survival season⏳ [24:00] — Permission to stop: run a calendar/meeting audit and reclaim energy⏳ [27:16] — Overnight journaling technique for solving problems you’re stuck on

    Your Move This Week (Listener Challenge)

    Look at your leadership rhythm: Are you grinding on autopilot—or is it time to declare a new season?

    * What needs to change (meetings, cadence, priorities, expectations)?

    * What needs to stop because it’s performative, draining, or just “we’ve always done it”?

    Connect With Us

    * Email: leadershipexploredmail.com

    * Website: leadershipexploredpod.com

    * New episodes every other Tuesday



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    29 m
  • Leadership Explored Season 2 - Trailer 2

    Leadership Explored Season 2 - Trailer 2
    Feb 9 2026

    Leadership right now has a vibe—and it’s uncertainty.

    A lot of leaders are waiting for the ground to settle. But it hasn’t. Priorities keep shifting, expectations keep changing, and the friction keeps piling up.

    That’s why we’re back with Season 2 of Leadership Explored.

    This season, Ed Schaefer and Andy Siegmund are diving deeper into the friction that gets in the way of doing good work—bad habits, confusing communication, misalignment, and burnout. Not with perfect answers, but with better questions—and practical insights you can actually use.

    🎙️ New episodes start February 10, 2026. Subscribe now so you don’t miss the Season 2 premiere.



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    1 m
  • Leadership Explored Season 2 - Trailer 1

    Leadership Explored Season 2 - Trailer 1
    Feb 8 2026

    Leadership has a public version—and a private reality.

    It’s the status report that says everything is “green,” while the team is quietly carrying risk. It’s the confident strategy leaders present on stage, followed by the uncertainty they feel when they sit back down.

    That’s the gap we’re stepping into in Season 2 of Leadership Explored.

    This season, hosts Ed Schaefer and Andy Siegmund are spending less time on textbook definitions of leadership and more time in the messy middle—where projects go sideways, communication breaks down, and leaders are expected to deliver results without burning themselves (or their teams) out.

    If you’re looking for a leadership conversation that feels like the ones that happen after the meeting ends—when the real story finally gets told—join us.

    🎙 Season 2 premieres February 10, 2026.



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    1 m
  • Leadership Explored Season 2 - Teaser

    Leadership Explored Season 2 - Teaser
    Feb 7 2026

    We took a break to practice sustainable leadership—and now we’re back to talk about what it really takes to lead right now.

    Leadership didn’t get any quieter while we were away.

    🎙️ Season 2 starts February 10, 2026—follow Leadership Explored so you don’t miss the premiere.



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    1 m
  • Season 1 Year-To-Date Leadership Reflection (2025)

    Season 1 Year-To-Date Leadership Reflection (2025)
    Dec 30 2025
    Hosts: Ed Schaefer & Andy SiegmundEpisode: Season 1 SpecialRuntime: ~75 minutesRelease Date: December 30, 2025Website: leadershipexploredpod.comEpisode DescriptionIn this Season 1 special, Ed and Andy do a “Leadership Year-to-Date” reflection—checking which beliefs got stronger, which shifted, and which messy lessons changed how they lead. From learning rate and team stability to slack time, strategy, communication, AI discernment, boundaries, and burnout, this episode is a practical end-of-year reset for leaders who want to stay honest and adaptive.Episode SummaryOver a year, your team changes, your workload changes, and the world changes—so your leadership beliefs should probably change too. In this episode, Ed and Andy walk through a simple reflection framework: what strengthened, what shifted, and what surprised you enough to change your behavior.They dig into why rate of learning is still the best career insurance, why stable teams beat constant re-teaming, and why slack time isn’t a luxury—it’s a prerequisite for good judgment. They wrestle with the gap between “strategy” as a slogan vs. strategy that actually names the crux problem and drives coherent action. They call out the hidden tax of vague, context-free communication (“hey, got a sec?”), and they get very real about taste and discernment in an AI world—where speed is cheap, but judgment is everything.The back half turns into the “messy lessons” section: discovery is almost always bigger than promised, sales optimism often outpaces delivery readiness, and burnout + context switching can narrow your world and quietly reduce effectiveness. They close with a challenge: don’t treat reflection like a scorecard—treat it like a way to learn fast enough to lead better next quarter.Episode Highlights⏳ [00:00] – Why do a Leadership Year-to-Date reflection (and how to use the three-question framework)⏳ [04:00] – Andy: Rate of learning matters more than almost anything⏳ [08:39] – Ed: Long-lived teams beat constant re-teaming (trust, flow, psychological safety)⏳ [13:26] – Slack time isn’t a luxury—no slack leads to “infinite wait time”⏳ [18:52] – Strategy beats reactivity: if you can’t name the problem, you can’t pick the next move⏳ [22:16] – Andy’s pushback: is it a capacity problem…or a skill/enablement gap?⏳ [28:06] – Professional communication as a force multiplier (context, clarity, urgency)⏳ [34:12] – “Good taste” matters more in an AI world (judgment > first draft speed)⏳ [40:07] – Self-respect and boundaries: sustainable pace, burnout prevention, stop working for free⏳ [46:49] – Andy: the “grass is greener” myth—every org has constraints that rhyme⏳ [49:20] – Ed’s reframe: growth isn’t just motivation—often it’s capacity, space, and energy⏳ [53:37] – “Confidence as a service”: draft first, iterate fast, don’t wait for perfect inputs⏳ [1:01:25] – Messy lessons: discovery is bigger than promised (even when everyone swears it’s defined)⏳ [1:07:11] – Sales optimism vs. delivery readiness (and why readiness checks matter)⏳ [1:09:04] – Burnout + context switching: how it narrows perspective and quietly degrades effectiveness⏳ [1:15:23] – Season 1 wrap + what’s next (Season 2 returns in early 2026)Key Takeaways* Learning rate beats raw talent. The advantage isn’t “never making mistakes”—it’s repeating fewer mistakes.* Team stability is a performance multiplier. Re-teaming is a skill, but stability reduces friction and accelerates trust.* Slack time protects leadership quality. Without space, judgment degrades, decision debt grows, and plans get brittle.* Strategy isn’t a slogan. If you can’t name the crux problem, you’re probably just staying busy.* Clarity is kindness in professional communication. Context + ask + timeframe prevents wasted cycles and anxiety.* AI doesn’t replace thinking—bad users are trying to bypass thinking. Draft speed is cheap; discernment is scarce.* Burnout is a leadership risk, not a personal weakness. Context switching and overload compound until effectiveness drops.“Your Move This Week” — Listener Reflection ExerciseGrab a note app or paper and answer these three prompts:* One belief that changed this year: What did reality force you to update?* One belief that got stronger: What did experience confirm?* One adjustment you’ll make next quarter: What will you do differently—calendar, communication, boundaries, or decision-making?If you want to go one layer deeper:* What did you stop doing because you ran out of space/energy?* What’s one “slack time” move you can protect weekly (even 30 minutes)?Concepts & Resources Mentioned* Slack time & utilization: The Phoenix Project (the “utilization → wait time” idea)* Strategy & “the crux”: Richard Rumelt (Good Strategy/Bad Strategy, The Crux)* Leading with intent, not orders: David Marquet (Turn the ...
    Más Menos
    1 h y 17 m