124: Drowning in Tasks: How Successful PMs Organize the Chaos

If your to-do list is 47 items long, your Slack won't shut up, and you ended the day thinking, "Cool… but what did I actually accomplish?"—welcome. You're among friends. In this episode, Kim and Kate take on the very real, very unsexy side of project management: figuring out how to manage your own work when everything (and everyone) is demanding your attention. This isn't about finding the perfect tool or building a prettier dashboard. It's about surviving—and actually functioning—in an interrupt-driven world where emails breed overnight, notifications multiply, and every task somehow feels urgent. They get into what actually works: setting a North Star for your week (yes, only a few priorities), getting tasks out of your brain before they haunt you at 10 PM, and why some tasks are secretly just traps that create even more work (looking at you, boomerang tasks). Also: a gentle reality check—you're not supposed to do everything. Grab a drink, ignore your inbox for a bit, and let's figure out how to organize the chaos without losing your mind.   🎙️ Spicy Quotes from the Episode On chaos: "If you have no North Star point, the rest of your week is going to feel like chaos." — Kate On overwhelm: "The human brain can't really process all of that. We can process having three priorities." — Kate On modern work life: "Notifications trying to notify you about notifications." — Kim On control: "Manage your tasks—don't let your tasks manage you." — Kim On reality: "There has to be things you can stop doing." — Kate 📌 Key Concepts & Takeaways The North Star Rule (a.k.a. calm down, it's not 47 priorities): Pick 2–3 things that actually matter this week. Everything else? It either supports those—or it waits. Get It Out of Your Head (your brain is not a storage system): If you're trying to remember everything, you've already lost. Write it down somewhere reliable so your brain can stop yelling at you. Boomerang Tasks (aka "this will take 5 minutes" lies): Some tasks look small but come with hidden side quests. Know the difference before you commit. Interrupt-Driven Work Is the Default—Act Accordingly: You're not bad at focusing. Your environment is designed to destroy it. Filter, batch, and control when you engage. Physical Lists Still Work (and no, it's not just nostalgia): Sometimes the best productivity hack is using something that doesn't ping, buzz, or open 12 tabs. Reflection Beats Hustling Harder: End your day or week by asking: what actually mattered? Not what felt urgent—what mattered. Not Doing Things Is a Skill: You don't need a better system. You probably need fewer things on your list.   🔗 Links & Resources Mentioned PM Happy Hour Website: https://www.pmhappyhour.com Scripts & Resources: https://www.pmhappyhour.com/scripts Books Mentioned: Essentialism by Greg McKeown Getting Things Done by David Allen Conquer the Chaos by Clate Mask Tools Referenced: Notion, Evernote, OneNote, Smartsheet, Jira, Monday  

If your weekly calendar looks like the loser in a state fair quilt competition - just solid blocks of mismatched colors with no room to breathe - this episode is for you. Today, we're joined by facilitation expert Evan Unger to talk about a topic that Kate and Kim geek out over: meetings. Specifically, why most of them are terrible, how they drain organizational productivity, and exactly what you can do to fix yours. We also tackle one of the most delicate situations in project management: how to handle the HIPPO (Highest Paid Person's Opinion) when they barge into your meeting and try to completely take over the flight controls. Grab a drink, settle in, and let's get into it. 🎙️ Spicy Quotes from the Episode On owning your time: "If you don't own your calendar, you don't own your life." – Kim On the true cost of bad meetings: "If you're spending 50% of your time in meetings [that are less than 50% effective], you're literally going to spend a year's worth of your life and hours in meetings in under a decade. How organizations tolerate this, I have no idea." – Evan On visibility: "Every meeting is a leadership moment." – Evan On career survival: "We don't want to make hippos wrong because there's career limiting interventions. I mean, let's be honest, they have power and authority over us." – Evan On meeting math: "Nine things on an agenda in a 40-minute meeting is 4.44 minutes per agenda item. That's just not possible. It is better to end early than to run over." – Kate 📌 Key Concepts & Takeaways The Meeting Metaphor (Flying the Plane): Every meeting needs three phases. Takeoff (getting aligned), the Flight (the process/agenda), and Landing (saving 5-10 minutes at the end to secure next steps and accountability). Do not run out of fuel and crash. Leave time to land the plane. The POPRA Model for Meeting Prep: Don't accept or run meetings without knowing these five things: Purpose: Why are we here? Objectives: What are the specific deliverables or decisions needed? Process: What is the agenda? Roles: Who is the ultimate decision-maker? Who is the SME? Agreements: How will we interact and handle disagreements? The AREA Model for Taming the HIPPO: When a senior leader tries to bulldoze the process: Acknowledge: Validate their right to a point of view without necessarily agreeing. Reframe: Tie the conversation back to the project's purpose or objectives. Engage: Ask neutral questions to open the floor ("Would you be willing to listen to other perspectives on this?") Align: Bring the group's feedback back to the leader to help them make a better, more informed decision. The Power of Simultaneous Chat: To break the dominance of the loudest voices (and the HIPPO), ask a question and have everyone type their answer in the chat without hitting enter. On the count of three, everyone submits at once. This holds space for introverts, junior staff, and non-native English speakers to contribute without getting run over. Process is Your Shield: If a leader has a strong opinion, use process structure to ensure all sides are heard. Force the group to list "Pros" before "Cons," or use a timer to keep long-winded talkers (even the boss) in check. 🔗 Links & Resources Mentioned Connect with Evan Unger: Find Evan on LinkedIn (look for the blue/black check shirt and the impish grin, not the doctor!). Note: Evan is generously offering $2,000 off a seat in his training program for PM Happy Hour listeners! Books Mentioned: The Five Dysfunctions of a Team and Death by Meeting by Patrick Lencioni. Join the Conversation: Want to geek out about project management with us? Check out the PM Happy Hour membership site at https://www.pmhappyhour.com/membership. Say Hello: Hit us up on Facebook at PM Happy Hour or find our contact info on the website under "About Your Hosts."  

Boss fights and boardrooms. Kate puts Kim through meeting hell in this tabletop roleplay episode. Kate: "Help me torture Kim." That was the prompt. What followed was a meeting dungeon built from listener-submitted horror stories, tabletop chaos, and the exact kinds of project meetings that make smart people question their career choices. In this April Fool's episode of Project Management Happy Hour, Kate becomes game master and throws Kim into a gauntlet of cursed kickoffs, bloated status meetings, executive dodging, and stakeholder nonsense. It's funny because it's absurd. It lands because it's true. "My dice are green like all of my status reports." The setup is playful. The meeting pain is not. Kim tries to survive a kickoff with distracted leaders, a giant update meeting nobody needed, a build-versus-buy conversation where nobody wants to own the decision, and a phase gate where "close enough" suddenly becomes everyone else's problem. As the dungeon gets worse, you hear what experienced project managers actually do under pressure: reset the room, cut through noise, force clarity, and keep momentum when everyone else is drifting. "This is how Kim would operate in a meeting." That's what makes this episode so fun - and insightful. The dice are a toy. The project management is real. If you've ever had a sponsor with a hard stop in ten minutes, a technical lead who gets defensive the second testing reveals a problem, or a leadership team that turns every decision into one more meeting, this episode will feel painfully familiar. "We survived that near miss. It's okay. Next time we'll be okay." A lot of bad meeting habits stick around because teams get used to surviving them. This episode turns that reality into entertainment—and into a sharp reminder that surviving dysfunction is not the same as managing well. And because it's PM Happy Hour, the whole thing is loaded with lines that hit for PMs immediately. "We can't food bribe our way out of every meeting disaster." "I need you to do a speed run of a project." "It is 2 hours long." That last one might be the most terrifying quote in the whole episode. What you'll hear in this episode a kickoff already heading off the rails a giant status meeting from hell executive indecision in full view a technical lead bringing equal parts talent and chaos a release decision that gets messy fast Key project management takeaways Get to purpose fast. Push for the real decision. Keep updates short and relevant. Make the cost of delay visible. Manage the room, not just the agenda. Don't let technical defensiveness hijack the issue. Find the compromise that keeps momentum. If your work depends on steering messy rooms, stubborn stakeholders, and overloaded calendars toward an actual outcome, this episode will feel like both comedy and continuing education. Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

Escalation: it's a word that can make even experienced project managers tense. But what if you approached it as a tool rather than a threat? In this Top Shelf Replay of Project Management Happy Hour, we revisit the classic episode "Embracing De-escalation," exploring how savvy project managers use escalation to enhance visibility, make informed decisions, and navigate risk—without losing their cool. Hosts Kim and Kate dive into the nuances of escalation, showing how the best project leaders balance assertiveness with thoughtful communication. Far from being a reactive panic button, escalation can be a strategic lever to guide projects, protect team morale, and keep stakeholders in the loop.  In this episode, we cover real-world examples of when to escalate, how to frame your message, and why keeping your sponsor engaged is critical for project success. From handling medium-urgency issues to preventing scope creep, Kim and Kate provide a roadmap for using escalation effectively—turning potential project risks into opportunities for alignment and growth. Expect memorable metaphors, including broccoli for "healthy escalation habits" and creative exercises from the improv world to illustrate collaboration and communication.  By the end of this episode, you'll understand how to elevate project visibility, manage competing priorities, and leverage escalation strategically, all while maintaining calm and confidence. Key Quotes from This Episode: "Escalation is just another tool in your project management box, and it's one of the best." "Sometimes you almost kinda need to grab the sponsor and tell them to step up—they are the sponsor, and it's their project." "Think of escalation as eating your vegetables: a healthy activity that keeps your project going strong." "Escalating helps your sponsor make decisions whether they want to or not." Key Concepts The strategic use of escalation to improve visibility and decision making. Balancing sponsor engagement with day-to-day project leadership. Recognizing when a problem exceeds your decision-making authority. Communication techniques for reducing tension during escalations. Viewing project status and benefits realization beyond standard red/amber/green metrics. Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

Why do smart teams still deliver failed projects? Most project failures don't begin with a catastrophic mistake. Instead, they begin with small deviations—minor compromises that seem harmless in the moment. A warning sign gets ignored. A shortcut becomes acceptable. A risk is acknowledged but tolerated because "nothing bad happened last time." Over time, those deviations quietly become the new normal. In this episode of Project Management Happy Hour, Kim Essendrup and Kate Anderson sit down with Dr. Bill Brantley to explore one of the most dangerous patterns in project leadership: normalization of deviance. The concept comes from sociologist Diane Vaughan's analysis of the Challenger space shuttle disaster. Engineers had long observed problems with the shuttle's O-ring seals. But earlier launches survived those anomalies. Each successful launch reinforced the belief that the risk was acceptable. Gradually, what began as an abnormal warning became accepted behavior. As Dr. Brantley explains: "We survived that near miss. It's okay. Next time we'll be okay." Project teams fall into this pattern all the time. A design review is skipped because the team is behind schedule. A test failure gets dismissed because it hasn't caused a real problem yet. A risk gets documented—but never truly addressed. Nothing breaks immediately. So the project keeps moving. The conversation explores how this slow drift toward failure mirrors patterns seen in aviation, engineering disasters, and even mountaineering expeditions. Experienced professionals—people who know better—gradually normalize increasingly risky decisions until the system finally breaks. But the episode goes further than just diagnosing the problem. Dr. Brantley and the hosts dive into the decision dynamics inside projects. A typical project team makes dozens—or even hundreds—of decisions every week. Some have immediate consequences, while others take months or years to reveal their impact. One story from the Apollo program illustrates this perfectly: a weld defect made years earlier ultimately contributed to the crisis of Apollo 13. This delay between decision and consequence creates a dangerous blind spot. Dr. Brantley jokingly calls it the "White Castle effect." "White Castle burgers are great going down… and then at three in the morning you realize you made a bad decision." The same thing happens in project management. Decisions that seem harmless in the moment can produce painful consequences much later. One of the most powerful insights from the discussion is that organizations often fail to reflect on their decisions. Teams act, move forward, and stay busy—but rarely pause to ask whether their decisions are actually improving outcomes. That reflection step is critical. "Reflection really helps you break that normalization of deviance." Without it, teams never notice when small compromises start compounding into systemic risk. The episode also explores practical techniques for improving project decision-making. One of Dr. Brantley's favorites is red teaming—a method borrowed from military strategy and cybersecurity. In a red-team exercise, someone deliberately challenges the plan and tries to break it. Their job is to expose weaknesses before reality does. It's a powerful way to counter groupthink and create psychological safety for dissent. Another theme throughout the conversation is something many project managers intuitively know but rarely articulate: Every action—or inaction—on a project is ultimately a decision. "Everything is a decision. Nobody is going to come after you around anything other than decisions." Whether it's changing scope, delaying work, ignoring a risk, or choosing not to act at all, project leaders are constantly making decisions that shape the outcome of the project. The real question isn't whether decisions are happening. It's whether those decisions are intentional, visible, and thoughtfully examined. Because in many projects, failure doesn't arrive suddenly. It arrives slowly—one accepted deviation at a time. Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

Have you ever gotten feedback that made you want to flip a table because it was both insulting and totally useless? In this Top Shelf Replay, we revisit "They Told Me I'm Too Nice" and break down what that kind of vague feedback is really doing (sometimes gendered, almost always inactionable), why it hits so hard, and how to respond without spiraling - or people-pleasing your way into a personality transplant. Then we go beyond the original episode with practical, real-world tactics: how to ask better follow-up questions, how to force examples without sounding defensive, how to "prime" your manager before a meeting so you get usable feedback, and how to figure out whether your boss is actually trying to coach you… or just dumping drive-by advice from a book they skimmed on a flight. If you lead people, we also flip the lens: how to avoid giving your team confusing feedback that basically translates to "please be a different person," and how to coach toward outcomes instead of vibes. Key actionable insights Treat vague feedback as a starting point, not a conclusion. Thank them, then ask them to say more until you have something observable and specific. Ask for examples on demand. Use: "Can you tell me about a time I did that well?" or "Who does that really well?" This forces specificity and gives you a model to study. Match your effort to their effort. If it was a drive-by comment, don't burn three weeks of anxiety trying to decode it. If they clearly invested in you, invest back proportionally. Prime your manager before a meeting so they know what "good" looks like. Tell them your goal (scope agreement, signature, commitment, decision) so their feedback anchors to outcomes, not vibes. If you want feedback, specify what kind you want. "I'm not looking for grammar edits—I want alignment on strategy" is a transferable skill for stakeholder reviews and exec comms. For managers: don't "coach" people who don't want coaching. Find out what they want first, or you'll waste time and damage trust. Key Quotes -  "I don't need you to be my Grammarly when you review this document. I need to know if we are strategically aligned." "Below the line? You just crossed the line, buddy." Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

"Three PMs walk into a bar: a business PM, an IT PM, and a Vendor PM…" Sounds like a bad joke, but if you don't get it right - the joke will be your project. Very often, you aren't the "one PM to rule them all" on your project - you may have other PMs involved that you need to work with. But how do you decide who does what, and how do you prevent turf wars from turning your project into a slow-motion train wreck? In this episode, we ditch the corporate fluff to dive into the messy reality of projects with "too many cooks". We discuss how to navigate the friction between different project management roles, how to handle "useless" vendor PMs who won't manage their own resources, and what to do when an executive buyer bypasses you to talk directly to the vendor. You'll learn how to look "one level up" in the hierarchy to identify what actually drives your counterparts and how to draw professional boundaries that keep you in the driver's seat. In this episode, you'll learn: How to use the "Hierarchy Hack" to uncover your counterparts' hidden motivations. Strategies for handling a vendor PM who refuses to do their job. Why a high-level human conversation beats a technical tool every time. The "Time and Materials" pivot to force vendor accountability. How to professionally block an executive from undermining your role. From this episode: "The first thing to do is to have a conversation and, honestly, call it out in the open." — Kate "One of the ways I like to think about situations like this is one level up in the hierarchy." — Kim "I've been like, 'No, you can talk to me. Shut up, talk to me.'" — Kate "If I and my team are going to be held accountable... I have to be able to plan what we're accountable for." — Kim Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

Project managers are constantly told they need to "learn how to say no." But in the real world—especially when the ask comes from a sponsor, executive, or important customer—just saying no often isn't productive, strategic, or even possible. In this Top Shelf Replay episode of Project Management Happy Hour, Kim Essendrup and Kate Anderson revisit one of the show's earliest "Appetizer" episodes: Say No by Saying Yes, originally aired in 2017. Short, deceptively simple, and still painfully relevant, this episode breaks down a technique that helps project managers protect scope, schedule, cost, and sanity—without sounding combative or inflexible The core idea is straightforward: Instead of responding to tough requests with a flat "no," you respond with "yes—but" or "yes—and here's what that would require." "Yes, we can do it faster—but it will require triple the resources." "Yes, we can release both languages at once—but we'll need more budget or a delayed launch." "Yes, we can remove that resource—but you'll need to help me explain the downstream impact to the sponsor." This approach reframes the conversation away from emotion and into trade-offs, which is where real project leadership lives. As the conversation unfolds, Kim and Kate explore why this technique works so well psychologically. Leaders—especially busy executives—often don't have full context. Their "ridiculous asks" aren't always malicious; they're frequently driven by incomplete information, pressure from above, or a misunderstood business constraint. Saying "yes" first acknowledges their goal, signals partnership, and keeps them engaged long enough to hear reality The episode also connects this technique to a broader leadership pattern the hosts have refined over the years: what they now describe as "affirm, caution, query." You affirm the request. You surface the risk or constraint. You return the decision to the person who actually owns it. In other words, you stop absorbing problems that don't belong to you—and you stop shielding leaders from the consequences of their own decisions. The replay discussion expands the idea further, touching on burnout, executive presence, and why many project managers get stuck in a defensive "control mindset" around the triple constraint. Kim and Kate argue that stepping back—mentally taking off the project manager hat and putting on the sponsor's hat—makes these conversations easier, calmer, and more strategic. When you focus on outcomes instead of guarding boundaries, you stop reacting and start partnering. There's also an unexpected but memorable parallel: gentle parenting. The same structure used to redirect an emotional five-year-old ("I see what you want—but here are your options") turns out to work remarkably well with stressed executives, difficult customers, and unrealistic stakeholders. You don't remove agency; you structure it. Ultimately, this episode is about more than saying no politely. It's about changing the power dynamic—from executor to partner. From order-taker to decision facilitator. From "blocking progress" to helping leaders make informed choices. If you've ever been handed an impossible deadline, an under-funded scope change, or a request that made your stomach drop, this episode gives you language, structure, and confidence to respond without burning trust—or yourself.  

Thinking about going contractor? Kate and Kim share how they each left corporate and made the leap—two very different stories (burnout vs acting early) with the same core truth: contracting is built on relationships, reputation, and value… not job boards and commodity rates. We cover how to know if you're ready, why sales is part of the job, what to watch out for (hello, 2008), and how to avoid racing to the bottom. Want us to teach the full process with scripts + steps? Head to http://pmhappyhour.com/be-free.  

As project managers, we spend a lot of time talking about tools, processes, and delivery frameworks—but far less time talking about the invisible structure that holds projects together: trust. In this Top Shelf Replay episode of Project Management Happy Hour, Kim Essendrup and Kate Anderson revisit one of the show's earliest and most enduring concepts: Trust Bricks. Originally recorded in 2018, this short but powerful episode explores how trust is built—not through grand gestures or heroic saves—but through consistent, everyday actions that compound over time. The core idea is simple: trust is predictability. When you repeatedly do what you say you'll do—whether that's sending meeting notes on time, honoring estimates, or showing up prepared—you lay one small Trust Brick at a time. Over weeks, months, and years, those bricks form a structure strong enough to withstand missed deadlines, bad news, or the occasional broken promise. Kim and Kate break down why Trust Bricks matter so much in project environments: Teams are more honest with you when they trust you Estimates improve when people believe they won't be punished for telling the truth Difficult conversations become easier when everyone believes you're on the same side Sponsors give you more latitude when your track record is consistent The conversation also explores what happens when trust breaks—and how the same Trust Brick approach can be used to rebuild credibility. Rather than trying to restore trust with a single "big win," the hosts argue that rebuilding starts small: partial deliverables, frequent check-ins, and deliberately meeting micro-commitments until confidence is restored. In the replay commentary, Kim and Kate reflect on how their thinking has evolved since the original recording. They discuss: The role of showing up consistently, even when no explicit promise was made How trust operates differently in virtual and remote teams Why strong performers can accidentally set expectations that lead to burnout How leaders vary widely in how much "trust damage" they tolerate before overreacting The episode also revisits the journey of Trust Bricks beyond the podcast, including Kim's experience delivering a TEDx talk on the topic and refining the framework into three enduring lessons: You are always building or breaking Trust Bricks—whether you realize it or not Missed expectations don't pause trust building; they actively tear it down Unspoken expectations are the fastest way to accidentally destroy trust This episode is a reminder that trust isn't soft, vague, or optional—it's a core delivery skill. If you want stakeholders who back you, teams who tell you the truth, and projects that don't require constant firefighting, it starts with sweating the small commitments. The next time you make a commitment—big or small—ask yourself: Am I laying a brick… or cracking one? Check out Kim's TEDx talk at trust-bricks.com or on the TED youtube channel Want more PM reality without the fluff? Join the PMHH membership for courses, templates, community, and direct access to Kate and Kim. https://pmhappyhour.com/membership