Jim Morris | How I Test My Teaching Process

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:

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/

If your leadership team is about to make a big strategic bet, the real risk usually isn’t the idea, it’s the assumptions behind it that haven’t been surfaced yet. A Decision Sprint is a focused 6–12 week engagement where we extract, map, and test those risks so leaders can make a clear Commit, Correct, or Cut decision before major capital moves. Learn more or apply at precoil.com.