Speaking Podcast
Five episodes on what is worth shipping
Vasco Duarte invited me to the Scrum Master Toolbox Podcast for a Product Owner week. Five episodes, one every weekday from 19 to 23 October 2026, with stories from EdTech product teams and from Product Build Days.
The podcast
Scrum Master Toolbox, with Vasco Duarte
Vasco Duarte has run the show as a weekday podcast since 2015. He interviews Scrum Masters and agile coaches from around the world about their work with real teams, and in a Product Owner week one product person is the guest for all five days.
He co-founded Agile Finland and wrote NoEstimates. By his count, the show has passed 10 million downloads.
2015
the year the weekday show started
2,800+
episodes
4.7
average from 401 ratings on Apple Podcasts and Podcast Addict
5 episodes
my guest week, 19–23 October 2026
Figures from Apple Podcasts, Podchaser, Podnews (ratings data by Rephonic) and Vasco's bio (downloads), checked 24 October 2026.
The week
What we talked about each day
69 minutes in total. Episode lengths as listed on Apple Podcasts.
- 1Monday, 19 October
When Product Owner success creates blind spots for agile teams
I told the story of an EdTech team with students and teachers to test with every week and a strong Product Owner. The tests kept coming back positive, and the team started to see itself as the best in the company. Other departments saw arrogance, and the dependencies on sales, marketing, e-commerce and payments got harder to manage. The product launched and never reached its sales targets, because user testing is not market testing.
“I am not the user. That is how I learned how important it is to keep your ego small.”
From Monday's episode - 2Tuesday, 20 October
The Product Owner lesson from agile teams that forget the user
Teams often talk about users as if they already know what users need. In one EdTech product, the obvious answer was a login for every student. But in a classroom of 20 or 30 students with 45 minutes, a few forgotten passwords turned the teacher into IT support. The fix was simpler: the teacher logs in and shares a code with the class. My book picks for the week were The Mom Test by Rob Fitzpatrick and Sprint by Jake Knapp.
“The user never wants to log in. That is never the goal of the user.”
From Tuesday's episode - 3Wednesday, 21 October
Product Owner discovery when agile stakeholders want delivery first
The challenge I'm working on right now: everyone says they want to understand the customer until discovery turns into real work, and then the pressure goes back to delivery. We used the Double Diamond to show why so many companies skip straight to solutions and become feature factories. My experiment is Product Build Day, which shrinks discovery into something stakeholders can accept: one day to build AI prototypes, pitch the options and design the test for the next day.
“If I can ship everything by the weekend, what is worth shipping?”
From Wednesday's episode - 4Thursday, 22 October
Product Owner ownership that gives agile teams real direction
Ownership is in the job title, but many companies don't give their Product Owners the authority to decide. At one Product Build Day, a founder said at the start that the prototypes and tests would shape the real product direction. That one sentence changed the energy in the room, because people knew their work would affect future sprints. Vasco connected it to Extreme Ownership by Jocko Willink.
My favorite retro format
Silent notes, clustering and dot voting
- Everyone writes notes alone, often anonymously.
- The notes go up and get grouped by theme.
- The team gives each theme a name.
- Everyone votes, and the top theme gets the time.
Vasco's check: after the vote, ask if anyone sees a better idea that didn't get picked. My tip: don't run the same format too many times in a row.
- 5Friday, 23 October
The Product Owner view of great Scrum Masters in agile teams
Because it was a Product Owner week, I closed it by describing great Scrum Masters from the product side. The best ones are flexible with the role. In one kickoff, the Scrum Master planned the workshop together with the Product Owner and the product designer, so the team named its assumptions, missing data and risks early, which can save weeks later. The anti-pattern is the Scrum Master who treats the role description as a fence.
“The skill of a great Scrum Master is being flexible with the role.”
From Friday's episode
What listeners can take away
One idea from each day of the week.
User testing is not market testing. A team can pass every usability test and still miss its sales targets.
The user never wants to log in. Keep asking what problem they came to solve, even when the team already loves a solution.
When you can ship anything by the weekend, the hard part is deciding what is worth shipping.
A Product Owner needs the authority to decide, and the team needs to know which decisions are real.
Great Scrum Masters treat the role description as a starting point. When product clarity is missing, they step in and ask the questions.
Thank you, Vasco, for inviting me for a whole week and for a great conversation.
Happy to come on your podcast too.