Post by Melissa Milloway

Do you know how to tell AI what to build to solve your users' problems? In video 3 of my LinkedIn Learning course, that's what we'll figure out. If you're just finding this, I'm collaborating with LinkedIn Learning on a 7-part course on building a proof of concept with AI to solve recurring problems in your organization. In video 2, we mapped the user journey and found the pain points. Now we turn those into something we can build from. That's what user stories do. A user story follows a simple format: As a user, I need to be able to [do something] so that [specific outcome happens]. Every story needs to come directly from what you heard in your interviews. If it doesn't, you're building from assumptions, not from what users need. Here are two from my communications situation: ➡️ As a user, I need to be able to create new layouts for newsletter stories to match new forms of content so I can keep communications current without waiting weeks for a new design. ➡️ As a user, I need to be able to easily edit copy without relying on someone else so I can make changes right before we hit send. Both came directly from user interviews. That's how you know you're building to solve the problems you identified. Write one user story for each pain point you heard. Those stories become your product requirements. In video 4, we'll take those user stories and build the product requirements document that we'll use to build with AI. #AI #FutureOfWork #BusinessStrategy

Video Content