Teams at Work by BUNCH

The episode offers a handful of usable tactical tips (permission-based questions, the self-audit of your daily task list, calendar blocking with explicit communication) but most of the runtime is occupied by broadly familiar coaching platitudes and meandering agreement between host and guest. The ratio of novel-to-obvious skews heavily toward obvious.

“hey, may I ask you something about that? Or can I give you some coaching or may I push back a bit on what you're saying? So these are permission based questions”

“I told this very senior, very talented BDR manager who was so overwhelmed... I was like, right, this is what you're gonna do my homework for you. You're going to write down every single thing you do in a typical day.”

The frameworks presented - 30-60-90 plans, soft skills as the future, calendar blocking, role plays for practice, Myers-Briggs team bonding - are all well-worn management and coaching staples. The rebranding of soft skills as 'super skills' is minor wordplay, not fresh thinking. Nothing is argued from first principles or counter to conventional wisdom.

“I call them super skills, I think the world calls them soft skills, I have no idea why.”

“block your calendar. So I know it sounds so, so simple. What does she mean, block your calendar?”

Stephanie Herre has genuine practitioner credentials - enterprise sales at SAP, Cisco, Freshworks, and a current leadership role at Remote - and has actually managed underperforming teams through a real turnaround scenario. However, she has clearly pivoted toward coaching/Udemy-course territory, and the depth of operational scale discussed is mid-management rather than executive.

“I had an underperforming team on my hands, all right? I had the challenge of transforming a low performing team to a high performing team in another language because it was a region that I've never sold to before, the France and Southern Europe region.”

“I actually created a udemy course, exactly talking you through how I did this. And I even threw in my original template that I used to get my first leadership role.”

Almost no concrete numbers, named companies, metrics, or verifiable data appear in the transcript. The closest thing to a data point is a vaguely attributed statistic about meeting buffer time and the detail that her first team had six people. Advice is delivered entirely through personal anecdote and abstraction.

“I think I read a statistic, but I think it takes 20 minutes before the meeting and then 20 minutes after each meeting for you to somehow, like, get up to speed.”

“It was six other people.”

The host occasionally asks a meaningful follow-up (pushing on what happens when people actually do push back on meeting declines) but mostly responds with validation and agreement rather than probing or challenging. Several questions are leading or simply hand the guest a topic to monologue on, and there is no instance of productive disagreement.

“And what happens, I mean, this Sounds really good. And I think in many cases makes sense in reality, I think people push back on it, of course. Right.”

“So true. And we're so glad to have you. We need more people like you in this corner of the world for sure.”