When teams apply service design methods they are trying o make sense of uncertainty and pick a direction with confidence. Supporting these teams can be tricky as progress is often unpredictable and non-linear. In this talk, Paul will use stories from real client projects to illustrate how we approach product discovery, and common pitfalls for stakeholders and sponsors to avoid. Paul will also deep dive into how you can run his favorite service design workshop with your team.
Related content in this Stream
A Two-Tiered Approach to User Adoption, AKA the 'User Adoption Sandwich'
When building enterprise software, looking at user adoption from two perspectives helps ensure stakeholder buy-in and happy users.
5 Tips for Adopting a Product Mindset for APIs
Designing and building APIs might seem like a different animal from traditional customer-facing products, but using some of the same principles can ensure a more successful result.
My All-Time Favorite Opening Question for User Interviews
Why the question "What do you love about your job?" is the best way to kick off a user interview.
How to Write User Stories Without Users
We can still write valuable stories—we just have to reframe our idea of user value. And that means redefining our idea of a user.
24:52Saving the DoD $800M: How Portfolio Management is the Missing Link Between Agile and Waterfall
Throughout the DoD, many branches of the military are starting to see the value in agile software delivery as a way to deliver capabilities faster and cheaper. Yet despite the favor for agile, many ar
Metrics, Product Management, and You: Knowing You Did a Good Thing
Defining success metrics can be daunting for even experienced product managers. This post explains how one simple question ("How do we know we did a good thing?") can help you create better metrics.
24:47Measure Twice, Cut Once: Using Team Operation Metrics to Optimize a Scaling Software Shop
Maintaining an efficient and productive software org is hard enough when it’s just a few teams—how do you keep it delivering high-priority value when it’s growing rapidly, without continuously hiring
20:27Outcomes-Oriented Roadmap: From Vision to Reality
As Product Managers, we have a love-hate relationship with product roadmaps. For example, in the past, we've struggled to answer questions such as: - How to create a roadmap that communicates
22:40A Recipe for Scale: Succeeding with Agile Software Development in the Enterprise
Many enterprises have enjoyed amazing results by adopting agile methods, but that success is not without its challenges. Increasing code quality, shipping value faster, and getting better software out
Learn the core values of the Balanced Team approach to product development, as well as the benefits these values can bring to your own team.
How and Why to Classify Problems in User Interviews
Measure Intensity, Frequency, and RecencyAs a product team, how do you know which problem to solve? This question might be hard to answer, especially if you don’t understand your customers...
Do You Have a Good Outcome-Oriented Roadmap?
Aloka Penmetcha, Director of Product Management at Pivotal San Francisco, maps out six tests she recommends all teams consider using to assess the quality of their outcome-oriented roadmaps.
5 Conversations You Should Be Having About Your User Stories
If a story is a placeholder for a conversation, when does that conversation happen? Who has it? What do they talk about? Here are five moments engineering and product should be checking in with each.
20:15The ‘Magic Box’ Problem, and How to Get Out of It
One of the most common frustrations you’ll hear from Agile teams is that stakeholders always want too much, too soon, for too little. Why? The Magic Box problem is often the culprit. Your software org