If you’re reading this, you’re probably a CEO with a product and you’re wondering if there is a more effective way to build it. Over the next few months, we will be researching and applying techniques to clearly define the problems we want to solve and create the stories and sprints aimed at solving them.
Today, you get to meet me! I’m the founder of Talent Edge, with a background in database design and Product Management. I’ve also owned an Astrology Digital Reports Company, a nightclub, and a bar. But I digress! I wanted to experiment and see how effective I could be as a Product Owner with AI by my side.
One challenge we often face is that stakeholders don’t always know what they want, which can be quite random at times. New clients tend to drop off a waterfall-like specification and then deviate as soon as you convert it into detailed stories. It’s a time-consuming effort to organize the thoughts of others in order to solve a customer’s problem.
I decided to focus on cutting out low-value work to concentrate on the most difficult part: ensuring we solve the right problem, in the right way, at the right time for each sprint.
Here is a simple semi-automation you can use:
Hold a grooming meeting with your stakeholders.
Discuss the application and its performance.
Review customer/user feedback.
Prioritize the list of stories.
Discuss details (don’t worry about taking notes 🙂)
Record this meeting using Fireflies. For live meetings, utilize the Live Recording feature. An iPad mic is usually sufficient for a 10-person meeting.
Take the transcript into Chat GPT and run the following prompt:
As a Product Owner focused on this user persona (paste in your persona or attach a PDF), break down this meeting transcript step by step as follows:
Step 1: List the core problems we hope to solve in the next sprint in prioritized order as discussed in the meeting.
Step 2: For each problem, create as many user stories as needed to solve the problem. Stories should follow the framework: As a [persona] I need to [task] so that I can [goal].
Step 3: For each story, define the necessary inputs and outputs.
Step 4: For each story, create the success criteria (test cases).
Step 5: Create the scripts needed to run unit tests against the inputs and outputs if they exist.
Step 6: For reference, create a detailed list of suggestions grouped by meeting participant.
This semi-automation can streamline your process, allowing you to focus on solving the right problems effectively.
Comments