Artwork

Innhold levert av AgileThought and Dan Neumann at AgileThought. Alt podcastinnhold, inkludert episoder, grafikk og podcastbeskrivelser, lastes opp og leveres direkte av AgileThought and Dan Neumann at AgileThought eller deres podcastplattformpartner. Hvis du tror at noen bruker det opphavsrettsbeskyttede verket ditt uten din tillatelse, kan du følge prosessen skissert her https://no.player.fm/legal.
Player FM - Podcast-app
Gå frakoblet med Player FM -appen!

Main Challenges of Product Practice with Ned Pope

37:31
 
Del
 

Manage episode 426094487 series 2502498
Innhold levert av AgileThought and Dan Neumann at AgileThought. Alt podcastinnhold, inkludert episoder, grafikk og podcastbeskrivelser, lastes opp og leveres direkte av AgileThought and Dan Neumann at AgileThought eller deres podcastplattformpartner. Hvis du tror at noen bruker det opphavsrettsbeskyttede verket ditt uten din tillatelse, kan du følge prosessen skissert her https://no.player.fm/legal.

This week, your host, Justin Thatil, welcomes Ned Pope, Director of Product Practice at Agile Thought. In this episode, Ned and Justin explore the most common challenges encountered while engaging with an enterprise client. Ned shares valuable insights regarding creating a new product effectively and timely, emphasizing the crucial value of openness and collaboration within a Team. Ned highlights the importance of focusing on the problem, the elements of the solution, and how they can be broken down to prioritize the most unique and highest value for clients and customers.

Key Takeaways

  • Enterprise clients are dealing with a massive sector of the marketplace.

    • There is a wide range of variance in what the clients are trying to accomplish, so it is important to ground them in their thinking around problem-solving. If you can remove even a minor inconvenience from someone's day, you add value to their life.

    • There must be a list of priorities from executive and senior leadership within the enterprise clients, along with the dates they will be needed. This road map is not based on capacity or capability to deliver a solution around a specific item to be delivered at a particular time.

    • Don’t get frustrated when trying to create a digital product. There is a reason this solution doesn’t exist yet, or in the form you are trying to build it.

    • Make sure everyone is aligned and on the same page.

  • Understand and respect the current processes within an Organization.

    • The organization has already figured out how to solve the problem in the current fashion, and you do not want to disrupt that but to provide something that makes that process more manageable, enhances that solution, and makes it more effective and scalable.

  • There are tangible elements that form a culture.

    • Empower teams to think creatively about a solution.

    • Openness, resourcefulness, and collaboration are critical elements of an Agile Team.

  • Move UX design and UI library components as visual references at the beginning of the process to save time and ultimately allow for a better product.

    • We often get to the details and the complexity of the work and then begin to get consumed with all the nuance and intricacy of the daily work, which can lead to overseeing the most basic aspects.

    • Remember, you are building a visual tool!

    • The vast majority of technology has some form of interface, which generates success and speed with quality and accuracy.

    • Provide visual references to align the Team with what you are trying to accomplish and execute. It is recommended that you bring in a highly skilled UX Designer to the heart of the Product Discovery. Don’t wait until the process is in development; the UX designer needs to join the process from the beginning.

    • Use a UI library.

Mentioned in this Episode:

Scaled Agile

Scrum.org

National Academy of Inventors

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

331 episoder

Artwork
iconDel
 
Manage episode 426094487 series 2502498
Innhold levert av AgileThought and Dan Neumann at AgileThought. Alt podcastinnhold, inkludert episoder, grafikk og podcastbeskrivelser, lastes opp og leveres direkte av AgileThought and Dan Neumann at AgileThought eller deres podcastplattformpartner. Hvis du tror at noen bruker det opphavsrettsbeskyttede verket ditt uten din tillatelse, kan du følge prosessen skissert her https://no.player.fm/legal.

This week, your host, Justin Thatil, welcomes Ned Pope, Director of Product Practice at Agile Thought. In this episode, Ned and Justin explore the most common challenges encountered while engaging with an enterprise client. Ned shares valuable insights regarding creating a new product effectively and timely, emphasizing the crucial value of openness and collaboration within a Team. Ned highlights the importance of focusing on the problem, the elements of the solution, and how they can be broken down to prioritize the most unique and highest value for clients and customers.

Key Takeaways

  • Enterprise clients are dealing with a massive sector of the marketplace.

    • There is a wide range of variance in what the clients are trying to accomplish, so it is important to ground them in their thinking around problem-solving. If you can remove even a minor inconvenience from someone's day, you add value to their life.

    • There must be a list of priorities from executive and senior leadership within the enterprise clients, along with the dates they will be needed. This road map is not based on capacity or capability to deliver a solution around a specific item to be delivered at a particular time.

    • Don’t get frustrated when trying to create a digital product. There is a reason this solution doesn’t exist yet, or in the form you are trying to build it.

    • Make sure everyone is aligned and on the same page.

  • Understand and respect the current processes within an Organization.

    • The organization has already figured out how to solve the problem in the current fashion, and you do not want to disrupt that but to provide something that makes that process more manageable, enhances that solution, and makes it more effective and scalable.

  • There are tangible elements that form a culture.

    • Empower teams to think creatively about a solution.

    • Openness, resourcefulness, and collaboration are critical elements of an Agile Team.

  • Move UX design and UI library components as visual references at the beginning of the process to save time and ultimately allow for a better product.

    • We often get to the details and the complexity of the work and then begin to get consumed with all the nuance and intricacy of the daily work, which can lead to overseeing the most basic aspects.

    • Remember, you are building a visual tool!

    • The vast majority of technology has some form of interface, which generates success and speed with quality and accuracy.

    • Provide visual references to align the Team with what you are trying to accomplish and execute. It is recommended that you bring in a highly skilled UX Designer to the heart of the Product Discovery. Don’t wait until the process is in development; the UX designer needs to join the process from the beginning.

    • Use a UI library.

Mentioned in this Episode:

Scaled Agile

Scrum.org

National Academy of Inventors

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

331 episoder

Semua episod

×
 
Loading …

Velkommen til Player FM!

Player FM scanner netter for høykvalitets podcaster som du kan nyte nå. Det er den beste podcastappen og fungerer på Android, iPhone og internett. Registrer deg for å synkronisere abonnement på flere enheter.

 

Hurtigreferanseguide

Copyright 2024 | Sitemap | Personvern | Vilkår for bruk | | opphavsrett