The Software House invited me to panel discussion on product-mode (or "durable teams" as they called it). Here's the video recording.
We deviated a bit from the planned agenda, which was to cover the following:
What are the differences between durable teams and initiative-based teams?
What works better – initiative-based teams or durable teams?
When are durable teams good for your business?
How to make durable teams attractive enough for developers?
How to keep your engineering team effective and motivated?
How do you prevent silos between durable teams?
How do you handle team fatigue?
Who owns the running of a developed system?
How does team setup influence the recruitment process?