#HowIPM - Bi-Weekly Product Management Tips and Tricks

The episode is roughly two minutes of a single practitioner tip, and both examples—having engineers narrate user stories and trialling async standups—are textbook agile hygiene with no non-obvious claims. The density of novel ideas per minute is extremely low, and the conclusion is purely generic.

“using small, little, small tweaks to your processes, you can really kind of pull out some of the trouble spots that you have”

“we experimented for two weeks where we said we will do slack stand ups on Friday and we'll decide if that works or not”

'Run small experiments to improve processes' is foundational lean/agile doctrine recycled without any contrarian angle, first-principles reasoning, or new framing. Nothing here would surprise a PM who has read a single book on agile.

“My product management trick is using small experiments to improve your team processes”

“using small, little, small tweaks to your processes, you can really kind of pull out some of the trouble spots”

Marzia is a self-identified senior PM at an unknown company called Depth Method; she is a practitioner rather than a thought-leader, which counts for something, but there is no evidence of scale, notable outcomes, or domain depth beyond a two-minute anecdote.

“I'm a senior product manager at Depth Method”

“I had a project where my engineers, I wasn't sure how fully they were grasping the user stories”

There are a handful of concrete details (two-week experiment window, Fridays as delivery/QA days) but zero metrics, no named clients or products, no measurable outcomes—just thin anecdotes that stop well short of evidence.

“we experimented for two weeks where we said we will do slack stand ups on Friday”

“because Fridays were delivery days, a lot of QA going on, it was actually better to get everyone on the call”

This is a solo monologue tip segment with no host, no interviewer, no questions, no pushback, and no follow-ups whatsoever; the format makes any evaluation of conversational craft essentially inapplicable, and what structure exists is loose and repetitive.

“And so using small, little, small tweaks to your processes, you can really kind of pull out some of the trouble spots that you have and improve your improved team processes in general. Sa.”