Sign up to save your podcasts
Or
Share Jim Morris | How I Test My Teaching Process
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Jim Morris | How I Test My Teaching Process
AI has made building cheap.
The cost of being wrong is still expensive.
I help organizations make better AI and growth investment decisions before committing major capital.
→ Book a Growth Strategy Call at Precoil.com/EMT
In this episode I’m joined by Jim Morris. We chat about the wake-up call that pushed him from building first to testing first. Jim and I discuss loyalty programs no one wanted, roadmaps filled with sequenced risk, AI prototypes that hallucinate and the uncomfortable reality that confidence often replaces evidence.
We also dig into something deeper: why smart teams ignore data, why leaders fall in love once an idea hits the roadmap, and why testing isn’t about better UX, it’s about real value.
Jim shares how he even tests his own teaching process for students at Berkeley.
Because as he puts it:
“We can build stuff. But if people don’t use it, we’re just creating product debt.”
Enjoy my conversation with Jim Morris.
Takeaways
- Testing is crucial to ensure product effectiveness and user engagement.
- Data analysis can reveal the true usage of product features.
- Mindset plays a significant role in how product ideas are perceived and developed.
- Not all ideas will succeed; testing helps identify the viable ones.
- User motivation is key to the success of features and programs.
- Prototyping tools can enhance the testing process but require careful implementation.
- Learning from failures in testing is essential for growth and improvement.
- Roadmaps should be flexible to adapt to changing priorities and evidence.
- It's important to focus on the core value proposition of a product.
- Continuous experimentation and adaptation are vital in product management.
Guest Links
Website: https://productdiscoverygroup.com/
LinkedIn Profile: https://www.linkedin.com/in/jimmorrisstanford/
View all episodes
By David J BlandAI has made building cheap.
The cost of being wrong is still expensive.
I help organizations make better AI and growth investment decisions before committing major capital.
→ Book a Growth Strategy Call at Precoil.com/EMT
In this episode I’m joined by Jim Morris. We chat about the wake-up call that pushed him from building first to testing first. Jim and I discuss loyalty programs no one wanted, roadmaps filled with sequenced risk, AI prototypes that hallucinate and the uncomfortable reality that confidence often replaces evidence.
We also dig into something deeper: why smart teams ignore data, why leaders fall in love once an idea hits the roadmap, and why testing isn’t about better UX, it’s about real value.
Jim shares how he even tests his own teaching process for students at Berkeley.
Because as he puts it:
“We can build stuff. But if people don’t use it, we’re just creating product debt.”
Enjoy my conversation with Jim Morris.
Takeaways
- Testing is crucial to ensure product effectiveness and user engagement.
- Data analysis can reveal the true usage of product features.
- Mindset plays a significant role in how product ideas are perceived and developed.
- Not all ideas will succeed; testing helps identify the viable ones.
- User motivation is key to the success of features and programs.
- Prototyping tools can enhance the testing process but require careful implementation.
- Learning from failures in testing is essential for growth and improvement.
- Roadmaps should be flexible to adapt to changing priorities and evidence.
- It's important to focus on the core value proposition of a product.
- Continuous experimentation and adaptation are vital in product management.
Guest Links
Website: https://productdiscoverygroup.com/
LinkedIn Profile: https://www.linkedin.com/in/jimmorrisstanford/