This is a short story I wrote about a PM lead working over at #linkedin, and how he saved the day using #chatgpt.
I wrote this to showcase one of the many ways on how an #AI can assist us with our many responsibilities in this complicated job called #productmanagement.
Specifically, here is the resulting user story for a new feature that the hero of our story ideated and "finalized" in less than 5 minutes:
User Story:
As a LinkedIn user, I want to be able to interact with the stories in the "Inspiration" feature by filtering them by industry, job role, and other criteria, and also be able to save stories that I find particularly interesting or useful for future reference, so that I can easily find the stories that are most relevant to me.
Acceptance Criteria:
- The user can filter the stories by industry, job role, and other criteria.
- The user can save stories that they find particularly interesting or useful for future reference.
- The user can view the saved stories in a separate section.
- The user can remove the stories from the saved section.
- The design of the frontend should be consistent with the LinkedIn's design guidelines.
- The frontend should be responsive and adaptable to different devices.
Edge Cases:
- The user should be able to filter the stories even if they have a low internet connection or a slow device.
- The user should be able to save stories even if they are not logged in.
-The user should be able to view the saved stories even if they change devices or log out and log in again.
-The feature should work properly if the user has a screen reader or other accessibility tools enabled.
Definition of Done:
-The feature should be able to filter the stories by industry, job role, and other criteria.
-The feature should be able to save stories that the user finds interesting or useful.
-The feature should be able to show the saved stories in a separate section.
-The feature should be able to remove the stories from the saved section.
-The design of the frontend should be consistent with the LinkedIn's design guidelines.
-The frontend should be responsive and adaptable to different devices.
-The feature should be tested across different browsers and devices to ensure compatibility.
-The feature should be tested with a small group of representative users to ensure it meets their needs and is easy to use.
-All necessary code changes should be committed to the codebase and be reviewed by other team members before being merged.
-The feature should be properly documented, including any necessary instructions and troubleshooting steps.
- The feature should be deployed to a staging environment and be tested by the team and stakeholders before being deployed to production.
1 comment
[ 3.5 ms ] story [ 11.4 ms ] threadI wrote this to showcase one of the many ways on how an #AI can assist us with our many responsibilities in this complicated job called #productmanagement.
Specifically, here is the resulting user story for a new feature that the hero of our story ideated and "finalized" in less than 5 minutes:
User Story: As a LinkedIn user, I want to be able to interact with the stories in the "Inspiration" feature by filtering them by industry, job role, and other criteria, and also be able to save stories that I find particularly interesting or useful for future reference, so that I can easily find the stories that are most relevant to me.
Acceptance Criteria: - The user can filter the stories by industry, job role, and other criteria. - The user can save stories that they find particularly interesting or useful for future reference. - The user can view the saved stories in a separate section. - The user can remove the stories from the saved section. - The design of the frontend should be consistent with the LinkedIn's design guidelines. - The frontend should be responsive and adaptable to different devices.
Edge Cases: - The user should be able to filter the stories even if they have a low internet connection or a slow device. - The user should be able to save stories even if they are not logged in. -The user should be able to view the saved stories even if they change devices or log out and log in again. -The feature should work properly if the user has a screen reader or other accessibility tools enabled.
Definition of Done: -The feature should be able to filter the stories by industry, job role, and other criteria. -The feature should be able to save stories that the user finds interesting or useful. -The feature should be able to show the saved stories in a separate section. -The feature should be able to remove the stories from the saved section. -The design of the frontend should be consistent with the LinkedIn's design guidelines. -The frontend should be responsive and adaptable to different devices. -The feature should be tested across different browsers and devices to ensure compatibility. -The feature should be tested with a small group of representative users to ensure it meets their needs and is easy to use. -All necessary code changes should be committed to the codebase and be reviewed by other team members before being merged. -The feature should be properly documented, including any necessary instructions and troubleshooting steps. - The feature should be deployed to a staging environment and be tested by the team and stakeholders before being deployed to production.