A Quick Guide to Avoid the #1 Mistake With User Stories

Here’s how not to confuse them for requirements.

Output is a fixation we can’t seem to shake in the product space.

We continue to think we know the right product to build before we build it. This often shows up in the way we treat user stories as requirements.

Even though many product teams and managers think user stories are requirements, they aren’t. The output-oriented among us (I’ve fallen into this trap myself) are notorious for saying: