A pattern began to emerge where user stories in product backlogs read like tasks that were part of a larger implementation plan (for example: configure page layout, create API, etc.)
Another trend surfaced where the first introduction of needs, whether a small enhancement request or more substantial feature requests included pre-determined solutions
The hypothesis became educating on user-centric user stories and understanding the problem from a customer perspective will empower product team members to deliver more creative solutions
Ashley's Actions
Led an experiment that resulted in a new norm for Product Owners to communicate the problem to be solved from a customer perspective upon initial introduction of a request to the cross-functional product team
Partnered with a cross-functional team of SMEs to conduct a case study to demonstrate the benefits of user story mapping as a visual model to understand customers and their journey within the product
Collaborated with an agile coach to create a user story mapping training initiative to 5+ cross-functional teams of Developers, UX Designers, Quality Assurance Engineers, Business Analysts and Product Owners
Results
Improved speed of program backlog prioritization due to clarity in the customer problems to be solved for a given initiative
Less waste and improved product value offering due to focusing on product features that solve a customer problem
Empowered product teams, those closest to delivering value to customers, resulting in more creative and innovative solutions such as improved flow of user activities within certain features
Transferable Skills
Understanding customer problems, needs, and desires
Cross-functional team collaboration
Ability to cultivate a deep understanding of the why
Ability to train and roll-out changes to large groups
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.