[Spooky23]

It's easy to spot when agile webdev types don't do this... you end up with a responsive mobile site that is missing half the features that you want.

It's easy for sharpie commandos to sort interactions by priority and build a user story that hits most of the priority interactions. Splitting isn't natural especially when the designers aren't very experienced.

IMO somebody representing the business who isn't a designer needs to be in the approval process to throw back work when all of the necessary interactions aren't captured.

[ethbro]

> IMO somebody representing the business who isn't a designer needs to be in the approval process to throw back work when all of the necessary interactions aren't captured.

Critical in my experience. I usually call this the "smart ass SME" (subject matter expert).

Or, "Go out on the floor and find me someone who does the work every day, has been doing so for a decent amount of time, and who still complains when things are broken and has no problem speaking up."

I can tease out issues from a generic complaint. I can't from silence.

The other thing you'll find they're useful for is throwing out ass-backward use cases that seem logical to management (and me) but are stupidly inappropriate for some obvious reason to an actual person doing the workm

[octalmage]

For us this is the product owner. They are the ones that do the user studies to backup feature requests with data. It's important to test assumptions about what users want.

This way we don't end up building stuff because someone random thought they wanted it.