Projectified

The episode contains a handful of non-obvious ideas - using gemba walks as a behavioral early-warning system, a weekly Monday-to-Friday cadence tied to leading indicators, and a strategy board for conflicting projects - but these are interspersed with a lot of standard PM platitudes and light conversational filler.

“I think once they hit your register, it has happened. It's almost too late. If we're talking about spotting red flags, we want that way before it hits your register.”

“we actually instituted this year a strategy board. And in that strategy board, when we've got projects that are in conflict for whatever reason, we then bring that back to our executive leadership team”

The intercultural nuance around how different nationalities signal problems is a genuinely fresh angle, and the point about challenging 'artificial constraints' by asking for documentation is mildly contrarian, but the bulk of the advice - document scope changes, escalate with solutions, build psychological safety - is recycled standard PM doctrine.

“Learn to understand how red flags are raised in different cultures and how to collaborate in projects. And that if someone maybe says, 'Oh, no worries. That's nothing.' It doesn't really mean, 'No worries.'”

“'This is how it is.' I'm like, 'Really? Can you show me where that's documented?' Because we've convinced ourselves that we could only do this”

Both guests are genuine working practitioners - a senior program leader at GE Aerospace and an international audit PM at ALDI - giving the episode real-world grounding; however, neither holds a scale-defining seniority level (VP+, founder, C-suite) and neither has built something at a scale that produces highly differentiated war stories.

“Mary Hladio, senior productivity and program leader at GE Aerospace in Grand Rapids, Michigan”

“Franziska Höhne, project manager for international internal auditing at ALDI based in Essen in Germany”

There are a few concrete practices (named meeting cadence, the 50%-of-time resource conversation, the strategy board) and some industry context (automotive, GE Aerospace, ALDI) but no real metrics, dollar figures, project timelines, or detailed post-mortems; examples stay mostly illustrative and vague.

“on Monday mornings, there is a meeting… then there's a meeting on Tuesday, which is a status meeting, and then Thursday, sort of a leadership escalation meeting. And on Friday”

“'You told us 50% of their time, and they're not able to make this meeting, this meeting and this meeting. So, am I really getting 50%'”

The host structures questions sensibly and offers one sharp framing ('working in negative space') that prompts a useful response, but he rarely pushes back on vague claims, never asks for hard numbers or specific outcomes, and lets generalities stand unchallenged throughout.

“That's interesting because it's like working in negative space. So how do you figure out what's a good silence or, you know, versus a troubling absence”

“Are there instances where the constraints are so specific that it constricts innovation, insight, iteration, all of those things?”