The Operations Room: A Podcast for COO’s

The episode introduces a substantive alternative framework (puzzle setting vs. OKRs) with concrete reasoning grounded in research about goal-setting psychology and historical context. However, significant portions consist of meandering discussion between hosts about their own experiences and tangential topics (AI, dating apps, Myers-Briggs), diluting the insight density. The core framework - Observation, Open Questions, Objective, and the three solving questions - is valuable but could have been tighter.

“What I was feeling was we just have so much passion and internal drive. And it's almost like goals and targets were designed to kill that internal drive where you're then focusing on external measures”

“targets and goals, they work well when you're doing a repetitive task, when there is one obvious right answer...if on the other hand, you're doing something that's more like a puzzle, that's akin to something complex where there's no single right answer, that is where goals and targets do not work”

The puzzle-setting framework is genuinely refreshing and contrarian within business podcast discourse, backed by behavioral research and historical critique of Drucker's 1940s assembly-line thinking. The maritime company case study and the explicit challenge to the 'do OKRs right' refrain show original thinking. However, the core insight - that ambiguous problems need exploration over target-hitting - while well-articulated, is not wholly novel; it echoes lean discovery and design thinking principles without explicit acknowledgment.

“Why did Peter Drucker then come up with this goal-based approach and management by objectives? The problem was he was working with General Motors at the time...on an assembly line in the 1940s...It's all repetitive tasks and so goals worked really well”

“It feels like the emperor has no clothes and someone has to call it out because it's not that if you do it right...There are fundamental issues with it”

Radhika Dutt is a former Chief Product Officer at MovePrice and author of *Radical Product Thinking*, giving her legitimate operational credibility. However, she is presented primarily as a thought-leader and frameworks evangelist rather than someone actively running a large-scale business or shipping at current scale. The maritime case study is compelling but second-hand; her current work appears advisory/consulting-focused. For a COO-focused podcast, deeper operational weight would be stronger.

“She's the author of Radical Product Thinking, the New Mindset for Innovating Smarter, and a former chief product officer for MovePrice”

“I was working with this Greek company, I still am. The maritime industry”

The maritime platform case study provides concrete specifics: tech-savvy brokers only; shift to cargo owners and vessel owners; filtering UX as false solution; doubled sales 2023 - 2024, again in 2025; churn reduced 26% to 4%. The dating app example names Tinder, Bumble, and cites a 30% layoff. However, many claims lack granularity: the research on goal-setting vs. puzzle-solving is cited but not sourced; the Boeing manufacturing criticism is asserted without data; broader O.K.R. failures are claimed but not detailed with examples.

“sales had stalled in 2023...we doubled sales in 2024, again in 2025...we've reduced customer churn from 26% to 4%”

“Only tech savvy brokers in the maritime industry are using this platform...Why only brokers? Why aren't people who own shipping vessels, or who own cargoes, why aren't they using this platform?”

The hosts (Brandon and Bethany) ask genuine follow-up questions and show curiosity ('how big are the teams, how many puzzles can you solve at one time'), and Brandon challenges whether puzzle-setting is simply repackaging OKRs - a sharp question. However, the conversation meanders extensively before introducing the guest (nearly 20 minutes on AI, coding, personal frustrations), and there is insufficient pushback on Radhika's claims. The hosts don't challenge the research citations, ask for implementation caveats, or explore failure cases. Questions are warm rather than incisive.

“So is this purely just a framing exercise from top to bottom, because it's kind of the same thing, right?...So I guess my question in summary is the puzzle, part of it is part of generally what happens in OKRs at some level”

“I have some questions on how big are the teams, how many puzzles can you solve at one time, like those COO practical questions”