MBA200: Take Action! The Best Advice from Over 200 Episodes

Here’s the best tips and advice from industry experts in over 200 episodes. Now take action!

Show Notes

As long-time listeners know, I ask guests for one action that we can take to start seeing some positive results. In this episode, I have gathered the best advice from over 200 episodes (199 full length episodes and 39 lightning casts).

THEME: Build the Right Thing

Episode 025: Advice from Gojko Adzic

Whenever you receive a requirement that is actually a solution, inquire about the behavior change that the solution is going to create. If we have a behavior change that allows us to monitor progress in a meaningful way, we will get more rapid feedback. Additionally, this helps guard against scope creep and makes sure we are aligning to organizational goals.

Episode 071: Advice from Jonathan Babcock

When we create something, be it a document or a visual, think of who is going to use it as our customer. Focus on their needs and afterwards, get their feedback on how you could have done better or how you could have helped them to be more successful. This kind of mindset builds trust and allows you to reach higher levels of performance.

Episode 091: Advice from Elizabeth Larson

When you’re provided with a solution to implement, practice asking the right kind of questions to better understand the intent of the solution and the current environment. Take the time to gather the facts and statistics about the current state so that you’ll be better prepared for conversations and make appropriate recommendations. Finally, don’t ask leading questions. Leading questions limit conversations and present a solution. Eliminate the phrase ‘have you thought about’. That phrase breaks trust.

Episode 185: Advice from James Robertson

Challenge the next solution you’re presented with to make sure you’re solving the right problem. Also, try to generate solutions to address the real business problem.

THEME: Use a Hypothesis

Episode 042: Advice from Jim Benson

Take a few User Stories (especially those that the team is doubtful about) and rewrite them as hypotheses. Treat it like a guess that you can prove or disprove and learn something.

Episode 081: Advice from David Hussman

When you decide to take on a user story or requirement, understand how you’ll measure the impact, not just how you’ll get it done. Stories need to include analytics. That helps you build less of the wrong thing by measuring the impact.

THEME: Iterate

Episode 130: Advice from Jerry Weinberg

Start talking requirements seriously. Explore options and impacts to understand your requirements. Finally, iterate on your requirements. You can’t know everything upfront.

Episode 133: Advice from Kent McDonald

In your current role, look for ways to do your work iteratively and incrementally. Ideally, get feedback after ever iteration and use that feedback to adjust not only the product, but also your approach.

THEME: Talk To Customers

Episode 016: Advice from Jeff Patton

Go to where your users are and talk to them. Also, stop writing stories and start telling stories. Have conversations . . . get to the whiteboard and start drawing pictures.

Episode 076: Advice from Roman Pichler

The single most important action you can take to make sure your requirements, backlog, and roadmap are aligned to user needs is to talk with your customers. Talking with customers gives you insights into what your customer needs are, how they use your product, and features that they don’t use. Use these insights to adapt your roadmap and requirements.

THEME: Build Relationship and Trust

Episode 080: Advice from Fay Thompson

Learn to say “I don’t know enough yet”. While we want to move projects forward quickly, get comfortable with the need to go back and investigate more to ensure you have a solid understanding of the problem you’re solving and the intended value. Also, adopt a servant leadership mindset and put the team’s and organization’s needs first.

Episode 019: Advice from Steve Sh