Product for Product Management

The episode layers philosophical concepts onto product management practice, but spends significant time on exposition of Sanskrit terms and yoga theory rather than distilling actionable insights. While the clarify/observer framework and the eight limbs structure offer genuine conceptual value, much of the latter half circles back to abstract spiritual principles without concrete application examples.

“Unless you don't have the clarity regarding why you are solving a problem, you know, your what and how comes very later, you know.”

“when you zoom in you look at things personally, but when you zoom out you look at a social welfare”

The core linking of Ashtanga yoga philosophy to product management disciplines is genuinely novel and not a recycled framework heard widely in product discourse. The crystal/rose perception analogy and the emphasis on the product manager working on themselves first as a product are fresh takes, though the execution occasionally falls into spiritual platitudes common in wellness circles.

“Product Ashtangi, what I'm trying to build over here is product of course, you know, when you are building products around you and you want to keep your mind state, uh, your state of mind as calm and composed. The first ever product you work on is actually your own self.”

“I literally schedule retrospects for myself every two weeks. And um, personal retrospects about yourself as a product.”

Bhavesh is a practitioner with legitimate domain experience: 15 years in product/project management at enterprises (TD Bank, Citibank, Telus), now a founder building products. However, he is primarily known as an author/thought-leader around this book concept rather than as a recognized operator at scale. His startup ventures (pet adoption app, governance tool) are nascent and not yet proven at meaningful scale, limiting his credibility to the level of mid-career practitioner with interesting thesis, not seasoned operator.

“I have around, I'd say 15 years of project product management experience, uh, with a complete, I would say I started as a Java developer back in India”

“I worked with TD Bank, I worked with Citibank, I worked with Telus. Um, I was working for Telus for a good 10 years”

The episode lacks concrete metrics, named companies (beyond his own employment history), or data-driven examples. The Kubernetes vs. Terraform decision is the clearest specific technical example, but remains high-level. References to Oppenheimer, Elon Musk, and Buddha lend historical weight but are not evidence of the framework's efficacy. The pet adoption app and governance tool are mentioned but not detailed with results or impact.

“one of the examples I was working on a product where we had to migrate weblogic applications from on premises to cloud, you know, and the right solution for that, because it was weblogic and because it was uh, old technology, the right solution could have been terraform. But when we were talking with the architects, Kubernetes was kind of new”

“I created uh, a SANA board for her. I read that, you know, the dog can learn one new trick a week. So I ended up creating 52 tickets for her”

The hosts ask reasonable opening questions and allow Bhavesh space to develop his thinking, but they rarely push back, challenge premises, or dig into contradictions. When Musha raises a legitimate tension - that yoga is individual while product is team-based - Bhavesh pivots to theory rather than addressing the friction directly. Matt and Musha ask softball follow-ups rather than probing feasibility or boundary conditions. No disagreement or intellectual tension surfaces.

“So how did you apply this in real life?”

“Can you tell us of a time where you implemented it yourself?”