retros with rigor
Week 4.
After every mock, I’ll run a formal retro with exercises—not just talk about what went wrong. The exercises need to happen immediately, before I even get up from the desk. That discipline will lock in learning while it’s fresh.
Daily Goals (Still Testing)
I’m sticking with daily goals. My hypothesis: once I have a steady set of reliable partners (hopefully starting this week), the daily rhythm will pay off. Until then, I’m testing how sustainable it is—and where it breaks down.
✨ Bottom line: Week 4 is about discipline—structured retros and daily consistency, even if it’s still an experiment.
My Plan
Day 22.
Product Sense Mock 9
Focus: Keeping Strategic Section short
Reto: Users or Solutions exercise post interview
Day 23.
Product Sense Mock 10
Focus: Keeping Strategic Section to short
Reto: Users or Solutions exercise post interview.
Day 24.
Product Sense Mock 11
Focus: Nailing User Groups
Reto: Users or Solutions exercise post interview.
Day 25.
Product Sense Mock 12
Focus: Clean end-to-end user experiences explained
Reto: Users or Solutions exercise post interview.
Day 26.
Product Sense Mock 13
Focus: Ask Partner to pick at risks/tradeoffs
Reto: Users or Solutions exercise post interview.
Days 27 & 28. Wiggle Room: No goals, anything I get is a bonus.
If you are following along, that Reto (5-15 minutes after your mock) should be re-thinking something that went wrong in your case.
Related Articles:
